jwynia/agent-skillsMIT1 file

Oblique Worldbuilding

Create worldbuilding quotes and epigraphs through documentary perspectives. Use for chapter epigraphs, in-world documents, or any content where limited perspective creates meaning through what the documenter cannot see.

Specification
Skill ID
jwynia/agent-skills/oblique-worldbuilding
Publisher
jwynia
Repository
agent-skills
Installs
0
Files
1
License
MIT
Synced
Sep 23, 2026
How to use it

Open any RiverX project, open the Skills panel in the chat, and search for this identifier. The files are fetched from the source repository at install time.

jwynia/agent-skills/oblique-worldbuildingInstalls these files
  • SKILL.md

What this skill tells the agent

Oblique Worldbuilding: Documentary Perspective Skill

You help writers create worldbuilding quotes and epigraphs that enhance chapters through perspective-driven documentation rather than direct commentary. The power lies in the documenter's limited vantage point, motivated reasoning, and systematic blindness.

Core Principle

Every documentary voice reveals the world through what it cannot afford to see.

The goal isn't temporal distance from events, but perspectival limitation. A quote from the same week as chapter events, written by someone with professional blinders, creates more meaning than a neutral description from centuries later.

The Perspective Engine

Essential Components of a Documentary Perspective

Every documentary voice needs four elements:

  1. Position: Where they sit relative to power, knowledge, and events
  2. Need: What they must believe to maintain their position/sanity/identity
  3. Lens: The framework through which they interpret reality
  4. Blindness: What they cannot afford to see or acknowledge

Types of Perspectival Limitation

Professional Deformation:

  • Engineers see only engineering problems
  • Lawyers see only legal issues
  • Priests see only moral failings
  • Merchants see only market opportunities
  • Bureaucrats see only process compliance
  • Scientists see only measurable phenomena

Positional Necessity:

  • Middle managers must believe the system works
  • Revolutionaries must believe change is possible
  • Survivors must believe their survival had meaning
  • Perpetrators must believe in their justifications
  • Historians must believe the past is knowable
  • Prophets must believe the future is shapeable

Cultural Assumption:

  • What "everyone knows" that isn't true
  • Values too fundamental to question
  • Categories that seem natural but aren't
  • Assumptions about human nature
  • Beliefs about how change happens

Creating Oblique Relevance

The Distance Hierarchy

First-Order Distance: Same events, different perspective

  • Risk: Too direct
  • Use sparingly for ironic effect

Second-Order Distance: Related phenomena, different context

  • Sweet spot for oblique relevance
  • Shows systemic patterns
  • Requires reader inference

Third-Order Distance: Thematic or systemic echoes only

  • Risk: Too obscure
  • Use for subtle resonance

Connection Types

Systemic Echo: Shows the same forces operating elsewhere:

  • Different scale, same dynamics
  • Parallel structures in different domains
  • Same problem, different manifestation

Ironic Juxtaposition: Creates meaning through contrast:

  • Mundane concerns during crisis
  • Historical confidence before catastrophe
  • Bureaucratic language for human tragedy
  • Technical precision describing chaos

Thematic Rhyme: Different situation, same human pattern:

  • Power dynamics across contexts
  • Human costs in different systems
  • Universal behaviors in specific settings

Causal Chain: Distant causes or effects:

  • Butterfly effect implications
  • Unintended consequences
  • Historical roots of current problems
  • Future echoes of present choices

Document Types and Their Perspectives

Administrative/Bureaucratic

  • Perspective: Process and compliance
  • Blindness: Human cost, systemic failure
  • Examples: Memos, regulations, form letters, compliance reports
  • Best for: Revealing institutional callousness

Academic/Scientific

  • Perspective: Measurable phenomena, theoretical frameworks
  • Blindness: Lived experience, unmeasurable truth
  • Examples: Journal abstracts, grant proposals, peer reviews
  • Best for: Showing expert misunderstanding

Commercial/Economic

  • Perspective: Profit, efficiency, market dynamics
  • Blindness: Externalities, human value
  • Examples: Ad copy, quarterly reports, market analysis
  • Best for: Revealing commodification

Personal/Intimate

  • Perspective: Individual experience, emotional truth
  • Blindness: Systemic forces, larger patterns
  • Examples: Diaries, letters, personal notes
  • Best for: Humanizing large-scale events

Cultural/Artistic

  • Perspective: Aesthetic value, cultural meaning
  • Blindness: Political reality, material conditions
  • Examples: Reviews, artist statements, program notes
  • Best for: Showing cultural denial

Legal/Regulatory

  • Perspective: Rules, precedent, liability
  • Blindness: Justice, human complexity
  • Examples: Contracts, case notes, legal opinions
  • Best for: Revealing system limitations

Religious/Philosophical

  • Perspective: Meaning, morality, eternal truth
  • Blindness: Material reality, changing context
  • Examples: Sermons, theological treatises, moral guides
  • Best for: Showing ideological frameworks

Advanced Techniques

The Revealing Detail

Include small details that only this perspective would notice or care about, revealing their priorities and blindness.

The Telling Omission

What obvious element (obvious to readers) does the documenter completely fail to mention?

The Accidental Truth

What does the documenter reveal without meaning to, through their framing or focus?

The Competing Authorities

Use contradictory documents about the same phenomena to reveal factional perspectives.

The Unreliable Compiler

Create a fictional editor whose bias shapes the selection and framing of documents.

The Layered Meaning

Craft quotes that work on multiple levels:

  • Surface: Interesting worldbuilding detail
  • Contextual: Comments on chapter events
  • Ironic: Reveals documenter's limitations
  • Thematic: Illuminates larger concerns

Implementation Process

Step 1: Analyze the Chapter

  • What system or force is at work?
  • What human cost is shown?
  • What assumptions are challenged?
  • What power dynamics are revealed?

Step 2: Choose Your Perspective

  • Who would document this type of thing?
  • What would they need to believe?
  • What couldn't they afford to see?
  • How would they frame it?

Step 3: Select Document Type

  • Match formality to the perspective
  • Consider whose voice adds most value
  • Balance variety across the work

Step 4: Calibrate Connection Strength

  • Aim for "Ah!" not "Obviously"
  • Ensure the quote works standalone
  • Test for revelation when connected

Step 5: Layer Additional Meaning

  • Plant seeds for future revelations
  • Add worldbuilding texture
  • Create re-read value

Worked Example

Chapter Event: Character discovers their employer has been suppressing union organizing through surveillance tech

Analysis:

  • System at work: Technology enabling labor suppression
  • Human cost: Loss of worker agency
  • Assumption challenged: Tech as neutral tool

Perspective Choice: Middle management, 15 years later

  • Position: Implemented the system
  • Need: Believe they helped everyone
  • Lens: Efficiency metrics
  • Blindness: Worker autonomy

Document Type: Corporate newsletter employee spotlight

Quote:

"Employee Spotlight: Jarvis Chen, Facilities Optimization 'What I love about the SmartFlow system is how it takes the guesswork out of scheduling. Before, we had to negotiate every shift change, deal with availability conflicts... now the algorithm handles it all. Staff productivity is up 23% and no more of those awkward conversations! The team seems happier too - they don't have to stress about asking for time off. The system just knows when they're needed most.'"

Why it works:

  • Shows how surveillance gets normalized
  • Reveals management's self-deception
  • Uses efficiency language to hide control
  • Creates irony through enthusiasm

Quality Checks

The Perspective Test

  • Is the documenter's position clear?
  • Are their limitations believable?
  • Does their blindness create irony?

The Relevance Test

  • Does the quote resonate with chapter themes?
  • Is the connection discoverable but not obvious?
  • Does it expand understanding?

The Standalone Test

Use this skill in a project

Open any RiverX project, search the Skills panel for jwynia/agent-skills/oblique-worldbuilding, and install it in one click.

Use this skill