New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Oblique Worldbuilding

by jwynia in jwynia/agent-skills

Create worldbuilding quotes and epigraphs through documentary perspectives.

MITAuto-check passedWriting & Content

Install Oblique Worldbuilding

skills CLI
$ npx skills add jwynia/agent-skills --skill oblique-worldbuilding -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jwynia/agent-skills oblique-worldbuilding --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jwynia/agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/creative/fiction/worldbuilding/oblique-worldbuilding .claude/skills/oblique-worldbuilding && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
oblique-worldbuilding
GitHub stars
170
Token cost
~4k tokens
SKILL.md length
1,853 words
Files
1
Skills in repo
111
Repo updated
First seen
Licence
MIT

At a glance

Create worldbuilding quotes and epigraphs through documentary perspectives.

  • Works in 10 steps: Analyze the Chapter → Choose Your Perspective → Select Document Type → …
  • Chapter epigraphs
  • SKILL.md covers Core Principle, The Perspective Engine, Creating Oblique Relevance and Document Types and Their…, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Oblique Worldbuilding is an agent skill from jwynia/agent-skills. 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.

Its SKILL.md is about 4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Writing & Content, covering Creative writing and fiction. The licence is MIT.

When your agent uses it

  • Chapter epigraphs
  • In-world documents
  • Any content where limited perspective creates meaning through what the documenter cannot see

Example prompts

  • “/oblique-worldbuilding”

Workflow steps

10 steps, taken from the step headings in SKILL.md.

  1. Analyze the Chapter
  2. Choose Your Perspective
  3. Select Document Type
  4. Calibrate Connection Strength
  5. Layer Additional Meaning
  6. Too Direct
  7. Too Obscure
  8. Missing Perspective
  9. Overexplanation
  10. Voice Inconsistency

What it can do on your machine

Read from SKILL.md and the folder at commit e02ec7e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Oblique Worldbuilding loads about 4k tokens when it runs. Until then it costs about 60 tokens; SKILL.md has 1,853 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~60
When it runs · the whole SKILL.md, loaded when a task matches
~4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jwynia/agent-skills at commit e02ec7e, republished under its MIT licence (© jwynia). 1,853 words, ~3,978 tokens.

Download SKILL.mdSave it as .claude/skills/oblique-worldbuilding/SKILL.md (or your agent's skills folder).
name
oblique-worldbuilding
description
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.
license
MIT
metadata.author
jwynia
metadata.version
1.0
metadata.type
generator
metadata.mode
generative
metadata.domain
worldbuilding

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
  • 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
  • Is the quote interesting without the chapter?
  • Does it build the world independently?
  • Could it seed its own story?

Output Persistence

Output Discovery
  1. Check for context/output-config.md in the project
  2. If found, look for this skill's entry
  3. If not found, ask user: "Where should I save epigraph documents?"
  4. Suggest: worldbuilding/documents/ or explorations/worldbuilding/
Primary Output
  • Documentary voice - Position, need, lens, blindness
  • Document type - Administrative, academic, commercial, etc.
  • Connection type - Systemic echo, ironic juxtaposition, thematic rhyme
  • Layered meanings - Surface, contextual, ironic, thematic
File Naming

Pattern: {chapter/section}-epigraph-{date}.md

Verification (Oracle)

What This Skill Can Verify
  • Perspective components - Position/need/lens/blindness defined? (High confidence)
  • Connection presence - Relevance to chapter identifiable? (Medium confidence)
  • Standalone quality - Quote interesting without chapter? (Medium confidence)
What Requires Human Judgment
  • Subtlety calibration - Too direct or too obscure?
  • Voice authenticity - Does it sound like the documenter?
  • Reader discovery - Will connection create "ah!" moment?
Show full SKILL.md (739 more words)Show less
Oracle Limitations
  • Cannot assess whether reader will make the intended connection
  • Cannot predict whether irony will land

Feedback Loop

Session Persistence
  • Output location: See context/output-config.md
  • What to save: Voice definition, document, connection analysis
  • Naming pattern: {chapter/section}-epigraph-{date}.md
Cross-Session Learning
  • Check for prior epigraphs in this work
  • Ensure variety of document types and perspectives
  • Failed connections inform anti-patterns

Design Constraints

This Skill Assumes
  • Story has chapters/sections that can receive epigraphs
  • World has documentary voices beyond the narrative
  • Writer wants implied depth, not exposition
This Skill Does Not Handle
  • Direct worldbuilding - Route to: worldbuilding
  • Cultural texture - Route to: memetic-depth
  • Prose voice - Route to: prose-style
Degradation Signals
  • Quotes summarize chapter events (too direct)
  • No discernible thematic connection (too obscure)
  • Generic voice without position/blindness

Reasoning Requirements

Standard Reasoning
  • Single epigraph creation
  • Basic perspective definition
  • Simple connection identification
Extended Reasoning (ultrathink)
  • Full epigraph series - [Why: must create variety and progression]
  • Multi-layer design - [Why: surface/contextual/ironic/thematic must cohere]
  • Fictional compiler voice - [Why: who selects these documents and why]

Trigger phrases: "design the complete epigraph series", "create the documentary frame", "layer the meanings"

Execution Strategy

Sequential (Default)
  • Analyze chapter before choosing perspective
  • Define voice before writing document
  • Draft before calibrating connection
Parallelizable
  • Creating multiple epigraphs for different chapters
  • Research into different document types
Subagent Candidates
TaskAgent TypeWhen to Spawn
Document researchgeneral-purposeWhen modeling on real document types
World consistencyExploreWhen checking against existing worldbuilding

Context Management

Approximate Token Footprint
  • Skill base: ~3k tokens (perspective engine + document types)
  • With process: ~4k tokens
  • With worked example: ~4.5k tokens
Context Optimization
  • Focus on current perspective and document type
  • Document type catalog is reference
  • Worked example optional
When Context Gets Tight
  • Prioritize: Current perspective, active document type
  • Defer: Full document type catalog, advanced techniques
  • Drop: Worked example, all quality checks

Anti-Patterns

1. Too Direct

Pattern: Quotes that summarize chapter events, documents directly about main characters, contemporary reactions to specific events. Why it fails: Direct commentary removes reader discovery. The power of oblique worldbuilding is inference—readers connect the document to the chapter themselves. Fix: Use second-order distance. Find related phenomena in different contexts. Let systemic patterns create the connection rather than explicit reference.

2. Too Obscure

Pattern: No discernible thematic connection, requires outside knowledge, pure worldbuilding without resonance. Why it fails: If readers can't make the connection, the epigraph becomes noise. Oblique doesn't mean random—it means indirect but discoverable. Fix: Test with a reader. Can they articulate why this quote precedes this chapter? The connection should be findable even if not obvious.

3. Missing Perspective

Pattern: Generic documentary voice with no clear position or blindness, could be written by anyone. Why it fails: The meaning comes from limitation. A neutral description reveals nothing about the world. The documenter's blindness tells us what the culture cannot see. Fix: Define all four components: position, need, lens, blindness. If you can't answer "What can't this documenter afford to see?" the perspective isn't sharp enough.

4. Overexplanation

Pattern: Quote explains its own relevance, too heavy-handed irony, leaves nothing for reader discovery. Why it fails: Reader discovery creates engagement. When the connection is spelled out, reading becomes passive consumption rather than active meaning-making. Fix: Remove explicit connections. Trust readers. The irony should emerge from juxtaposition, not commentary.

5. Voice Inconsistency

Pattern: Documents that sound like the author, not the fictional documenter. Academic papers without jargon, bureaucrats without bureaucratese. Why it fails: Voice authenticity sells the fiction. When documents sound generic, the world feels thin. The documenter should write like themselves, not the author. Fix: Research the document type. How do real bureaucrats, academics, journalists write? Match formality, jargon, assumptions. The voice should feel found, not written.

Final Principles

  1. Perspective is Power: The documenter's position and limitations create meaning
  2. Blindness Reveals: What they can't see tells us about the world
  3. Systems Echo: Same forces create different documents across contexts
  4. Irony Emerges: Let perspective create irony naturally
  5. Trust the Reader: They will make connections without hand-holding

Integration

Inbound (feeds into this skill)
SkillWhat it provides
worldbuildingSystems that create documentary voices
memetic-depthCultural texture for document authenticity
prose-styleVoice techniques for different document types
Outbound (this skill enables)
SkillWhat this provides
scene-sequencingChapter openings that prime thematic concerns
story-zoomDifferent abstraction level (document vs. narrative)
Complementary
SkillRelationship
memetic-depthMemetic-depth creates cultural texture; oblique-worldbuilding uses that texture in specific documents. Use together for authentic in-world voices
perspectival-constellationBoth work with limited perspective—perspectival-constellation for POV characters, oblique-worldbuilding for documentary voices

© jwynia, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/creative/fiction/worldbuilding/oblique-worldbuilding of jwynia/agent-skills.

Open the folder on GitHubat commit e02ec7e

Compare with similar skills

Oblique Worldbuilding next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Oblique Worldbuilding compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Oblique Worldbuilding this skilljwynia/agent-skills170—~4kAutomated safety check: PassMIT
Story Multi-Perspective Reviewzenstory-ai/oh-story-claudecode7.4k3 repos~3kAutomated safety check: PassMIT
Short Web Fiction Trend Scanzenstory-ai/oh-story-claudecode7.4k2 repos~1.2kAutomated safety check: PassMIT
InkOS Creative HarnessNarcooo/inkos10k1 repos~1.1kAutomated safety check: PassAGPL-3.0
Novel Arteternityspring/shuohao-skills4.3k—~1.1kAutomated safety check: NotesApache-2.0
SepiaNanako0129/sepia3.1k—~3.6kAutomated safety check: PassMIT

Similar skills

  • Story Multi-Perspective Review

    zenstory-ai/oh-story-claudecode

    Reviews Chinese web-novel text with several reviewer agents in parallel, falling back to a single-agent pass, and reports structure, character, prose and setting problems with fixes.

    7.4k GitHub starsUsed in 3 repos~3k tokens
    Writing & ContentAuto-check passed

  • Short Web Fiction Trend Scan

    zenstory-ai/oh-story-claudecode

    Scans popular short web-fiction rankings on Chinese platforms such as Dianzhong and Heiyan to surface trending emotional hooks, themes and topic candidates with an expiry warning.

    7.4k GitHub starsUsed in 2 repos~1.2k tokens
    Writing & ContentAuto-check passed

  • InkOS Creative Harness

    Narcooo/inkos

    Drives long-form fiction, scripts, storyboards, interactive films and long-document translation through InkOS, with every change made by a typed action.

    10k GitHub starsUsed in 1 repo~1.1k tokens
    Writing & ContentAuto-check passed

  • Novel Art

    eternityspring/shuohao-skills

    给 AI 短剧出美术设定集（场景 + 叙事道具）：场景的设计意图、一致性锚点、光照时段变体、 空景提示词；道具的戏剧功能、状态变体、尺度参照、白底无手提示词。

    4.3k GitHub stars~1.1k tokensUpdated 2 days ago
    Writing & ContentAuto-check: notes

  • Sepia

    Nanako0129/sepia

    Make AI-generated writing read as human-written, in fiction and in professional prose.

    3.1k GitHub stars~3.6k tokensUpdated yesterday
    Writing & ContentAuto-check passed

  • Story Toolbox Router

    zenstory-ai/oh-story-claudecode

    Routes a Chinese web-novel writing request to the matching tool in a 13-skill toolbox, covers author habit memory, and can launch a local dashboard for browsing a project.

    7.4k GitHub stars~1.7k tokensUpdated today
    Writing & ContentAuto-check passed

More from jwynia/agent-skills

All 111 skills in this repo

  • Devcontainer

    jwynia/agent-skills

    Diagnose devcontainer configuration problems and guide development environment setup.

    170 GitHub stars~1.2k tokensUpdated 7 mo ago
    Auto-check: notes

  • Frontend Design

    jwynia/agent-skills

    Create distinctive, production-grade frontend interfaces with high design quality.

    170 GitHub stars~3.2k tokensUpdated 7 mo ago
    Auto-check passed

  • Gitea Workflow

    jwynia/agent-skills

    Orchestrate agile development workflows for Gitea repositories using the tea CLI.

    170 GitHub stars~3.8k tokensUpdated 7 mo ago
    Auto-check passed

  • Godot Asset Generator

    jwynia/agent-skills

    Generate game assets using AI image generation APIs (DALL-E, Replicate, fal.ai) and prepare them for Godot.

    170 GitHub stars~3.8k tokensUpdated 7 mo ago
    Auto-check passed

  • Mastra Hono

    jwynia/agent-skills

    Develop AI agents, tools, and workflows with Mastra v1 Beta and Hono servers.

    170 GitHub stars~2.9k tokensUpdated 7 mo ago
    Auto-check passed

  • PPTX Generator

    jwynia/agent-skills

    Create and manipulate PowerPoint PPTX files programmatically.

    170 GitHub stars~3.1k tokensUpdated 7 mo ago
    Auto-check passed

Categories

Questions about Oblique Worldbuilding

What does Oblique Worldbuilding do?

Create worldbuilding quotes and epigraphs through documentary perspectives. Oblique Worldbuilding is an agent skill from jwynia/agent-skills. Create worldbuilding quotes and epigraphs through documentary perspectives.

When should I use Oblique Worldbuilding?

Oblique Worldbuilding fits situations like: chapter epigraphs; in-world documents; any content where limited perspective creates meaning through what the documenter cannot see.

How do I install Oblique Worldbuilding in Claude Code?

Run `npx skills add jwynia/agent-skills --skill oblique-worldbuilding -a claude-code`. Or copy the skill folder (skills/creative/fiction/worldbuilding/oblique-worldbuilding in jwynia/agent-skills) into .claude/skills/oblique-worldbuilding in your project. Claude Code loads it when a task matches its description.

How do I install Oblique Worldbuilding in Codex?

Run `npx skills add jwynia/agent-skills --skill oblique-worldbuilding -a codex`. Or copy the skill folder (skills/creative/fiction/worldbuilding/oblique-worldbuilding in jwynia/agent-skills) into .agents/skills/oblique-worldbuilding in your project. Codex loads it when a task matches its description.

Can I use Oblique Worldbuilding in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jwynia/agent-skills --skill oblique-worldbuilding -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/oblique-worldbuilding, .gemini/skills/oblique-worldbuilding, .github/skills/oblique-worldbuilding and .opencode/skills/oblique-worldbuilding in your project.

What does Oblique Worldbuilding need to run?

SKILL.md names no scripts, command-line tools or credentials: Oblique Worldbuilding is instructions for the agent only.

Does Oblique Worldbuilding access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Oblique Worldbuilding safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Oblique Worldbuilding use?

Oblique Worldbuilding is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Oblique Worldbuilding use?

About 4k tokens (SKILL.md is roughly 16k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Oblique Worldbuilding?

Skills that share tags, products or a category with Oblique Worldbuilding: Story Multi-Perspective Review (zenstory-ai/oh-story-claudecode, 7.4k stars), Short Web Fiction Trend Scan (zenstory-ai/oh-story-claudecode, 7.4k stars), InkOS Creative Harness (Narcooo/inkos, 10k stars) and Novel Art (eternityspring/shuohao-skills, 4.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Oblique Worldbuilding?

jwynia (a GitHub user) maintains it in jwynia/agent-skills, which has 170 GitHub stars. The repository holds 111 skills in this directory. The repository was last updated on February 24, 2026.

Source: jwynia/agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.