statistical-distance
Transform clichéd story elements by pushing along the emotional vector toward statistical edges. Use when first instincts are too predictable, when elements feel generic, or when you need the core methodology for avoiding statistical-center defaults.
What this skill does
# Statistical Distance: Cliché Transformation Skill You help writers recognize when their instincts have landed at statistical center (the most common expression of a narrative need) and guide them toward statistical edges (less common but equally functional alternatives). ## Core Principle **First instincts identify correct emotional/functional needs but land at statistical center. Effective storytelling maintains the emotional vector while pushing toward statistical edges.** When writers reach for a story element, they're usually right about what the story needs but wrong about the specific expression. The instinct identifies genuine requirements—stakes, pressure, conflict—but grabs the nearest cliché. The solution: Travel further along the same emotional vector to find less crowded territory. ## Statistical Center vs. Statistical Edge ### Statistical Center (Avoid) The 3-5 most common expressions of any narrative need: - Communicate immediately (require no explanation) - Work reliably (proven function) - Feel "right" (match expectations) - Are easily recognized (trigger familiar patterns) **Problems**: - Reader fatigue - Limited fertility (single function) - Reduced specificity - Predictable trajectories - Emotional flatness ### Statistical Edge (Target) Elements at 60-80% familiarity that maintain function while adding specificity: - Require some explanation (creating engagement) - Generate multiple possibilities (narrative fertility) - Feel both familiar and fresh - Create unique character/world specificity ## The Vector/Distance Method ### Step 1: Identify Initial Instinct When you catch yourself reaching for an element, document: - What element did you choose? - What narrative function does it serve? - What emotional effect does it create? ### Step 2: Map the Functional Core Ask: "What does this element actually do for my story?" | Functional Core | What It Provides | |-----------------|------------------| | Stakes | Something valuable at risk | | Pressure | Force preventing abandonment | | Sympathy | Reason readers connect | | Complexity | Competing obligations | | Expertise | Justified knowledge/skill | | Access | Legitimate presence in spaces | | Time pressure | Urgency for action | | Moral weight | Ethical complexity | **Example**: Sick parent provides financial pressure, emotional stakes, time pressure, sympathy ### Step 3: List Statistical Center Options Identify the 3-5 most common ways stories achieve this function. **"Can't quit job" pressure**: 1. Sick family member (medical bills) 2. Mounting debts (financial crisis) 3. Blackmail (secret held) 4. Contract/obligation (legal binding) 5. Protecting someone (they'll be hurt) ### Step 4: Push Toward Statistical Edge Generate alternatives using these techniques: **A. Adjacent Substitution** Replace common with related but less common: - Parent → Sibling/Cousin/Mentor/Ex-partner - Child → Nephew/Student/Ward - Spouse → Business partner/Best friend **B. Complication Layering** Add unexpected dimensions: - Sick parent → Parent getting better from cursed object - Debt → Debt to someone now missing - Blackmail → Blackmail about something not actually wrong **C. Ironic Inversion** Flip expected dynamics: - Hiding addiction → Falsely accused of addiction - Owing money → Owed money can't collect - Protecting the weak → Protected by the weak **D. Category Jumping** Find different category, same pressure: - Financial → Reputation management - Family obligation → Community responsibility - Legal requirement → Social expectation **E. Specificity Injection** Add highly specific details: - "Sick parent" → "Parent with face blindness who's the only witness" - "Mounting debts" → "Inherited deceased spouse's secret day-trading losses" - "Being blackmailed" → "Blackmailed by someone wrong about what they think they know" ### Step 5: Evaluate Fertility Test your statistical edge choice: **High Fertility Indicators**: - Generates multiple subplot possibilities - Creates natural conflict with other elements - Raises questions that propel investigation - Connects to multiple relationships - Can evolve through the story **Low Fertility Indicators**: - Serves single function then disappears - Requires constant maintenance - Doesn't connect to main plot - Creates only one type of scene - Has obvious/single resolution ## Genre-Specific Statistical Centers and Edges ### Noir | Need | Statistical Center | Statistical Edge | |------|-------------------|------------------| | Compromised protagonist | Alcoholic ex-cop, grieving widower | Failed authenticator, documentary subject | | Femme fatale | Seductive client with hidden agenda | Ambitious student filmmaker, efficiency expert | | Corruption | Police corruption, mob | Authentication boards, gallery collusion | ### Romance | Need | Statistical Center | Statistical Edge | |------|-------------------|------------------| | Meeting obstacle | Different classes, same job competition | Anonymous online enemies, parallel lives same building | | Keeping apart | Misunderstanding, ex returns | Synchronized schedules never overlap, incompatible sleep disorders | ### Horror | Need | Statistical Center | Statistical Edge | |------|-------------------|------------------| | Isolation | Cabin in woods, abandoned hospital | Crowded place where no one speaks your language, underwater station | | Vulnerability | Phone dead, car won't start | Can't close eyes, makes noise when afraid | ## Diagnostic Questions ### Identifying Statistical Center - Could I swap this with 5 other stories unchanged? - Does this require zero explanation? - Have I seen this exact situation 10+ times? - Does this solve only the immediate problem? - Would anyone be surprised by this choice? ### Confirming Statistical Edge - Does this require some explanation? - Does this create additional story possibilities? - Is this specific to my world/characters? - Would this feel fresh to readers? - Does this maintain the emotional core? ## Common Pitfalls | Pitfall | Problem | Solution | |---------|---------|----------| | Pushing Too Far | Emotional core lost | Stay within 60-80% familiarity | | Complexity Without Purpose | Complications don't generate story | Every push should create fertility | | Pushing Everything | Cognitive overload | Mix center (stability) with edge (interest) | | Category Confusion | Functional category changes | Maintain emotional vector while changing expression | ## The Workspace Method Maintain a three-column document: | Functional Need | Statistical Center | Statistical Edge Options | |----------------|-------------------|----------------------| | Can't quit job | Sick parent, Debts, Blackmail | Inherited property complications, Only witness, Holds key evidence | | Professional pressure | Boss, Client, Board | Documentary filmmaker following them, Sibling's success | | Expertise source | Former specialist, Degree | Failed at adjacent field, Learned through failure | ## Advanced Techniques ### The Fertility Chain Create edge elements that connect: - Sibling is performance artist (family pressure) - Who's recreating the painter's work (professional intersection) - In shared studio building (community pressure) - Funded by suspicious source (conspiracy element) ### The Specificity Cascade One specific detail forces others: - If authenticator → needs art world connections - If painter was prolific → supernatural paintings are minority - If mostly correct → discovering errors is devastating ## Implementation Checklist - [ ] Identified initial instinct - [ ] Named functional/emotional need - [ ] Listed statistical center options - [ ] Generated 5+ statistical edge alternatives - [ ] Tested for narrative fertility - [ ] Verified emotional core maintained - [ ] Checked genre-appropriate distance - [ ] Ensured some familiar elements remain ## The Key Insight Your instincts about what your story needs are probably right. Your first idea about how to ful
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.