Skip to content
TrustedSkillsbeta
Back to all skills

Accelint Ts Performance

Checked
gohypergiant·vlatest·backend·Apache-2.0

Analyzes TypeScript code for performance bottlenecks using advanced static analysis and provides actionable optimization suggestions.

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-performance -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 passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • 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 undeclared network calls: passed

    Makes no network calls.

    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.

  • 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-performance/SKILL.md
Scanned
18 files, 3,136 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, Accelint Ts Performance, systematically analyzes TypeScript codebases to identify performance bottlenecks. It combines an audit workflow with expert-level optimization patterns specifically focused on runtime performance. The tool highlights potential anti-patterns and provides suggestions for improvement, but emphasizes that users should carefully evaluate trade-offs before applying any optimizations. This is distinct from general best practices; use the accelint-ts-best-practices skill for those concerns.

When to use it

  • When optimizing JavaScript/TypeScript codebases for runtime performance.
  • To identify potential performance anti-patterns in utility functions, formatters, parsers, and validators.
  • Before making significant changes or deployments where performance is critical.

Key capabilities

  • Static analysis of TypeScript code to detect performance bottlenecks.
  • Identification of common performance anti-patterns.
  • Reporting of potential optimizations with expected gains.
  • Emphasis on algorithmic complexity analysis (e.g., identifying O(n²) operations).
  • Highlights trade-offs associated with different optimization techniques.

Example prompts

  • "Analyze this TypeScript code for performance bottlenecks: [paste code here]"
  • "What are the potential performance anti-patterns in this function? [paste code here]"
  • "Suggest optimizations for improving the runtime performance of this module. [paste code here]"

Tips & gotchas

  • Audit all code: Don't skip auditing seemingly simple functions, as they may be called frequently.
  • Prioritize algorithmic improvements: Focus on fixing inefficient algorithms (e.g., changing O(n²) to O(n)) before micro-optimizations.
  • Verify correctness: Thoroughly test optimized code, especially edge cases, to avoid introducing performance bugs.