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
prompt-engineering
System prompt architecture, few-shot design, chain-of-thought, structured output (JSON mode, response_format), tool use patterns, prompt versioning, and regression testing. Use when writing, reviewing, or debugging any LLM prompt — system prompts, user templates, or tool descriptions.
privacy-engineering
Privacy engineering patterns — PII classification and inventory, GDPR consent flows, data minimization, right-to-erasure implementation, pseudonymization/encryption, privacy-by-design architecture, and DPIA checklist.
platform-engineering
Platform Engineering: Internal Developer Platforms (IDP), CNCF Platform definition, Team Topologies, IDP components (Service Catalog, Self-Service Infra, Golden Paths, Developer Portal), platform maturity model, make-vs-buy (Backstage vs Port vs Cortex), adoption strategy, DORA correlation.
engineering-metrics
Engineering effectiveness metrics: DORA Four Keys (Deployment Frequency, Lead Time, Change Failure Rate, MTTR), SPACE Framework (Satisfaction, Performance, Activity, Communication, Efficiency), Goodhart's Law pitfalls, Velocity vs. Outcomes, Developer Experience measurement.
data-engineering
Data engineering patterns: dbt for SQL transformation (models, tests, incremental), Dagster for orchestration (assets, jobs, sensors), data quality checks, warehouse patterns (BigQuery/Snowflake/Redshift), and modern data stack setup. Covers the ELT pipeline from raw ingestion to analytics-ready models.
content-hash-cache-patterns
Cache expensive file processing results using SHA-256 content hashes — path-independent, auto-invalidating, with service layer separation.
chaos-engineering
Chaos Engineering for production resilience: steady-state hypothesis design, fault injection tools (Chaos Monkey, Litmus, Gremlin, Toxiproxy, tc netem), GameDay format, and maturity model from manual to continuous chaos.
zero-trust-patterns
Zero-Trust security patterns — mTLS between microservices (Istio/SPIFFE), SPIRE workload identity, OPA/Envoy authorization, NetworkPolicy default-deny-all, short-lived credentials, service mesh security, and Kubernetes RBAC hardening.
wireframing
Wireframing and prototyping workflow: fidelity levels (lo-fi sketch → mid-fi wireframe → hi-fi prototype), tool selection (Figma, Excalidraw, Balsamiq), user flow diagrams, wireframe annotation standards, information architecture (IA) mapping, and the handoff from wireframe to visual design. For developers who need to communicate UI structure before writing code.
webrtc-patterns
WebRTC patterns — peer connection setup, ICE/STUN/TURN configuration, signaling server design, SFU vs mesh topology, screen sharing, media track management, and reconnect/ICE restart handling.
webhook-patterns
Webhook patterns for receiving, verifying (HMAC), and idempotently processing third-party events. Covers Stripe, GitHub, and generic webhook patterns, delivery guarantees, retry handling, and testing.
web-performance
Web performance optimization: Core Web Vitals (LCP, CLS, INP), Lighthouse CI with budget configuration, bundle analysis (webpack-bundle-analyzer, vite-bundle-visualizer), hydration performance, network waterfall reading, image optimization (WebP/AVIF, srcset), and font performance.