MCP HubMCP Hub
SKILL·F71DBE

suede-public-relations

JasonColapietro
Mis à jour 27 days ago
4 vues
129
9
129
Voir sur GitHub
Métadesign

À propos

Cette compétence Claude gère les tâches de relations presse de Suede, telles que la constitution de listes de médias, la rédaction de propositions pour les journalistes et la préparation de dossiers de presse. Elle est spécifiquement conçue pour créer des briefs médias respectueux à partir de jalons vérifiés et d'angles narratifs. Ne l'utilisez pas pour les soumissions d'annuaires, l'emballage de lancement, la publication sur les réseaux sociaux ou les démarches non autorisées.

Installation rapide

Claude Code

Recommandé
Principal
npx skills add JasonColapietro/suede-creator-skills -a claude-code
Commande PluginAlternatif
/plugin add https://github.com/JasonColapietro/suede-creator-skills
Git CloneAlternatif
git clone https://github.com/JasonColapietro/suede-creator-skills.git ~/.claude/skills/suede-public-relations

Copiez et collez cette commande dans Claude Code pour installer cette compétence

Documentation

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 as concise as the verified outlet preference and story complexity allow?
  • Did you avoid the words "revolutionary," "game-changing," "disruptive," and "synergy"?
  • Is the ask clear? (Interview? Embargo? Exclusive? Quote?)

Keep the output draft-only. Each recipient, channel, identity, and exact message requires explicit approval before any external action.


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.

Dépôt GitHub

JasonColapietro/suede-creator-skills
Chemin: skills/suede-public-relations
0
agent-orchestrationagent-skillagent-skillsai-agentsai-codinganthropic
FAQ

Questions fréquentes

Qu’est-ce que le Skill suede-public-relations ?

suede-public-relations est un Skill Claude créé par JasonColapietro. Un Skill regroupe des instructions et des ressources que Claude charge à la demande pour effectuer des tâches liées à suede-public-relations sans consigne supplémentaire.

Comment installer suede-public-relations ?

Utilisez les commandes d’installation de cette page : ajoutez suede-public-relations à Claude Code comme plugin ou clonez son dépôt dans votre dossier skills, puis redémarrez Claude pour charger le Skill.

À quelle catégorie appartient suede-public-relations ?

suede-public-relations appartient à la catégorie Méta.

suede-public-relations est-il gratuit ?

Oui. suede-public-relations est référencé sur AIMCP et son installation est gratuite.

Compétences associées

content-collections
Méta

Cette compétence propose une configuration éprouvée en production pour Content Collections, un outil axé sur TypeScript qui transforme des fichiers Markdown/MDX en collections de données typées de manière sûre avec une validation Zod. Utilisez-la lors de la création de blogs, de sites de documentation ou d'applications Vite + React riches en contenu pour garantir la sécurité de typage et la validation automatique du contenu. Elle couvre tout, de la configuration du plugin Vite et de la compilation MDX à l'optimisation des déploiements et la validation des schémas.

Voir la compétence
polymarket
Méta

Cette compétence permet aux développeurs de créer des applications avec la plateforme de marchés prédictifs Polymarket, incluant l'intégration d'API pour le trading et les données de marché. Elle fournit également une diffusion de données en temps réel via WebSocket pour surveiller les transactions en direct et l'activité du marché. Utilisez-la pour mettre en œuvre des stratégies de trading ou pour créer des outils traitant les mises à jour de marché en direct.

Voir la compétence
creating-opencode-plugins
Méta

Cette compétence aide les développeurs à créer des plugins OpenCode qui s'interconnectent avec plus de 25 types d'événements tels que les commandes, les fichiers et les opérations LSP. Elle fournit la structure du plugin, les spécifications de l'API événementielle et les modèles d'implémentation pour les modules JavaScript/TypeScript. Utilisez-la lorsque vous avez besoin d'intercepter, de surveiller ou d'étendre le cycle de vie de l'assistant IA OpenCode avec une logique personnalisée pilotée par les événements.

Voir la compétence
sglang
Méta

SGLang est un framework de service LLM haute performance spécialisé dans la génération rapide et structurée pour les workflows JSON, regex et agentiques grâce à son cache de préfixe RadixAttention. Il offre une inférence nettement plus rapide, particulièrement pour les tâches avec des préfixes répétés, ce qui le rend idéal pour les sorties complexes et structurées ainsi que les conversations multi-tours. Choisissez SGLang plutôt que des alternatives comme vLLM lorsque vous avez besoin d'un décodage contraint ou que vous construisez des applications avec un partage étendu de préfixes.

Voir la compétence