content-engine
Create platform-native content systems for X, LinkedIn, TikTok, YouTube, newsletters, and repurposed multi-platform campaigns. Use when the user wants social posts, threads, scripts, content calendars, or one source asset adapted cleanly across platforms.
Best use case
content-engine is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Create platform-native content systems for X, LinkedIn, TikTok, YouTube, newsletters, and repurposed multi-platform campaigns. Use when the user wants social posts, threads, scripts, content calendars, or one source asset adapted cleanly across platforms.
Teams using content-engine should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/content-engine/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How content-engine Compares
| Feature / Agent | content-engine | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Create platform-native content systems for X, LinkedIn, TikTok, YouTube, newsletters, and repurposed multi-platform campaigns. Use when the user wants social posts, threads, scripts, content calendars, or one source asset adapted cleanly across platforms.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agents for Marketing
Discover AI agents for marketing workflows, from SEO and content production to campaign research, outreach, and analytics.
AI Agent for YouTube Script Writing
Find AI agent skills for YouTube script writing, video research, content outlining, and repeatable channel production workflows.
SKILL.md Source
# Content Engine Turn one idea into strong, platform-native content instead of posting the same thing everywhere. ## When to Activate - writing X posts or threads - drafting LinkedIn posts or launch updates - scripting short-form video or YouTube explainers - repurposing articles, podcasts, demos, or docs into social content - building a lightweight content plan around a launch, milestone, or theme ## First Questions Clarify: - source asset: what are we adapting from - audience: builders, investors, customers, operators, or general audience - platform: X, LinkedIn, TikTok, YouTube, newsletter, or multi-platform - goal: awareness, conversion, recruiting, authority, launch support, or engagement ## Core Rules 1. Adapt for the platform. Do not cross-post the same copy. 2. Hooks matter more than summaries. 3. Every post should carry one clear idea. 4. Use specifics over slogans. 5. Keep the ask small and clear. ## Platform Guidance ### X - open fast - one idea per post or per tweet in a thread - keep links out of the main body unless necessary - avoid hashtag spam ### LinkedIn - strong first line - short paragraphs - more explicit framing around lessons, results, and takeaways ### TikTok / Short Video - first 3 seconds must interrupt attention - script around visuals, not just narration - one demo, one claim, one CTA ### YouTube - show the result early - structure by chapter - refresh the visual every 20-30 seconds ### Newsletter - deliver one clear lens, not a bundle of unrelated items - make section titles skimmable - keep the opening paragraph doing real work ## Repurposing Flow Default cascade: 1. anchor asset: article, video, demo, memo, or launch doc 2. extract 3-7 atomic ideas 3. write platform-native variants 4. trim repetition across outputs 5. align CTAs with platform intent ## Deliverables When asked for a campaign, return: - the core angle - platform-specific drafts - optional posting order - optional CTA variants - any missing inputs needed before publishing ## Quality Gate Before delivering: - each draft reads natively for its platform - hooks are strong and specific - no generic hype language - no duplicated copy across platforms unless requested - the CTA matches the content and audience
Related Skills
content-hash-cache-pattern
Cache expensive file processing results using SHA-256 content hashes — path-independent, auto-invalidating, with service layer separation.
wpds
Use when building UIs leveraging the WordPress Design System (WPDS) and its components, tokens, patterns, etc.
wp-wpcli-and-ops
Use when working with WP-CLI (wp) for WordPress operations: safe search-replace, db export/import, plugin/theme/user/content management, cron, cache flushing, multisite, and scripting/automation with wp-cli.yml.
wp-rest-api
Use when building, extending, or debugging WordPress REST API endpoints/routes: register_rest_route, WP_REST_Controller/controller classes, schema/argument validation, permission_callback/authentication, response shaping, register_rest_field/register_meta, or exposing CPTs/taxonomies via show_in_rest.
wp-project-triage
Use when you need a deterministic inspection of a WordPress repository (plugin/theme/block theme/WP core/Gutenberg/full site) including tooling/tests/version hints, and a structured JSON report to guide workflows and guardrails.
wp-plugin-development
Use when developing WordPress plugins: architecture and hooks, activation/deactivation/uninstall, admin UI and Settings API, data storage, cron/tasks, security (nonces/capabilities/sanitization/escaping), and release packaging.
wp-playground
Use for WordPress Playground workflows: fast disposable WP instances in the browser or locally via @wp-playground/cli (server, run-blueprint, build-snapshot), auto-mounting plugins/themes, switching WP/PHP versions, blueprints, and debugging (Xdebug).
wp-phpstan
Use when configuring, running, or fixing PHPStan static analysis in WordPress projects (plugins/themes/sites): phpstan.neon setup, baselines, WordPress-specific typing, and handling third-party plugin classes.
wp-performance
Use when investigating or improving WordPress performance (backend-only agent): profiling and measurement (WP-CLI profile/doctor, Server-Timing, Query Monitor via REST headers), database/query optimization, autoloaded options, object caching, cron, HTTP API calls, and safe verification.
wp-interactivity-api
Use when building or debugging WordPress Interactivity API features (data-wp-* directives, @wordpress/interactivity store/state/actions, block viewScriptModule integration, wp_interactivity_*()) including performance, hydration, and directive behavior.
wp-block-themes
Use when developing WordPress block themes: theme.json (global settings/styles), templates and template parts, patterns, style variations, and Site Editor troubleshooting (style hierarchy, overrides, caching).
wp-block-development
Use when developing WordPress (Gutenberg) blocks: block.json metadata, register_block_type(_from_metadata), attributes/serialization, supports, dynamic rendering (render.php/render_callback), deprecations/migrations, viewScript vs viewScriptModule, and @wordpress/scripts/@wordpress/create-block build and test workflows.