skill-creatorlisted

# Skill Creator Author Claude Code skills that work in someone else's environment. A skill encodes a workflow; the tools that workflow runs on differ from machine to machine. This skill covers the mechanics of separating the two. The full architecture spec is `docs/plugin-architecture.md`, at the root of the skills repository this skill ships in. Read it before authoring anything non-trivial. If you installed this skill on its own and do not have that repository, carry on — what follows is self-contained, and the spec supplies rationale, worked migrations, and the full capability catalog rather than any step you are missing. ## When to Use - Creating a new skill from scratch - Adapting an existing skill so it stops depending on one person's tools and paths - Auditing a skill for conformance before publishing or sharing it ## The Core Idea Skills declare *what* they need from the environment. Separate configuration files declare *how* it is provided. The model reads both and resolves the binding by understanding — there is no template engine and no runtime. A workflow step coupled to one vendor's tooling: ```markdown before When CI fails, notify the user with the Telegram MCP notify tool. ``` becomes: ```markdown after When CI fails, use the messaging capability to send an informational notification. If no binding is configured, print the status to the terminal. ``` The workflow did not change. A tool-specific reference became a semantic one, and the fallback made t