seo-write
Skill0 starsChanged 4 months agoMITView on GitHub
Write an SEO-optimized blog post for the target website from the topic queue or a given topic. Use when the user asks to write a blog post, article, or content for a keyword/topic.
- Reads credentials
1 other project uses a version of this.
Adopted by
Most recently taken up by
- lsidore/seo-mdtheir own version, first seen Jul 7, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- lsidore/seo-md★ 1same 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 repository3 other files it gives its agents.
- seo-auditSkill
- seo-fixSkill
- seo-statusSkill
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 11
Read config/project-notes.md if it exists for repo-specific conventions.
- Distinctive: line 13
Write 1200–1800 words, genuinely useful, human-first.
- Distinctive: line 15
Never use third-party trademarked brand names in the title or headings.
- Very specific: line 16
Run the build (BUILD_CMD, default npm run build) and make sure it succeeds.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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 Write
Draft a blog post in the target website repo, following its existing conventions.
- Determine the topic: the user's explicit topic, or the highest-scored
approvedtopic in the database (data/seo.db, tabletopics) — query it withnode -eand better-sqlite3, or ask the user. - Read
config/project-notes.mdif it exists for repo-specific conventions. - In the target repo (
TARGET_REPOin.env): find where blog content lives, study 1–2 existing posts, and match their file structure, metadata, and structured-data patterns exactly. - Write 1200–1800 words, genuinely useful, human-first. Structure for AI citability: H2/H3 questions with direct answers in the first sentence, key-takeaways block near the top, FAQPage JSON-LD with 4–6 real questions if the repo supports it.
- Register the post wherever the repo lists posts (blog index, sitemap). Add 2–3 internal links.
- Never use third-party trademarked brand names in the title or headings.
- Run the build (
BUILD_CMD, defaultnpm run build) and make sure it succeeds. - Report the new slug, title, and files touched. The user reviews, commits, and deploys.
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.

