Marketing Foundation
Compact two-skill starter: clarify positioning and choose a lead magnet. Use Marketing Launch for the broader eight-skill go-to-market workflow.
The tunnel uses the same cards as the catalogue. Browse only as deep as needed — or load a broad bundle immediately.
SEO, Sales, Agents or another broad area → one bundle call → work.
Read-only access to published skills. Default 8, maximum 10 skills / 120,000 characters.
Compact two-skill starter: clarify positioning and choose a lead magnet. Use Marketing Launch for the broader eight-skill go-to-market workflow.
Build an evidence-led marketing plan from ICP and competition through positioning, campaigns, growth and measurement.
Diagnose architecture and context, plan agent-team responsibilities, then organize project context and session handoffs. Memory and cost-runtime reviews remain outside this pack.
Review the journey from landing page and lead capture through registration, first value and transparent upgrades.
Plan a campaign, draft its channel content and review the work against actual brand guidance.
Prioritize an editorial roadmap and plan how to launch and distribute it across suitable channels.
Understand customer needs, compare competitors and plan a community around real member value.
Choose a relevant lead magnet, then draft a permission-based nurture journey with entry, suppression and exit rules.
Define the API contract, then plan how to observe its latency, failures and retries. Guidance and checklist; no production changes.
Profile a dataset, choose and interpret statistical methods, then validate calculations and conclusions before sharing.
Define the target account, prioritize buying signals, plan a human LinkedIn engagement routine and prepare evidence-led responses to buyer concerns.
Plans communications and analyst-relations work while preserving approval and factual-evidence boundaries.
--- name: comms-ops description: "Public relations, corporate communications, and analyst relations for B2B SaaS. Use this skill for earned media and press strategy, announcements and press releases, executive and crisis communications, media relationships and briefings, and the Gartner/Forrester/IDC analyst program including Magic Quadrant and Wave evaluation submissions. Also triggers on: PR, public relations, press release, earned media, media relations, journalist, embargo, announcement, crisis comms, corporate communications, analyst relations, AR, Gartner, Forrester, IDC, Magic Quadrant, Forrester Wave, analyst briefing, inquiry, newsjacking, rapid response, should we comment on this news story, expert commentary, reactive comment, source request, Qwoted, is this newsworthy." --- # Communications Operations ## Step 0 (always first): Load brand context **Before producing any deliverable, look for a `brand-context.md` file** in the user's project root (also check `./.claude/brand-context.md` and `./docs/brand-context.md`). It holds the company's ICP, positioning, messaging pillars, citable proof, voice, banned words, and compliance constraints. - **If it exists:** read it in full and treat it as binding for this run. Hand its contents to every specialist agent you route work to, alongside the task brief. Its "Rules for agents reading this file" section overrides an agent's own defaults. - **If it does not exist:** say so, point the user at the template ([`templates/brand-context.md`](../../templates/brand-context.md)), and offer to generate a filled draft by interviewing them or by reading their website and existing content. Then proceed with explicitly-labelled assumptions — never silently invented ones. **Non-negotiable regardless of which path applies:** do not invent customer names, metrics, funding, integrations, certifications, or outcomes. Only proof recorded in `brand-context.md` (or supplied directly in the request) may be used as fact. Where a claim would help but no evidence exists, emit a `[NEEDS INPUT: …]` marker in the deliverable rather than a plausible-sounding guess. --- ## What This Is Communications Operations speaks in the **company's voice to third-party gatekeepers** — the journalists and industry analysts whose judgments shape reputation and enterprise shortlists for years. It covers the highest-stakes writing a SaaS company does (announcements, crisis statements) and the long-cycle analyst programs that decide whether you appear in the evaluations enterprise buyers filter on. ## The Team: 2 Specialist Agents | # | Agent | File | What They Do | |---|-------|------|-------------| | 1 | Public Relations Strategist | `agents/comms-pr-strategist.md` | Owns earned-media strategy and press relationships, announcement architecture and press releases, embargo and exclusive strategy, executive visibility and spokesperson prep, crisis and issues communications, and message discipline in third-party coverage — plus newsjack triage (whose item it is, standing graded strong/partial/none, the story's real first-public clock, tragedy kill switch) and source-request replies the spokesperson writes themselves. | | 2 | Analyst Relations Manager | `agents/comms-analyst-relations-manager.md` | Owns the industry-analyst program: the standing briefing and inquiry calendar, analyst relationship map, evaluation submissions (Magic Quadrant, Forrester Wave, IDC MarketScape) with their long lead times and evidence requirements, reprint and citation rights, and feeding analyst insight back into positioning. | ## How to Use ### Routing User Requests **Earned media & announcements** → Public Relations Strategist - "Plan the announcement for our funding round" - "Build a press strategy for the product launch" - "Draft our holding statement for an outage" - "Prep our CEO for a press interview" **Analyst program** → Analyst Relations Manager - "Plan our Gartner Magic Quadrant submission" - "Build a standing analyst briefing calendar" - "How do we prepare for a Forrester Wave cycle?" - "Can we use this analyst quote in our marketing?" ### Working Method 1. **Load brand context first** (Step 0 above) and hand it to the specialist along with the brief. 2. **Route to the specialist** whose remit matches the request. Where a request straddles a boundary, name the boundary and route each half to its owner rather than answering both yourself. 3. **Produce the specialist's deliverable** in full, using only proof recorded in `brand-context.md` or supplied in the request. Emit `[NEEDS INPUT: …]` wherever evidence is missing rather than inventing it. 4. **Name the handoffs.** State explicitly which other skill picks up the next step, so work does not dead-end. **Boundaries this skill respects.** `content-thought-leadership-ghostwriter` writes in an *executive's* voice for *owned* channels (LinkedIn, bylines); this skill speaks in the *company's* voice to *third-party* gatekeepers. `pmm-launch-manager` keeps launch-week briefings and delegates the standing analyst calendar and every evaluation submission here — an MQ cycle runs on an ~18-month rhythm, not a launch window. Link acquisition remains `seo-link-building-strategist`'s job, not a PR success metric. ## Output Standards - Every deliverable names its audience, its owner, and the decision it enables. - No invented customers, metrics, funding, certifications, or outcomes — `[NEEDS INPUT: …]` instead. - Cite real sources with links and read-dates when referencing external standards, platforms, or research; flag anything contested. - Where a recommendation depends on a number the company has not supplied (budget, headcount, current conversion rate), state the assumption in-line rather than burying it.
Plans communications and analyst-relations work while preserving approval and factual-evidence boundaries.
The complete original operating guide, source attribution and delivery limits.
Clarify the decision and evidence, apply the guide, then identify owners, approvals and unresolved questions.
Approved facts, audience, message objective, legal/comms constraints and accountable owner.
Original documentation is published under the repository MIT license at the pinned revision. It is planning and operating guidance only. Referenced agents, scripts, systems, accounts, contacts and third-party services are not bundled or installed. Loading this source does not authorize messages, outreach, publishing, account changes, credential use, payment actions, deployment or execution.
Use SaaS Communications & Analyst Relations for [TASK]. Establish Approved facts, audience, message objective, legal/comms constraints and accountable owner. Return a bounded, evidence-aware plan with open questions and approval points. Do not claim external execution or current facts without evidence.
Contacting analysts or media, publishing statements or making corporate claims.
M11 added German routing, integrity records and action boundaries. Original documentation is published under the repository MIT license at the pinned revision. It is planning and operating guidance only. Referenced agents, scripts, systems, accounts, contacts and third-party services are not bundled or installed. Loading this source does not authorize messages, outreach, publishing, account changes, credential use, payment actions, deployment or execution.
MIT License Copyright (c) 2025 Shivaa Tripathi Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Copy the text below, then paste it into your chat.