blog-writing
Skill27 starsChanged 7 days agoApache-2.0View on GitHub
Use when planning, drafting, reviewing, or rewriting a post for the Coppice blog (website/src/content/blog/). Covers what a post is for, how to pick the topic and the reader's real problem, the structure, how much Coppice detail to include, and the checks to run. Not for user docs, READMEs, or social posts.
10 other projects use a version of this.
Adopted by
Most recently taken up by
- doeixd/writing-skilltheir own version, first seen Nov 16, 2026
- leek/agent-skillstheir own version, first seen Nov 16, 2026
- delorenj/skillstheir own version, first seen Nov 7, 2026
- ianlkl11234s/mini-taiwan-pulsetheir own version, first seen Nov 2, 2026
- astDeniss/business-skillstheir own version, first seen Nov 1, 2026
- goldtagworks/skillstheir own version, first seen Oct 15, 2026
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- ianlkl11234s/mini-taiwan-pulse★ 547same name
- youlaitech/youlai-skills★ 63same name
- delorenj/skills★ 17same name
- astDeniss/business-skills★ 8same name
- leek/agent-skills★ 5same name
- doeixd/writing-skill★ 4same name
- metraton/gaia★ 4same name
- xiaoshuai1024/skills★ 1same name
- goldtagworks/skills★ 0same name
- su-ekachai/skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- english-technical-writingSkill
- fr-technical-writingSkill
- ja-technical-writingSkill
- vietnamese-technical-writingSkill
- zh-cn-technical-writingSkill
- zh-hk-technical-writingSkill
- zh-tw-technical-writingSkill
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 4 are distinctive, and 6 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Start from a generic question, not a Coppice feature: "How to use Claude Code and Codex together on one project", not "Assigning agents in …
- Very specific: line 20
Before you write, state the problem the reader actually has.
- Distinctive: line 24
If you are not sure what the real problem is, ask the owner before you draft.
- Distinctive: line 34
Keep the whole post short.
- Very specific: line 38
Write for someone who has never opened Coppice.
- Very specific: line 40
Leave out internal terms and settings: connectors, auto_start_runs, column rules, exact error messages, every button on a form.
- Distinctive: line 41
Leave out edge cases and troubleshooting.
- Very specific: line 47
Do not recommend or pitch a competing product.
- Distinctive: line 51
Use one or two at most, only where a picture saves words.
- Very specific: line 53
Delete any image the post no longer uses from website/public/blog/<slug>/.
“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Blog writing
The Coppice blog exists for search. Each post answers a question people already type into Google about coding agents, then shows Coppice as one good way to solve it. A post is not a getting-started guide and not product documentation.
For English prose, also follow english-technical-writing. For frontmatter, routes, images, and checks, see website/BLOG.md.
1. Pick a topic people search for
- Start from a generic question, not a Coppice feature: "How to use Claude Code and Codex together on one project", not "Assigning agents in Coppice".
- Phrase the title the way someone would search for it. "How to …" and "… vs …" titles work well.
- One post answers one question.
2. Name the reader's real problem
Before you write, state the problem the reader actually has. Do not invent one to set up Coppice.
Check it against how people work today. Example: for using Claude Code and Codex together, the hard part is not telling who changed what. One agent can plan and another can build from that plan without trouble. The hard part is switching between terminals, and it gets worse with several tasks in parallel.
If you are not sure what the real problem is, ask the owner before you draft.
3. Structure
answer(frontmatter): the direct answer in two to four sentences. It mentions the options, including Coppice.- The problem: a short section on why this is hard, in the reader's terms.
- The options: two to four ways to solve it. Most should work without Coppice, such as plain terminals, git worktrees, or a script. Give each one a sentence or two on when it works and where it stops working. Show a command only when it is the whole option, such as
git worktree add. - The Coppice option: what Coppice does for this problem in one or two sentences, then at most five short steps to try it. Link to the docs for the details.
- Which one to pick: one line per option, matched to a situation.
Keep the whole post short. A reader should finish it in a few minutes.
4. How much Coppice detail
Write for someone who has never opened Coppice.
- Leave out internal terms and settings: connectors,
auto_start_runs, column rules, exact error messages, every button on a form. Say "pick Claude Code or Codex for each agent", not "choose a connector". - Leave out edge cases and troubleshooting. Link to Getting started, Concepts, or Providers instead.
- Each Coppice claim must match the current docs or code. Check
website/src/pages/docs/and, when in doubt, the server code. Do not promise a feature that is not shipped.
5. Other tools
- Generic approaches are fine to describe: terminals, git worktrees, shell scripts, the CLIs themselves.
- Do not recommend or pitch a competing product. If one is relevant, mention it in a few words at most and move on to Coppice.
6. Screenshots
- Use one or two at most, only where a picture saves words.
- Captions describe what the reader sees. Do not write "Demo data" or "fixture" in a caption.
- Delete any image the post no longer uses from
website/public/blog/<slug>/.
7. Before you finish
From website/:
npm run build
npm run check:seo
npm run check:links
node --experimental-strip-types --test src/lib/blog.test.tsThen read the post once as a new visitor who searched for its title. Ask:
- Does the first paragraph answer the question?
- Is the problem one the reader would recognize?
- Could they try the Coppice option from the steps alone, and find more in the linked docs?
- Is there any sentence that only makes sense to someone who already uses Coppice? Cut it.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

