write-article
Skill7 starsChanged 40 days agoApache-2.0View on GitHub
Use when the author wants a new article, post or essay about this project for Substack, Medium, dev.to or another outlet and gives a topic direction to start from — "напиши статтю про…", "стаття для сабстеку", "пост на dev.to", "write an article about…", "/write-article <direction>". Not for docs, READMEs, changelogs or release notes, and not for publishing an article that is already written (publish-substack).
5 other projects use a version of this.
Adopted by
Most recently taken up by
- simonwong/skillstheir own version, first seen Nov 8, 2026
- greglas75/zuvotheir own version, first seen Oct 16, 2026
- UXMagicai/seosorted-skillstheir own version, first seen Oct 4, 2026
- vishalsachdev/claude-skillstheir own version, first seen Aug 12, 2026
- dongzhang84/vibe-writing-skillstheir own version, first seen Apr 21, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- dongzhang84/vibe-writing-skills★ 17same name
- simonwong/skills★ 9same name
- greglas75/zuvo★ 7same name
- vishalsachdev/claude-skills★ 2same name
- UXMagicai/seosorted-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 repository2 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- publish-substackSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 91
Create articles/<outlet>/<slug>/ and write brief.md:
- Very specific: line 106
When STYLE.md names a working language for the author that differs from the article's language, the article exists in two files.
- Distinctive: line 118
When a paragraph wants a detail you do not have, ask for it or drop the paragraph.
- Distinctive: line 145
Read it once for the shapes that mark prose nobody decided on: three-item lists by reflex, "it's not X, it's Y" turns, a paragraph that …
“Common” is measured: kept by at least 6 in 10 of the 3 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
Write an article
An article about this project needs two kinds of material. The author holds one: why something was built, what went wrong on the way, what they now believe. The repository holds the other: the numbers, names and dates the author would misremember. This skill gets the first by interviewing the author and the second by reading, and puts nothing into the article that came from neither.
The layout, the front matter and what each outlet's editor drops are in
articles/README.md. The author's voice and standing facts are in
articles/STYLE.md once the first interview has written it.
1. Research before asking
articles/README.md,articles/STYLE.md, and the front matter of every existing article, so the new one neither repeats an old one nor misses a chance to link to it.- The direction itself, in the repository: code,
docs/,CHANGELOG.md, ADRs,git log, merged PRs. Keep a fact sheet as you go, one line per fact with where it comes from (path:line, commit, PR number). - What the outlet's readers have been reading on this subject. Search the web
for what was published on it in about the last month, on the target outlet
first, and on all of them while the outlet is still open. dev.to has a public
listing,
https://dev.to/api/articles?tag=<tag>&top=30, which returns a tag's posts from the last 30 days with their reaction and comment counts. Substack and Medium have none, so search by topic restricted to the site. For each post that matters, note the title, author, date, link, its claim in one line, and how it was received where that is visible. Then write down what these posts agree on, what they argue about, and what none of them has said.
The repository research decides the quality of the interview. It removes every question the repository can answer, and it turns the rest from generic ("what challenges did you face?") into specific ("PR #355 fixed an 11-hour hang; is that the story here, or a footnote?").
The outlet research shows which conversation the article walks into: what the reader has already seen, the words they use for it, the tags that are active. It shapes the angles and the framing. The thesis still comes from what the author did and found; when that material does not support a trend, the article leaves the trend alone. If the web cannot be searched in this session, tell the author before the interview starts.
2. Interview
Hold the interview in the language the author writes to you in, whatever language the article will be in. Ask in rounds of at most four questions, and write each round after reading the answers to the one before.
First round: the frame. Open with what the outlet research found, in a few
lines. Then offer two to four angles, each as a working title, the one claim
that article would defend, and where it stands against the recent posts: which
one it answers, extends or contradicts, or what gap it fills. The author picks
one, merges two, or redirects. Then settle whatever the invocation and
STYLE.md have not: the outlet, the reader (who they are, what they already
know, what they should do after reading), the article's language, the rough
length. These are choices, so AskUserQuestion suits them.
Later rounds: the substance. These answers are stories, so ask them as plain numbered questions and end your turn. Draw on the ones this angle needs:
- the episode: what happened, on which day, that made this worth building or changing
- what was tried first, and why it failed
- what surprised them
- the claim a skeptical reader will reject, and the author's answer to it
- what they are not claiming, and what is still unsolved
- what the reader should do next
Then follow the answer that is most interesting or least precise down to an instance: which session, how many, measured how, what the screen showed.
When to stop. You can state the thesis in one sentence the author agrees with, and every section of the outline has something concrete to carry it: an episode, a number, an example, a quoted line. That usually takes two to four rounds. If the author ends the interview sooner, a section still without material is cut from the outline.
First article only, when articles/STYLE.md does not exist: add a round on
voice. Ask for one or two pieces whose tone they want (their own or someone
else's), whether it is "I" or "we", how blunt they want to sound, their bio line
and the links every article should carry. Write the answers to STYLE.md.
3. Brief, then approval
Create articles/<outlet>/<slug>/ and write brief.md:
- Thesis: one sentence.
- Reader: who, and what they know coming in.
- Outline: each section's point and the material that carries it.
- Landscape: the recent posts found, each with its link, date and claim, and what this article adds to them.
- Facts: each claim about the project with its source.
- Interview: the questions and the author's answers, verbatim.
- Open: what is still unverified or undecided.
Show the thesis and the outline in chat. Draft once the author approves them.
4. Draft article.md
When STYLE.md names a working language for the author that differs from the
article's language, the article exists in two files. Write
article.<lang>.md in the author's language first (article.uk.md for
Ukrainian): that is the version the author reads and edits. Then write
article.md in the article's language as its translation; that is the version
that gets published. Both carry the same paragraphs in the same order with the
same numbers, and every later edit to one is carried into the other in the same
turn.
- Every sentence has a source. A fact about the project comes from the fact sheet. An experience, motive, opinion or reaction comes from an interview answer. What someone else's post says is attributed to that post and linked. When a paragraph wants a detail you do not have, ask for it or drop the paragraph.
- The author's words are the raw material. Reuse their phrasing. When the
interview was in another language, translate the bluntness and the jokes along
with the meaning. Write in the first person, as
STYLE.mdsets it. - The reader arrives cold. They have never seen this repository. Introduce each project term where it first appears, and link the thing you name.
- Open on the episode or on the claim. The reader came for what happened here; a general sentence about agents or software stays only when the next sentence needs it.
- Code and commands are copied from the repository and run before they are shown.
- Write within the outlet's limits from
articles/README.md. They differ by outlet: Substack and Medium take no tables, while dev.to takes them but turns every line break inside a paragraph into a visible one and has its own front matter format. - Images: list each one the article needs and what it must show, for the
author to capture into
assets/. Reference only files that exist.
5. Check the draft
- Re-read every fact against its source as the repository stands now.
- Give the article to one fresh subagent with nothing but its text and the reader's description. Ask it for the thesis in one sentence, the place it lost the thread, the claim it did not believe, and what it would cut. A thesis that differs from the brief's means the structure is hiding the point; fix the structure.
- Read it once for the shapes that mark prose nobody decided on: three-item lists by reflex, "it's not X, it's Y" turns, a paragraph that ends by restating itself, a heading phrased as a question. Each one marks a spot where a specific fact belongs. Put the fact there, or cut the sentence.
6. Hand over
Report the path of each version, the word count, three title options with a
subtitle of at most 255 characters, what is still unverified, and the images the author has to
supply. When the author edits the draft or comments on it, write the part that
will hold for the next article into articles/STYLE.md.
Publishing is a separate step: publish-substack.
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.

