mcpbeat

Perf Investigation Logger

composio-community/perf-investigation-logger

Use when appending structured perf investigation notes and evidence.

187 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-investigation-logger

The instruction itself

4 sections, as written by the author

perf-investigation-logger

Append structured investigation notes to {state-dir}/perf/investigations/<id>.md.

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

Required Content

  • Exact user quotes (verbatim)
  • Phase summary
  • Decisions and rationale
  • Evidence pointers (files, metrics, commands)

Output Format

## <Phase Name> - <YYYY-MM-DD>

**User Quote:** "<exact quote>"

**Summary**
- ...

**Evidence**
- Command: `...`
- File: `path:line`

**Decision**
- ...

Constraints

  • Use AI_STATE_DIR for state path (default .claude).
  • Do not paraphrase user quotes.

How to use it

Copy the folder

Take composio-community/perf-investigation-logger 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.