Progress0/0
Phase 1

## Set up the canvas

Open `canvas/MR-CANVAS-v0.8.html` in a browser.

Drop everything in `features/` onto the canvas.

Phase 2

## Load the tour

Identities → IMPORT → paste `identity/identity-tour-author.json`.

Drop the three tone stylesheets and `xsl-skill-doc.xml` from `stylesheets/`.

Drop `stream/stream-skill-author.xml` and all six `chunk-skill-*.xml` files.

Open Streams. Confirm "skill-author — 6 chunks · all verified ✓".

Phase 3

## Author the skill (chunks 1-3)

Read chunk 1 in your preferred tone. The annotated tone covers the commercial case for cryptographic skill provenance.

Read chunk 2. Drop `examples/skill-example.xml` onto the canvas.

show detail ▾

Default content: a `regulated-document-author` skill teaching Claude Code to author SOX controls, FDA records, IRB protocols. The choice of example is deliberate — skill provenance matters most where outputs face regulatory scrutiny.

Customize via text editor + re-paste to build your own skill. The same XML shape works for any skill domain.

Read chunk 3. Tree → click the skill source → pick reader `xsl:skill-doc`.

show detail ▾

The skill renders as styled documentation with: a header (name + activation description), when-to-use guidance in a highlighted block, numbered instructions, examples, and at the bottom a code block containing the raw SKILL.md ready to copy into Claude Code.

Phase 4

## Sign as author (chunk 4)

Read chunk 4. Identities → CREATE the skill-author identity (e.g. your name + organization).

Sign tab → pick the skill source → SIGN.

show detail ▾

The skill source gains a `<signature>` child with your ECDSA-P256 signature and embedded public key. Anyone with the skill can verify it was authored by you without contacting you.

For multi-author review: a second identity can sign the same skill source (counter-signature), without invalidating the first signature. Same multi-party attestation pattern as the compliance-audit-trail stream.

Phase 5

## Bundle + install (chunks 5-6)

Read chunk 5. Bundle tab → EXPORT BUNDLE HTML.

show detail ▾

One HTML file (~90 KB) containing the canvas, all features, your signed skill, the stylesheet, the public keys for verification. Distribution-channel-agnostic: email, static site, USB stick, anywhere.

Read chunk 6. Open your bundle.html in a new browser tab to verify recipient experience.

In the new tab: click the skill, pick `xsl:skill-doc`, click your signature → ✓ verified appears.

Install the skill: copy the SKILL.md code block, create `~/.claude/skills/{skill-name}/SKILL.md`, paste, restart Claude Code.

show detail ▾

Claude Code picks up the skill on next session and will invoke it when task descriptions match the activation description in the skill's frontmatter.

You now have a signed, verifiable, transferable skill installed. The bundle.html remains as your permanent record of the skill's authorship and content.

## Skill published. Trust is mathematical.

Signed by you · verifiable in any browser · installable in any Claude Code · no marketplace required.