Design the content system: content jobs, themes and clusters from customer and product evidence, format selection, prioritization, production-ready briefs, distribution and reuse, CMS content model, editorial governance, and freshness and retirement rules. Use when deciding what content should exist, why, and how it will be maintained; use page-copy or organic-social to produce individual pieces.
Pro scans all 3 files and shows the line behind each finding
Scanned 9/24/2026
npx -y skills add MTEnt/special-skills --skill content-engine --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Content Engine?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/mtent-content-engine)More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.
---
name: content-engine
description: Design the content system: content jobs, themes and clusters from customer and product evidence, format selection, prioritization, production-ready briefs, distribution and reuse, CMS content model, editorial governance, and freshness and retirement rules. Use when deciding what content should exist, why, and how it will be maintained; use page-copy or organic-social to produce individual pieces.
license: MIT
metadata:
version: "2.0.0"
author: MTEnt
---
# Content Engine
Treat content as a maintained product serving an audience decision, not a publishing quota.
If `.agents/marketing-context.md` exists, read it first; it is the truth file every skill in this hub shares, and its evidence states are constraints. Read [content-system.md](references/content-system.md) for content jobs, searchable versus shareable work, themes, formats, prioritization, the brief contract, distribution, CMS, and governance.
## Operating contract
1. Define audience, situation, content job, business relationship, evidence advantage, distribution access, and capacity.
2. Derive themes from customer, product, search, sales, support, research, and industry evidence; separate searchable, shareable, sales, product, and lifecycle content where their jobs differ.
3. Prioritize a supportable portfolio and write production-ready briefs.
4. Plan distribution and reuse while designing the source asset.
5. Define ownership, freshness, performance, consolidation, and retirement.
Do not create volume targets detached from value or capacity, and do not mechanically slice one asset into contextless fragments.
## Return
Strategy, prioritized roadmap, briefs, distribution plan, governance, and measurement.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!