mcpbeat

Perf Code Paths

composio-community/perf-code-paths

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

194 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
1856
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/composio-community/awesome-claude-plugins --skill perf-code-paths

The instruction itself

4 sections, as written by the author

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.

How to use it

Copy the folder

Take composio-community/perf-code-paths from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.