content-marketing
Skill8 starsChanged 7 months agoMITView on GitHub
Blog engine setup, CMS integration, SEO-optimized content workflows, and editorial calendars.
- Reads credentials
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
1
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 34
No internal linking — every post should link to 2-3 related posts
“Common” is measured: kept by at least 6 in 10 of the 4 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
Content Marketing
Rules
- Keyword-driven content: every blog post targets a primary keyword — use YepAPI
POST /v1/seo/keyword-researchto find volume and difficulty - CMS setup: use MDX with frontmatter (title, description, publishedAt, tags, slug) — works with Next.js, Astro, or any static site
- Editorial calendar: maintain a
content-calendar.jsonor database table with status (draft, review, scheduled, published), publish date, author, and target keyword - SEO checklist per post: meta title (<60 chars), meta description (<160 chars), one H1, structured headings, internal links, alt text on images
- Trend validation: use YepAPI
POST /v1/seo/keyword-suggestionsto find related topics and long-tail variations before committing to a content piece - Content types: mix informational (how-to, guides), commercial (comparisons, reviews), and transactional (landing pages) — aim for 60/30/10 split
- Publish workflow: draft -> review -> scheduled -> published — use status field to track, never publish without meta tags
- RSS feed: auto-generate from published posts — include full content or summary, publish date, and canonical URL
CMS Integration Patterns
- Headless CMS (Sanity, Contentful): fetch at build time with ISR, webhook to trigger rebuild on publish
- File-based (MDX):
content/blog/directory, frontmatter schema validation at build, dynamic route[slug] - Database-backed: posts table with status enum, slug unique index, full-text search index on title + body
Avoid
- Publishing without keyword research — content without search demand wastes effort
- Missing canonical URLs — causes duplicate content issues
- No internal linking — every post should link to 2-3 related posts
- Skipping meta descriptions — search engines will auto-generate poor ones
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- vivy-yi/xiaohongshu-skills★ 455same name
- OpenAnalystInc/10x-Team★ 8same name
- busyeugene/content-marketing-skills★ 1same name
- m-binimran/marketing-pack★ 1same name
- docaohieu2808/claude-skills★ 0same name
- vindreshsingh/engineering-skills★ 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 repository110 other files it gives its agents.
- yepapiSkill
- ab-testingSkill
- accessibilitySkill
- admin-panelSkill
- ai-agentsSkill
- ai-chatbotSkill
- ai-visibilitySkill
- analyticsSkill
- animationsSkill
- api-designSkill
- api-documentationSkill
- api-securitySkill
- auth-securitySkill
- authSkill
- background-jobsSkill
- backlink-researchSkill
- blog-engineSkill
- caching-strategySkill
- chartsSkill
- cli-toolsSkill
- code-reviewSkill
- command-paletteSkill
- comments-discussionsSkill
- competitor-researchSkill
- content-researchSkill
- content-strategySkill
- copywritingSkill
- cron-jobsSkill
- csrf-protectionSkill
- dark-modeSkill
- dashboard-designSkill
- databaseSkill
- data-encryptionSkill
- data-pipelinesSkill
- data-visualizationSkill
- dependency-securitySkill
- deploymentSkill
- drag-and-dropSkill
- drizzle-ormSkill
- e2e-testingSkill
- e-commerceSkill
- email-marketingSkill
- emailSkill
- error-handlingSkill
- error-securitySkill
- express-fastifySkill
- feature-flagsSkill
- file-uploadsSkill
- financial-planningSkill
- formsSkill
- funnel-analyticsSkill
- gdpr-complianceSkill
- git-workflowSkill
- i18nSkill
- image-optimizationSkill
- infinite-scrollSkill
- input-validationSkill
- invoice-generatorSkill
- keyword-researchSkill
- landing-pagesSkill
- The first 60 shown.
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.

