Skill Introduction

Overview

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.

Core value

Turns reusable Documentation know-how into an installable skill, helping users complete github, community work faster.

Target users

Developers, testers, and maintainers who handle Documentation tasks in Focus Code.
Teams that already trust workflows or content from affaan-m.
Users who want standardized prompts, steps, or conventions instead of repeating setup work.

Best practices

Read the skill content first to confirm required inputs, expected outputs, and dependencies.
Try it on a small task before relying on it for critical work.
Add project-specific constraints such as coding style, target platform, test expectations, and delivery format.
For external sources, verify the source link, version, and recent maintenance activity.

Best use cases

Tasks related to github, community that need a reusable execution flow.
Converting a community repo, team convention, or personal workflow into day-to-day assistance.
Starting from a proven skill instead of writing prompts or procedures from scratch.

Limits and boundaries

Results depend on the quality of the original skill content and may need human correction.
It does not replace code review, tests, security review, or professional judgment.
External tools, APIs, account permissions, and local dependencies still need separate setup.

Differentiation

Structured around Documentation, making it easier to discover and reuse than loose prompt snippets.
Marked as GitHub, which helps users judge trust and maintenance expectations.
Keeps the original source link available for repository, documentation, or discussion follow-up.
Tagged with github, community, so it can be filtered by concrete task intent.

Detail Preview

SKILL.md

Primary filemarkdown3 KB

name: content-engine description: 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. origin: ECC

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

Adapt for the platform. Do not cross-post the same copy.
Hooks matter more than summaries.
Every post should carry one clear idea.
Use specifics over slogans.
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

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

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:

anchor asset: article, video, demo, memo, or launch doc
extract 3-7 atomic ideas
write platform-native variants
trim repetition across outputs
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

content engine