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

public-relations

Plans and executes earned media — press strategy, journalist outreach, announcements, commentary, and crisis response. Use this to plan a press push, write a pitch or release, find and approach the right journalists, prepare for an interview, decide whether something is newsworthy, or respond to a story going badly.

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

설치 방법 보기

포함된 파일(2)

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

SKILL.md(원문)

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

Public relations

Newsworthy is a high bar

Most company news is not news. Before pitching, find the actual story — the thing a journalist's readers would care about with your company removed from the sentence.

Genuinely newsworthy: a first, a significant number, a counter-intuitive finding from data you uniquely have, a named conflict, a consequential person moving. Not newsworthy: a funding round of ordinary size, a feature release, a partnership, an award, a rebrand.

If there is no story, the answer is to build one — original research is the most reliable way — not to pitch harder.

Pitching

Journalists receive hundreds of pitches a day and reject most in seconds.

  • Pitch a person, not an outlet. Read three of their recent pieces first and reference one specifically and accurately. Generic personalization is worse than none.
  • Subject line is the pitch. If it does not carry the story, nothing else will be read.
  • Three sentences: the story, why now, why you can speak to it. Offer the assets — data, interview, images — rather than attaching them.
  • No embargo without agreement. Declaring one unilaterally is not binding and reads as presumptuous.
  • One follow-up, then stop.

Interviews

Decide the two or three things you want to have said, and find honest routes back to them. Never speculate, never say anything you would not want printed, and treat nothing as off the record unless explicitly agreed in advance — and even then, assume it may not hold.

"I don't know, I'll find out" is a complete and respectable answer.

When a story goes badly

  • Speed matters, but accuracy matters more. A fast wrong statement extends the story.
  • Say what happened, what you are doing, and when you will update. Only that.
  • Never dispute a factual detail you have not verified, and never attack the reporter. Both guarantee a second story.
  • Correct genuine errors privately, with evidence, and specifically. Vague complaints about tone achieve nothing.

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

Media databases and pitching: Muck Rack, Cision, Prowly, Roxhill, and similar. They are expensive, and their value is contact accuracy and beat data rather than the ability to send in bulk — a list-blast through one of them is the fastest way to be ignored by the journalists on it.

Wire distribution: Business Wire, PR Newswire, and similar. A wire buys disclosure and syndication, not coverage; treat it as a compliance or record-keeping tool unless you have a reason otherwise.

Monitoring: Meltwater, Brandwatch, Google Alerts, and similar. Set it up before the story you need to see, not after.

Never

  • Pitch a story that is only news to you. A funding round, a hire, and a redesign are not news outside the company.
  • Send a pitch to a journalist whose recent work you have not read.
  • Enter an interview without deciding in advance what you will not say.
  • Respond to a damaging story before establishing whether it is accurate.

리뷰

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

댓글

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

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

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. 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의 스킬 모두 보기

이 스킬의 문제 신고