seo-article
Skill0 starsChanged 6 days agoMITView on GitHub
Plan and write a blog article meant to rank in Google for a keyword. Use when the user gives a keyword or topic and asks for a blog post, SEO article, "content that ranks", or to rewrite an existing post for search.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- AI-XLabs-Innovation/launchranked-agenttheir own version, first seen Oct 15, 2026
- yori44/claude-skillstheir own version, first seen Aug 22, 2026
- kronus-tech/kronustheir own version, first seen Mar 30, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- kronus-tech/kronus★ 4same name
- AI-XLabs-Innovation/launchranked-agent★ 0same name
- yori44/claude-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 repository24 other files it gives its agents.
- api-docsSkill
- changelogSkill
- ci-failure-fixSkill
- code-reviewSkill
- commit-messageSkill
- competitor-analysisSkill
- data-analystSkill
- debug-detectiveSkill
- dependency-upgradeSkill
- dockerizeSkill
- email-replierSkill
- eval-promptSkill
- incident-postmortemSkill
- meeting-notesSkill
- migration-safetySkill
- pr-descriptionSkill
- product-specSkill
- readme-writerSkill
- refactor-safelySkill
- research-briefSkill
- security-checkSkill
- sql-helperSkill
- support-replySkill
- write-testsSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
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 13
Ask the user for, or mark as [TO ADD]:
- Distinctive: line 27
Use the keyword and close variants where natural: H1, first paragraph, one H2, meta.
- Very specific: line 32
Every statistic, price, date or study needs a source you opened, linked inline.
- Distinctive: line 33
Never invent quotes, studies, expert names or "according to" attributions.
≈ “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
SEO article writer
1. Intent and competition
- Classify the intent: learn (guide), compare (X vs Y, best X), buy (product/category page, not an article), fix (troubleshooting steps). If the intent is "buy", say an article is the wrong format.
- If you have web search: look at the top results for the exact keyword. Note their format, length range, the subtopics they all cover (the baseline) and what none of them covers (your angle). If you do not have web search, say the outline is based on your judgment, not on the current results.
2. Collect what makes it worth ranking
Ask the user for, or mark as [TO ADD]:
- first-hand experience: their own tests, cases, screenshots, numbers, opinions
- product or business details the article should mention
- the site's existing pages to link to (real URLs) An article with nothing original is a rewrite of the top 10. Say so if the user has nothing to add.
3. Outline (show it before writing a long article)
- H1 containing the keyword, written for a human.
- H2s that follow the order a reader needs; each answers one sub-question.
- FAQ with 3-5 questions only if you found them (People Also Ask, forums, the user's support inbox). Otherwise skip the FAQ rather than invent questions.
4. Write
- The first 2-3 sentences answer the query directly. No intro about the topic's importance.
- Short paragraphs, specific examples, a table or checklist where readers compare or follow steps.
- Use the keyword and close variants where natural: H1, first paragraph, one H2, meta. No stuffing.
- Length is what the topic needs, roughly in the range of what ranks. Do not pad to a word count.
- Banned filler: "In today's fast-paced world", "It's important to note", "In conclusion", "game-changer".
5. Facts
- Every statistic, price, date or study needs a source you opened, linked inline. If you cannot verify one, write
[SOURCE NEEDED: claim]or remove the claim. - Never invent quotes, studies, expert names or "according to" attributions.
- Time-sensitive facts (prices, versions, laws): add "as of
<month year>".
Output
- Intent and angle (2 lines).
- Meta title (<= 60 characters) and meta description (<= 155), keyword included naturally. Suggested URL slug.
- The article in Markdown.
- Internal links: only to URLs the user gave you, with anchor text. If none were given, say which kinds of pages to link to.
- Checklist of every
[TO ADD]and[SOURCE NEEDED]left in the text.
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.