- Home
- Skills
- Tenequm
- Claude Plugins
- Web3 Protocol Gtm
web3-protocol-gtm_skill
- Python
14
GitHub Stars
4
Bundled Files
2 months ago
Catalog Refreshed
3 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill tenequm/claude-plugins --skill web3-protocol-gtm- CHANGELOG.md376 B
- package.json376 B
- project.json591 B
- SKILL.md24.2 KB
Overview
This skill is a go-to-market playbook for web3 builders: protocols, products, services, and solo founders. It focuses on community-led growth, developer adoption, Crypto Twitter narrative, composability, and practical sequences from testnet to token launch. Use it to plan growth, developer relations, hackathon pipelines, grant applications, and protocol traction metrics.
How this skill works
The skill inspects your stage, product type (protocol vs hosted product), and ICP to produce prioritized GTM actions, a 90-day sprint, and channel-specific tactics. It evaluates docs, SDK UX, integration friction, DevRel capacity, and CT narrative readiness, then recommends concrete steps: outreach targets, hackathon bounties, metrics to track, and token/launch sequencing. It also offers templates for outreach, threads, docs checklists, and DevRel automation with AI agents.
When to use it
- Planning go-to-market for a protocol, SDK, or crypto product
- Building or scaling a developer community and DevRel program
- Crafting founder-led Crypto Twitter narrative and content cadence
- Sequencing testnet → mainnet → token launch and grant applications
- Designing hackathon strategy, bounties, and follow-up conversion
- Evaluating ecosystem partnership and standards adoption tactics
Best practices
- Treat product quality and composability as primary marketing — make integration trivial
- Prioritize signal over size: 50 engaged builders beat 5k giveaway followers
- Founder-led CT narrative: post as a person, not a brand; follow a clear content mix
- Invest in docs and quickstarts before hiring large DevRel teams
- Use agentic DevRel to automate triage, 24/7 support, and personalized outreach
- Measure revenue, shipped integrations, GitHub activity, active wallets — ignore vanity TVL
Example use cases
- A solo founder prepping a 90-day GTM sprint for a new SDK and CT account
- A protocol team designing hackathon bounties, workshops, and post-event follow-up
- An infra project optimizing docs and SDK for AI-readability and fast onboarding
- A product team planning token launch sequencing and market narrative
- A DevRel lead implementing AI agents to scale support and retention
FAQ
Yes — core principles apply, but hosted products need adapted pricing, embedded wallet UX, and direct conversion funnels; treat distribution and metrics differently.
How should I prioritize channels with limited time?
Focus on developer channels (GitHub, hackathons, Discord) and founder-led Crypto Twitter first, then add targeted KOLs and partnerships once integrations are shipping.