Sepia
Nanako0129/sepia
Make AI-generated writing read as human-written, in fiction and in professional prose.
Outline, draft, or revise a Foldkit version release blog post using the repository's announcement style and editorial preferences.
Install Write Release Blog Post
$ npx skills add foldkit/foldkit --skill write-release-blog-post -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install foldkit/foldkit write-release-blog-post --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/foldkit/foldkit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/write-release-blog-post .claude/skills/write-release-blog-post && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "write-release-blog-post" agent skill from https://github.com/foldkit/foldkit/tree/main/.agents/skills/write-release-blog-post into .claude/skills/write-release-blog-post/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-release-blog-post", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/foldkit/foldkit/tree/main/.agents/skills/write-release-blog-postType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add foldkit/foldkit --skill write-release-blog-post -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install foldkit/foldkit write-release-blog-post --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/foldkit/foldkit.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/write-release-blog-post .agents/skills/write-release-blog-post && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "write-release-blog-post" agent skill from https://github.com/foldkit/foldkit/tree/main/.agents/skills/write-release-blog-post into .agents/skills/write-release-blog-post/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-release-blog-post", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add foldkit/foldkit --skill write-release-blog-post -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install foldkit/foldkit write-release-blog-post --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/foldkit/foldkit.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/write-release-blog-post .cursor/skills/write-release-blog-post && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "write-release-blog-post" agent skill from https://github.com/foldkit/foldkit/tree/main/.agents/skills/write-release-blog-post into .cursor/skills/write-release-blog-post/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-release-blog-post", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/foldkit/foldkit.git --path .agents/skills/write-release-blog-post--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add foldkit/foldkit --skill write-release-blog-post -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install foldkit/foldkit write-release-blog-post --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/foldkit/foldkit.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/write-release-blog-post .gemini/skills/write-release-blog-post && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "write-release-blog-post" agent skill from https://github.com/foldkit/foldkit/tree/main/.agents/skills/write-release-blog-post into .gemini/skills/write-release-blog-post/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-release-blog-post", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install foldkit/foldkit write-release-blog-postInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add foldkit/foldkit --skill write-release-blog-post -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/foldkit/foldkit.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/write-release-blog-post .github/skills/write-release-blog-post && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "write-release-blog-post" agent skill from https://github.com/foldkit/foldkit/tree/main/.agents/skills/write-release-blog-post into .github/skills/write-release-blog-post/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-release-blog-post", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add foldkit/foldkit --skill write-release-blog-post -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install foldkit/foldkit write-release-blog-post --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/foldkit/foldkit.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/write-release-blog-post .opencode/skills/write-release-blog-post && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "write-release-blog-post" agent skill from https://github.com/foldkit/foldkit/tree/main/.agents/skills/write-release-blog-post into .opencode/skills/write-release-blog-post/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-release-blog-post", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
write-release-blog-post- GitHub stars
- 918
- Token cost
- ~1k tokens
- SKILL.md length
- 569 words
- Files
- 3 (incl. references)
- Skills in repo
- 18
- Repo updated
- First seen
- Licence
- MIT
At a glance
Outline, draft, or revise a Foldkit version release blog post using the repository's announcement style and editorial preferences.
- Release announcements
- SKILL.md covers Choose the amount of detail, Keep the announcement distinct… and Add the post to the website
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Not general guides
What it does
Write Release Blog Post is an agent skill from foldkit/foldkit. Outline, draft, or revise a Foldkit version release blog post using the repository's announcement style and editorial preferences. Use for release announcements, not general guides or changelog entries.
Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `agents/openai.yaml` and `references/posts.md`).
It sits in Writing & Content, covering Blog and article writing and Changelog and release notes. The licence is MIT.
When your agent uses it
- Release announcements
- Not general guides
- Changelog entries
Example prompts
- “/write-release-blog-post”
What it can do on your machine
Read from SKILL.md and the folder at commit d21db42. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Write Release Blog Post loads about 1k tokens when it runs, and up to ~2.3k if it reads all its reference files. Until then it costs about 57 tokens; SKILL.md has 569 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from foldkit/foldkit at commit d21db42, republished under its MIT licence (© foldkit). 569 words, ~1,021 tokens.
Download SKILL.mdSave it as
.claude/skills/write-release-blog-post/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- write-release-blog-post
- description
- Outline, draft, or revise a Foldkit version release blog post using the repository's announcement style and editorial preferences. Use for release announcements, not general guides or changelog entries.
Write a Foldkit release blog post
Use this skill for the editorial shape of a version announcement. The repository's
prose, snippet, historical-post, and contributor-attribution rules live in
AGENTS.md and .agents/writing-prose.md.
Choose the amount of detail
Foldkit's version posts give selected changes room to explain themselves. They usually open with the version and a short summary, group the highlights under feature headings, and close with release notes and contributor thanks. A release with one substantial addition can revolve around that addition. Do not give every package or changeset a section just to complete the inventory.
Read the post examples to choose a relevant model. The 0.167.0 post is the clearest example of the current balance. Earlier posts offer useful shapes for a focused addition, several smaller features, and combined releases. Their older API examples describe those releases, not today's API.
Allocate detail according to what helps the reader understand the change:
- A new API: Explain the operation it replaces or simplifies, then show a
compact, realistic snippet when the call shape is the useful part. A changeset
example can supply the starting point. The
foldChildAtsection in 0.167.0 shows the parent selecting an Applicant Submodel by key without teaching the whole Submodel architecture. - Interactive behavior: Reuse an existing guide demo when trying it conveys more than additional prose. Introduce the visible behavior and give readers concrete actions to try. The VirtualList section in 0.167.0 needs only two short paragraphs before its chat demo; row measurement and lifecycle wiring belong in the linked guide. This is an example of appropriate depth, not a paragraph limit or a requirement to add a demo to every post.
- Moves and renames: Make the reorganization the news. Show both prior and new names, with a small table when several mappings deserve highlighting. Explain any behavioral change separately. A move into a new module does not make the existing helpers new functionality. Avoid following a rename table with a compressed tutorial on wiring the renamed APIs.
- Smaller changes: Include a short “More in this release” list when the items warrant a mention. The release-notes link can carry the rest. Do not expand minor fixes into feature paragraphs to account for every change.
Show full SKILL.md (204 more words)Show less
Keep the announcement distinct from the guides
Link a feature's guide or complete example beside that feature. Include enough code or explanation for the reader to see why the change is useful, then let the linked material teach configuration and integration.
Put upgrade instructions, complete package versions, and the full change list in the release notes. Do not add an “Upgrading” section by default, even though older posts have one. An old/new mapping can belong in the announcement when the rename itself is a highlight; a complete migration recipe belongs in the release notes.
The usual closing points to the relevant version's release notes, followed by “Thanks to everyone building with Foldkit!” and “Devin”. When covering several releases, state that scope near the opening and link each release's notes.
Place verified contributor thanks beside the relevant feature or near the closing for smaller contributions. Follow the repository's attribution pass over the full release range, including work omitted from the highlights.
A casual personal line can fit the voice. Past jokes and launch narratives are individual author choices, not a required release-post formula.
Add the post to the website
The authoring notes point to frontmatter, cover, snippet, and demo conventions when the task includes implementation.
© foldkit, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 2 other files (references) in .agents/skills/write-release-blog-post of foldkit/foldkit.
- SKILL.md
- agents/openai.yaml
- references/posts.md
Open the folder on GitHubat commit d21db42
Compare with similar skills
Write Release Blog Post next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Write Release Blog Post this skillfoldkit/foldkit | 918 | — | ~1k | Automated safety check: Pass | MIT | |
| SepiaNanako0129/sepia | 3k | — | ~3.6k | Automated safety check: Pass | MIT | |
| Blog Postnteract/semiotic | 2.7k | — | ~3.4k | Automated safety check: Pass | Apache-2.0 | |
| Blogtheopenco/llmgateway | 1.7k | — | ~2.2k | Automated safety check: Pass | Custom licence | |
| Release Postquarto-dev/quarto-r | 160 | 1 repos | ~2.5k | Automated safety check: Pass | MIT | |
| Penguin Harness DevPrism-Shadow/penguin-harness | 2.5k | — | ~3.4k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Blog Post
nteract/semiotic
Author a new entry for the Semiotic blog. An agent skill from nteract/semiotic.
Blog
theopenco/llmgateway
Write and validate an LLM Gateway marketing blog post in the repository's current house style, including structured frontmatter and a gpt-image-2 OpenGraph image.
Release Post
quarto-dev/quarto-r
Create professional package release blog posts following Tidyverse or Shiny blog conventions.
Penguin Harness Dev
Prism-Shadow/penguin-harness
A skill your agent uses when developing PenguinHarness itself — changing packages/{core,server,web,cli,desktop,landing,docs,skills}, the built-in model catalog, the installers or the release…
Release Blog Drafter
obot-platform/obot
Drafts a release announcement blog post for an obot release as a Markdown file, with an optional WordPress draft through MCP and no live publishing without confirmation.
More from foldkit/foldkit
All 18 skills in this repoCommit Changes
foldkit/foldkit
Create a git commit in the Foldkit monorepo with changeset enforcement and formatting.
Foldkit
foldkit/foldkit
A skill your agent uses whenever working with Foldkit. An agent skill from foldkit/foldkit.
Audit Program
foldkit/foldkit
Audit an existing Foldkit program against the architecture, conventions, and quality bar.
Generate Program
foldkit/foldkit
Generate a complete, idiomatic Foldkit program from a natural language description.
Changesets
foldkit/foldkit
Concise PR finalization changesets. An agent skill from foldkit/foldkit.
Dependency Maintenance
foldkit/foldkit
Dependency maintenance. An agent skill from foldkit/foldkit.
Related
Categories
Questions about Write Release Blog Post
What does Write Release Blog Post do?
Outline, draft, or revise a Foldkit version release blog post using the repository's announcement style and editorial preferences. Write Release Blog Post is an agent skill from foldkit/foldkit. Outline, draft, or revise a Foldkit version release blog post using the repository's announcement style and editorial preferences.
When should I use Write Release Blog Post?
Write Release Blog Post fits situations like: release announcements; not general guides; changelog entries.
How do I install Write Release Blog Post in Claude Code?
Run `npx skills add foldkit/foldkit --skill write-release-blog-post -a claude-code`. Or copy the skill folder (.agents/skills/write-release-blog-post in foldkit/foldkit) into .claude/skills/write-release-blog-post in your project. Claude Code loads it when a task matches its description.
How do I install Write Release Blog Post in Codex?
Run `npx skills add foldkit/foldkit --skill write-release-blog-post -a codex`. Or copy the skill folder (.agents/skills/write-release-blog-post in foldkit/foldkit) into .agents/skills/write-release-blog-post in your project. Codex loads it when a task matches its description.
Can I use Write Release Blog Post in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add foldkit/foldkit --skill write-release-blog-post -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/write-release-blog-post, .gemini/skills/write-release-blog-post, .github/skills/write-release-blog-post and .opencode/skills/write-release-blog-post in your project.
What does Write Release Blog Post need to run?
SKILL.md names no scripts, command-line tools or credentials: Write Release Blog Post is instructions for the agent only.
Does Write Release Blog Post access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Write Release Blog Post safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Write Release Blog Post use?
Write Release Blog Post is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Write Release Blog Post use?
About 1k tokens (SKILL.md is roughly 4.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.2k tokens, read only when the agent opens those files.
What are the alternatives to Write Release Blog Post?
Skills that share tags, products or a category with Write Release Blog Post: Sepia (Nanako0129/sepia, 3k stars), Blog Post (nteract/semiotic, 2.7k stars), Blog (theopenco/llmgateway, 1.7k stars) and Release Post (quarto-dev/quarto-r, 160 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Write Release Blog Post?
foldkit (a GitHub organization) maintains it in foldkit/foldkit, which has 918 GitHub stars. The repository holds 18 skills in this directory. The repository was last updated on October 8, 2026.
Source: foldkit/foldkit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.