worldbuilding

jwynia/agent-skills · updated Apr 12, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/jwynia/agent-skills --skill worldbuilding
0 commentsdiscussion
summary

Diagnose world-level problems in fictional settings. Identify what's missing or unconvincing and recommend specific interventions.

skill.md

Worldbuilding: Diagnostic Skill

Diagnose world-level problems in fictional settings. Identify what's missing or unconvincing and recommend specific interventions.

When to Use This Skill

Use this skill when:

  • Setting feels like a painted backdrop
  • Technology/magic hasn't transformed society
  • Institutions feel designed rather than evolved
  • Economy doesn't make sense
  • Cultures lack depth

Do NOT use this skill when:

  • Story problems are character-focused (use character-arc)
  • Plot structure issues (use scene-sequencing)
  • Need to generate worlds from scratch (use systemic-worldbuilding)

Core Principle

Worlds fail when they feel designed rather than evolved.

Good worldbuilding creates the perception that the setting has history, internal logic, and processes that operate independently of the plot.

The World States

W1: Backdrop World

Symptoms: Setting exists but has no independent logic Interventions: systemic-worldbuilding (trace consequences)

W2: World Without Consequences

Symptoms: Technology/magic exists but hasn't transformed society Interventions: Consequence Cascade Analysis

W3: Institutions Without History

Symptoms: Organizations feel designed last week Interventions: Organic Institutional Design

W4: Economy Doesn't Make Sense

Symptoms: Trade exists without supply chains; prices arbitrary Interventions: economic-systems

W5: Belief Systems Are Shallow

Symptoms: Religion is flavor without theological depth Interventions: belief-systems

W6: Culture Without Depth

Symptoms: Traditions feel random; surface-level aesthetic Interventions: memetic-depth

W7: Flat Non-Humans

Symptoms: Aliens/species are humans in costume Interventions: conlang, alien-sensory frameworks

W7.5: Language Feels Generic

Symptoms: Names sound like English; no linguistic texture Interventions: conlang, language-evolution

Consequence Cascade

Apply to any major speculative element:

Initial Element
├── 1st Order: Direct practical effects
│   ├── Who gains immediate advantage?
│   ├── What becomes obsolete?
│   └── Technical limitations?
├── 2nd Order: Systemic adaptations
│   ├── How do economic structures adapt?
│   ├── How do power structures respond?
│   └── What resistance movements arise?
└── 3rd Order: Cultural evolution
    ├── What new language emerges?
    ├── What ethical questions arise?
    └── What becomes normalized?

Key Diagnostic Questions

For Technology/Magic

  • What's your initial divergence from our world?
  • Who gains power? What becomes obsolete?
  • How would the powerful try to control this?

For Institutions

  • When was this organization founded?
  • What crises has it survived?
  • What are its internal contradictions?

For Economics

  • What's the fundamental scarcity?
  • How is value determined?
  • What's the underground economy?

For Belief Systems

  • What explains existence?
  • How do beliefs affect daily decisions?
  • What are the schisms and debates?

Common Anti-Patterns

The Monoculture

One unified culture for entire planets/species. Fix: Add regional variation, class differences, schisms.

The Convenient Technology

Technology exists when plot needs it. Fix: Trace consequence cascade.

The Static History

World unchanged for centuries. Fix: Add recent disruptions, reforms in progress.

The Evil Empire

Antagonist nation uniformly evil. Fix: Add internal debates, ordinary people.

The Rubber Forehead Alien

Non-humans with minor cosmetic differences. Fix: Start with biology, trace to cognition, trace to culture.

Depth vs Breadth

Go Deep When:

  • Element is central to plot
  • Element will be examined closely
  • Element creates ongoing conflict

Stay Shallow When:

  • Element is background detail
  • POV character wouldn't know depth
  • Mystery is more interesting

Related Skills

  • systemic-worldbuilding - Build worlds from initial divergence
  • belief-systems - Deep theological design
  • economic-systems - Economic logic
  • governance-systems - Political structures
  • conlang - Language design
  • settlement-design - Cities and geography
how to use worldbuilding

How to use worldbuilding on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add worldbuilding
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/jwynia/agent-skills --skill worldbuilding

The skills CLI fetches worldbuilding from GitHub repository jwynia/agent-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/worldbuilding

Reload or restart Cursor to activate worldbuilding. Access the skill through slash commands (e.g., /worldbuilding) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

Task Automation & Efficiency

Automate repetitive workflows and reduce manual effort

Example

Generate reports, summarize documents, draft communications

Save 3-5 hours per week on routine tasks

Knowledge Enhancement

Learn new skills, understand complex topics, get expert guidance

Example

Explain concepts, provide examples, suggest learning resources

Accelerate learning and skill development by 2x

Quality Improvement

Enhance output quality through reviews, suggestions, and refinements

Example

Review drafts, suggest improvements, catch errors

Improve work quality by 30-40% with less effort

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client with skill support
  • Clear understanding of task or problem to solve
  • Willingness to iterate and refine outputs

Time Estimate

15-45 minutes depending on use case complexity

Installation Steps

  1. 1.Install skill using provided installation command
  2. 2.Test with simple use case relevant to your work
  3. 3.Evaluate output quality and relevance
  4. 4.Iterate on prompts to improve results
  5. 5.Integrate into regular workflow if valuable

Common Pitfalls

  • Expecting perfect results without iteration
  • Not providing enough context in prompts
  • Using skill for tasks outside its intended scope
  • Accepting outputs without review and validation

Best Practices

✓ Do

  • +Start with clear, specific prompts
  • +Provide relevant context and constraints
  • +Review and refine all outputs before using
  • +Iterate to improve output quality
  • +Document successful prompt patterns

✗ Don't

  • Don't use without understanding skill limitations
  • Don't skip validation of outputs
  • Don't share sensitive information in prompts
  • Don't expect skill to replace human judgment

💡 Pro Tips

  • Be specific about desired format and style
  • Ask for multiple options to choose from
  • Request explanations to understand reasoning
  • Combine AI efficiency with human expertise

When to Use This

✓ Use When

Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.

✗ Avoid When

Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.

Learning Path

  1. 1Familiarize yourself with skill capabilities and limitations
  2. 2Start with low-risk, non-critical tasks
  3. 3Progress to more complex and valuable use cases
  4. 4Build expertise through regular use and experimentation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.542 reviews
  • Arya Gupta· Dec 24, 2024

    I recommend worldbuilding for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Valentina Abbas· Dec 4, 2024

    We added worldbuilding from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Rahul Santra· Nov 15, 2024

    We added worldbuilding from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Harper Kim· Nov 15, 2024

    worldbuilding reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Pratham Ware· Oct 6, 2024

    worldbuilding fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Mateo Perez· Oct 6, 2024

    Registry listing for worldbuilding matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Noah Thompson· Sep 25, 2024

    Solid pick for teams standardizing on skills: worldbuilding is focused, and the summary matches what you get after install.

  • Aisha Kim· Sep 17, 2024

    Registry listing for worldbuilding matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Aisha Kapoor· Sep 13, 2024

    Keeps context tight: worldbuilding is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Yash Thakker· Sep 1, 2024

    Registry listing for worldbuilding matched our evaluation — installs cleanly and behaves as described in the markdown.

showing 1-10 of 42

1 / 5