본문으로 건너뛰기
cccskills
무료GitHub에 공개

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(1)

  • SKILL.md4.9 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Content Engine

Build platform-native content without flattening the author's real voice into platform slop.

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, docs, or internal notes into public content
  • building a launch sequence or ongoing content system around a product, insight, or narrative

Non-Negotiables

  1. Start from source material, not generic post formulas.
  2. Adapt the format for the platform, not the persona.
  3. One post should carry one actual claim.
  4. Specificity beats adjectives.
  5. No engagement bait unless the user explicitly asks for it.

Source-First Workflow

Before drafting, identify the source set:

  • published articles
  • notes or internal memos
  • product demos
  • docs or changelogs
  • transcripts
  • screenshots
  • prior posts from the same author

If the user wants a specific voice, build a voice profile from real examples before writing. Use brand-voice as the canonical workflow when voice consistency matters across more than one output.

Voice Capture Workflow

Run brand-voice first when:

  • there are multiple downstream outputs
  • the user explicitly cares about writing style
  • the content is launch, outreach, or reputation-sensitive

At minimum, produce a compact VOICE PROFILE covering:

  • rhythm
  • compression
  • capitalization
  • parenthetical use
  • question use
  • preferred moves
  • banned moves

Do not start drafting until the voice profile is clear enough to enforce.

Affaan / ECC Voice Reference

When the user wants Affaan / ECC voice specifically, default to this unless newer examples clearly override it:

  • direct, compressed, concrete
  • strong preference for specific claims, numbers, mechanisms, and receipts
  • parentheticals used to qualify, narrow, or over-clarify, not to do corny bits
  • lowercase is optional, not mandatory
  • questions are rare and should not be added as bait
  • transitions should feel earned, not polished
  • tone can be sharp or blunt, but should not sound like a content marketer

Hard Bans

Delete and rewrite any of these:

  • "In today's rapidly evolving landscape"
  • "game-changer", "revolutionary", "cutting-edge"
  • "no fluff"
  • "not X, just Y"
  • "here's why this matters" unless it is followed immediately by something concrete
  • "Excited to share"
  • fake curiosity gaps
  • ending with a LinkedIn-style question just to farm replies
  • forced lowercase when the source voice does not call for it
  • forced casualness on LinkedIn
  • parenthetical jokes that were not present in the source voice

Platform Adaptation Rules

X

  • open with the strongest claim, artifact, or tension
  • keep the compression if the source voice is compressed
  • if writing a thread, each post must advance the argument
  • do not pad with context the audience does not need

LinkedIn

  • expand only enough for people outside the immediate niche to follow
  • do not turn it into a fake lesson post unless the source material actually is reflective
  • no corporate inspiration cadence
  • no praise-stacking, no "journey" filler

Short Video

  • script around the visual sequence and proof points
  • first seconds should show the result, problem, or punch
  • do not write narration that sounds better on paper than on screen

YouTube

  • show the result or tension early
  • organize by argument or progression, not filler sections
  • use chaptering only when it helps clarity

Newsletter

  • open with the point, conflict, or artifact
  • do not spend the first paragraph warming up
  • every section needs to add something new

Repurposing Flow

  1. Pick the anchor asset.
  2. Extract 3 to 7 atomic claims or scenes.
  3. Rank them by sharpness, novelty, and proof.
  4. Assign one strong idea per output.
  5. Adapt structure for each platform.
  6. Strip platform-shaped filler.
  7. Run the quality gate.

Deliverables

When asked for a campaign, return:

  • a short voice profile if voice matching matters
  • the core angle
  • platform-native drafts
  • posting order only if it helps execution
  • gaps that must be filled before publishing

Quality Gate

Before delivering:

  • every draft sounds like the intended author, not the platform stereotype
  • every draft contains a real claim, proof point, or concrete observation
  • no generic hype language remains
  • no fake engagement bait remains
  • no duplicated copy across platforms unless requested
  • any CTA is earned and user-approved

Related Skills

  • brand-voice for source-derived voice profiles
  • crosspost for platform-specific distribution
  • x-api for sourcing recent posts and publishing approved X output

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Use AtomLane to compile and execute safe atomic parallel plans on macOS and native Windows Preview for worthwhile independent argv tasks, dependency DAGs, supported platform entrypoints, or Apple-silicon operators. Use at task start or an execution boundary when structured local work may contain two or more worthwhile units; skip plain answers, one quick command, and work whose effects cannot be safely bounded.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

hashgraph-online/awesome-codex-plugins1.4천2026년 10월 20일 업데이트

add

무료

Register a deferred decision in the debt registry. Trigger by judgment, not a marker scan, whenever a future reader would ask "why this way?": an unmade decision, stub, loosened type, bypassed check, swallowed error, a default picked "for now", or a TODO/FIXME/HACK/XXX marker. Trigger immediately whenever you defer work, or when the user invokes $add. Over-register freely; the developer drops with "drop A", "drop A,C", or "drop all".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

hashgraph-online/awesome-codex-plugins1.4천2026년 10월 20일 업데이트

ADK 框架适配层。为 LangChain / EINO / AutoGen / AgentScope / CrewAI 提供框架特定的 代码模板、惯用模式、API 映射和项目结构,供 agent-dev-workshop Phase 5 代码生成使用。 每个框架 reference 文件标注 verified_date 用于版本锁定。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

hashgraph-online/awesome-codex-plugins1.4천2026년 10월 20일 업데이트

中文调试修复技能。用于报错、测试失败、页面异常、功能不符合预期、需要定位根因并做最小修复时。触发语包括"进入调试模式""帮我修问题""报错了""测试失败""页面坏了""找根因"。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

hashgraph-online/awesome-codex-plugins1.4천2026년 10월 20일 업데이트

交互式 AI Agent 开发工作坊:通过 6 阶段深度协作对话,引导用户完成 Agent 需求分析、架构设计、 工具定义、Prompt 与编排设计、代码生成、验证迭代,产出可直接运行的 Agent 项目。 框架无关设计优先,支持 LangChain / EINO / AutoGen / AgentScope / CrewAI 等 ADK 框架。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

hashgraph-online/awesome-codex-plugins1.4천2026년 10월 20일 업데이트

中文漂移审计技能。用于项目或学习过程变乱、上下文漂移、任务分叉、多个方案冲突、命名不一致、Codex 可能顺手改多了时。触发语包括"漂移检查""感觉跑偏了""项目变乱了""检查是否失控""分叉太多""上下文漂移"。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

hashgraph-online/awesome-codex-plugins1.4천2026년 10월 20일 업데이트

hashgraph-online의 스킬 모두 보기

이 스킬의 문제 신고