the skill
Colophon
Stamp a deliverable with a provenance colophon (who made it, with what model, how much effort, what the reader can rely on). Use whenever Warren says "add a colophon", "stamp this", "provenance line", or is about to ship an artefact from this repo — HTML workshop pieces, decks, markdown docs, business cases. Also use when he asks how much effort went into something before sending it.
A colophon states how an artefact was made and what the reader owes it. Counts come from git and the session log, never from memory. The trust claims come from Warren, never assumed.
Steps
- Identify the artefact file(s). Ask if ambiguous.
- Gather machine-fillable slots. Run:
Session count and elapsed time: readgit log --follow --format='%ad %h' --date=short -- <file> | wc -l # commits git log --follow --format='%ad' --date=short -- <file> | sort -u # distinct days.colophon.login the repo root if present (one line per session, appended by the Stop hook:date model minutes files). If absent, ask Warren for session count and rough hours; say the numbers are self-reported. Model: from.colophon.log, else the model running now. - Ask Warren two questions, nothing else:
- Tier: built, drafted, or directed (see templates).
- Is "Numbers checked against source" true? Include only on yes. Never default it in.
- Render with the matching template. Fill slots. No extra sentences.
- Insert in the artefact's native form:
- HTML:
<footer class="colophon">…</footer>before</body>, styled from wb-base-ui if present. - Markdown: final paragraph, preceded by
---. - pptx: last slide, single text box, via the template populator.
- Email/Slack: last line, plain text.
- HTML:
- Show the rendered line before writing it. Do not commit.
Templates
built — Warren wrote or shaped most of it; Claude edited.
This document was created by Warren with Claude Code ({model}) as editor. Completed in {sessions} sessions spanning {hours} hrs. {Numbers checked against source. }Judgement, and any mistakes, are mine.
directed — Claude drafted most of it; Warren directed and reviewed.
This document was created with Claude Code ({model}) drafting, Warren directing and reviewing. Completed in {sessions} sessions spanning {hours} hrs. {Numbers checked against source. }Judgement, and any mistakes, are mine.
drafted — low effort, lightly reviewed.
This document was drafted by Warren with Claude Code ({model}) in {sessions} session, under {minutes} min. Unreviewed beyond a skim. Treat as a starting point.
Singular/plural: 1 session, 2 sessions. Round hours to the nearest half; minutes to the nearest 10.
Rules
- Never invent counts. If a slot can't be filled from git or the log, ask.
- "Numbers checked against source" is a falsifiable claim. Omit unless confirmed.
- Model name as the user sees it (Opus, Sonnet, Haiku), not the API string.
- No adjectives. The colophon reports; it does not persuade.
- A colophon is not a signature. Do not add it to files Warren will not send.
Hook (optional, one-time setup)
Append a session line to .colophon.log on stop. Add to .claude/settings.json:
{ "hooks": { "Stop": [ { "hooks": [ { "type": "command",
"command": "python3 .claude/hooks/colophon_log.py" } ] } ] } }
colophon_log.py reads the transcript path from stdin JSON, computes minutes from first to last timestamp, lists files written, and appends date model minutes files to .colophon.log. Verify the hook event name and stdin schema against the current Claude Code hooks docs before relying on it; the schema has changed before.