Infinite Game OS

Definition

Skill Creator builds new skills with a five-phase process. Phase 1 is the interview: five required questions the operator must answer before any drafting begins (one-sentence purpose, trigger conditions, inputs and outputs, governance constraints, related references). Phase 2 researches existing patterns and conventions. Phase 3 writes the complete SKILL.md to the canonical location with required sections (purpose and trigger, when to use, steps or behavior, constraints, refinements). Phase 4 proposes the install path for the operator's platform. Phase 5 proposes registry updates. The skill never auto-creates junctions or symlinks. Always proposes first.

The five-phase build

Phase 1 is the interview, required before any writing begins. Five questions: what does this skill do in one sentence, when should it activate, what are the inputs and outputs, are there governance constraints, are there existing protocols or tools to reference. Phase 2 researches existing patterns. Phase 3 writes SKILL.md with required sections (purpose and trigger, when to use, steps or behavior, constraints, refinements as empty placeholder).

Phase 4 proposes the install path for the operator's platform (PowerShell junction on Windows, ln -s on Unix). Phase 5 proposes registry updates (CLAUDE.md or AGENTS.md, local skills index). The skill never auto-creates junctions or registers anything. Always proposes first. The operator approves at each gate. An external-system check applies to skills that touch APIs, git remotes, web services or any external surface.

Use Cases

Building a recurring workflow as a callable skill

The operator notices they walk through the same workflow every week. Skill Creator interviews them, researches existing patterns, drafts a SKILL.md and proposes the install path. The workflow becomes invocable by name; the operator stops re-explaining it each session.

Wrapping a new tool or API as an interface

A new external tool enters the operator's stack. Skill Creator builds an interface skill: when to use, what inputs, what governance gates, what to do at the external-system check. The tool becomes legible to the operator's existing workflow rather than a separate context.

Codifying a discovered pattern after it earns its keep

A pattern proved itself across multiple sessions. The operator decides to codify it. Skill Creator runs the interview to surface the load-bearing constraints, drafts the SKILL.md and proposes the registry entry. The pattern becomes permanent infrastructure.

FAQ

Why a five-question interview before writing?

Skipping the interview produces generic templates, not system-native skills. The five questions force clarity on purpose, trigger, inputs/outputs, governance and references before any words land. A skill that survives is one whose load-bearing constraints were explicit at creation.

What is the external-system check?

Before finalizing any SKILL.md that interacts with external systems (APIs, git remotes, web, messaging, calendar tools, image generation, browser automation, MCP tools), the skill prompts for explicit notes about what data flows out and what authorization is required. This protects the operator's external surface area.

Does it auto-install the skill it builds?

No. Phases 4 and 5 propose the install path and the registry update. Both wait for explicit approval. Auto-install would route around governance; the proposal-then-approval pattern preserves operator control over what becomes permanent.