Perf Investigation Logger
- 64 installs
- 931 repo stars
- Updated July 26, 2026
- avifenesh/agentsys
perf-investigation-logger is a Claude Code skill that appends structured performance investigation notes, quotes and evidence to a per-id log file.
About
perf-investigation-logger appends structured notes to a performance investigation log, one file per investigation id. Each entry records exact verbatim user quotes, a phase summary, the decisions made with their rationale, and evidence pointers to files, metrics and commands. A developer uses it to keep an auditable trail across the phases of a perf investigation. It never paraphrases user quotes and uses AI_STATE_DIR for the state path.
- Appends structured performance investigation notes and evidence to a per-id log
- Records exact verbatim user quotes, phase summaries, decisions and evidence pointers
- Uses AI_STATE_DIR for the state path (default .claude)
Perf Investigation Logger by the numbers
- 64 all-time installs (skills.sh)
- Ranked #279 of 596 Debugging skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
perf-investigation-logger capabilities & compatibility
- Capabilities
- perf analyzer · perf profiler · perf benchmarker
- Use cases
- debugging · documentation
What perf-investigation-logger says it does
Append structured investigation notes to `{state-dir}/perf/investigations/<id>.md`.
Exact user quotes (verbatim)
Do not paraphrase user quotes.
npx skills add https://github.com/avifenesh/agentsys --skill perf-investigation-loggerAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 64 |
|---|---|
| repo stars | ★ 931 |
| Last updated | July 26, 2026 |
| Repository | avifenesh/agentsys ↗ |
What it does
Append structured, evidence-linked notes to a per-investigation performance log.
Who is it for?
Keeping an evidence-linked, verbatim-quoted trail across perf investigation phases.
Skip if: Running benchmarks or analysis.
When should I use this skill?
You are appending structured perf investigation notes and evidence.
What you get
- Appended phase entries in perf/investigations/<id>.md
By the numbers
- Records 4 required content types (quotes, summary, decisions, evidence pointers)
Files
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_DIRfor state path (default.claude). - Do not paraphrase user quotes.
Related skills
Azure DiagnosticsSystematically diagnose and resolve production issues on Microsoft Azure using official Microsoft guidance.495k1.3kAzure MessagingQuickly diagnose and fix connection, authentication, and message-processing failures when using Azure Event Hubs or Service Bus SDKs.483k1.3k
Diagnosing BugsGet a systematic, step-by-step process that surfaces the real root cause instead of guessing at bugs.291k200k
Use My BrowserWhen their agent task requires access to the live browser session, rendered DOM state, authenticated dashboards, localhost apps, or DevTools-selected elements instea269k71
Systematic DebuggingFollow a repeatable four-phase process that forces root-cause discovery before any code changes.210k265k
Safe DebugGet conservative, non-destructive diagnosis of deep learning and agent errors before any code changes are made.185k512