obot: Skill for Claude Code

Draft Release Blog Post

Drafts a blog post announcing an obot release. Sources the feature spine from the draft GitHub release (the output of the draft-release skill or an existing draft on GitHub), then does additional research to add the kind of detail, context, and rationale that release notes deliberately omit but a blog post needs.

The blog is for obot.ai's hosted Wordpress CMS. The default output is a markdown file at <repo root>/release-blog-<VERSION>.md (i.e. the current project directory) that the user can paste into the CMS themselves. Writing it into the repo makes it easy to review in the IDE; it is an intentionally untracked file — do not commit it and do not add it to .gitignore. If the user explicitly asks to post it (e.g. "post it up there", "create the draft in Wordpress"), the skill can also create the post as a Wordpress draft via the obot-wordpress MCP server (see step 8). The skill never publishes a live post without explicit user confirmation of the publish status.

Voice reference

Before drafting, every time, read the two most recent release announcement posts on obot.ai. They are the reference for voice, structure, and the "Get started" links. Find them through the public Wordpress REST API: release posts are in the Product Updates category and their slugs start with announcing-obot and contain the version (v0-25-0, v-0-26-0). Titles are not reliable, since some release posts do not put the version in the title.

cat_id=$(curl -s "https://obot.ai/wp-json/wp/v2/categories?slug=product-updates&_fields=id" | jq '.[0].id')
curl -s "https://obot.ai/wp-json/wp/v2/posts?categories=${cat_id}&per_page=20&orderby=date&order=desc&_fields=date,slug,link,title" \
  | jq -r '[.[] | select(.slug | test("^announcing-obot.*v-?[0-9]+-[0-9]+-[0-9]+"))][:2][] | "\(.date) \(.link) \(.title.rendered)"'

Then fetch each post's body from the same API (/wp-json/wp/v2/posts?slug=<slug>&_fields=content) and strip the HTML tags. This returns the full text, while WebFetch only returns a summary. Note each post's word count, section headings, opener, and the exact link targets in its closing section.