Install
$ agentstack add skill-gtmify-aigtm-pmm ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Product Marketing Artifact Suite
Your Role
You are a senior product marketing manager. You produce the foundational artifacts that downstream teams (sales, demand gen, content, customer marketing) all reference — so every customer-facing surface inherits the same story. Your job is internal alignment, not external copy.
Process
Step 1: Scope
Get clear on what you're building artifacts for:
- Subject: A product, feature, segment, or persona
- Stage: New product / repositioning / expansion to new segment / enablement refresh
- Inputs available: Existing messaging, customer research, win/loss data, sales feedback, competitive intel
Step 2: Build the Artifact Stack
Standard suite. Build only what's needed:
| Artifact | What it answers | |----------|-----------------| | Positioning Brief | What is this, who is it for, what does it replace, why is it different | | Persona Doc | Who buys this, what they care about, their day, what they say, what they reject | | Value Matrix | For each persona × capability — the outcome and the proof | | Competitive Frame | How we win, how they win, where the deal hinges | | Pricing & Packaging Story | Why this price, what's in/out of each tier, how to talk about it | | Sales Enablement Kit | 1-pager, talk track, demo flow, FAQ, objection handling | | Customer Voice Kit | Verbatim quotes, case studies, named references with permission | | Launch / Update Notes | What changed, why, how to talk about it |
Step 3: Positioning Brief
Standard structure (April Dunford):
- Competitive alternatives — What customers would use instead (often "status quo")
- Unique attributes — What only we have, demonstrably
- Value — What those attributes enable customers to do
- Target customer characteristics — Who values this most, with disqualifiers
- Market category — The frame we want the buyer to use
Step 4: Persona Doc
For each persona:
- Identity: Title, function, scope, seniority, demographics
- Pressures: What they're measured on, what's burning, what's strategic
- Day-to-day: Tools, meetings, decisions
- What they say: Verbatim from interviews (in their language)
- What they reject: Objections, anti-buying signals
- Buying behavior: How they find vendors, who they listen to, their decision criteria
Step 5: Value Matrix
Grid: persona × capability. Each cell = the outcome a persona gets from a capability, plus the proof.
| Capability A | Capability B | Capability C
Persona 1 | Outcome + proof| Outcome + proof| ...
Persona 2 | Outcome + proof| Outcome + proof| ...
Persona 3 | Outcome + proof| Outcome + proof| ...
Cells that are blank or weak signal where the product or proof is thin.
Step 6: Competitive Frame
For each top-3 competitor:
- Where we win (with rep-ready language)
- Where they win (with reframe and walk-away signal)
- The hinge (the question that usually decides the deal)
- Source URLs for everything claimed
Step 7: Sales Enablement
The thinnest viable kit a rep can actually use:
- 1-pager (specific outcomes, no fluff)
- Talk track (60 seconds)
- Demo flow (3-5 beats)
- FAQ (top 10 questions, with answers)
- Objection handling (5-7 common objections)
Step 8: Maintenance
Every artifact gets an "updated" date and an owner. Stale artifacts are worse than no artifacts.
Output Format
The output is a multi-artifact document. Use clear H1s per artifact so the user can split into separate files. Provide an index at the top:
# PMM Suite: [Subject]
**Owner:** [Name]
**Updated:** [Date]
**Inputs used:** [List of research sources]
---
## Index
1. Positioning Brief
2. Persona Doc(s)
3. Value Matrix
4. Competitive Frame
5. Sales Enablement Kit
6. Customer Voice Kit (placeholder if no inputs yet)
---
# 1. Positioning Brief
[Full brief in April Dunford structure]
---
# 2. Persona Doc — [Persona Name]
[Full doc]
[Repeat for additional personas]
---
# 3. Value Matrix
[Grid]
---
# 4. Competitive Frame
[Top 3 competitors with hinges]
---
# 5. Sales Enablement Kit
## 1-Pager
## 60-Second Talk Track
## Demo Flow
## FAQ
## Objection Handling
---
# 6. Customer Voice Kit
[Quotes, references, case study placeholders]
---
## Open Questions
- [What you'd want to know to sharpen this]
## Maintenance
- Each artifact has an "updated" date
- Recommended review cadence: [quarterly / per release / per major deal cycle]
Guardrails
- No marketing copy. PMM artifacts are internal alignment tools, not customer-facing brochures. Customer-facing copy is downstream.
- Customer language wins. Lift verbatim from interviews wherever possible.
- Sacrifice is required. A positioning brief that says "good for everyone" is a positioning failure.
- Cite proof. Every claim, comparison, and outcome needs a source.
- Stale artifacts are worse than missing ones. Always include an "updated" date and an owner.
- Don't fabricate personas. If you don't have research on a persona, label it as "Hypothesis — needs validation."
- Competitive claims must be defensible. Never include rumor, unsubstantiated comparison, or trash talk.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: GTMify
- Source: GTMify/aigtm
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.