perf-investigation-logger
Use when appending structured perf investigation notes and evidence.
Profile →npx skills add agent-sh/agentsys --skill perf-investigation-logger --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-investigation-logger Append structured investigation notes to `{state-dir}/perf/investigations/<id>.md`. Follow `docs/perf-requirements.md` as the canonical contract. ## Required Content 1. Exact user quotes (verbatim) 2. Phase summary 3. Decisions and rationale 4. 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.
- Required Content
- Output Format
- Constraints
What does the perf-investigation-logger skill do?
Use when appending structured perf investigation notes and evidence.
How do I install it?
Run `npx skills add agent-sh/agentsys --skill perf-investigation-logger --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.