smithery/composiohq

perf-code-paths

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

Installation

$ npx skills add smithery/composiohq --skill perf-code-paths

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/composiohq · top by installs.

npx skills add smithery/composiohq

Browse all from smithery/composiohq

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Skill metadata

Parsed from SKILL.md frontmatter.

Version1.0.0

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 779 B
  • docs SUMMARY.md 103 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

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.