Perf Investigation Logger
- 2 installs
- 931 repo stars
- Updated July 26, 2026
- avifenesh/awesome-slash
perf-investigation-logger is a skill that appends structured, evidence-backed notes and verbatim user quotes to a performance investigation log file.
About
This skill appends structured notes to a performance investigation log. A developer uses it to keep a durable, evidence-backed record of each phase, including verbatim user quotes, decisions with rationale, and pointers to files, metrics, and commands. It writes to a per-investigation markdown file and never paraphrases user quotes.
- Appends structured performance investigation notes and evidence
- Captures verbatim user quotes, phase summaries, decisions, and evidence pointers
- Writes to a per-investigation markdown file under the state directory
Perf Investigation Logger by the numbers
- 2 all-time installs (skills.sh)
- Ranked #467 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
- investigation logging · decision recording · documentation
- Use cases
- documentation · debugging
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/awesome-slash --skill perf-investigation-loggerAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 2 |
|---|---|
| repo stars | ★ 931 |
| Last updated | July 26, 2026 |
| Repository | avifenesh/awesome-slash ↗ |
What it does
Append structured, evidence-backed notes and verbatim user quotes to a performance investigation log.
Who is it for?
Developers running a long performance investigation who need a durable, auditable trail of decisions and evidence.
Skip if: Producing recommendations or running benchmarks; this skill only records notes.
When should I use this skill?
You are appending structured perf investigation notes and evidence.
What you get
A structured markdown log with verbatim quotes, phase summaries, decisions, and evidence pointers.
- structured investigation markdown log
By the numbers
- 4 required note sections (quotes, summary, decisions, evidence)
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.185k512FAQ
Are user quotes paraphrased?
No, the skill records exact user quotes verbatim and forbids paraphrasing.
Where are notes stored?
In a per-investigation markdown file under the state directory's perf/investigations folder.