メニュー
Preview, validate, and publish a colophon site — run doctor, build, serve a local preview, and deploy to the configured publishers. Use when the user asks to preview, build, check, deploy, or publish their colophon blog.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Review a colophon site's received webmentions for spam/abuse and distill the bad ones into small, general glob rules in the committed blocklist (.colophon/webmention-block.yml), so moderation survives the cache's full regenerate. Use when the user asks to moderate, clean up, or block webmention spam/replies.
Fill or improve a colophon post's metadata — the description, the seo: block (title/description/keywords/social), tags reusing the site's existing vocabulary, and (rarely) a glossary entry for genuinely obscure jargon. Use when the user asks to add SEO, a summary/description, social copy, tags, or a glossary definition to a post.
Write a new blog post (or page) for a colophon site in a chosen author's byline and persona's voice. Use when the user asks to draft, write, or create a new post/article/entry for their colophon blog. colophon supplies the voice context and scaffolds the file; you write the prose.
Add cross-references between colophon posts — wikilinks and "related posts" — so entries connect to each other. Use when the user asks to link posts together, add related/see-also links, or wire up internal references on their colophon blog.
Revise an existing colophon blog post — retitle, expand a section, tighten, or fix — while preserving the author's voice and the frontmatter contract. Use when the user asks to edit, rewrite, expand, shorten, or fix an existing post on their colophon site.
| name | colophon-publish |
| description | Preview, validate, and publish a colophon site — run doctor, build, serve a local preview, and deploy to the configured publishers. Use when the user asks to preview, build, check, deploy, or publish their colophon blog. |
Drive colophon's operational commands. Deploy is gated and explicit, and deploy secrets are read from the environment by colophon itself — never handle or pass them.
The user wants to preview, validate, or deploy their colophon project.
This skill drives the colophon CLI. Before the first command, confirm it's installed:
command -v colophon || echo "colophon not found"
If it's missing, stop and offer the install — don't install it silently:
go install github.com/jmylchreest/colophon/cmd/colophon@latest (or a release binary). Proceed
only once it's on PATH.
Validate the project first:
colophon doctor # checks config, sites, publishers, environments
colophon env # lists the env vars this project needs (incl. deploy secrets)
If doctor reports problems, fix them before deploying. If env lists unset secrets needed
by a target, tell the user to set them in their shell — do not put secrets in config.
Preview locally (drafts included where an environment enables them):
colophon serve --open=latest # opens the newest post; prints home/sitemap/feed URLs too
Review the output with the user. A build also prints any warnings (empty posts, slug collisions) — surface those.
Publish — only when the user explicitly approves. Pick the environment:
colophon publish --env production
allow_publish: false) refuse without --allow-publish — only add it
when the user says so.--create provisions a missing destination (e.g. a Pages project / R2 bucket).Report back the deployed URL(s) from the publish summary.
colophon isn't installed, surface the install command and ask — never install it silently.--allow-publish on your own.