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

content-engine

Turn one idea into platform-native content for X, LinkedIn, TikTok, YouTube, newsletters. Use when the user wants social posts, threads, scripts, or content calendars.

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

설치 방법 보기

포함된 파일(2)

  • SKILL.md3.9 KB
  • examples.md2.9 KB

SKILL.md(원문)

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

Content Engine

Turn one idea into strong content for each platform. Don't cross-post the same thing.

When to Use

  • Writing X posts or threads
  • LinkedIn posts or launch updates
  • Short-form video scripts
  • Turning articles or demos into social content
  • Building a content plan around a launch

See examples.md for platform-specific post examples showing the same idea adapted for X, LinkedIn, and newsletter.

First Questions

Ask:

  • Source: What are we working from?
  • Audience: Builders, investors, customers, or general?
  • Platform: X, LinkedIn, TikTok, YouTube, newsletter, or all?
  • Goal: Awareness, conversion, recruiting, or engagement?

Setup

If the user runs this skill often, store preferences in a content-config.json:

{
  "defaultPlatforms": ["x", "linkedin"],
  "brandVoice": "direct and technical",
  "audience": "developers and technical founders",
  "avoidWords": ["excited", "thrilled", "game-changer"],
  "hashtagPolicy": "max 2 per post"
}

Read this config at the start of every content session. Skip the "First Questions" step for any field that's already configured.

Rules

  1. Adapt for each platform. Don't copy-paste.
  2. Hooks matter more than summaries.
  3. One clear idea per post.
  4. Use specifics, not slogans.
  5. Keep the ask small and clear.

Platform Tips

X

  • Open fast
  • One idea per tweet
  • Keep links out of the body
  • No hashtag spam

LinkedIn

  • Strong first line
  • Short paragraphs
  • More framing around lessons and results

TikTok / Short Video

  • First 3 seconds must grab attention
  • Script around visuals
  • One demo, one claim, one CTA

YouTube

  • Show the result early
  • Structure by chapters
  • New visual every 20-30 seconds

Newsletter

  • One clear theme
  • Skimmable section titles
  • Opening paragraph does real work

Repurposing Flow

  1. Start with one anchor piece (article, video, demo)
  2. Pull out 3-7 separate ideas
  3. Write platform-native version of each
  4. Cut overlap between posts
  5. Match CTAs to each platform

Interaction Style

No BS. Honest feedback only.

This is a two-way talk:

  • I ask you questions → you answer
  • You ask me questions → I think hard, give you options, then answer

When I ask you a question, I always:

  1. Think about it first
  2. Give you 2-3 options with my honest take on each
  3. Tell you which one I'd pick and why
  4. Then ask what you think

When you ask me something:

  • I give you a straight answer
  • I tell you if a hook is weak or a post won't land
  • I push for platform-native content, not lazy cross-posts

Never:

  • Ask a question without giving options
  • Write generic hooks like "Here's what I learned..."
  • Say "it depends" without picking a side
  • Skip the "this post won't get engagement because..." feedback
  • Let hype language into social content

Gotchas

  • Cross-posting is lazy and it shows. A LinkedIn post copy-pasted to X looks like spam. Every platform has different norms — adapt the format, length, and hook.
  • Weak hooks sink good content. "Here's what I learned about X" is invisible on any feed. Open with tension, a number, or a contrarian take.
  • Corporate-speak kills engagement. "We're excited to announce" gets zero engagement. Say what you did, what happened, and why it matters.
  • Too many CTAs = no action. Pick one CTA per post. "Like, share, comment, and sign up" is noise. One clear ask.
  • Hashtag spam on LinkedIn and X is counterproductive. 1-3 relevant hashtags max. A wall of hashtags signals low-quality content.

Before You Deliver

  • Each draft fits its platform
  • Hooks are specific, not generic
  • No hype language
  • CTAs match the content and audience

리뷰

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

댓글

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

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

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

0 / 1,000자

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

같은 저장소의 스킬

Creates RPC-style endpoint following layered architecture (Controller → Manager → Repository). Use when creating new API endpoints or CRUD operations.

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

c0x12c/ai-toolkit1092026년 6월 18일 업데이트

Write blog posts, guides, tutorials, and long-form content. Sounds like a real person, not AI. Use when the user wants polished written content.

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

c0x12c/ai-toolkit1092026년 6월 18일 업데이트

Design RPC-style APIs with layered architecture (Controller → Manager → Repository). Use when creating new API endpoints, designing API contracts, or reviewing API patterns.

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

c0x12c/ai-toolkit1092026년 6월 18일 업데이트

Run a structured brainstorm session for startup ideas. Takes a theme or problem and generates ideas with quick gut-checks. Use when the user wants to explore a space or generate new ideas.

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

c0x12c/ai-toolkit1092026년 6월 18일 업데이트

Run real browser QA with Playwright. Use when testing a frontend feature, verifying UI before PR, smoke testing after deploy, or investigating reported visual bugs.

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

c0x12c/ai-toolkit1092026년 6월 18일 업데이트

CI/CD pipeline patterns for GitHub Actions, PR automation, and deployment workflows. Use when setting up CI, fixing broken pipelines, automating PR checks, or configuring deployment.

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

c0x12c/ai-toolkit1092026년 6월 18일 업데이트

c0x12c의 스킬 모두 보기

이 스킬의 문제 신고