Profession · operations
Skill Creator
Skill Creator — a hireable role that turns an existing backend (an API, a CLI, an MCP surface) into a skill agents can actually reach. Bootstraps its own authoring toolkit before it works, gates hard on whether the thing is worth wrapping at all, decides Path-1 vs guidance-only before any file is written, authors the seven layers against researched evidence, then drives the house's WHOLE release chain — one surface at Di-Atomic, eight at OPVS, four plus a scaffold at SpiderIQ — and proves each one shipped by fetching the published artifact rather than trusting a green build. The CREATE half of how we ship; the LAUNCH half is @di-atomic/propaganda. Internal tooling for Di-Atomic, SpiderIQ, and OPVS. 9 links, 8 workflows, and the skill-creator guild.
skill-creator is the Skill Creator role — the productization of the discipline behind 35 published Di-Atomic packages, built to run from Claude Code, Cursor, Antigravity, or Windsurf. It exists because wrapping a backend is a job, not a checklist: it has a method (intake, plan, build, verify, publish, prove), a judgment layer (is this worth wrapping at all, does it actually DO something, and which surfaces does THIS house have?), and a craft that compounds at skill-creator@profession.md. Its defining constraint is that the three houses share the method and differ only in the release map — so there is one publish workflow and three recipes, and adding a fourth house means dropping in a fourth config rather than forking a directory. Its second constraint is that publish is not the finish line: both house runbooks name the same dominant failure, shipped code is not shipped function, so every surface must be proven by a fetched artifact you have grepped. This is internal tooling for the three houses we own; the sibling that launches what it produces is @di-atomic/propaganda. Same standard, opposite half of the lifecycle.
What this profession guarantees
Bootstraps its own toolkit
An IDE session starts empty. Workflow one acquires the tools, proves both halves work, and resolves which release map you are under.
Declines before it builds
Scores the candidate first. A weak score earns an honest call-the-MCP-tool-directly, and saying so is the job.
Shape is decided once
Does it DO something, or is it methodology? That verdict picks the bundle shape and is not patchable after the fact.
One method, three release maps
Di-Atomic publishes one surface, OPVS eight, SpiderIQ four plus a scaffold. Same workflow, a per-house config.
Proves it shipped
Fetches every published artifact and greps it. A green build, a 200, and a local file that says beta are each worth nothing.
The craft it carries
Where it operates
Package
- Registry id
- @di-atomic/skill-creator
- Version
- 0.1.3
- Published by
- Di-Atomic