blog-writing-skill
Skill1 starsChanged 41 days agoMITView on GitHub
Develop an author's idea into a well-written, site-aware SEO article in any language, with approval of the angle and outline before drafting and a revision round before final delivery. Use for editorial articles, blog posts and journalistic pieces.
In this repository2 other files it gives its agents.
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 10 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈10
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Use the context already supplied.
- Distinctive: line 20
Read Website and SEO research before investigating the destination and search opportunities.
- Distinctive: line 34
Search intent, target query or topic, useful related terms and verified internal-link opportunities.
- Distinctive: line 37
If the proposed article promises practical advice that the supplied material cannot support, ask for the concrete problem or example, or …
- Distinctive: line 41
If site evidence or search data is unavailable, state the limitation and mark the resulting assumptions in the proposal.
- Distinctive: line 47
Use the composition guidance in Editorial profile and composition to choose an opening, develop sections, address relevant objections and …
- Distinctive: line 57
Before showing the draft, perform distinct checks:
- Distinctive: line 60
Evidence: verify factual claims against inspected sources or supplied material.
- Distinctive: line 64
SEO fit: ensure the title describes the article, the structure fits its search intent and links are relevant.
- Distinctive: line 66
When the author requests or accepts an optional assisted language check, follow LanguageTool checks.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Editorial Article Writing
Turn an idea, theme or editorial direction into an article that expresses the author's thinking, suits its publication and reads naturally in the reader's language. Adapt to any website; no particular site, commercial objective or writing register is the default.
1. Understand the intention
Use the context already supplied. Ask only for missing information that affects the article: destination website, intended message, purpose, reader, language and desired research depth. An informal idea is a valid starting point; help develop it rather than requiring a finished brief.
Restate the author's central thought in a short paragraph. Distinguish their position from questions they are still exploring. Ask about tone preferences and propose a suitable tone after examining the site. Use any supplied writing samples or editorial guidance.
Agree whether to work mainly from the author's material or also conduct external research. Respect that choice while flagging factual claims that cannot be supported with the permitted material. Research should inform the author's argument, not silently replace it with the prevailing view.
2. Understand the publication and search context
Read Website and SEO research before investigating the destination and search opportunities. Summarize the relevant findings in the proposal; keep research notes outside the article.
Infer a baseline voice from representative existing articles: register, vocabulary, rhythm, narration, humour, headings and audience knowledge. Adapt the tone to this article's theme and purpose. Preserve useful conventions without copying passages or reproducing poor writing. Author preferences override the inferred baseline.
Build or reuse an EDITORIAL PROFILE using Editorial profile and composition. Present its key choices with the article proposal for author validation. Keep the site's stable voice separate from this article's tone, and reuse confirmed choices for later articles on the same site and editorial section.
3. Propose and obtain approval
Present one main recommendation, not an obligatory menu of alternatives:
- The author's intended message and the reader's likely need.
- The proposed angle and its distinct contribution.
- Tone and voice, with a brief explanation grounded in the site or samples.
- A provisional title and outline; explain what each section contributes.
- Search intent, target query or topic, useful related terms and verified internal-link opportunities.
- A proposed length and any needed research, factual qualification or optional deliverables.
If the proposed article promises practical advice that the supplied material cannot support, ask for the concrete problem or example, or agree a narrower promise before approval.
Ask the author to approve or adjust the angle, tone and outline. Stop before drafting the article until the angle and outline have been approved. A request to “write an article” alone does not approve an unseen proposal. Approval already given for a supplied angle and outline counts; do not ask again unnecessarily.
If site evidence or search data is unavailable, state the limitation and mark the resulting assumptions in the proposal. Ask for excerpts only when they are needed to make a useful recommendation.
4. Draft faithfully
Write the approved article in the agreed language and tone. Give each section a purpose and connect the ideas into a continuous argument. Use concrete examples, mechanisms, observations or evidence where they help the reader. Support the approved viewpoint without inventing quotes, statistics, credentials or lived experience. First-person narration can express the agreed position; personal memories, feelings and preferences must come from the author rather than being added to make the voice seem authentic.
Use the composition guidance in Editorial profile and composition to choose an opening, develop sections, address relevant objections and finish the piece. Treat these as craft choices suited to the approved form, not a universal article template.
Apply profile and evidence rules through the prose rather than narrating the writing process inside the article. Keep instructions about inventing details, tool availability and approval out of publishable text; include factual qualifications when they matter to the reader's understanding.
The author has the final say on their position. When sources contradict a factual assertion, show the discrepancy and propose wording that distinguishes verified facts, uncertainty, interpretation and opinion. An unconventional viewpoint can remain; an unsupported claim must not acquire a fabricated citation or be described as established evidence. If the author retains a disputed assertion, attribute it as their position and preserve relevant uncertainty.
Use search terms naturally where they name the actual subject. Headings and links should help readers. Preserve intentional literary or theatrical devices, including scenes, tension, dialogue, irony and expansive sentences, when they serve the agreed article. Label fictional illustrations where readers might otherwise mistake them for reported events.
5. Edit for quality in the actual language
Before showing the draft, perform distinct checks:
- Meaning and structure: the article preserves the author's thesis, answers the reader's need, progresses logically and gives each section new work. Remove contradictions, repetition and gaps; explain unfamiliar terms for the intended audience.
- Evidence: verify factual claims against inspected sources or supplied material. Preserve quotation accuracy and citation context. Keep opinions recognizable as opinions.
- Voice and tone: compare the draft with the agreed profile and site samples. Keep the intended character without imitating their wording or importing unsuitable conventions.
- Language and rhythm: correct grammar, spelling, syntax, punctuation and local usage. Rewrite translated idioms and unnatural phrasing. Read the prose as connected speech in that language; vary rhythm where useful, without imposing short sentences everywhere.
- Generic AI prose: replace empty openings, vague abstractions, inflated praise, stock transitions, repeated sentence patterns and mechanical summaries with specific content or remove them. Avoid decorative headings, redundant lists and forced engagement questions. Judge the passage in context; do not apply an English blacklist to every language or treat stylistic patterns as proof of AI authorship.
- SEO fit: ensure the title describes the article, the structure fits its search intent and links are relevant. Check that optimization has not distorted the argument or readability.
When the author requests or accepts an optional assisted language check, follow LanguageTool checks. Ordinary editorial proofreading remains part of every draft; an external checker is not automatically invoked.
6. Revise and deliver
Deliver the first draft as a title and article, then ask for feedback on fidelity to the author's thought, tone, structure and wording. Apply the feedback and rerun the affected quality checks before returning the final version. If feedback changes the angle or outline substantially, present the updated angle and outline and wait for approval before restructuring; a request for a different thesis does not approve a newly invented outline. If the author supplies and approves the replacement angle and outline, proceed directly. If the author accepts the draft unchanged, it becomes the final version.
Default to Markdown unless another format is requested. A separately labelled conclusion, summary, companion article, SEO title, meta description or slug is optional; propose relevant additions during the brief and include them only when requested or accepted. An article can have a natural ending without a mandatory “Conclusion” section. Keep editorial notes and unresolved questions separate from publishable prose.
Writing does not authorize publishing, changing the website or saving data in an external SEO service. Perform those actions only under a separate user request.
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.

