Code paths
Skill composio-community/awesome-claude-plugins/perf/skills/code-paths
Use when mapping code paths, entrypoints, and likely hot files before profiling.From its SKILL.md
npx -y skills add composio-community/awesome-claude-plugins --skill code-pathsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
SKILL.md
0.8 KB, 155 tokens by cl100k_base, as published. Nobody here has run it
perf-code-paths
Identify likely implementation paths for a performance scenario.
Follow docs/perf-requirements.md as the canonical contract.
Required Steps
- Use repo-map if available; otherwise use grep for entrypoints and handlers.
- List top candidate files/symbols tied to the scenario.
- 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.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.