perf-code-paths
Use when mapping code paths, entrypoints, and likely hot files before profiling.
Profile →npx skills add agent-sh/agentsys --skill perf-code-paths --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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-intel 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.
- Required Steps
- Output Format
- Constraints
What does the perf-code-paths skill do?
Use when mapping code paths, entrypoints, and likely hot files before profiling.
How do I install it?
Run `npx skills add agent-sh/agentsys --skill perf-code-paths --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From agent-sh/agentsys, a repository with 923 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.