content-publisher
Skill35 starsChanged 8 months agoMITView on GitHub
Use when creating new blog posts or comparison pages for tinyagents.dev. Handles the full pipeline from keyword research to code change to deploy.
- Commits and pushes
1 other project uses a version of this.
Adopted by
Most recently taken up by
- neoforge-dev/forgetheir own version, first seen Oct 13, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- neoforge-dev/forge★ 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 repository5 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- public/llms.txtllms.txt
- ceoSkill
- cmoSkill
- keyword-researchSkill
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 5 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
No social media access — content lives on the site only
- Distinctive: line 13
All content is TypeScript data (not markdown files)
- Distinctive: line 14
Must pass pre-commit: tsc + eslint + related tests
- Very specific: line 21
Check .agents/keyword-research.md for existing research
- Very specific: line 33
Blog posts: Add to the posts array in src/lib/blog/posts.ts.
- Very specific: line 35
If posts.ts exceeds 200 lines, split into src/lib/blog/posts/[slug].ts
- Very specific: line 37
Compare pages: Create src/lib/seo/comparisons/[framework].ts.
- Distinctive: line 44
Add relatedLinks to the new content pointing to /learn and /compare pages
- Distinctive: line 45
Update related existing content to link back
- Very specific: line 57
Add to .agents/cmo-tracker.md shipped section.
- Very specific: line 58
Update .agents/keyword-research.md if new gaps found.
≈ “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
Content Publisher — tinyagents.dev
End-to-end workflow for publishing new SEO content to tinyagents.dev.
Constraints
- No social media access — content lives on the site only
- 200-line file limit on all source files
- All content is TypeScript data (not markdown files)
- Must pass pre-commit: tsc + eslint + related tests
Workflow
1. Research (use keyword-research skill)
- Identify target keyword and who ranks for it
- Find the content gap (our unique angle)
- Check
.agents/keyword-research.mdfor existing research
2. Decide Content Type
| Type | Where it lives | When to use |
| Blog post | src/lib/blog/posts.ts | Thought leadership, unique angles, shareable |
| Compare page | src/lib/seo/comparisons/[name].ts | "[Framework] vs" keywords |
| Learn article | Already exists per lesson | Expanding lesson content for depth |
3. Write Content
Blog posts: Add to the posts array in src/lib/blog/posts.ts. Fields:
- slug, title, description, date, keywords, sections[], cta, relatedLinks[]
- If posts.ts exceeds 200 lines, split into
src/lib/blog/posts/[slug].ts
Compare pages: Create src/lib/seo/comparisons/[framework].ts. Copy pattern from langchain.ts:
- slug, name, title, description, keywords, intro, rows[], verdict, sections[], faqs[]
- Add to
src/lib/seo/comparisons/index.ts
4. Add Schema + Cross-Links
- Compare pages get: CompareJsonLd + FaqJsonLd automatically (via page route)
- Blog posts get: BlogPosting JSON-LD automatically
- Add relatedLinks to the new content pointing to /learn and /compare pages
- Update related existing content to link back
5. Build + Commit + Push
npx tsc --noEmit # Must pass
npm run build # Must pass
git add [files]
git commit -m "..."
git push origin master # Auto-deploys via Railway6. Update Tracker
Add to .agents/cmo-tracker.md shipped section.
Update .agents/keyword-research.md if new gaps found.
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.

