Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Content Engine

ASecurity

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.

2 stars
0 votes
0 copies
2 views
Added 9/24/2026
ai-agentsgoperformance

Security Analysis

A100/100

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-code

Installs 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.

Security grade badge for Content Engine
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/mtent-content-engine/badge)](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.

Download with Pro
Files
SKILL.md
---
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.

Attribution

MTEntMTEnt
View sourceSee grades on GitHubMore from MTEnt →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698621 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →