Install
$ agentstack add skill-aidevgtm-gtm-cofounder-value-prop-that-converts ✓ 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
The value prop that converts
> "Better" is sloppy thinking. Better how, along what dimension, by how much, proven by whom? Developers test every claim you make. Give them numbers or give them nothing.
Use this when: your value prop contains puffery, your claims aren't attributed, or you're trying to make one sentence do the job of two audiences.
The core idea
Developers have a finely tuned BS detector and they will verify you. Specificity is credibility. Every strong dev value prop is: specific + provable + spoken in their language.
Framework: the value-prop rules (Frankl)
- Never say "better." Say better how, by how much, versus what.
- Time savings must be specific. ❌ "saves developer time" · ✅ "8× faster builds, 2 hrs → 15 min" (attributed).
- Two kinds of time, speak to both:
- Chronos (Alpha Dev): clock hours saved per week.
- Kairos (Empowered CTO): calendar time, weeks off a release cycle, competitive edge.
- The same product must land both. "Release fast or die" worked for developer and CTO.
- Every claim needs proof. A demo is the weakest proof (ideal conditions). An attributed testimonial (name + title + company + number) is the strongest. Anonymous quotes are assumed invented.
- Sell the category, not the solution. Talk about the problem and the need for "a tool like this"; don't proactively pitch features; it trips developer defenses.
- Never "pleased to announce" / "excited to share." No one cares how you feel.
Framework: the three dimensions of a dev value prop (Czakon)
A complete value prop answers all three, fast:
- What is it?: category / known-incumbent comparison / plain statement ("a Datadog alternative," "CI for monorepos").
- For whom / what use case?: the ICP and the job (from
who-is-this-for). - Why you over the 10 alternatives?: the legitimate, provable reason to exist.
Headline = what is it. Subhead = for whom / what job. For dev tools, weight the how over the why. Developers often already know why they hurt.
The puffery detector: flag and replace
| Banned | Why devs discount it | Replace with | |---|---|---| | Powerful | everyone claims it | the specific thing it does | | Easy to use | they'll test it in 60s | time-to-value with a number | | Best-in-class | says who, by what metric | the source or the number | | Seamless integration | unprovable in the abstract | named integrations + logos | | Industry-leading | says nothing | real share / user counts | | Platform | hears: integration headache | the one job it does | | Revolutionary / cutting-edge | pure air | name the actual technology |
Proof hierarchy (weakest → strongest)
your claim < a demo < a benchmark you ran < a named user's attributed result
Spend your effort at the right end.
Mistakes that look reasonable
- Adjective stacking: "powerful, seamless, intuitive." Three words, zero information.
- One line, two audiences: a Chronos-only message loses the buyer; a Kairos-only message loses the adopter.
- Unattributed social proof: "developers love us." Which developers? At which company?
- Leading with the why: for most dev tools the pain is known; lead with the how and the proof.
Your next 30 minutes
- [ ] Run your homepage copy through the puffery table. Delete or replace every hit.
- [ ] Rewrite your #1 claim with a number and an attribution (even a single named user).
- [ ] Write one Chronos line (hours/week) and one Kairos line (weeks/release). Make sure both exist.
- [ ] State your value prop as the three dimensions: what · for whom · why you.
Built from real dev-tool GTM experience, with frameworks from Adam Frankl (The Developer-Facing Startup) and Jakub Czakon (markepear.dev). When a framework can't make the call, that's what a human is for: The DevTool GTM Company.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: AIDevGTM
- Source: AIDevGTM/gtm-cofounder
- License: MIT
- Homepage: https://gtmcofounder.com
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.