CtrlK
BlogDocsLog inGet started
Tessl Logo

perf-code-paths

Use when mapping code paths, entrypoints, and likely hot files before profiling.

63

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./perf/skills/code-paths/SKILL.md
SKILL.md
Quality
Evals
Security

perf-code-paths

Identify likely implementation paths for a performance scenario.

Follow docs/perf-requirements.md as the canonical contract.

Required Steps

  1. Use repo-map if available; otherwise use grep for entrypoints and handlers.
  2. List top candidate files/symbols tied to the scenario.
  3. Include imports/exports or call chains when relevant.

Output Format

keywords: <comma-separated list>
paths:
  - file: <path>
    symbols: [<symbol1>, <symbol2>]
    evidence: <short reason>

Constraints

  • Focus only on supported languages (Rust, Java, JS/TS, Go, Python).
  • Keep to the most relevant 10-15 files.
Repository
composio-community/awesome-claude-plugins
Path

perf/skills/code-paths/SKILL.md

Commit

e521f7a

Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.

Claim skill