Skip to content
Agentmart
Submit a tool

gtm

Build an evidence-aware go-to-market plan for a product, feature, segment, or positioning change across positioning, channels, messages, timeline, metrics…

Skill by ThorStarlord

IndexedMIT
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/thorstarlord-gtm

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Build an evidence-aware go-to-market plan for a product, feature, segment, or positioning change across positioning, channels, messages, timeline, metrics, contingencies, and cross-functional coordination. Use for a commercial_strategy responsibility and produce gtm_plan. Treat reach, conversion, revenue, timing, channel fit, messaging resonance, and customer claims as hypotheses or proposals unless evidence supports them; planning never sends outreach, schedules campaigns, publishes assets, changes pricing, or grants external execution authority.

Use cases: sales

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/gtm

What's inside

Skill name
gtm
Description
Build an evidence-aware go-to-market plan for a product, feature, segment, or positioning change across positioning, channels, messages, timeline, metrics, contingencies, and cross-functional coordination. Use for a commercial_strategy responsibility and produce gtm_plan. Treat reach, conversion, revenue, timing, channel fit, messaging resonance, and customer claims as hypotheses or proposals unless evidence supports them; planning never sends outreach, schedules campaigns, publishes assets, changes pricing, or grants external execution authority.
License
MIT
Instructions
27 lines in SKILL.md · view on GitHub

Files (2)

  • SKILL.md
  • contract.md · references/

SKILL.md (first lines)

# Go-to-market

Satisfy a `commercial_strategy` responsibility by producing `gtm_plan`.

## Inputs

Require the offer/product change, target segment, launch/commercial objective, and evidence/currentness boundary. Prefer strategy, ICP/persona, market analysis, pricing, customer research, channel performance, budget/constraint, and launch-readiness evidence when available.

## Procedure

1. Read [references/contract.md](references/contract.md).
2. Bind the offer, segment, objective, evidence window, constraints, and any ratified commitments before planning tactics.
3. Inventory positioning/customer/market/channel evidence and separate observed claims from inference and hypotheses.
4. Draft positioning claims whose strength matches the evidence actually available.
5. Select a bounded set of channels and explain the evidence or hypothesis behind each; do not fabricate reach or conversion history.
6. Derive audience-specific messages from declared claims rather than inventing customer proof points.
7. Define proposed actions/timing, success metrics, guardrails, and contingencies. Unknown baselines stay unknown and targets remain proposals unless supplied as ratified commitments.
8. Mark externally consequential actions as planned only; sending, publishing, ad spend, outreach, price changes, or campaign activation require separate authority.
9. Preserve unresolved channel, message, budget, positioning, timing, and measurement uncertainty.
10. Stop when further analysis would not change the bounded plan or when required evidence/authority is unavailable.
11. Return `gtm_plan` and control.

## Boundary

`GTM plan != campaign execution`, `target != observed result`, `message != proven resonance`, `channel recommendation != budget authorization`, `timeline proposal != commitment`, and `artifact valid != market success`.

From ThorStarlord/sensemaking-skills, MIT.

More from ThorStarlord/sensemaking-skills

Signals

Stars
0
Forks
0
Open issues
7
Last commit (this folder)
Sep 10, 2026 (1 month ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from ThorStarlord

Cite this page

gtm skill. Agent Mart. https://agentmart.dev/skills/thorstarlord-gtm (last updated 2026-10-24)