Agent skill

Blog

Write release blog posts for Chorus — problem-first narrative, bilingual (zh/en), following the project's editorial style.

AGPL-3.0Auto-check passedWriting & Content

Install Blog

skills CLI

$ npx skills add Chorus-AIDLC/Chorus --skill blog -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install Chorus-AIDLC/Chorus blog --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/Chorus-AIDLC/Chorus.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/blog .claude/skills/blog && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "blog" agent skill from https://github.com/Chorus-AIDLC/Chorus/tree/main/.claude/skills/blog into .claude/skills/blog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blog", 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

$skill-installer install https://github.com/Chorus-AIDLC/Chorus/tree/main/.claude/skills/blog

Type 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.

skills CLI

$ npx skills add Chorus-AIDLC/Chorus --skill blog -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install Chorus-AIDLC/Chorus blog --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Chorus-AIDLC/Chorus.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/blog .agents/skills/blog && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "blog" agent skill from https://github.com/Chorus-AIDLC/Chorus/tree/main/.claude/skills/blog into .agents/skills/blog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blog", 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.

skills CLI

$ npx skills add Chorus-AIDLC/Chorus --skill blog -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install Chorus-AIDLC/Chorus blog --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Chorus-AIDLC/Chorus.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/blog .cursor/skills/blog && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "blog" agent skill from https://github.com/Chorus-AIDLC/Chorus/tree/main/.claude/skills/blog into .cursor/skills/blog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blog", 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

$ gemini skills install https://github.com/Chorus-AIDLC/Chorus.git --path .claude/skills/blog

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add Chorus-AIDLC/Chorus --skill blog -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install Chorus-AIDLC/Chorus blog --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Chorus-AIDLC/Chorus.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/blog .gemini/skills/blog && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "blog" agent skill from https://github.com/Chorus-AIDLC/Chorus/tree/main/.claude/skills/blog into .gemini/skills/blog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blog", 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.

GitHub CLI

$ gh skill install Chorus-AIDLC/Chorus blog

Installs 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).

skills CLI

$ npx skills add Chorus-AIDLC/Chorus --skill blog -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/Chorus-AIDLC/Chorus.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/blog .github/skills/blog && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "blog" agent skill from https://github.com/Chorus-AIDLC/Chorus/tree/main/.claude/skills/blog into .github/skills/blog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blog", 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.

skills CLI

$ npx skills add Chorus-AIDLC/Chorus --skill blog -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install Chorus-AIDLC/Chorus blog --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Chorus-AIDLC/Chorus.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/blog .opencode/skills/blog && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "blog" agent skill from https://github.com/Chorus-AIDLC/Chorus/tree/main/.claude/skills/blog into .opencode/skills/blog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blog", 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: blog
GitHub stars: 1.2k
Token cost: ~1.2k tokens
SKILL.md length: 616 words
Files: 1
Skills in repo: 64
Repo updated: Oct 9, 2026
First seen: Oct 7, 2026
Licence: AGPL-3.0

At a glance

Write release blog posts for Chorus — problem-first narrative, bilingual (zh/en), following the project's editorial style.

Works in 4 steps: Gather context → Draft the Chinese version first → Write the English version → …
Tasks that involve Blog and article writing
SKILL.md covers Prerequisites, Editorial Style and Steps
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Blog is an agent skill from Chorus-AIDLC/Chorus. Write release blog posts for Chorus — problem-first narrative, bilingual (zh/en), following the project's editorial style.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Writing & Content, covering Blog and article writing and Translation. The repository describes itself as: The Agent Harness for AI-Human Collaboration, inspired by the AI-DLC (AI-Driven Development Lifecycle). The licence is AGPL-3.0.

When your agent uses it

Tasks that involve Blog and article writing
Tasks that involve Translation

Example prompts

“/blog”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

Gather context
Draft the Chinese version first
Write the English version
Self-review checklist

What it can do on your machine

Read from SKILL.md and the folder at commit 37d62d9. 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 (its code samples are markdown and bash).
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

Blog loads about 1.2k tokens when it runs. Until then it costs about 32 tokens; SKILL.md has 616 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~32
When it runs · the whole SKILL.md, loaded when a task matches: ~1.2k

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 Chorus-AIDLC/Chorus at commit 37d62d9, republished under its AGPL-3.0 licence (© Chorus-AIDLC). 616 words, ~1,230 tokens.

Download SKILL.mdSave it as .claude/skills/blog/SKILL.md (or your agent's skills folder).

name: blog
description: Write release blog posts for Chorus — problem-first narrative, bilingual (zh/en), following the project's editorial style.
license: AGPL-3.0
metadata.author: chorus
metadata.version: 0.1.0
metadata.category: content

Chorus Blog Post

Write bilingual (zh/en) release blog posts for the Chorus landing site.

Prerequisites

You know what version / feature to write about (user will tell you, or check recent CHANGELOG / git log)
Existing blog posts live in packages/landing/src/content/blog/
Naming convention: zh-chorus-vX.Y.Z-release.md (Chinese), chorus-vX.Y.Z-release.md (English)

Editorial Style

These rules come from the project owner. Follow them strictly.

Narrative structure

Open from the reader's pain point, not the feature. Don't start with "we released X." Start with the problem the reader is living with. Describe the scenario vividly so they recognize themselves in it.
One line to introduce the solution. After the pain point lands, say what this version does in one sentence.
Break down the supporting mechanisms. Explain the layers / building blocks that make the solution work. Order them by the flow the user experiences, not by importance.
Industry context as supporting evidence, not the opening. If there are relevant industry trends (e.g., new tools from Anthropic, competitor features), reference them to validate the direction. But they go in the middle or late section, never the lead.
Converge to a conclusion. Tie the pieces back together. The punchline should echo the opening pain point: "this is why you can now do X."

Tone and voice

Don't speak for the reader. Never write "you probably think X" or "you definitely feel Y." Describe the situation, let readers identify with it on their own.
Casual, not corporate. Write like you're explaining to a sharp colleague, not writing a press release. No marketing speak, no filler adjectives.
No em dashes (——) in Chinese. Use commas, periods, or sentence breaks instead.
Chinese should read like Chinese. Not translated-from-English. Spoken rhythm, natural phrasing.
English should read like English. Not translated-from-Chinese. Prefer short punchy sentences. Avoid "materialize," "leverage," "utilize" — use plain words.
Logical consistency matters. The owner will catch contradictions immediately. If you say "we had X from day one," make sure that's actually true. If something was added in a specific version, say so.
No filler. If one sentence covers it, don't stretch it to three.

Title

Include the version number: Chorus vX.Y.Z: <hook>
The hook is the real title. It should make someone want to click.
Can mix Chinese and English, use slang, be playful.
Examples:
- "Chorus v0.6.1: 你的时间比 Token 贵，/yolo it！"
- "Chorus v0.6.0: 给你的 Agent 团队派个监工"

Show full SKILL.md (229 more words)Show less

Frontmatter

markdown

---
title: "Chorus vX.Y.Z: <hook>"
description: "<1-2 sentences, written as a question or provocation, not a summary>"
date: YYYY-MM-DD
lang: zh  # or en
postSlug: chorus-vX.Y.Z-release
---

description should hook the reader, not summarize the post. A question or a challenge works well.
postSlug must be the same for both zh and en versions so they link together.

Steps

1. Gather context

bash

# Find the version's CHANGELOG entry
# Read recent commits if needed
# Read the relevant feature code / skill docs to understand what was built

Understand the feature deeply before writing. Read the code, the skill docs, the PR descriptions. Don't write from summaries alone.

2. Draft the Chinese version first

Write zh-chorus-vX.Y.Z-release.md. Chinese is the primary version, not a translation.

Present the draft to the user for review. Expect multiple rounds of feedback on:

Narrative structure (what goes first, what to cut)
Tone (too stiff, too corporate, too presumptuous)
Logical consistency
Title and description

Do NOT proceed to the English version until the Chinese version is approved.

3. Write the English version

Write chorus-vX.Y.Z-release.md. This is NOT a literal translation. Rewrite for an English-speaking audience:

Same structure and arguments
Natural English phrasing and rhythm
Adapt metaphors and references that don't cross language boundaries

4. Self-review checklist

Before presenting each version:

Opens from pain point, not feature announcement
Doesn't speak for the reader ("you probably think...")
No em dashes in Chinese version
No translation-smell in either language
Title has version number + hook
Description is a hook, not a summary
All factual claims are accurate (which version introduced what)
No logical contradictions between sections
No filler paragraphs — every section earns its space
postSlug matches between zh and en versions

Files

Just SKILL.md in .claude/skills/blog of Chorus-AIDLC/Chorus.

Open the folder on GitHubat commit 37d62d9

Compare with similar skills

Blog 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.

Blog compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Blog this skillChorus-AIDLC/Chorus	1.2k	—	~1.2k	Automated safety check: Pass	AGPL-3.0	today
Create Release Blogweb-infra-dev/rstest	505	—	~4.7k	Automated safety check: Pass	MIT	today
Blog Post ProcessorJustin3go/justin3go.com	172	—	~1.5k	Automated safety check: Pass	Custom licence	18 days ago
Humanizer Zhai-zixun/humanizer-zh	179	—	~1.2k	Automated safety check: Pass	MIT	4 mo ago
Blog TranslateAgriciDaniel/claude-blog	2.3k	1 repos	~2.1k	Automated safety check: Pass	MIT	yesterday
Blog LocalizeAgriciDaniel/claude-blog	2.3k	1 repos	~2.3k	Automated safety check: Pass	MIT	yesterday

Similar skills

Create Release Blog
web-infra-dev/rstest
Generate a narrative version release blog post from commits within a tag range.
505 GitHub stars~4.7k tokensUpdated today
Writing & ContentAuto-check passed
Blog Post Processor
Justin3go/justin3go.com
Process Chinese blog posts for the justin3go.com VitePress blog: rename to English slug, add frontmatter and AI summary, and translate to English.
172 GitHub stars~1.5k tokensUpdated 18 days ago
Writing & ContentAuto-check passed
Humanizer Zh
ai-zixun/humanizer-zh
Remove signs of AI-generated, translated, or overly mechanical Chinese prose.
179 GitHub stars~1.2k tokensUpdated 4 mo ago
Writing & ContentAuto-check passed
Blog Translate
AgriciDaniel/claude-blog
Translate existing blog posts into one or more target languages with SEO-optimized localization.
2.3k GitHub starsUsed in 1 repo~2.1k tokens
Writing & ContentAuto-check passed
Blog Localize
AgriciDaniel/claude-blog
Deep cultural adaptation of translated blog posts. An agent skill from AgriciDaniel/claude-blog.
2.3k GitHub starsUsed in 1 repo~2.3k tokens
Writing & ContentAuto-check passed
Blog Multilingual
Infrasity-Labs/dev-gtm-claude-skills
One-command multilingual blog creation. An agent skill from Infrasity-Labs/dev-gtm-claude-skills.
136 GitHub starsUsed in 1 repo~2.6k tokens
Writing & ContentAuto-check passed

Questions about Blog

What does Blog do?

Write release blog posts for Chorus — problem-first narrative, bilingual (zh/en), following the project's editorial style. Blog is an agent skill from Chorus-AIDLC/Chorus. Write release blog posts for Chorus — problem-first narrative, bilingual (zh/en), following the project's editorial style.

When should I use Blog?

Blog fits situations like: tasks that involve Blog and article writing; tasks that involve Translation.

How do I install Blog in Claude Code?

Run `npx skills add Chorus-AIDLC/Chorus --skill blog -a claude-code`. Or copy the skill folder (.claude/skills/blog in Chorus-AIDLC/Chorus) into .claude/skills/blog in your project. Claude Code loads it when a task matches its description.

How do I install Blog in Codex?

Run `npx skills add Chorus-AIDLC/Chorus --skill blog -a codex`. Or copy the skill folder (.claude/skills/blog in Chorus-AIDLC/Chorus) into .agents/skills/blog in your project. Codex loads it when a task matches its description.

Can I use Blog 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 Chorus-AIDLC/Chorus --skill blog -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/blog, .gemini/skills/blog, .github/skills/blog and .opencode/skills/blog in your project.

What does Blog need to run?

SKILL.md names no scripts, command-line tools or credentials: Blog is instructions for the agent only.

Does Blog 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 Blog 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 Blog use?

Blog is published under the AGPL-3.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Blog use?

About 1.2k tokens (SKILL.md is roughly 4.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Blog?

Skills that share tags, products or a category with Blog: Create Release Blog (web-infra-dev/rstest, 505 stars), Blog Post Processor (Justin3go/justin3go.com, 172 stars), Humanizer Zh (ai-zixun/humanizer-zh, 179 stars) and Blog Translate (AgriciDaniel/claude-blog, 2.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Blog?

Chorus-AIDLC (a GitHub organization) maintains it in Chorus-AIDLC/Chorus, which has 1,192 GitHub stars. The repository holds 64 skills in this directory. The repository was last updated on October 9, 2026.

Source: Chorus-AIDLC/Chorus on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Blog

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Chorus Blog Post

Prerequisites

Editorial Style

Narrative structure

Tone and voice

Title

Frontmatter

Steps

1. Gather context

2. Draft the Chinese version first

3. Write the English version

4. Self-review checklist

Files

Compare with similar skills

Similar skills

More from Chorus-AIDLC/Chorus

Related

Questions about Blog