Skip to content
TrustedSkillsbeta
Back to all skills

Accelint Ts Testing

Listed
gohypergiant·vlatest·testing·Apache-2.0

Automates TypeScript unit tests using Accelint, identifying code style issues and potential bugs for faster development cycles.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add gohypergiant/agent-skills --skill accelint-ts-testing -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

gohypergiant

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • No undeclared network calls: failed

    Contacts 1 host that is neither well-known infrastructure nor declared in the skill's frontmatter: api.com.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

    Hosts contacted

    api.comundeclared

    What it found

    • skills/accelint-ts-testing/references/property-based-testing.md:699contacts api.com
      const config = { apiUrl: 'http://api.com', timeout: 0, retries: 3, enabled: true }
    • skills/accelint-ts-testing/references/property-based-testing.md:704contacts api.com
      const config = { apiUrl: 'http://api.com', timeout: 1000, retries: 10, enabled: false }

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned gohypergiant/agent-skills at fe1ce07cb2.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
fe1ce07cb2
Manifest
skills/accelint-ts-testing/SKILL.md
Scanned
16 files, 5,997 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill automates TypeScript unit testing using Accelint, providing guidance on best practices for Vitest tests. It focuses on expert-level advice to improve test organization, clarity, and performance, helping developers identify code style issues and potential bugs more efficiently. The skill emphasizes writing maintainable and effective tests by discouraging common anti-patterns.

When to use it

  • When you want to ensure your TypeScript unit tests are well-organized and efficient.
  • To avoid common pitfalls in Vitest testing, such as testing files with no behavior or skipping global mock cleanup.
  • For guidance on structuring test descriptions for improved readability and consistency.
  • When refactoring existing Vitest tests to improve their maintainability.

Key capabilities

  • Provides best practices for writing maintainable Vitest tests.
  • Offers advice on avoiding common anti-patterns in testing (e.g., testing constant files, skipping mock cleanup).
  • Guides users on structuring test descriptions for readability and consistency.
  • Focuses on expert-level guidance for test organization, clarity, and performance.

Example prompts

  • "What are some best practices for writing Vitest tests?"
  • "How can I avoid order-dependent failures in my Vitest tests?"
  • "Give me advice on structuring my Vitest test descriptions."

Tips & gotchas

  • The skill focuses specifically on Vitest testing and assumes a working knowledge of TypeScript.
  • Pay close attention to the guidance regarding global mock cleanup; failing to configure clearMocks: true, mockReset: true, and restoreMocks: true can lead to difficult-to-debug issues.
  • Keep test descriptions concise and readable by avoiding deep nesting of describe blocks.