create-post
Skill7 starsChanged 19 days agoMITView on GitHub
Add an OpenBlog Markdown post with valid frontmatter and structure when the user provides body or brief. Use when drafting or adding a blog article — not autonomous content generation.
In this repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- audit-seoSkill
- blog-cmsSkill
- integrate-product-siteSkill
- publishSkill
- setup-blog-moduleSkill
- validate-blog-seoSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Read AGENTS.md and inspect existing posts in content/blog/.
- Distinctive: line 18
Write Markdown body with:
- Very specific: line 22
Run npm run validate:posts in templates/next.
- Very specific: line 24
Create the file at templates/next/content/blog/{slug}.md.
≈ “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
Create Post
Guardrail: The user provides the article body, outline, or brief. This skill ensures valid frontmatter, filename/slug alignment, and Markdown structure — it is not an autonomous article factory.
For content strategy, keyword targeting, GEO, or post optimization → use marketing-skills.
Steps
- Read
AGENTS.mdand inspect existing posts incontent/blog/. - Confirm the user supplied content or a clear brief; do not invent long-form copy without input.
- Choose a unique kebab-case
slugmatching the filename. - Write frontmatter that passes
postFrontmatterSchema; follow the article copy responsibilities inAGENTS.mdinstead of substituting fields for one another. Select existing author IDs fromcontent/authors/and an ordered, uniquecategoriesID list fromcontent/categories/. Ancestors are derived; do not repeat them merely to populate parent archives. OptionalarticleTypefollows the independent values defined inAGENTS.md, not a layout name. Do not derive identities, category URLs, or credentials from display names. Tags are non-link labels, not archive-page destinations. - Write Markdown body with:
- One
#title (optional; stripped if duplicate of frontmatter title) ##sections for structure- Internal links to other posts using
/blog/{slug}paths
- One
- Run
npm run validate:postsintemplates/next.
Create the file at templates/next/content/blog/{slug}.md.
Frontmatter template
---
title: ""
description: ""
dek: ""
excerpt: ""
slug: ""
date: "YYYY-MM-DD"
authors: ["existing-author-id"] # select actual IDs from content/authors/
categories: ["existing-category-id"] # select actual IDs from content/categories/
tags: []
draft: false
---Related skills
- Pre-publish SEO checks?
validate-blog-seo - Ready to merge?
publish
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.

