
non-fiction-precision
Use when a document's argument buries its conclusion or has logical gaps—applies Minto's Pyramid (Answer First, MECE grouping) and Orwell's concision rules to rebuild structure.
- Installs
- 46
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/joellewis/skill-library --skill non-fiction-precision- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads non-fiction-precision automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Overview
Non-fiction precision is the art of structural integrity and prose economy. It focuses on the "bones" of a piece (structure) and the "concision" of the sentence (clarity). By applying Minto's logical grouping, Strunk's grammatical orders, and McPhee's narrative discipline, writing becomes a tool for strategic action rather than a swamp for the reader to drown in.
Guiding Principles
Principle 1: The Answer First (Source: Minto, The Pyramid Principle)
Start every document or section with the conclusion or recommendation. The reader's most valuable resource is attention—earn it in the first sentence by providing the "Answer" before the supporting "Logic."
Principle 2: Omit Needless Words (Source: Strunk, The Elements of Style)
Vigorous writing is concise. A sentence should contain no unnecessary words and a paragraph no unnecessary sentences. This does not mean making all sentences short, but ensuring that every word tells.
Principle 3: Write Like You Talk (Source: Graham, "Write Like You Talk")
Write in the same language you would use when explaining a concept to a friend. If a sentence sounds "written" or "academic," it is likely obscuring the truth. Avoid "fancy" words where a simple one suffices.
Principle 4: The 1,000 Details Rule (Source: McPhee, Draft No. 4)
A thousand details add up to one impression. Use specific, concrete language to evoke images and sensations. No single detail is essential, but the collective selection must be absolute to what follows.
Principle 5: The "Six Rules" of Clarity (Source: Orwell, "Politics and the English Language")
- Never use a metaphor or figure of speech you're used to seeing in print.
- Never use a long word where a short one will do.
- If it is possible to cut a word out, always cut it out.
- Never use the passive where you can use the active.
- Never use a foreign phrase or jargon if an everyday English equivalent exists.
- Break any of these rules sooner than say anything outright barbarous.
When to Use This Skill
- Drafting memos, reports, or PRDs.
- Structuring complex arguments or whitepapers.
- Refining prose for executive-level communication.
- Explaining technical concepts to non-technical audiences.
When NOT to Use This Skill
- Writing fiction (where "Show, Don't Tell" and subtext may require more indirect prose).
- Creative/Experimental prose where ambiguity or rhythmic "padding" is an intentional stylistic choice.
Core Process
Step 1: The SCQ Discovery (Source: Minto, The Pyramid Principle)
Define the Situation (the context everyone agrees on), the Complication (what changed to create a problem), and the Question (the implicit need for a solution). The Answer to this question is your lead.
Step 2: The Pyramid Build (Source: Minto, The Pyramid Principle)
Group your supporting points using the MECE (Mutually Exclusive, Collectively Exhaustive) principle. Ensure that every point in a group is of the same kind and summarizes the points below it.
Step 3: The Lead and Structure (Source: McPhee, Draft No. 4)
Develop a structural "blueprint" before writing. Choose between a Chronological flow (if a journey or sequence is key) or a Thematic flow (if topics need grouping). Write the Lead as a "promise" to the reader that you must keep.
Step 4: The Strunkian Pruning (Source: Strunk, The Elements of Style)
Review every sentence for three core commands:
- Use Active Voice: Make the subject act.
- Put Statements in Positive Form: Tell the reader what is, not what is not.
- Use Concrete Language: Replace "unfavorable weather" with "it rained every day."
Step 5: The "Read Aloud" Audit (Source: Graham, "Write Like You Talk")
Read the entire draft aloud. Any passage that makes you stumble or sounds unnatural in speech must be rewritten. If you wouldn't say it in a conversation, don't write it in a memo.
Frameworks & Models
SCQ Framework (Source: Minto, The Pyramid Principle)
- Situation: Background context the reader already knows.
- Complication: A change that creates a problem or opportunity.
- Question: The specific problem the reader wants solved.
- Answer: Your core recommendation (The "Answer First").
MECE Principle (Source: Minto, The Pyramid Principle)
- Mutually Exclusive: No overlaps between points; each sub-point is distinct.
- Collectively Exhaustive: No gaps; the sum of the sub-points covers the entire parent topic.
Cross-Skill Invocations
REQUIRED SUB-SKILL: None. RECOMMENDED SUB-SKILL: copy-editor — for line-level polishing after the structure is set.
Common Mistakes
- The "Nut Graph" Trap: Burying the main point in the third or fourth paragraph. (Source: Minto)
- Passive Evasion: Using "The decision was made..." to avoid naming who made it. (Source: Strunk)
- Jargon Crutch: Using specialized terms to sound "sophisticated" while hiding a lack of clarity. (Source: Orwell)
- Mechanical Symmetry: Making all sentences the same length/structure, creating a "singsong" monotony. (Source: McPhee)
Diagnostic Checklist
- Is the "Answer" or recommendation in the first paragraph?
- Have I eliminated all "needless words" (e.g., "the fact that", "very", "basically")?
- Are the supporting points MECE (no overlaps, no gaps)?
- Does the piece sound like a natural conversation when read aloud?
- Have I used specific, concrete examples for every general principle?
Sources
- Minto, Barbara. The Pyramid Principle. Ch. 1 (Pyramid Structure), Ch. 2 (SCQ).
- McPhee, John. Draft No. 4. Ch. 2 (Structure), Ch. 3 (Draft No. 4), Ch. 4 (Checkpoints).
- Strunk, William. The Elements of Style. Ch. 2 (Principles of Composition).
- Orwell, George. "Politics and the English Language".
- Graham, Paul. "Write Like You Talk".
FAQ
What does the non-fiction-precision skill do?
Use when a document's argument buries its conclusion or has logical gaps—applies Minto's Pyramid (Answer First, MECE grouping) and Orwell's concision rules to rebuild structure.
How do I install non-fiction-precision?
Run npx skills add https://github.com/joellewis/skill-library --skill non-fiction-precision in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/non-fiction-precision/ (personal) or .claude/skills/non-fiction-precision/ (project).
Which AI agents can use non-fiction-precision?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is non-fiction-precision safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains non-fiction-precision?
It is published by joellewis in joellewis/skill-library. It has 46 recorded installs.
More from joellewis/skill-library
fiction-architect
joellewis/skill-library
Open the skill to read its SKILL.md instructions.
dialogue-craft
joellewis/skill-library
Writes and refines dialogue that serves plot and reveals character through subtext, intention, and behavioral exchange — applying McKee's subtext principle and Sorkin's intention-and-obstacle model. Use when dialogue feels flat, expository, or 'on the nose.'
world-building-logic
joellewis/skill-library
Engineers internally consistent fictional worlds using Brand's Pace Layers for social structure and Sanderson's Laws of Magic for system constraints. Use when building settings, designing magic or tech systems, or auditing a world for logical contradictions.
problem-framing
joellewis/skill-library
Use when beginning analytical or strategic tasks, facing undefined problems, or facing analysis paralysis—requires explicit problem definition before proceeding.
character-vulnerability
joellewis/skill-library
Use when a character feels flat, too competent, or unrelatable—identifies the Sacred Flaw (Storr's Theory of Control) and dials the Three Sliders (Sanderson) to create earned vulnerability.
one-pager
joellewis/skill-library
Use when compressing a complex strategy or analysis into a strictly one-page narrative—enforces Pyramid SCQ structure and Orwell word-budget discipline.
Popular other skills
hyperframes-cli
heygen-com/hyperframes
The HyperFrames CLI by job - scaffold, check, look at frames, edit the timeline, preview, render locally or in the cloud, publish, project history - plus reading its JSON and recovering from build or render failures.
triage
mattpocock/skills
Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.
ask-matt
mattpocock/skills
Ask which skill or flow fits your situation. A router over the skills in this repo.
to-questionnaire
mattpocock/skills
Turn a decision you can't fully answer into a questionnaire for someone else to fill in.
loop-me
mattpocock/skills
Grill me about specs for the workflows I want to build, within this workspace.