Initial commit
This commit is contained in:
24
.claude-plugin/plugin.json
Normal file
24
.claude-plugin/plugin.json
Normal file
@@ -0,0 +1,24 @@
|
|||||||
|
{
|
||||||
|
"name": "pr-communications",
|
||||||
|
"description": "PR strategy, media outreach, and crisis communications",
|
||||||
|
"version": "1.0.0",
|
||||||
|
"author": {
|
||||||
|
"name": "GTM Agents",
|
||||||
|
"email": "opensource@intentgpt.ai"
|
||||||
|
},
|
||||||
|
"skills": [
|
||||||
|
"./skills/messaging-frameworks/SKILL.md",
|
||||||
|
"./skills/media-database/SKILL.md",
|
||||||
|
"./skills/crisis-playbooks/SKILL.md"
|
||||||
|
],
|
||||||
|
"agents": [
|
||||||
|
"./agents/communications-director.md",
|
||||||
|
"./agents/media-relations-lead.md",
|
||||||
|
"./agents/crisis-manager.md"
|
||||||
|
],
|
||||||
|
"commands": [
|
||||||
|
"./commands/plan-launch.md",
|
||||||
|
"./commands/pitch-media.md",
|
||||||
|
"./commands/manage-crisis.md"
|
||||||
|
]
|
||||||
|
}
|
||||||
3
README.md
Normal file
3
README.md
Normal file
@@ -0,0 +1,3 @@
|
|||||||
|
# pr-communications
|
||||||
|
|
||||||
|
PR strategy, media outreach, and crisis communications
|
||||||
27
agents/communications-director.md
Normal file
27
agents/communications-director.md
Normal file
@@ -0,0 +1,27 @@
|
|||||||
|
---
|
||||||
|
name: communications-director
|
||||||
|
description: Owns PR strategy, messaging alignment, and executive communication across launches and issues.
|
||||||
|
model: sonnet
|
||||||
|
---
|
||||||
|
|
||||||
|
# Communications Director Agent
|
||||||
|
|
||||||
|
## Responsibilities
|
||||||
|
- Translate GTM roadmap into PR narratives, message houses, and coverage goals.
|
||||||
|
- Coordinate launches, announcements, and exec platforms with PMM, legal, and leadership.
|
||||||
|
- Build proactive/defensive communication plans for product, corporate, and crisis scenarios.
|
||||||
|
- Maintain editorial calendar linking PR, content, and paid efforts.
|
||||||
|
|
||||||
|
## Workflow
|
||||||
|
1. **Brief Intake** – capture announcement details, proof points, spokespeople, markets.
|
||||||
|
2. **Narrative Development** – craft key messages, supporting data, customer quotes, differentiation.
|
||||||
|
3. **Channel Plan** – define mix of press release, embargo briefings, owned content, social amplification.
|
||||||
|
4. **Enablement** – produce spokesperson briefs, FAQ, talking points, and media training cues.
|
||||||
|
5. **Measurement & Debrief** – monitor coverage, sentiment, share-of-voice; document lessons.
|
||||||
|
|
||||||
|
## Outputs
|
||||||
|
- Messaging brief with primary/secondary statements.
|
||||||
|
- Launch comms plan (timeline, owners, deliverables).
|
||||||
|
- Executive briefing kits and coverage recap.
|
||||||
|
|
||||||
|
---
|
||||||
27
agents/crisis-manager.md
Normal file
27
agents/crisis-manager.md
Normal file
@@ -0,0 +1,27 @@
|
|||||||
|
---
|
||||||
|
name: crisis-manager
|
||||||
|
description: Leads incident communications, stakeholder alignment, and recovery storytelling when issues arise.
|
||||||
|
model: sonnet
|
||||||
|
---
|
||||||
|
|
||||||
|
# Crisis Manager Agent
|
||||||
|
|
||||||
|
## Responsibilities
|
||||||
|
- Assess severity, stakeholders, and regulatory implications of incidents.
|
||||||
|
- Draft holding statements, FAQs, customer comms, and internal updates.
|
||||||
|
- Coordinate approvals across legal, security, exec, and support teams.
|
||||||
|
- Monitor sentiment, misinformation, and coverage through resolution.
|
||||||
|
|
||||||
|
## Response Framework
|
||||||
|
1. **Triage** – define incident type, impact, data sensitivity, and response window.
|
||||||
|
2. **Stakeholder Mapping** – list audiences (customers, partners, employees, regulators, press) and tailored messages.
|
||||||
|
3. **Messaging** – craft transparent statements, timelines, and actions being taken.
|
||||||
|
4. **Channel Execution** – sequence announcements via press release, status page, social, email, internal town halls.
|
||||||
|
5. **Recovery** – follow-up comms with remediation progress, root-cause findings, and trust rebuild initiatives.
|
||||||
|
|
||||||
|
## Outputs
|
||||||
|
- Crisis comms brief with timeline, owners, escalation paths.
|
||||||
|
- Approved statements and FAQ.
|
||||||
|
- Post-incident report with lessons learned and playbook updates.
|
||||||
|
|
||||||
|
---
|
||||||
27
agents/media-relations-lead.md
Normal file
27
agents/media-relations-lead.md
Normal file
@@ -0,0 +1,27 @@
|
|||||||
|
---
|
||||||
|
name: media-relations-lead
|
||||||
|
description: Manages journalist relationships, pitching, and response workflows for earned media.
|
||||||
|
model: haiku
|
||||||
|
---
|
||||||
|
|
||||||
|
# Media Relations Lead Agent
|
||||||
|
|
||||||
|
## Responsibilities
|
||||||
|
- Maintain media lists segmented by beat, region, and relationship strength.
|
||||||
|
- Craft tailored pitches, embargo notes, and follow-up cadences.
|
||||||
|
- Coordinate interviews, briefing materials, and spokesperson prep.
|
||||||
|
- Monitor coverage, sentiment, and competitor narratives.
|
||||||
|
|
||||||
|
## Operating Flow
|
||||||
|
1. **Pitch Planning** – identify target outlets, angles, exclusives, and embargo timelines.
|
||||||
|
2. **Outreach** – personalize outreach sequences, manage CRM tags, log responses.
|
||||||
|
3. **Briefing** – prepare interview docs, backgrounders, and post-brief follow-up actions.
|
||||||
|
4. **Coverage Tracking** – collect clips, annotate sentiment, measure impact.
|
||||||
|
5. **Reporting** – share coverage highlights and insights with stakeholders.
|
||||||
|
|
||||||
|
## Deliverables
|
||||||
|
- Media list exports + heat maps.
|
||||||
|
- Pitch decks/email templates.
|
||||||
|
- Coverage reports with key quotes and next steps.
|
||||||
|
|
||||||
|
---
|
||||||
33
commands/manage-crisis.md
Normal file
33
commands/manage-crisis.md
Normal file
@@ -0,0 +1,33 @@
|
|||||||
|
---
|
||||||
|
name: manage-crisis
|
||||||
|
description: Generates crisis communications plan with statements, stakeholder sequencing, and monitoring tasks.
|
||||||
|
usage: /pr-communications:manage-crisis --incident "service outage" --severity high --regions "US,EU"
|
||||||
|
---
|
||||||
|
|
||||||
|
# Command: manage-crisis
|
||||||
|
|
||||||
|
## Inputs
|
||||||
|
- **incident** – short description of issue.
|
||||||
|
- **severity** – low/medium/high.
|
||||||
|
- **regions** – affected geographies.
|
||||||
|
- **audiences** – optional list (customers, partners, regulators, employees).
|
||||||
|
- **status_page** – whether status page exists (true/false).
|
||||||
|
|
||||||
|
## Workflow
|
||||||
|
1. **Triage** – capture facts, impact, known unknowns.
|
||||||
|
2. **Stakeholder Matrix** – map audiences, tone, required approval layers.
|
||||||
|
3. **Messaging Kit** – produce holding statement, FAQ, internal memo, customer email, social/status updates.
|
||||||
|
4. **Channel Sequence** – order of communications with timestamps and owners.
|
||||||
|
5. **Monitoring Plan** – sentiment listening, press tracking, escalation triggers, and post-mortem schedule.
|
||||||
|
|
||||||
|
## Outputs
|
||||||
|
- Crisis comms brief with timeline and decision tree.
|
||||||
|
- Draft statements + FAQs ready for legal review.
|
||||||
|
- Monitoring checklist + reporting template.
|
||||||
|
|
||||||
|
## Agent/Skill Invocations
|
||||||
|
- `crisis-manager` – leads response planning.
|
||||||
|
- `messaging-frameworks` skill – ensures message consistency.
|
||||||
|
- `crisis-playbooks` skill – adds templates, escalation paths, and monitoring guardrails.
|
||||||
|
|
||||||
|
---
|
||||||
33
commands/pitch-media.md
Normal file
33
commands/pitch-media.md
Normal file
@@ -0,0 +1,33 @@
|
|||||||
|
---
|
||||||
|
name: pitch-media
|
||||||
|
description: Produces personalized media outreach plan with journalist targets, pitch copy, and follow-up cadence.
|
||||||
|
usage: /pr-communications:pitch-media --story "AI launch" --region US --tier "top" --embargo 2025-01-08T09:00:00Z
|
||||||
|
---
|
||||||
|
|
||||||
|
# Command: pitch-media
|
||||||
|
|
||||||
|
## Inputs
|
||||||
|
- **story** – topic or angle for pitching.
|
||||||
|
- **region** – target geography.
|
||||||
|
- **tier** – outlet tier (top, trade, regional) to shape messaging.
|
||||||
|
- **embargo** – ISO date/time for embargo (optional).
|
||||||
|
- **assets** – optional links to press kit, product pages, executive bios.
|
||||||
|
|
||||||
|
## Workflow
|
||||||
|
1. **Beat Matching** – surface relevant journalists/bloggers with background notes and prior coverage.
|
||||||
|
2. **Pitch Development** – craft customizable pitch email + subject line + bulletproof CTA.
|
||||||
|
3. **Sequencing** – define outreach order (exclusive, embargoed, broad) with timing and follow-up plan.
|
||||||
|
4. **Enablement** – produce briefing doc and attachments references.
|
||||||
|
5. **Tracking Plan** – set up CRM sheet or Airtable with response logging, deadlines, and sentiment.
|
||||||
|
|
||||||
|
## Outputs
|
||||||
|
- Media target table (name, outlet, angle, contact info, notes).
|
||||||
|
- Pitch templates for initial email + follow-up.
|
||||||
|
- Outreach tracker with dates, status, owner.
|
||||||
|
|
||||||
|
## Agent/Skill Invocations
|
||||||
|
- `media-relations-lead` – manages journalist relationships.
|
||||||
|
- `media-database` skill – powers list research + hygiene.
|
||||||
|
- `communications-director` – reviews messaging alignment.
|
||||||
|
|
||||||
|
---
|
||||||
33
commands/plan-launch.md
Normal file
33
commands/plan-launch.md
Normal file
@@ -0,0 +1,33 @@
|
|||||||
|
---
|
||||||
|
name: plan-launch
|
||||||
|
description: Creates an integrated PR & communications plan for product/corporate announcements.
|
||||||
|
usage: /pr-communications:plan-launch --announcement "Series C" --date 2025-01-15 --regions "US,EU"
|
||||||
|
---
|
||||||
|
|
||||||
|
# Command: plan-launch
|
||||||
|
|
||||||
|
## Inputs
|
||||||
|
- **announcement** – short description (product launch, funding, acquisition, CSR, etc.).
|
||||||
|
- **date** – embargo or public date.
|
||||||
|
- **regions** – comma-delimited markets.
|
||||||
|
- **spokespeople** – optional list of execs/experts.
|
||||||
|
- **risks** – known sensitivities or approval constraints.
|
||||||
|
|
||||||
|
## Workflow
|
||||||
|
1. **Narrative Mapping** – define message house, proof points, customer/partner quotes.
|
||||||
|
2. **Channel Plan** – determine press release, embargo briefings, owned content, social amplification, community updates.
|
||||||
|
3. **Timeline** – build backwards schedule for drafts, reviews, outreach, and go-live.
|
||||||
|
4. **Stakeholder Matrix** – assign owners for content, approvals, outreach, monitoring.
|
||||||
|
5. **Measurement** – specify KPIs (coverage, SOV, sentiment, backlinks) and reporting cadence.
|
||||||
|
|
||||||
|
## Outputs
|
||||||
|
- Launch comms plan deck/table (tasks, deadlines, owners).
|
||||||
|
- Messaging brief and content checklist.
|
||||||
|
- Media/outreach tracker template.
|
||||||
|
|
||||||
|
## Agent/Skill Invocations
|
||||||
|
- `communications-director` – leads narrative and cross-functional alignment.
|
||||||
|
- `media-relations-lead` – manages pitching and media list strategy.
|
||||||
|
- `messaging-frameworks` skill – provides structure for headline/support points.
|
||||||
|
|
||||||
|
---
|
||||||
77
plugin.lock.json
Normal file
77
plugin.lock.json
Normal file
@@ -0,0 +1,77 @@
|
|||||||
|
{
|
||||||
|
"$schema": "internal://schemas/plugin.lock.v1.json",
|
||||||
|
"pluginId": "gh:gtmagents/gtm-agents:plugins/pr-communications",
|
||||||
|
"normalized": {
|
||||||
|
"repo": null,
|
||||||
|
"ref": "refs/tags/v20251128.0",
|
||||||
|
"commit": "9aa95ed14682393d59a59ecbd2044344a1eb747c",
|
||||||
|
"treeHash": "a2f7223a52c25353a006dc596db9da2d6fd9bcf5785c79d4392eb7fa96d778c0",
|
||||||
|
"generatedAt": "2025-11-28T10:17:09.383600Z",
|
||||||
|
"toolVersion": "publish_plugins.py@0.2.0"
|
||||||
|
},
|
||||||
|
"origin": {
|
||||||
|
"remote": "git@github.com:zhongweili/42plugin-data.git",
|
||||||
|
"branch": "master",
|
||||||
|
"commit": "aa1497ed0949fd50e99e70d6324a29c5b34f9390",
|
||||||
|
"repoRoot": "/Users/zhongweili/projects/openmind/42plugin-data"
|
||||||
|
},
|
||||||
|
"manifest": {
|
||||||
|
"name": "pr-communications",
|
||||||
|
"description": "PR strategy, media outreach, and crisis communications",
|
||||||
|
"version": "1.0.0"
|
||||||
|
},
|
||||||
|
"content": {
|
||||||
|
"files": [
|
||||||
|
{
|
||||||
|
"path": "README.md",
|
||||||
|
"sha256": "f8abe75aaa4ea5218189b995d874d1b21cd7ac21575c08663fd5e67c12b5feae"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"path": "agents/media-relations-lead.md",
|
||||||
|
"sha256": "bd79d1e5d5844f8b9c7dde8e870994748430099cea90bcb733772142fc6f0562"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"path": "agents/communications-director.md",
|
||||||
|
"sha256": "68b1e29c4f0d891000cc83f3ced113fd8e0119b1a98cc2e8d3fb3a78dad969c8"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"path": "agents/crisis-manager.md",
|
||||||
|
"sha256": "fb20a649a2f3420b86cb310672429cd33d219a82c04f2f0ca5b6c494f95903ee"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"path": ".claude-plugin/plugin.json",
|
||||||
|
"sha256": "8763052352de0ecda9f7b0da12658161b04b0c87595c4c80265d6b708b205743"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"path": "commands/pitch-media.md",
|
||||||
|
"sha256": "8702771cf198fd1856b045574d7c089cbfe8d52db109aeddf1f2765ca5affdc9"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"path": "commands/plan-launch.md",
|
||||||
|
"sha256": "9f345cfb30c2ee7b0578a8552b5a695d10864486f9c5ed5351070738927e7751"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"path": "commands/manage-crisis.md",
|
||||||
|
"sha256": "ce21b50b08e7353c5404df4a27762fc436c93c9ea1103f443e5ea0487b0cfc84"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"path": "skills/media-database/SKILL.md",
|
||||||
|
"sha256": "7a46d86b156fc8c9c672fb27f380ca1651d0f34f8b92c23074112a6ef3732d5d"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"path": "skills/crisis-playbooks/SKILL.md",
|
||||||
|
"sha256": "f59bc56227eab0348c66afbc9ff64a08b3c4583c03c0773e24a44f6f3fd17ba5"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"path": "skills/messaging-frameworks/SKILL.md",
|
||||||
|
"sha256": "5b6c8c4b60404f890836d579f9d7d7c1eb616d8904e78815ddfda3289026c981"
|
||||||
|
}
|
||||||
|
],
|
||||||
|
"dirSha256": "a2f7223a52c25353a006dc596db9da2d6fd9bcf5785c79d4392eb7fa96d778c0"
|
||||||
|
},
|
||||||
|
"security": {
|
||||||
|
"scannedAt": null,
|
||||||
|
"scannerVersion": null,
|
||||||
|
"flags": []
|
||||||
|
}
|
||||||
|
}
|
||||||
31
skills/crisis-playbooks/SKILL.md
Normal file
31
skills/crisis-playbooks/SKILL.md
Normal file
@@ -0,0 +1,31 @@
|
|||||||
|
---
|
||||||
|
name: crisis-playbooks
|
||||||
|
description: Use when incidents occur and you need pre-approved workflows, templates,
|
||||||
|
and escalation paths.
|
||||||
|
---
|
||||||
|
|
||||||
|
# Crisis Communications Playbooks Skill
|
||||||
|
|
||||||
|
## When to Use
|
||||||
|
- Service outages, security incidents, compliance/regulatory events.
|
||||||
|
- Negative press cycles or social media escalations.
|
||||||
|
- Sensitive executive/HR news requiring coordinated messaging.
|
||||||
|
|
||||||
|
## Framework
|
||||||
|
1. **Severity Matrix** – classify incidents (P1-P4) with response SLAs and approvers.
|
||||||
|
2. **Escalation Tree** – who to notify, in what order, via which channels.
|
||||||
|
3. **Message Kits** – holding statements, customer/partner/internal scripts, social/status updates.
|
||||||
|
4. **Channel Sequence** – timeline for status page, email, press, social, internal posts.
|
||||||
|
5. **Monitoring & Recovery** – tracking sentiment, rumor control, follow-up updates.
|
||||||
|
|
||||||
|
## Templates
|
||||||
|
- Incident briefing doc (facts, unknowns, owners, deadlines).
|
||||||
|
- Approval checklist for legal/security/executive signoff.
|
||||||
|
- Post-incident report with RCA, comms metrics, and improvement actions.
|
||||||
|
|
||||||
|
## Tips
|
||||||
|
- Rehearse quarterly with tabletop exercises.
|
||||||
|
- Keep localized versions for regulated markets.
|
||||||
|
- Archive every incident’s comms artifacts for compliance and learning.
|
||||||
|
|
||||||
|
---
|
||||||
31
skills/media-database/SKILL.md
Normal file
31
skills/media-database/SKILL.md
Normal file
@@ -0,0 +1,31 @@
|
|||||||
|
---
|
||||||
|
name: media-database
|
||||||
|
description: Use when researching, segmenting, and maintaining journalist/analyst
|
||||||
|
contact lists.
|
||||||
|
---
|
||||||
|
|
||||||
|
# Media Database Operations Skill
|
||||||
|
|
||||||
|
## When to Use
|
||||||
|
- Building pitch lists for launches or thought-leadership campaigns.
|
||||||
|
- Cleaning and deduping media contacts after staffing changes.
|
||||||
|
- Tracking interactions, responses, and embargo agreements.
|
||||||
|
|
||||||
|
## Framework
|
||||||
|
1. **Research** – pull inputs from tools (MuckRack, Propel, manual research) covering recent articles, beats, social handles.
|
||||||
|
2. **Segmentation** – categorize by beat, outlet tier, region, relationship status, preferred format.
|
||||||
|
3. **Compliance** – store consent notes, GDPR considerations, embargo agreements, NDAs.
|
||||||
|
4. **Maintenance** – monthly hygiene (bounces, role changes, new publications).
|
||||||
|
5. **Insights** – log interactions to inform future pitches and avoid over-contacting.
|
||||||
|
|
||||||
|
## Templates
|
||||||
|
- Media list CSV schema.
|
||||||
|
- Outreach CRM board (status, last touch, next step).
|
||||||
|
- Consent/embargo tracking sheet.
|
||||||
|
|
||||||
|
## Tips
|
||||||
|
- Keep tags consistent so filters work across launches.
|
||||||
|
- Track social handles for quick DM coordination during crises.
|
||||||
|
- Note journalist preferences (format, lead time, exclusives) to personalize outreach.
|
||||||
|
|
||||||
|
---
|
||||||
31
skills/messaging-frameworks/SKILL.md
Normal file
31
skills/messaging-frameworks/SKILL.md
Normal file
@@ -0,0 +1,31 @@
|
|||||||
|
---
|
||||||
|
name: messaging-frameworks
|
||||||
|
description: Use when building message houses, key statements, and proof structures
|
||||||
|
for announcements or crises.
|
||||||
|
---
|
||||||
|
|
||||||
|
# Messaging Frameworks Skill
|
||||||
|
|
||||||
|
## When to Use
|
||||||
|
- Preparing PR/AR launches or executive communications.
|
||||||
|
- Aligning cross-functional teams on talking points.
|
||||||
|
- Rapid response situations requiring consistent statements.
|
||||||
|
|
||||||
|
## Framework
|
||||||
|
1. **Headline Statement** – core POV or claim.
|
||||||
|
2. **Support Pillars** – 2-3 proof points with data, customer stories, or analyst quotes.
|
||||||
|
3. **Evidence** – metrics, testimonials, product differentiators.
|
||||||
|
4. **Call to Action** – what audiences should think/feel/do next.
|
||||||
|
5. **Guardrails** – what not to say, words to avoid, regional nuances.
|
||||||
|
|
||||||
|
## Templates
|
||||||
|
- Message house diagram (headline, pillars, proof).
|
||||||
|
- FAQ builder (question, short answer, long answer, owner).
|
||||||
|
- Talking point checklist per spokesperson.
|
||||||
|
|
||||||
|
## Tips
|
||||||
|
- Update frameworks quarterly to reflect roadmap and market shifts.
|
||||||
|
- Provide short + long versions for different formats (press release vs interview).
|
||||||
|
- Pair with creative briefs to keep visuals aligned.
|
||||||
|
|
||||||
|
---
|
||||||
Reference in New Issue
Block a user