blog-post
Skill1 starsChanged 7 months agoMITView on GitHub
Write blog posts from ideation to publish-ready draft. Trigger with "write a blog post about", "draft a post on", "create an article about", "blog about", or when the user needs a how-to, listicle, opinion piece, or tutorial post with SEO optimization and calls to action.
27 other projects use a version of this.
Adopted by
Most recently taken up by
- neomjs/neo-agent-skillstheir own version, first seen Nov 15, 2026
- alfredang/ai-cmstheir own version, first seen Nov 7, 2026
- alfredang/ai4kidstheir own version, first seen Nov 2, 2026
- rsdlt/rsdlt.github.iotheir own version, first seen Oct 25, 2026
- langchain-ai/deepagentstheir own version, first seen Oct 13, 2026
- nteract/semiotictheir own version, first seen Oct 8, 2026
Used with
Projects with it also use remote-db-sync, tia-frontend-design-site and 3 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
alfredangSkillremote-db-sync
Push local DB content (menus, settings, taxonomy, pages, posts) to the production database via bearer-token-protected sync APIs. Use when the user wants to publish local CMS/admin edits to the live site without logging into the production admin UI, or to extend the sync surface for new tables. Triggers — "push to production", "sync to remote", "deploy menu/settings/page/post", "the live site doesn't show my change".
Also in 3 projects that use this
alfredangSkilltia-frontend-design-site
This site's own design system for Tertiary Infotech Academy (tertiaryinfotech.edu.sg) — light mint public pages, a dark animated matrix-green hero with the fibre-optic globe, generated artwork, Exo 2 + Inter, compact non-template layouts, live-online copy. Load with the user-level tia-frontend-design skill whenever building, restyling or reviewing ANY UI in this repo.
Also in 3 projects that use this
ukunal91appSkilllead-magnets
When the user wants to create, plan, or optimize a lead magnet for email capture or lead generation. Also use when the user mentions "lead magnet," "gated content," "content upgrade," "downloadable," "ebook," "cheat sheet," "checklist," "template download," "opt-in," "freebie," "PDF download," "resource library," "content offer," "email capture content," "Notion template," "spreadsheet template," or "what should I give away for emails." Use this for planning what to create and how to distribute it. For interactive tools as lead magnets, see free-tool-strategy. For writing the actual content, see copywriting. For the email sequence after capture, see email-sequence.
Also in 3 projects that use this
VercelSkillfind-skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
Also in 3 projects that use this
- +1 more from alfredang
Other versions27 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 27
- langchain-ai/deepagents★ 31ksame name
- samuelclay/NewsBlur★ 7.7ksame name
- nteract/semiotic★ 2.7ksame name
- AlemTuzlak/skills★ 45same name
- byronxlg/skillfold★ 15same name
- neomjs/neo-agent-skills★ 11same name
- ropensci-review-tools/ropensci-skills★ 8same name
- xcrrr/claude-skills★ 6same name
- alfredang/ai-cms★ 4same name
- broomva/skills★ 4same name
17 more not listed
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 repository164 other files it gives its agents.
- instrument-data-to-allotropeSkill
- literature-reviewSkill
- nextflow-developmentSkill
- scientific-problem-selectionSkill
- scvi-toolsSkill
- single-cell-rna-qcSkill
- discover-brandSkill
- enforce-voiceSkill
- generate-guidelinesSkill
- csat-reportSkill
- customer-escalationSkill
- customer-researchSkill
- draft-responseSkill
- kb-articleSkill
- sentiment-analysisSkill
- ticket-triageSkill
- analyzeSkill
- build-dashboardSkill
- create-vizSkill
- data-context-extractorSkill
- data-modelingSkill
- data-pipelineSkill
- etl-designSkill
- explore-dataSkill
- sql-queriesSkill
- statistical-analysisSkill
- validate-dataSkill
- write-querySkill
- accessibility-reviewSkill
- component-librarySkill
- design-critiqueSkill
- design-handoffSkill
- design-systemSkill
- frontend-designSkill
- research-synthesisSkill
- user-researchSkill
- ux-copySkill
- wireframingSkill
- Agent DevelopmentSkill
- CLAUDE.md ManagementSkill
- MCP Server BuilderSkill
- Plugin DevelopmentSkill
- Prompt EngineeringSkill
- Skill CreatorSkill
- curriculum-designSkill
- lesson-planningSkill
- quiz-generatorSkill
- study-guideSkill
- tutoringSkill
- api-designSkill
- architectureSkill
- ci-cd-pipelineSkill
- code-reviewSkill
- database-migrationSkill
- debugSkill
- dependency-auditSkill
- deploy-checklistSkill
- documentationSkill
- error-handlingSkill
- git-workflowSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
11 rules. 0 are common, 11 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 23 edited versions we read keep these.
11
Distinctive
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 31
Write a complete blog post from topic research through publish-ready draft, including SEO optimization, internal structure, and calls to …
- Distinctive: line 56
Write the full post following the approved outline:
- Distinctive: line 59
Body: Use subheadings (H2/H3) for scanability.
- Distinctive: line 76
Ensure the URL slug is concise and keyword-rich.
- Distinctive: line 82
Check readability: aim for Flesch-Kincaid grade 7-9 for general audiences.
- Distinctive: line 83
Remove filler words and passive voice where possible.
- Distinctive: line 84
Verify all claims have supporting evidence or examples.
- Distinctive: line 85
Ensure the CTA is specific and actionable, not generic.
- Distinctive: line 122
Always present the outline for approval before writing the full draft.
- Distinctive: line 124
Use concrete examples over abstract advice — "We reduced deploy time by 40%" beats "It improves efficiency."
- Distinctive: line 128
If the user provides a brand voice guide or style reference, follow it strictly.
“Common” is measured: kept by at least 6 in 10 of the 23 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
Blog Post Writing
Write a complete blog post from topic research through publish-ready draft, including SEO optimization, internal structure, and calls to action.
Workflow
Step 1: Research and Angle
Clarify the topic and develop a strong angle:
- Confirm the target audience, tone, and desired format with the user.
- Identify the core value proposition: what will the reader learn, feel, or do after reading?
- Note 3-5 key points or subtopics that must be covered.
- Identify a unique angle or hook that differentiates the post from existing content.
Step 2: Outline
Build a structured outline before drafting:
- Title options: Propose 3 headline variants (curiosity-driven, benefit-driven, direct).
- Introduction: Hook, context, and thesis statement.
- Body sections: 3-7 sections with subheadings, each covering one key point.
- Conclusion: Summary, key takeaway, and call to action.
- Present the outline to the user for approval before drafting.
Step 3: Draft
Write the full post following the approved outline:
- Introduction: Open with a hook (question, stat, story, or bold claim). State the problem and preview the solution. Keep it under 150 words.
- Body: Use subheadings (H2/H3) for scanability. Include examples, data, or anecdotes in each section. Vary paragraph length (2-4 sentences). Use transition phrases between sections.
- Conclusion: Restate the key takeaway. Include a clear call to action (subscribe, comment, try, download).
Format-specific guidance:
- How-to: Numbered steps, prerequisites, expected outcomes per step.
- Listicle: Consistent item structure, most compelling items first and last.
- Opinion: Strong thesis, counterarguments addressed, evidence-backed claims.
- Tutorial: Code blocks or screenshots, prerequisites section, troubleshooting tips.
Step 4: SEO Optimization
Apply on-page SEO best practices:
- Include the primary keyword in the title, first paragraph, one H2, and conclusion.
- Suggest a meta description (150-160 characters) with the keyword and a benefit statement.
- Recommend 2-3 internal link placements and 1-2 external authority links.
- Suggest alt text for any proposed images.
- Ensure the URL slug is concise and keyword-rich.
Step 5: Polish
Final quality pass:
- Check readability: aim for Flesch-Kincaid grade 7-9 for general audiences.
- Remove filler words and passive voice where possible.
- Verify all claims have supporting evidence or examples.
- Ensure the CTA is specific and actionable, not generic.
Output Format
## [Blog Post Title]
**Meta description**: <150-160 chars>
**Target keyword**: <primary keyword>
**Suggested URL slug**: /blog/<slug>
**Estimated reading time**: <X> min
---
[Full blog post in Markdown with H2/H3 subheadings]
---
## SEO Notes
- **Internal links**: [suggested placements]
- **External links**: [authority sources]
- **Image suggestions**: [descriptions with alt text]Examples
User: "Write a blog post about remote team productivity" Action: Clarify audience (managers vs. ICs), propose a how-to format, outline 5 strategies with examples, draft with SEO targeting "remote team productivity tips."
User: "Listicle on 10 JavaScript testing tools" Action: Research current tools, outline with consistent item format (name, what it does, pros/cons, when to use), draft with comparison angle, optimize for "JavaScript testing tools 2024."
User: "Opinion post arguing that monorepos are better for startups" Action: Build thesis with 3 supporting arguments, address polyrepo counterarguments, include real-world examples, draft with authoritative but accessible tone.
Best Practices
- Always present the outline for approval before writing the full draft.
- Front-load value: readers decide to stay or leave in the first 100 words.
- Use concrete examples over abstract advice — "We reduced deploy time by 40%" beats "It improves efficiency."
- Break up long sections with bullet points, pull quotes, or callout boxes.
- End every post with a single, clear CTA — multiple CTAs dilute effectiveness.
- Match tone to audience: conversational for developer blogs, authoritative for B2B, warm for consumer.
- If the user provides a brand voice guide or style reference, follow it strictly.
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.

