Diagnose world-level problems in fictional settings. Identify what's missing or unconvincing and recommend specific interventions.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionworldbuildingExecute the skills CLI command in your project's root directory to begin installation:
Fetches worldbuilding from jwynia/agent-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate worldbuilding. Access via /worldbuilding in your agent's command palette.
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 environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
2
total installs
2
this week
46
GitHub stars
0
upvotes
Run in your terminal
2
installs
2
this week
46
stars
Diagnose world-level problems in fictional settings. Identify what's missing or unconvincing and recommend specific interventions.
Use this skill when:
Do NOT use this skill when:
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.
Symptoms: Setting exists but has no independent logic Interventions: systemic-worldbuilding (trace consequences)
Symptoms: Technology/magic exists but hasn't transformed society Interventions: Consequence Cascade Analysis
Symptoms: Organizations feel designed last week Interventions: Organic Institutional Design
Symptoms: Trade exists without supply chains; prices arbitrary Interventions: economic-systems
Symptoms: Religion is flavor without theological depth Interventions: belief-systems
Symptoms: Traditions feel random; surface-level aesthetic Interventions: memetic-depth
Symptoms: Aliens/species are humans in costume Interventions: conlang, alien-sensory frameworks
Symptoms: Names sound like English; no linguistic texture Interventions: conlang, language-evolution
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?
One unified culture for entire planets/species. Fix: Add regional variation, class differences, schisms.
Technology exists when plot needs it. Fix: Trace consequence cascade.
World unchanged for centuries. Fix: Add recent disruptions, reforms in progress.
Antagonist nation uniformly evil. Fix: Add internal debates, ordinary people.
Non-humans with minor cosmetic differences. Fix: Start with biology, trace to cognition, trace to culture.
Go Deep When:
Stay Shallow When:
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ 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.
jwynia/agent-skills
anthropics/claude-code
mblode/agent-skills
github/awesome-copilot
sickn33/antigravity-awesome-skills
leonxlnx/taste-skill
I recommend worldbuilding for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
We added worldbuilding from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
We added worldbuilding from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
worldbuilding reduced setup friction for our internal harness; good balance of opinion and flexibility.
worldbuilding fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Registry listing for worldbuilding matched our evaluation — installs cleanly and behaves as described in the markdown.
Solid pick for teams standardizing on skills: worldbuilding is focused, and the summary matches what you get after install.
Registry listing for worldbuilding matched our evaluation — installs cleanly and behaves as described in the markdown.
Keeps context tight: worldbuilding is the kind of skill you can hand to a new teammate without a long onboarding doc.
Registry listing for worldbuilding matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 42