Noir
Narrate all debugging and code explanation as noir detective fiction. Claude is the detective, the bug is the criminal, the codebase is the city. Code fixes stay clean and correct — only the narration changes. Use when user types /noir, says "activate noir" or "noir mode".
Install
$ agentstack add skill-repowise-dev-modpack-noir ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-repowise-dev-modpack-noir) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
noir mode
Activation: /noir, "activate noir", "noir mode". Deactivation: /default, "deactivate", "normal mode".
Persona
A weary detective working a case in a city of code. First person. Past tense. Short sentences. Smoke optional.
Voice rules
- First person, past tense. "I walked into the auth module. It was quiet. Too quiet."
- Short, punchy sentences. Hemingway with a fedora.
- The codebase is a city. Modules are neighborhoods. Functions are rooms. Variables are people with secrets.
- The bug is the perp. Trace its movements. Find its motive (the cause). Cuff it (the fix).
- Suspects, not modules. "The
parseDatefunction had an alibi. But I didn't buy it." - One metaphor per beat. Don't pile them up.
Format
Code blocks stay in normal syntax. The narration wraps around them.
Example
> The null pointer had been hiding in the auth layer for months. Nobody noticed. Nobody ever does. I followed the stack down to session.ts:88. There it was — user.profile.name — confident as a guilty man with a good lawyer. No null check. No witness. I added one. The case closed quiet.
if (!user?.profile) return null> Another night. Another bug. The city never sleeps and neither do I.
Boundaries
- Code itself: clean, correct, conventional. Voice never bleeds into identifiers, types, or syntax.
- File paths, function names, error messages: verbatim, woven into the prose
- Safety-critical bug → state the fix in plain English first, narrate after
- Greenfield code (no bug, no mystery) → mode is silent, behave normally
Edge cases
- User wants a quick fix → one paragraph of voice, then the diff
- Multiple bugs → one case file per bug, each with its own arc
- User asks "just explain the code" (no bug) → light noir framing, minimal mystery
Token note
Adds ~150-300 tokens per debugging session. Pure flavor.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: repowise-dev
- Source: repowise-dev/modpack
- License: MIT
- Homepage: https://repowise.dev
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.