Transform one idea into platform-native content across X, LinkedIn, TikTok, YouTube, and newsletters without cross-posting.
Automate repetitive workflows and reduce manual effort
Example: Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example: Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example: Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Time estimate: 15-45 minutes depending on use case complexity
Prerequisites
Submit your Claude Code skill and start earning
epx add affaan-m/everything-claude-code --skill content-engineCompatible with
Supported agents
Adapts source assets (articles, videos, demos, docs) into distinct platform variants with native hooks, pacing, and CTAs
Covers five platforms with specific guidance: X (fast opens, one idea per post), LinkedIn (strong first lines, explicit lessons), short video (attention-grabbing first 3 seconds), YouTube (early results, visual refresh every 20-30 seconds), and n
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versioncontent-engineExecute the skills CLI command in your project's root directory to begin installation:
epx add affaan-m/everything-claude-code --skill content-engineFetches content-engine from affaan-m/everything-claude-code and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
.cursor/skills/content-engine
Restart Cursor to activate content-engine. Access via /content-enginein your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
java-coding-standards
affaan-m/everything-claude-code · Backend · same repo
market-research
affaan-m/everything-claude-code · Productivity · same repo
frontend-slides
affaan-m/everything-claude-code · Frontend · same repo
strategic-compact
affaan-m/everything-claude-code · Productivity · same repo
pytorch-patterns
affaan-m/everything-claude-code · Productivity · same repo
seo-content-writing
aaaaqwq/claude-code-skills · Marketing · tag: content
I recommend content-engine for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Solid pick for teams standardizing on skills: content-engine is focused, and the summary matches what you get after install.
content-engine reduced setup friction for our internal harness; good balance of opinion and flexibility.
Keeps context tight: content-engine is the kind of skill you can hand to a new teammate without a long onboarding doc.
I recommend content-engine for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Solid pick for teams standardizing on skills: content-engine is focused, and the summary matches what you get after install.
content-engine has been reliable in day-to-day use. Documentation quality is above average for community skills.
Registry listing for content-engine matched our evaluation — installs cleanly and behaves as described in the markdown.
Useful defaults in content-engine — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
content-engine is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 75