Source profileQuality 72/100

affaan-m/ECC/.cursor/skills/content-engine/SKILL.md

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.

Source repository stars
234,327
Declared platforms
0
Static risk flags
0
Last source update
2026-07-27
Source checked
2026-07-28

Decision brief

What it does—and where it fits

Turn one idea into strong, platform-native content instead of posting the same thing everywhere.

Best for

  • Use when the user wants social posts, threads, scripts, content calendars, or one source asset adapted cleanly across platforms.

Not for

  • Tasks that require unconfirmed production actions or broad system permissions.
  • Environments where the pinned source and install steps cannot be inspected.

Compatibility matrix

Platform support, with evidence labels

PlatformStatusEvidenceWhat to check
CodexNot declaredNo explicit evidencePortability before use
Claude CodeNot declaredNo explicit evidencePortability before use
CursorNot declaredNo explicit evidencePortability before use
Gemini CLINot declaredNo explicit evidencePortability before use
Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource
npx skills add https://github.com/affaan-m/ECC --skill ".cursor/skills/content-engine"
Safe inspection promptEditorial

Inspect the Agent Skill "content-engine" from https://github.com/affaan-m/ECC/blob/4e973d3eaf92d97f8d2e2d8abb39d8bdc8711b38/.cursor/skills/content-engine/SKILL.md at commit 4e973d3eaf92d97f8d2e2d8abb39d8bdc8711b38. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

Workflow

What the source asks the agent to do

  1. 01

    When to Activate

    writing X posts or threads

    writing X posts or threadsdrafting LinkedIn posts or launch updatesscripting short-form video or YouTube explainers
  2. 02

    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 engageme…

    source asset: what are we adapting fromaudience: builders, investors, customers, operators, or general audienceplatform: X, LinkedIn, TikTok, YouTube, newsletter, or multi-platform
  3. 03

    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.

    Adapt for the platform. Do not cross-post the same copy.Hooks matter more than summaries.Every post should carry one clear idea.
  4. 04

    Platform Guidance

    open fast

    open fastone idea per post or per tweet in a threadkeep links out of the main body unless necessary

Permission review

Static risk signals and limitations

No configured static risk pattern was detected

This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.

Evidence record

Why each signal appears

EvidenceSourceComputedTestedEditorial
SignalValueEvidence typeMeaning
Quality score72/100ComputedDocumentation, specificity, maintenance, and trust rules
Repository stars234,327SourceRepository attention, not individual Skill quality
Compatibility0 platformsSourceDeclared in the catalog source record
Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository
affaan-m/ECC
Skill path
.cursor/skills/content-engine/SKILL.md
Commit
4e973d3eaf92d97f8d2e2d8abb39d8bdc8711b38
License
MIT
Collected
2026-07-28
Default branch
main
View the original SKILL.md

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

Alternatives

Compare before choosing