Create Feature Announcement
Coordinates docs, a blog post, and a changelog entry to announce a shipped feature.
Install
npx skills add appwrite/appwrite --skill create-announcement -g -a claude-code -y- Repository
- appwrite/appwrite57.8k
- Category
- Marketing
- Updated
- 3d ago
- License
- BSD-3-Clause
- Context cost
- Mediumabout 2,418 tokens
- Runs scripts
- No, instructions only
What it does
Coordinates the three artifacts that ship a new Appwrite feature announcement: docs updates under src/content/docs/, an announcement blog post under blog/announcing-<slug>/, and a changelog entry under src/content/changelog/entries/. Use when the user asks to announce, launch, or ship a feature, product, SDK, runtime, integration, or plugin.
Repository layout (apps/console)
This skill targets the Console app at apps/console in appwrite/appwrite; paths are relative to it. Path mapping from the upstream appwrite/website skills:
| Artifact | Path |
|---|---|
| Blog post | src/content/blog/posts/<slug>.markdoc |
| Docs page | src/content/docs/{path}/index.markdoc |
| Changelog entry | src/content/changelog/entries/<YYYY-MM-DD>.markdoc |
| Cover image | public/images/blog/<slug>/cover.avif (min 1200px wide; run bun run generate:cover-manifest after adding) |
Also apply the unslop skill to all user-facing prose.
Create Announcement
What this skill produces
A complete Appwrite feature announcement is three coordinated artifacts:
- Docs update in
src/content/docs/..., the canonical reference for how the feature works. - Announcement blog at
src/content/blog/posts/announcing-<slug>.markdoc, narrative framing of why it matters and how to use it. - Changelog entry at
src/content/changelog/entries/<YYYY-MM-DD>.markdoc, short summary on the changelog feed linking back to the blog and/or docs.
The docs are the source of truth. The blog cites them. The changelog links into one or both. Ship them together.
This skill builds on writing-blogs for voice, tone, SEO, formatting, slug conventions, and cover-image generation. Read that skill before writing the blog and complete both sections of its SEO checklist before publishing. This skill only covers what is specific to announcements.
When to use each artifact
- Docs only: A small reference change. No blog, no changelog.
- Docs + changelog: A useful improvement that does not justify a narrative post. The changelog is the front-facing surface.
- Docs + blog + changelog: A launch worth telling a story about, new products, new SDKs/runtimes, major capabilities, integrations, plugins, compliance milestones.
If unsure, ask the user which subset to produce before writing anything.
