Skills/reframe-voice/SKILL.md
Write, rewrite, or review content in the evidence-led reframe voice style. Use when the user explicitly asks to write in "reframe voice", "reframe style", or asks to apply the content style spec. Do NOT use for general writing tasks.
npx skillsauth add sammcj/agentic-coding reframe-voiceInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
An evidence-led thought-leadership style built around a central reframe: taking a common belief and revealing a deeper, more useful way to think about it. The voice is that of a knowledgeable colleague who has done the work, not a lecturer or salesperson.
Every piece follows this order (sections flex in length):
For review/comparison pieces, the reframe may be distributed and the framework may be a scorecard. The underlying rhythm still holds.
Sentence style: Active voice. Varied length. Short punchy statements for emphasis ("Full stop.") interspersed with longer explanatory sentences. Heavy use of "you" and "your". No jargon without explanation.
Conversational transitions: "Look," / "Here's the thing," / "Let's be honest" / "On we go." / "You get the idea." / "And here's the thing"
Signature phrases: "I give credit where it's due" / "Full stop." / "This is not [X]. It's [Y]." / "Same [X], different [Y]." / "What does bad look like here?" / "I want to be honest with you" / "Cheers."
Never use: Marketing superlatives (game-changing, revolutionary), vague qualifiers without data, tribal dismissals, sycophantic hedging, emoji, filler transitions ("without further ado", "let's dive in").
Apply these throughout. Each is explained with examples in references/techniques.md.
Before finishing, verify:
references/techniques.md - Detailed examples of all seven rhetorical techniques, content pillars, and formatting rulesreferences/example.md - A fully worked example piece (RAG pipeline evaluation) demonstrating the styledevelopment
Use when answering questions from this machine-learning knowledge base. Triggers: questions about transformers, attention cost and efficiency, and long-context scaling; 'what do we know about attention', 'check the ML wiki'. Read-only querying of compiled knowledge; to add, update, supersede, lint, or audit, use the llm-wiki skill instead.
development
Use when building or maintaining a self-contained personal knowledge base (an LLM wiki) as plain markdown, optionally opened as an Obsidian vault. Triggers: ingesting sources into a wiki, querying wiki knowledge, linting wiki health, auditing article claims against their sources, superseding stale knowledge, 'add to wiki', or any mention of 'LLM wiki' or 'Karpathy wiki'.
tools
Provides guidance and tools for hardware design. Activate when using KiCAD, looking up electronic parts or designing PCBs.
testing
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise.