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

social-post-craft

Writes, structures, and evaluates social posts end to end — hooks, body, formatting for how each platform renders, and a quality check before publishing. Use this to draft a post, rewrite one that underperformed, turn a longer piece into social content, sharpen an opening, or judge whether a draft is worth publishing.

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

설치 방법 보기

포함된 파일(2)

  • SKILL.md3.4 KB
  • references/sources.md1.3 KB

SKILL.md(원문)

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

Social post craft

The hook decides everything

Most posts are lost in the first line, before any of the substance is reached. The opening has one job: make continuing feel more attractive than scrolling.

Openings that work:

  • A specific claim with a number — concrete beats clever.
  • A stated tension — two things the reader believes that cannot both be true.
  • A named mistake — especially one the reader is probably making.
  • An outcome, before the method — the result first, the how afterward.

Openings that do not: a question the reader can answer "no" to, a definition, throat-clearing about why the topic matters, and anything beginning "In today's world."

Write the hook last, after you know what the post actually says. Written first, it commits you to a post you have not thought through.

Structure

One idea. A post carrying two ideas gets remembered for neither.

Then: hook, the turn (why the obvious view is incomplete), the substance (specific, ideally first-hand), and the landing — a conclusion, not a request for engagement.

Cut the first two lines of your draft. They are almost always warm-up.

Formatting is not cosmetic

Line breaks control pace and determine what is visible before the "see more" fold. On every major platform, the visible portion is one to three lines — everything about whether the post is read is decided there.

Short paragraphs. One thought per line for emphasis. No walls. Emphasis carried by structure, since most platforms strip formatting.

Check before publishing

  • Is the first line strong enough alone, with no context?
  • Does it survive the fold — is the visible part a complete enough thought to earn expansion?
  • One idea, or two?
  • Is anything in it specific to you? A post anyone in your field could have written performs like it.
  • Would you send this to one person you respect? If not, do not send it to everyone.

A draft that fails these gets rewritten, not published with a caveat.

Sources

references/sources.md in this skill lists the outside authorities that settle the questions here — what each one is authoritative for, and what you may do with it. Check them before answering on anything they cover, and cite what you used. Most are free to read and not free to reproduce; the use note on each is binding.

Tooling

Scheduling and publishing: Buffer, Hootsuite, Later, Sprout Social, Typefully, and similar. Native composers usually get better reach handling and newer formats first, so schedule what benefits from timing and post natively what benefits from features.

Whatever you use, keep the draft somewhere the copy can be reviewed before it enters the scheduler. Editing inside a publishing queue is how a typo goes out at 6am.

Never

  • Publish a post whose first line only works after the reader expands it.
  • Reuse one format across platforms unchanged. Line breaks and truncation differ, and the post breaks in ways the composer does not show you.
  • Post a link without deciding whether the platform suppresses them.

리뷰

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

댓글

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

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

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

0 / 1,000자

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

같은 저장소의 스킬

Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process. Use this to design a permissions model, run an access review, reduce standing privilege, handle offboarding, set up SSO or MFA, manage service and machine credentials, or diagnose why permissions have sprawled.

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

cbrock84/headcount2.1천2026년 10월 19일 업데이트

Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group inside each, tiering effort against account value, coordinating so the account experiences one campaign rather than several, and measuring account progression instead of leads. Use this to decide whether to run an account-based program, build one, or work out why an existing one produces activity and no pipeline.

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

cbrock84/headcount2.1천2026년 10월 19일 업데이트

Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone becomes a user or a lapsed account. Use this to design or fix signup and onboarding, diagnose why signups do not convert to active use, reduce time-to-value, or decide what a new user must accomplish first.

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

cbrock84/headcount2.1천2026년 10월 19일 업데이트

Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a script that runs in CI. Use this whenever the user wants to set up, expand, audit, or fix a multi-agent or subagent structure for a codebase; asks how to divide work between agents; wants agent charters, roles, or a surface map written; or is hitting agents that collide on the same files, review their own work, or drift from their remit. Also use when sizing a roster or deciding whether a new agent is justified.

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

cbrock84/headcount2.1천2026년 10월 19일 업데이트

Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire. Use this before deploying a model or AI feature, when defining evaluation criteria, when a model's behavior has drifted, when assessing AI risk or regulatory exposure, or when deciding whether an AI system is fit for a consequential decision.

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

cbrock84/headcount2.1천2026년 10월 19일 업데이트

Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit. Use this to analyze a market or industry, map competitors, evaluate a market-entry or build-versus-buy decision, produce a research brief, or assemble evidence for a decision. Also use when comparing options that need a structured, evidence-based verdict rather than an opinion.

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

cbrock84/headcount2.1천2026년 10월 19일 업데이트

cbrock84의 스킬 모두 보기

이 스킬의 문제 신고