sapiom-js: Skill for Claude Code

Establishing authoring clarity

Overview

Before you author a Sapiom template or agent, establish what you're building from. Same rule as its sibling intake, establishing-studio-design-clarity: search first; then — only if you can't find it — ask before you build. Never ask before searching; never invent the product in a vacuum.

The authoring-specific trap: a published template is judged by the person deciding whether to use it (examples/AUTHORING.md) — so the outcome, the target user, and the copy are the substance, and the copy is "most of the work." Writing the index.ts before those are clear produces a runnable agent nobody can evaluate, with placeholder copy you'll rewrite. This skill is deliberately thin — it does not re-teach the SDK; it encodes where the authoring sources live, the classification, the ask-default, and the dispatch.

The intake — run it before you author

1. Classify the work:

2. Find what you're building from — search before you ask, in order, stop when you have it:

• The ask itself — the ticket/issue for a spec, or a named reference agent to model.
• Sibling templates — examples/ almost always has one that solved a similar job. AUTHORING.md: "look at an existing one — examples/hello-agent is the smallest — and copy its shape." Match a sibling's defineAgent/defineStep graph and template.json shape rather than inventing structure.
• The authoring guide — examples/AUTHORING.md: the manifest fields, the "runnable with nothing" bar (§1a — {} in, a real run out), categorization (category / discipline / cadence / complexity / step kind), and the voice/copy rules.
• The gate — pnpm examples:check (house-style limits; run it, don't guess them).