Turns research (win/loss notes, call transcripts, G2/Capterra reviews, analyst reports) into a named alternatives map across direct competitors, adjacent tools, DIY and status quo, each with why-chosen, why-left and unclaimed territory, then deepens brain Section 3. Trigger with "map our alternatives", "who do we actually compete with", "status quo analysis", "our alternatives section is just a competitor list", or any request to identify, evidence, or sharpen who buyers compare you to.

Builds a "you vs a named rival" comparison page or a "best alternatives to X" page from your brain, your competitor records and fresh public sources, with a sourced claims ledger so every row on the page can be defended. One dataset renders the public SEO page and the sales-sent version. Trigger on: "comparison page brief", "build a comparison page", "X vs Y page", "alternatives to [competitor] page", "versus page for [competitor]", "migration or switch page from [competitor]", "refresh our vs page". Not for a seller card (competitive-battlecard), one competitor question (competitive-profile), a long write-up (competitor-deep-dive), the leadership brief (competitive-briefing) or a weekly page sweep (media-monitoring).

Builds a dated 360-degree brief on one existing customer from your CRM, email, calls, docs, chat, support and usage, checks it against your brain (ICP fit, competitors, objections, approved claims) and shows what changed since the last brief. Built for Slack first: a seller tags Claude in a thread and gets a short sourced answer, and the same skill works in Claude chat, Cowork, Claude Code and scheduled runs. Trigger on: "customer context for [customer]", "catch me up on [customer]", "what's going on with [customer]", "brief me on [customer] before the renewal", "what changed at [customer]", "is [customer] at risk". Not for a company that is not yet a customer (prospect-research), a competitor (competitive-profile), a competitor in a live deal (competitive-battlecard) or a customer story (customer-stories).

Runs a B2B customer story from kickoff to customer approval: kickoff questions, internal brief, interview questions, a draft in one fixed structure, the customer review pack and an audit, with every stat and quote checked. Trigger on: "write a customer story", "kick off a case study", "customer interview questions", "prepare the customer review", "audit this customer story". Related: interview-summary, proof-points, writing-assistant.

Generates several concrete, cost-efficient growth ideas, each with a channel, core message and cost-efficiency rationale, grounded in your brain's ICP, alternatives and market context. Trigger with "give me marketing ideas", "brainstorm growth tactics", "what should we try", "cheap ways to promote this", or any request to generate raw campaign or channel ideas before committing to one to test.

Builds the weekly industry newsletter for GTM leaders: what changed with your competitors and in your industry, in one locked layout with numbered competitor tables (3 to 5 product updates), a pricing watch and role-owned actions. Asks where it will be read (Google Doc, email or Slack), pulls leads from your other CI skills, Gong, Slack, Klue and Drive, and publishes only what a public page confirms. Grades its last call. Triggers: "write this week's industry newsletter", "weekly competitor and industry newsletter", "grade the last industry newsletter call", "forwardable industry newsletter for the exec team". Not for the euro decision brief (competitive-briefing), an opportunities list (signal-monitor), one competitor question (competitive-profile), a seller card (competitive-battlecard), a long write-up (competitor-deep-dive), a public newsletter (writing-assistant) or the scheduled sweep (media-monitoring).

Turns raw customer interview transcripts into structured discovery outputs anchored in JTBD theory, with signal-level pattern detection and confidence scoring. Trigger on: "summarize interview", "process transcript", "interview summary", "what did customers say", "synthesize discovery", "interview debrief", "JTBD analysis", "customer insight", "research synthesis", or any request to process, structure, or extract meaning from a customer or prospect interview.

Sweeps the public pages of your 3 to 5 core competitors on a schedule and returns a one-screen brief: what needs you this week with the fix already drafted, what needs no action, and what the sweep could not see. One person runs it with a named backup; the team reads the Slack post and Doc. Nothing is changed or sent without your go. Trigger on: "run the media monitoring", "weekly competitor sweep", "monitor my competitors' public pages", "what did the monitoring catch", "set up media monitoring". Not for the leadership brief (competitive-briefing), one competitor's question (competitive-profile), a seller card (competitive-battlecard), a long write-up (competitor-deep-dive), a weekly opportunities list (signal-monitor) or the industry newsletter (industry-newsletter).

Turns your existing positioning into one clean table: your core story at the top, your 3 supporting reasons to believe it below. Use when someone asks to "build a message house," "put our messaging in a message house," or wants positioning laid out as one scannable page.

Reads /context/skill-sessions.md to detect patterns that repeat across 2+ sessions, proposes new guardrails for /context/meta-patterns.md, and proposes brain updates for confirmed learnings. Reads the ledgers other skills keep (outcomes, patterns, usage), not only the session log, and in weekly mode shows adoption per skill and one promotion queue. Trigger on: "run meta-synthesis", "what patterns are emerging", "detect cross-skill signals", "update guardrails", "compound our learnings", "what should we remember", "run the weekly learning sweep". Not for a sales-only weekly report (sales-research-digest).

Builds a complete, export-ready quarterly OKR set for PMM leaders and individual PMMs: Objective, Key Results, Projects, Scorecard metrics and Exec Summary language, paste-ready for the PMM OKR Builder spreadsheet. Use when setting quarterly OKRs, reviewing existing OKRs, stress-testing KR quality, or building a measurement plan. Trigger on: "help me set our OKRs", "are my KRs measurable", "build a scorecard", "stress-test this KR", "write OKRs for my team", "present goals to exec team".

Turns what your sales team's research skills logged this week into one plain-language report for the PMM: who used them, whether the advice held up, what the companies have in common, and up to three things to do. Reads outcomes from your CRM and pushes you to connect it if it is missing. Covers the pmm-sales skills only. Trigger on: "weekly sales digest", "how is the sales team using the research briefs", "which research briefs got ignored", "what are sellers seeing at prospects this week". Not for the repo-wide weekly sweep across every skill (meta-synthesis), research on one company (prospect-research) or one customer (customer-context).