← ClaudeAtlas

opus-mindlisted

Use when the user edits CLAUDE.md / AGENTS.md / .cursorrules / GEMINI.md / **/SKILL.md or any chatbot system prompt (LINT), OR when the user wants to tighten a vague one-shot prompt before sending it to an LLM (BOOST). Fires on audit/score/review/fix requests, on symptoms like refuse-relent, narration leak, rule conflict, and on "help me improve this prompt" messages.
Hybirdss/opus-mind · ★ 2 · AI & Automation · score 66
Install: claude install-skill Hybirdss/opus-mind
# opus-mind Two products, one skill. **LINT** audits production system prompts against 11 structural invariants reverse-engineered from the leaked Claude Opus 4.7 system prompt. **BOOST** coaches a user's single request against 10 slots — 7 for specification quality and 3 for reasoning quality (chain-of-thought, verification, decomposition). Python helpers are deterministic (regex, counts, string templates). Synthesis — composing rewrites, applying semantic review, judging domain context — is done by you, the Claude running this session. No API key, no extra cost, no shell-out. ## When to use - User edits or audits: `CLAUDE.md`, `AGENTS.md`, `.cursorrules`, `GEMINI.md`, `**/SKILL.md`, `system-prompt*.md`, or a chatbot system prompt → **LINT**. - User pastes a vague one-shot request meant for Claude / ChatGPT / Cursor and wants it concrete → **BOOST**. - User describes a symptom — refuse-relent, narration leak, rule conflict, adjective drift, jailbreak, injection, tool-call drift → **LINT Debug**. ## When NOT to use - The target file has fewer than 3 directives or fewer than 10 lines. Run audit anyway and quote the `THIN` verdict back at the user verbatim; do not invent coverage. - The user wants a generic "make this better" with no file, no pasted text, and no repo context. Ask for the concrete prompt first. - The request is about Claude's own safety policy (e.g. "why did Claude refuse X?"). Point to Anthropic docs. This skill is about prompt struc