本文へ移動
cccskills
無料GitHub で公開

suede-public-relations

Suede-owned earned-media discipline. Use when building a media list, validating a story angle, drafting a journalist pitch, preparing a press kit, evaluating newsjacking, or answering a reporter request. NOT FOR: directory submissions (use suede-directory-submissions), launch packaging (use suede-launch-packaging), social publishing (use suede-social), or contacting anyone without approval.

インストール方法を見る

含まれるファイル(7)

  • SKILL.md8.9 KB
  • agents/openai.yaml588 B
  • CARD.md4.2 KB
  • references/journalist-pitching.md12.2 KB
  • references/media-outlets.md9.0 KB
  • references/newsjacking.md9.3 KB
  • references/press-platforms.md7.3 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Suede Public Relations & Earned Media

Suede Public Relations turns verified milestones, evidence, and timely angles into respectful earned-media briefs for journalists, podcasts, and newsletters. It optimizes story fit and source usefulness without treating a drafted pitch as sent or coverage as earned.

Before Starting

Check for product marketing context first: If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.


Core Philosophy

PR is not a substitute for distribution. Treat it as a channel hypothesis whose value must be measured against the current audience, story, and sales motion.

  • Do not assume a placement drives or cannot drive conversion. Track referral behavior, brand search, citations, and sales influence for this campaign.
  • Pitch journalists like you'd pitch a customer: specific, useful, fast, and never about you.
  • The story is not your product. The story is the trend, the data, the conflict, or the human. Your product is the evidence.
  • Test speed against relevance and accuracy. Use the story's observed coverage curve and deadline; never trade verification for haste.

When PR is worth it

  • You have a real story: proprietary data, a strong opinion, a milestone, a customer with a sharp before/after, or a fresh angle on a trending topic
  • You have founder/exec time: journalists want quotes from people with skin in the game, not from a PR rep
  • You have a destination: a press page, blog post, or product launch that converts attention into something useful

When to skip PR (for now)

  • Pre-launch with no story beyond "we exist"
  • No one on the team can sustain the approved, measured test window
  • You don't have a clear ICP: journalists ask "who reads my piece because of this?" and if you can't answer, neither can they

The PR Mix

Four possible modes. Select only those supported by the story, audience, capacity, and current source access.

ModeWhat it isEffortSpeed to coverage
Reactive (newsjacking)Inject your POV into trending newsLow–mediumHours to days
Proactive (pitching)Build a media list, draft original-story pitchesMeasure current capacitySet from story flow and response data
Inbound (press requests)Respond to journalist queries on HARO/Qwoted/FeaturedLowDays to weeks
Owned (press page + media kit)Make it easy for journalists to find youOne-time setupN/A

For the reactive newsjacking workflow: see references/newsjacking.md

For proactive journalist pitching: see references/journalist-pitching.md

For inbound press-request platforms (HARO, Qwoted, etc.): see references/press-platforms.md

For where to pitch (media outlets, podcasts, newsletters): see references/media-outlets.md. For startup/SaaS/AI directories, use the separate suede-directory-submissions skill: different intent, different list.


Owned: Press Page + Media Kit

Build this when verified newsroom assets and a maintained press contact would reduce friction for the current media motion; measure usage rather than assuming ROI.

Press page (/press or /newsroom) should include:

  • One-paragraph company description (copy/paste ready)
  • Founder bios with headshots (high-res, downloadable)
  • Logo pack (SVG + PNG, light + dark, with usage guidelines)
  • Product screenshots (high-res)
  • Recent coverage list (social proof for the next journalist)
  • Founding date, employee count, funding (if disclosed)
  • A current press contact path in the format the intended outlets accept
  • Recent press releases / announcements

State a response expectation only if the team has approved and staffed it. Use the team's real service level rather than a universal 24-hour promise.


Quick Reference: Pitch Quality Bar

Before presenting any draft for send approval, resolve these checks:

  • Does a bounded recent sample show that this journalist covers the beat?
  • Is there a clear news hook: something that just happened or is about to?
  • Could this journalist write a complete story from this email alone? (Data, quotes, customer name, contact.)
  • Is the subject line specific enough to predict the article's headline?
  • Is the pitch within the outlet's published word or character limit, or, if the outlet publishes none, within the limit the user stated?
  • Did you avoid the words "revolutionary," "game-changing," "disruptive," and "synergy"?
  • Is the ask clear? (Interview? Embargo? Exclusive? Quote?)

Pass rule: any unchecked box blocks the draft from being presented for send approval. Fix it or, if it cannot be resolved (the outlet publishes no limit and the user has not stated one), name the box as unresolved in the handover below rather than checking it.

Send-approval handover (the one gate in this skill)

Every workflow in this skill and its references ends here. Contacting a journalist is unrecallable, so nothing leaves as a draft-plus-send. At the handover:

  1. Stop. The work is complete; the output is a draft and nothing has been sent.
  2. Name the four variables, one line each: recipient (person and outlet), channel (email, platform form, DM), visible sending identity, and the exact message to be sent.
  3. State cost and timing if either applies (platform fee, embargo time).
  4. Offer three options: approve as written / revise (name what changes) / drop.
  5. Wait for the user's explicit pick. Approval for one recipient never transfers to another, and any edit to the message re-opens this gate.

Measurement

What to track:

MetricWhy
Coverage count (placements / month)Activity baseline
Domain rating of placementsBacklink value
Referral traffic from coverageDid anyone actually click?
Brand search liftDid people search you after reading?
AI citation rate (ChatGPT, Perplexity quote your brand?)The new measurement that matters
Sales conversations citing the articleOne revenue-influence signal to reconcile with attribution limits

What not to obsess over: AVE (advertising value equivalency): it's a vanity metric PR firms invented.


Common Workflows

"Help me newsjack [trending story]"

Go to newsjacking.md, run the scoring rubric, draft a bounded set of evidence-backed angles, and return a recommended draft for review. Do not pitch or publish.

"Find journalists who cover [beat]"

Go to journalist-pitching.md, use the discovery checklist, and first discover whether an authorized browser or research connector is callable. If not, work from user-supplied article URLs, exports, or a manual research worksheet. Build a sourced, scored list without claiming any profile or article was reviewed unless it actually was.

"What's worth pitching this week?"

Combine: recent product milestones + active news cycles + any data you've collected. Score each potential story by the quality bar above.

"Respond to this HARO query"

Go to press-platforms.md, use the response template, follow current outlet limits, and keep the result draft-only.

"Build my press page"

Use the checklist above. Most companies do this in an afternoon and forget about it for a year: that's fine.

Boundaries

  • Do not contact journalists, submit reporter responses, publish press releases, or represent that a draft has been sent without explicit approval and a confirmed recipient.
  • Do not fabricate claims, data, quotes, customers, credentials, urgency, or coverage; separate verified facts from proposed angles.
  • Do not impersonate a source, promise exclusivity, or decide legal disclosure, embargo, or crisis-response policy.

Routing

  • Use suede-launch-packaging to coordinate a broader product launch.
  • Use suede-directory-submissions for directory and catalog listings.
  • Use suede-social for approved social distribution and engagement.
  • Use suede-copy to polish a verified press-page or announcement draft.
  • Use suede-co-marketing when the announcement is a joint launch with a partner.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Suede-affiliated Amazon money-recovery audit for restocking fees, short or denied refunds, and Amazon-billed subscriptions. Use when the user mentions a restocking fee, a short or denied Amazon refund, or a forgotten Prime Video Channel, Audible, Kindle Unlimited, or Prime charge, or asks whether Amazon still owes or bills them. Read-only discovery; no chat, cancellation, or dispute without the account owner's per-item confirmation, and never a promise of recovery. Requires an authenticated Claude in Chrome session. NOT FOR: bank chargebacks, marketplace A-to-z seller claims, price-protection claims, or subscriptions billed outside Amazon (use subscription-recovery).

日本語の概要は準備中です。原文の説明を表示しています。

JasonColapietro/suede-creator-skills1272026年10月12日 更新

Suede Labs Android app factory: plan, build, test, and release a production-grade native Android app from a product idea through Google Play. Use for requests to create, ship, submit, monetize, or modernize an Android app. Covers Kotlin and Jetpack Compose architecture, API-level policy verification, accessibility, privacy and Data Safety, Play Billing, Play Integrity, account deletion, testing, performance, store assets, signing, staged rollout, and a release evidence gate. NOT FOR: iOS work (private Suede Labs companion, not in this pack: ios-app-factory), a review-only pass on an existing app (use suede-code-review), or live Play listing and keyword audits on a shipped app (use suede-aso).

日本語の概要は準備中です。原文の説明を表示しています。

JasonColapietro/suede-creator-skills1272026年10月12日 更新

Design, review, and visually QA web and app interfaces against explicit design laws so shipped screens look intentional instead of generic AI output.

日本語の概要は準備中です。原文の説明を表示しています。

JasonColapietro/suede-creator-skills1272026年10月12日 更新

Suede AI full-stack surface builder that runs design, copy, and visual QA as one pass: landing pages, brand surfaces, product UI, dashboards, campaigns, launch pages, and reference-to-target restyles (suedify). Use when a build needs layout and words together, when a redesign or launch surface has to ship end to end, when the request is 'make this site look like that one', or when design, copy, asset, and QA lanes have to move at once. NOT FOR: a design-token, dark-mode, or single-component decision (use suede-design); copy with no layout work (use johnny-suede-write, or suede-copy for one standalone conversion surface); conversion and funnel architecture (use suede-site-alchemy); multi-agent orchestration protocols, WIP protection, and rollback trees (use suede-agent-teams).

日本語の概要は準備中です。原文の説明を表示しています。

JasonColapietro/suede-creator-skills1272026年10月12日 更新

Suede Labs full writing stack: sharper copy for docs, pages, email, social, headlines, CTAs, product listings, and public explainers, with an SEO/AEO/AI EO pass, persona and framework selection, brand-voice alignment, and a scored ship gate. Use when a writing job spans more than one surface, needs a voice retune as well as a draft, needs discoverability metadata alongside the copy, when the document is one an agent reads such as a SKILL.md, CLAUDE.md, or AGENTS.md, or when the user asks for 'the full writing stack', a launch package, or a public explainer talk-track. NOT FOR: one standalone conversion surface in one pass (use suede-copy); stripping AI patterns from text you did not write (use suede-deslop); a researched multi-phase piece for a high-stakes public surface (use suede-ship-copy); a deep standalone SEO audit (use suede-seo-audit); copy that ships inside a design or layout build (use johnny-suede-design).

日本語の概要は準備中です。原文の説明を表示しています。

JasonColapietro/suede-creator-skills1272026年10月12日 更新

Suede Labs workflow for turning a website, PWA, dashboard, or marketplace into an iOS app. Use when the user has a live site or web app and asks to put it on the App Store, wrap it in an app, ship an iOS version, or convert a PWA to native, covers URL audit, shell-vs-native strategy, App Store 4.2 wrapper risk, native value requirements, screenshots, metadata, privacy answers, and the release gate. NOT FOR: building a native iOS app with no existing site (private Suede Labs companion, not in this pack: ios-swiftui-product); repairing or releasing an existing Capacitor shell (private Suede Labs companion, not in this pack: ios-capacitor-shell); Android conversions (use android-app-factory); live listing and keyword audits on a shipped app (use suede-aso).

日本語の概要は準備中です。原文の説明を表示しています。

JasonColapietro/suede-creator-skills1272026年10月12日 更新

JasonColapietro のスキルをすべて見る

このスキルの問題を報告する