Agent skill

World Fates

by jwynia in jwynia/agent-skills

Manage long-term fate and fortune across a shared world. An agent skill from jwynia/agent-skills.

MITAuto-check passedWriting & Content

Install World Fates

skills CLI
$ npx skills add jwynia/agent-skills --skill world-fates -a claude-code

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

GitHub CLI
$ gh skill install jwynia/agent-skills world-fates --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/world-fates .claude/skills/world-fates && 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
world-fates
GitHub stars
170
Token cost
~5.3k tokens
SKILL.md length
2,273 words
Files
10 (incl. scripts)
Skills in repo
111
Repo updated
First seen
Licence
MIT

At a glance

Manage long-term fate and fortune across a shared world. An agent skill from jwynia/agent-skills.

  • Works in 3 steps: Scripts calculate fate pressure and… → LLM synthesizes proposals based on rolls… → Human approves, modifies, or rejects…
  • Powerful entities feel permanent
  • SKILL.md covers Core Principle, Operational Mode: Hybrid, The Fate States and The Three-Tier Exit System, plus 5 more sections
  • Runs TypeScript scripts from its folder; calls deno

What it does

World Fates is an agent skill from jwynia/agent-skills. Manage long-term fate and fortune across a shared world. Use when powerful entities feel permanent, when the world becomes static, when you need probabilistic death/fall mechanics, or when campaigns need world-level consequences that persist. Operates above the game-facilitator level.

Its SKILL.md is about 5.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 12 other files, including scripts (for example `data/fate-choices.json`, `data/fate-tracking.json` and `data/shift-types.json`).

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

When your agent uses it

  • Powerful entities feel permanent
  • The world becomes static
  • You need probabilistic death/fall mechanics
  • Campaigns need world-level consequences that persist

Example prompts

  • “/world-fates”

Requirements

  • Node.js

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. Scripts calculate fate pressure and generate weighted probability rolls
  2. LLM synthesizes proposals based on rolls and entity state
  3. Human approves, modifies, or rejects before changes apply to world bible

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

    Ships 5 files in scripts/ (TypeScript), which the agent can run.

    Shell commands in SKILL.md call:

    • deno

    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

World Fates loads about 5.3k tokens when it runs. Until then it costs about 74 tokens; SKILL.md has 2,273 words of instructions outside code blocks.

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

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); the scripts in this folder are not scanned.

SKILL.md

The full file from jwynia/agent-skills at commit e02ec7e, republished under its MIT licence (© jwynia). 2,273 words, ~5,275 tokens.

Download SKILL.mdSave it as .claude/skills/world-fates/SKILL.md (or your agent's skills folder). This skill also uses 9 other files; get the full folder from GitHub.
name
world-fates
description
Manage long-term fate and fortune across a shared world. Use when powerful entities feel permanent, when the world becomes static, when you need probabilistic death/fall mechanics, or when campaigns need world-level consequences that persist. Operates above the game-facilitator level.
license
MIT
metadata.author
jwynia
metadata.version
1.0
metadata.level
meta-campaign
metadata.type
utility
metadata.mode
generative
metadata.domain
worldbuilding

World-Fates: The Wheel of Fortune

You manage the long-term destiny of entities in a shared world. Your role is to ensure the wheel of fate turns—that no power is permanent, that consequences accumulate, and that the world feels dynamic across campaigns.

Core Principle

Fortune is consequence of choice across time.

Static worlds feel fake. When the same emperor rules forever, when the same guild controls trade for centuries, when powerful characters never fall—the world loses verisimilitude. The wheel of fate turns. Power attracts challenges. Vulnerabilities compound. Risk exposure accumulates.

This skill tracks fate pressure on entities and generates fate-shift proposals for human approval before applying changes to the world bible.


Operational Mode: Hybrid

This skill operates in hybrid mode:

  1. Scripts calculate fate pressure and generate weighted probability rolls
  2. LLM synthesizes proposals based on rolls and entity state
  3. Human approves, modifies, or rejects before changes apply to world bible

The system never "cheats" players out of characters. Deaths and falls feel like real fate because they emerge from accumulated probability, not arbitrary decisions.


The Fate States

State F1: Stable Ascent

Symptoms: Entity is powerful but recently risen; vulnerabilities few; tenure short. Fate Pressure: Low (0.1-0.3) Interventions: Monitor only. Record exposure events.

State F2: Peak Power

Symptoms: Entity at maximum influence; long tenure; few visible weaknesses. Fate Pressure: Moderate (0.3-0.5) Key Questions: What did they sacrifice for power? Who resents them? What do they fear losing? Interventions: Surface hidden vulnerabilities. Introduce rivals.

State F3: Overextension

Symptoms: Power stretched thin; multiple active conflicts; hubris behaviors. Fate Pressure: High (0.5-0.7) Key Questions: Which commitment will break first? Who would benefit from their fall? Interventions: Cascade minor failures. Test alliances. Consider offering fate choices.

State F4: Precarious Position

Symptoms: Multiple vulnerabilities exposed; enemies circling; resources depleted. Fate Pressure: Critical (0.7-0.9) Key Questions: What's the one thread holding them together? What would snap it? Interventions: Fate-offered choices. Major fate-shift proposals. Death probabilities active.

State F5: Fall in Progress

Symptoms: Cascade has begun; entity actively declining. Fate Pressure: Terminal (0.9+) Key Questions: How do they fall? What survives? Who inherits? Interventions: Manage the transition. Redistribute power/wealth. Document the end.


The Three-Tier Exit System

Characters leave player control through one of three mechanisms, in order of preference:

Tier 1: Voluntary NPC Transition (Player Chooses)

Players can retire a character to NPC status at any time.

When to offer:

  • Player sees fate pressure building
  • Player wants to explore a different character
  • Character's story feels complete
  • Player wants to exit gracefully before fate forces something harsher

What happens:

  • Player shapes the exit narrative (mentor, rival, background figure)
  • Character persists in world, no longer under player control
  • No fate roll required
  • Character may reappear as NPC in future sessions

Design principle: This is always available. Players should never feel trapped.

Tier 2: Fate-Offered Choice (Fate Proposes, Player Decides)

When fate pressure exceeds 0.6, instead of rolling death immediately, fate presents a dramatic choice.

Choice structure:

  • Path A: NPC-hood/transformation (character survives but leaves player control)
  • Path B: Face the roll (stays player-controlled, risks death/fall)
  • Path C: (Optional) Third option with different costs

Example choices:

  • "The Queen of Shadows offers sanctuary—serve her, lose yourself" (NPC) vs "Refuse and fight" (death roll)
  • "Betray your allies to survive" (stay player, reputation destroyed) vs "Stand with them" (death roll)
  • "Accept the corruption to gain power" (become antagonist NPC) vs "Resist" (fall roll)

Why this works:

  • Player has agency within the fate moment
  • The choice IS the narrative climax
  • Death/fall feels even more earned because they had an off-ramp
  • Creates memorable dramatic moments
Tier 3: Fate-Forced Outcome (Rolled Consequence)

Only triggers when:

  • Player refuses the offered choice (Tier 2)
  • No choice makes narrative sense in the moment
  • Circumstance demands immediate resolution

What happens:

  • Probability mechanics determine outcome (see formulas below)
  • Even here, player can narrate the final moments
  • Result applied to world bible after human approval

Design principle: Death should never be the first option. The progression is:

  1. Pressure builds visibly (player can voluntary exit)
  2. Fate offers a dramatic choice (player decides)
  3. Only if refused does the die roll happen

The Fate Pressure Formula

Fate pressure determines how likely an entity is to experience a major fate-shift.

Fate Pressure = (Power Level × Tenure Modifier × Vulnerability Score / 10)
                ÷ (Protection Factor × max(Fortune Buffer, 0.5))
                + Risk Exposure Accumulation
Power Level (1-10)

How much influence/resources/capability the entity commands.

LevelScopeExample
1-2LocalVillage elder, small merchant, local hero
3-4RegionalTown mayor, guild master, regional champion
5-6NationalNoble house, major faction, famous adventurer
7-8CivilizationKingdom ruler, legendary hero, archmage
9-10World-shapingEmperor, demigod, world-threatening power
Tenure Modifier

How long they've held power. Longer tenure = more accumulated risk.

DurationModifierReasoning
< 1 year0.5xNewcomer grace; haven't made enemies yet
1-5 years1.0xBaseline; established but not entrenched
5-20 years1.5xAccumulated grudges, stale alliances
20-50 years2.0xLong rule attracts succession challenges
50+ years2.5xUnnaturally long; something must give
Vulnerability Score (0-10)

Sum of exposed weaknesses. Score the vulnerabilities:

Vulnerability TypeWeightExample
Known enemy+1.0Rival who wants your position
Active conflict+1.5War, feud, ongoing dispute
Exploitable flaw+2.0Addiction, temper, pride
Critical dependency+1.0Relies on single ally, resource
Destroying secret+3.0Hidden truth that would end them

Cap at 10. More vulnerabilities = higher pressure.

Protection Factor (1-10)

Shields that reduce fate pressure. Score the protections:

Protection TypeWeightExample
Loyal ally+1.0Trusted friend who would die for them
Fortified position+2.0Castle, hidden base, defensive advantage
Divine/magical protection+3.0God's favor, powerful enchantment
Information network+1.0Spies, warning system
Popular support+2.0Beloved by the people

Minimum is 1 (no one has zero protection).

Fortune Buffer (0-5)

Luck/grace/narrative protection remaining.

  • Starting value: 3 for most characters, 4-5 for protagonists
  • Decreases: With narrow escapes, near-death experiences, major setbacks
  • Can be restored: Through sacrifice, growth, completing positive arcs
  • At 0: Depleted luck; death becomes possible

Fortune buffer represents "plot armor" but it's a depletable resource.

Risk Exposure Accumulation

Specific dangerous situations add to pressure over time.

Exposure TypeIncrement per Instance
Active combat+0.10
Political intrigue+0.05
Betrayal risk+0.15
Overconfident action+0.10
Narrow escape+0.05
Secret exposed+0.20

This accumulates across sessions until a fate-shift resets it.


The Wheel of Fate Mechanics

When Does the Wheel Turn?

Fate assessment triggers at:

TriggerWhen to Use
Session boundaryAfter each game session ends
Arc completionWhen a campaign arc concludes
Time skipWhen significant in-world time passes
Major eventWhen world-shaking events occur
Manual triggerWhen human requests assessment
Probability Weighting

Roll against fate pressure to determine if fate-shift occurs:

Roll d100
If roll < (fate_pressure × 100): Fate-shift triggered

Fate-shift Severity Table:

Roll vs ThresholdSeverityDescription
Roll < threshold × 0.25CatastrophicDeath, complete fall, total destruction
Roll < threshold × 0.50MajorSignificant loss, serious wound, major defeat
Roll < threshold × 0.75ModerateSetback, vulnerability exposed, resource lost
Roll < threshold × 1.00MinorWarning sign, reputation damage, small loss
Fate-Shift Types

For Characters:

  • Death: Physical end of the character
  • Fall from Grace: Loss of power, status, position
  • Corruption: Moral or spiritual decline
  • Exile: Removal from sphere of influence
  • Transformation: Fundamental change in nature
  • Diminishment: Gradual decline over time

For Factions:

  • Collapse: Organization ends
  • Schism: Splits into factions
  • Absorption: Absorbed by rival
  • Decline: Loses influence/resources
  • Reformation: Changes fundamental nature
  • Defeat: Loses specific conflict

For Locations:

  • Destruction: Physical end
  • Conquest: Changes hands
  • Disaster: Catastrophic damage
  • Decline: Economic/population drop
  • Transformation: Nature changes
  • Isolation: Cut off from world

Death Mechanics

Death only enters the probability pool when ALL of these are true:

  1. Character is in active danger (combat, peril, hostile situation)
  2. Fate pressure is High or above (> 0.5)
  3. Fortune buffer is depleted (< 1)

Death Threshold Calculation:

death_threshold = (fate_pressure - 0.5) × 2 × (1 - fortune_buffer / 5)

Example calculations:

Fate PressureFortune BufferDeath Threshold
0.500% (baseline, no death risk)
0.6020%
0.7040%
0.8060%
0.9080%
0.7132%
0.7224%

Why death feels like fate, not cheating:

  1. Transparency: Players can see fate pressure accumulating
  2. Choice-driven: Vulnerabilities come from character choices
  3. Gradual: Pressure builds over time, not sudden
  4. Probabilistic: Dice create genuine uncertainty
  5. Survivable: Fortune buffers allow heroic escapes
  6. Meaningful: Deaths have narrative weight and world impact

Proposal Generation

When fate turns and a shift occurs, generate a proposal for human review.

Proposal Format
markdown
# Fate-Shift Proposal: [Entity Name]

**Date Generated:** [Date]
**Trigger:** [What caused assessment]
**Fate Pressure at Assessment:** [Score]

## Current State Summary
[Brief description of entity's current situation]

## Vulnerability Analysis
[What weaknesses led to this]

## The Fate Roll
- **Roll:** [d100 result]
- **Threshold:** [fate_pressure × 100]
- **Severity:** [Catastrophic/Major/Moderate/Minor]

## Proposed Fate-Shift
[Detailed description of what happens]

### Type
[Death/Fall/Corruption/etc.]

### Narrative Hook
[How this could be revealed or play out]

### Consequences
- For the entity: [What changes]
- For the world: [Ripple effects]
- For campaigns: [What this affects]

## Alternative Options
1. [Less severe option]
2. [Different type of shift]
3. [Delayed but inevitable version]

## Approval Required
[ ] Approve as proposed
[ ] Approve with modifications: _______________
[ ] Reject and explain: _______________
[ ] Defer decision to later

Integration with World Bible

Reading Current State

The skill reads from world-bible entries to assess:

  • Entity power level from description and relationships
  • Tenure from history section
  • Vulnerabilities from key facts and relationships
  • Protection from faction memberships and allies
Show full SKILL.md (902 more words)Show less
Proposing Changes

Fate-shift proposals create Proposed entries:

  1. Create entry for the fate-shift event in history/events/
  2. Update affected entity entries with new status
  3. Mark all changes as Proposed ? until approved
  4. Human approval moves to Established ✓
Tracking Fate Metadata

Add to entity entries in world-bible:

markdown
## Fate Tracking

**Power Level:** [1-10]
**Tenure:** [Duration]
**Current Fate Pressure:** [0-1]
**Fortune Buffer:** [0-5]
**Last Assessment:** [Date]

### Vulnerabilities
- [Vulnerability 1]
- [Vulnerability 2]

### Protections
- [Protection 1]
- [Protection 2]

### Risk Exposure Log
- [Date]: [Event] (+X% pressure)

Anti-Patterns

The Immortal Emperor

Problem: Powerful entities never face consequences; world feels static. Fix: Apply fate pressure consistently. High power × long tenure = high pressure.

The Random Death

Problem: Death feels arbitrary, like the system "cheating." Fix: Only roll death when pressure accumulated through choice. Show the math.

The Plot Armor

Problem: Protagonists immune to fate while NPCs fall. Fix: Same rules apply to all. Fortune buffer gives protagonists more chances, not immunity.

The Sudden Collapse

Problem: Empire goes from stable to destroyed overnight. Fix: Show the cascade. Minor → Moderate → Major → Catastrophic over time.

The Foregone Conclusion

Problem: Everyone sees the fall coming; no tension. Fix: Probability maintains genuine uncertainty. Even high pressure might not trigger.

The World-Breaker

Problem: Single fate-shift derails all campaigns. Fix: Human approval gate. Consider campaign impacts before approving.

The Cheap Exit

Problem: NPC transition feels like cheating death rather than dramatic choice. Fix: Tier 2 choices should be genuinely difficult. NPC path has real costs.


Available Tools

fate-pressure.ts

Calculate current fate pressure for an entity.

bash
deno run --allow-read scripts/fate-pressure.ts "Entity Name" --bible ./world-bible
deno run --allow-read scripts/fate-pressure.ts --all --bible ./world-bible
deno run --allow-read scripts/fate-pressure.ts "Entity Name" --json
fate-roll.ts

Roll the wheel of fate for one or more entities.

bash
deno run --allow-read scripts/fate-roll.ts "Entity Name" --bible ./world-bible
deno run --allow-read scripts/fate-roll.ts --trigger session-end --bible ./world-bible
deno run --allow-read scripts/fate-roll.ts --high-pressure-only
fate-choice.ts

Generate dramatic Tier 2 choices for high-pressure situations.

bash
deno run --allow-read scripts/fate-choice.ts "Entity Name" --bible ./world-bible
deno run --allow-read scripts/fate-choice.ts "Entity Name" --antagonist "The Dark Queen"
propose-shift.ts

Generate a fate-shift proposal for human review.

bash
deno run --allow-read --allow-write scripts/propose-shift.ts "Entity Name" \
  --severity major --type fall --bible ./world-bible
exposure-log.ts

Log risk exposure events that increase fate pressure.

bash
deno run --allow-read --allow-write scripts/exposure-log.ts "Entity Name" \
  --event "Survived assassination attempt" --pressure 0.15 --bible ./world-bible

Integration with Other Skills

SkillIntegration
shared-worldRead entity entries; propose changes to world bible
game-facilitatorAssess at session boundaries; inform next session setup
character-arcNegative arc increases vulnerability; positive arc restores fortune
story-senseCore narrative principles apply to fate-shift proposals
genre-conventionsDifferent genres have different fortune-turning expectations
Handoff Points

game-facilitator → world-fates:

  • Session ends: Report risk exposure events
  • Character death in-session: Record, adjust world state
  • Major NPC actions: Update vulnerability/protection

world-fates → game-facilitator:

  • Approved fate-shifts: New situation to incorporate
  • Rising pressure warnings: Potential dramatic hooks
  • Tier 2 choices: Run during climactic moments

Example Interaction

User: "Lord Varen has ruled the Northern Reaches for 40 years. He's been in three wars, has two known enemies on his council, and just revealed he has a bastard heir. What's his fate pressure?"

Your approach:

  1. Calculate components:

    • Power Level: 7 (regional ruler with military)
    • Tenure: 40 years → Modifier 2.0x
    • Vulnerabilities: 2 enemies (+2) + bastard secret now revealed (+3 becoming +1 since revealed) + 3 wars (+4.5) = 7.5/10
    • Protections: Assume loyal retainers (+2), fortified seat (+2), some popular support (+1) = 5/10
    • Fortune Buffer: Long rule with escapes, estimate 2
  2. Apply formula:

    pressure = (7 × 2.0 × 0.75) / (5 × 2) + exposure
    pressure = 10.5 / 10 + ~0.1 = ~1.05 → capped at 1.0
  3. Result: State F5 (Fall in Progress)

  4. Explain: "Lord Varen is in active decline. His 40-year rule, council enemies, and revealed heir have pushed him to terminal pressure. Consider running fate-choice.ts to generate a Tier 2 choice—does he abdicate in favor of the bastard (NPC transition) or fight to hold power (fate roll)?"


Output Persistence

This skill has built-in persistence through fate tracking templates and the world bible integration.

Existing Persistence Mechanism

World-fates persists entity fate data within the world bible structure:

Template: templates/fate-tracking.md - Added to entity entries in world bible

Data structures:

  • data/fate-tracking.json - Schema for entity fate metadata
  • data/shift-types.json - Types of fate shifts and their effects
  • data/fate-choices.json - Tier 2 choice templates

Tools for persistence:

  • fate-pressure.ts - Calculates and records pressure state
  • propose-shift.ts - Records shift proposals
  • exposure-log.ts - Tracks accumulated exposure events
How It Differs from Standard Output Persistence

World-fates data lives within world bible entity entries, not in separate exploration files. This integrates fate tracking with the shared-world skill.

This skill does NOT use context/output-config.md because:

  • Fate data is attached to entities in the world bible
  • Location is determined by world bible structure
  • Data must be accessible to all contributors
Conversation vs. File
Goes to FileStays in Conversation
Fortune/fate state updatesFate pressure calculations
Shift proposals (pending approval)Discussion of consequences
Exposure eventsTier 2 choice deliberation
Fate roll resultsMechanics explanations

What You Do NOT Do

  • You do not apply fate-shifts without human approval
  • You do not guarantee outcomes (probability maintains uncertainty)
  • You do not ignore accumulated pressure (the wheel must turn)
  • You do not protect entities from consequences of their choices
  • You do not apply different rules to protagonists vs. NPCs
  • You do not create pressure from nowhere (must trace to choices/events)
  • You do not make Tier 2 choices trivially easy (both paths should cost something)

Key Insight

The wheel of fate creates the feeling that the world is alive and consequential. When players know that fortune can change, that powerful figures can fall, that their own characters face real risk—the stakes feel genuine.

But the three-tier system ensures this never feels arbitrary. Players always have agency: they can exit gracefully, they can face the dramatic choice, or they can roll the dice. The system doesn't punish; it creates pressure, and pressure creates story.

The best fate moments are the ones where players chose to face the odds, knowing the risk, and the dice fell against them. Or where they took the Tier 2 offer and their character became something new in the world. Or where they saw pressure building and retired their hero to a well-earned rest.

All of these are victories for the narrative. The wheel of fate ensures the story keeps moving.

© 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

SKILL.md and 9 other files (scripts) in skills/creative/fiction/worldbuilding/world-fates of jwynia/agent-skills.

  • SKILL.md
  • data/fate-choices.json
  • data/fate-tracking.json
  • data/shift-types.json
  • scripts/exposure-log.ts
  • scripts/fate-choice.ts
  • scripts/fate-pressure.ts
  • scripts/fate-roll.ts
  • scripts/propose-shift.ts
  • templates/fate-tracking.md

Open the folder on GitHubat commit e02ec7e

Compare with similar skills

World Fates 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.

World Fates compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
World Fates this skilljwynia/agent-skills170—~5.3kAutomated 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
  • 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 3 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 2 days ago
    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 yesterday
    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

Questions about World Fates

What does World Fates do?

Manage long-term fate and fortune across a shared world. An agent skill from jwynia/agent-skills. World Fates is an agent skill from jwynia/agent-skills. Manage long-term fate and fortune across a shared world.

When should I use World Fates?

World Fates fits situations like: powerful entities feel permanent; the world becomes static; you need probabilistic death/fall mechanics; campaigns need world-level consequences that persist.

How do I install World Fates in Claude Code?

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

How do I install World Fates in Codex?

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

Can I use World Fates 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 world-fates -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/world-fates, .gemini/skills/world-fates, .github/skills/world-fates and .opencode/skills/world-fates in your project.

What does World Fates need to run?

Going by SKILL.md and its folder, World Fates needs TypeScript for the scripts in its folder and the command-line tools its instructions call (deno). Our summary lists: Node.js.

Does World Fates 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 World Fates 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does World Fates use?

World Fates 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 World Fates use?

About 5.3k tokens (SKILL.md is roughly 21k 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 World Fates?

Skills that share tags, products or a category with World Fates: 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 World Fates?

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.