workflow-performance-investigation SKILL.md skillA
workflow-performance-investigation from lugassawan/swe-workbench is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add lugassawan/swe-workbench/workflow-performance-investigation@git:20260828.71a6399Pins git:20260828.71a6399 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- lugassawan/swe-workbench
- Path
skills/workflow-performance-investigation/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260828.71a6399, committed Aug 28, 2026
- First version recorded
- Jul 12, 2026
- Size
- 5,517 bytes
- Repository stars
- 3
- License
- MIT
Profile-first performance investigation runbook — reproduce and baseline a metric, pick a profiler from the ecosystem tooling matrix (Go/Python/JVM/Node/Rust/Ruby/.NET/native), capture CPU + alloc profiles under load, hand the profile to the performance-tuner agent for ranked hotspot read, form one hypothesis, make one isolated change, regression guard. Keywords — profile flame graph hotspot bottleneck slow endpoint investigation benchmark.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# workflow-performance-investigation Profile-first runbook: baseline → profile → ranked hotspots → hypothesize → isolate → measure → regression guard. **Announce at start:** "I'm using the workflow-performance-investigation skill to structure this performance investigation." ## When to invoke - An endpoint, job, or service is slow and the bottleneck is unknown. - "Profile this and confirm the fix works before/after." - You have a hypothesis but no profile to validate it. ## When NOT to invoke - Design-time hot-path review (Big-O, allocation choices, N+1 avoidance) → use `swe-workbench:principle-performance` directly. - You already have a profile and only need the ranked hotspot read → invoke the `swe-workbench:performance-tuner` agent directly via `/swe-workbench:review --mode perf`. - Reviewing a PR diff for perf regressions → `/swe-workbench:review --mode perf`. ## Composition - **`swe-workbench:principle-performance`** — design-time discipline (Big-O, allocation, N+1, data locality). Run inline or hand off; never skip the discipline layer. …
Read the whole file at its exact version.
How to install
mdr add lugassawan/swe-workbench/workflow-performance-investigation@sha256:60f5c2243d1aee5aThe line at the top of this page pins the label git:20260828.71a6399, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_xtzkqjvsducryu7v)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Jul 12, 2026 and Aug 28, 2026, about one every 12 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260828.71a6399 latest | 2026-08-28 | 71a6399 | 5,517 B | A | view · diff |
| git:20260820.16e7f08 | 2026-08-20 | 16e7f08 | 5,612 B | A | view · diff |
| git:20260811.925e30f | 2026-08-11 | 925e30f | 5,609 B | A | view · diff |
| git:20260802.bba96ce | 2026-08-02 | bba96ce | 5,595 B | A | view · diff |
| git:20260712.65243d2 | 2026-07-12 | 65243d2 | 5,553 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (5517 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
lugassawan/swe-workbench · 3 stars · license MIT · pushed 2026-11-07 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_xtzkqjvsducryu7v GET https://markdownregistry.com/api/v1/resolve?ref=lugassawan/swe-workbench/workflow-performance-investigation GET https://markdownregistry.com/api/v1/blob/60f5c2243d1aee5a6c64b21a950ea2528ac9f23bf803e478d914b36952d055e0
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.