worldos-authoringlisted

Create, remix, inspect, validate, update, or explicitly publish an owned WorldOS Simulation through the WorldOS MCP. Use when a user wants to design a new world, select and configure WorldOS apps, author characters and opening state, remix an existing world, edit an owned draft, upload its cover, or publish it after review without using a code repository or database access.
Story-Engine-Inc/worldos-agent-skills · ★ 0 · API & Backend · score 72

Install: claude install-skill Story-Engine-Inc/worldos-agent-skills

# WorldOS Authoring Build a playable WorldOS Simulation through the public WorldOS MCP. Use only MCP capabilities exposed to the authorized account. Do not use Supabase, SQL, private APIs, platform source code, or repository-specific scripts as a fallback. ## Start with the live contract 1. Call `get_authoring_guide` before designing or editing a draft. 2. Treat the live guide, current tool schemas, and validation results as authoritative when they differ from this skill. 3. If the WorldOS MCP is unavailable or unauthorized, stop and explain how to connect or reauthorize it. Never request an access token in chat. Read the supporting material that matches the task: - For gameplay and content design, read [references/world-design.md](references/world-design.md). - For deciding which app owns each persistent fact, read [references/state-ownership.md](references/state-ownership.md). - For locale overlays and template variables, read [references/i18n-and-templates.md](references/i18n-and-templates.md). - Before any write, read [references/acceptance-checklist.md](references/acceptance-checklist.md). ## Respect write intent Read-only requests such as “review,” “audit,” “explain,” or “show me a proposal” do not authorize creation or updates. Stop after research, a candidate draft, or validation. Call a write tool only when the user clearly asks to create, import, remix, modify, upload to, or publish a WorldOS resource. Publishing is never implied by creation or editing. Call