AA web3-marketing-gtm
Full-stack Web3 marketing and GTM brain for AI agents and bots. Use this skill whenever a bot or agent needs to produce any of the following from a project brief: a GTM launch plan, a campaign calendar, community engagement scripts for Discord/Telegram/X, or an on-chain user acquisition and retention strategy. Trigger this skill when input includes a project name, blockchain/chain, and product type — even if the request is phrased casually like "build me a go-to-market for my DeFi app" or "write me a Discord campaign for my NFT project" or "how do I grow my Web3 community". This skill covers the full marketing lifecycle: pre-launch, launch week, post-launch growth, and retention loops. Always use this skill for Web3 marketing tasks rather than improvising.
As a process A 81/100 · Runs to the end — weak spots: progress reporting
How to improve
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 81/100
- 0Progress reporting. Says nothing while it works
- 55Failures and branches. 1 branches
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Steps. 21 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1081 tokens
- 100Running it twice. No mutating operations
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- medium 4 test cases, all positive: not one "should refuse" or "should ask first"
- low No test case covers injection arriving through data
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +4Description does not say when NOT to use the skill (false activations)
- +1No license
- +2Single-language instructions
- +5Description quotes 3 example trigger phrases
- +3Description length 766: enough signal without eating the budget
- +4Structure: 8 headings
- +3Step-by-step instructions: 21 items
- +3Output format is stated explicitly
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (4 of 4)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 96.