technical-blog-writer
Skill3 starsChanged 11 days agoMITView on GitHub
Write developer-focused technical blog posts that rank in search and get cited by AI answer engines. Use when the user asks for a tutorial, how-to, comparison or explainer on programming, AI engineering, DevOps or web development.
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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 22
All code must be complete enough to run.
- Distinctive: line 23
No filler intros ("In today's fast-paced world").
- Distinctive: line 24
Prefer concrete numbers over adjectives.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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
Technical Blog Writer
Before writing
Confirm: target keyword and search intent, reader level (beginner, working dev, senior), stack and versions, and the one outcome the reader should get. If missing, assume a working developer and state the assumption in one line.
Structure
- Title: specific, includes the keyword, promises an outcome.
- Answer first: 2-3 sentences that solve or summarise the problem before any backstory.
- Prerequisites: versions and tools, as a short list.
- Steps: each H2 is one action. Show the code, then explain why in 1-3 sentences.
- Common errors: real error messages and fixes.
- Comparison or trade-offs: a table when choosing between approaches.
- FAQ: 3-5 questions real developers search, one-paragraph answers.
- Next steps: links to related posts and docs.
Quality bar
- All code must be complete enough to run. Pin versions. Mark anything you did not run as untested.
- No filler intros ("In today's fast-paced world"). No claims without a source or a reproducible example.
- Prefer concrete numbers over adjectives. Cite official docs for API behaviour.
- Short paragraphs, descriptive headings, one idea per section.
Output
Return: SEO title, meta description (155 chars max), URL slug, the full post in Markdown, and suggested JSON-LD (BlogPosting + FAQPage).
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- Cure-Consulting-Group/ProductEngineeringSkills★ 3same 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.
- mcp-server-builderSkill
- seo-geo-auditSkill
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.