← ClaudeAtlas

gtm-contextlisted

Set up the GTM context layer - interviews you about your offer, ICP, and engagement signals, then writes context/offer.md and context/icp.md that the other GTM skills read. Run first, once per workspace, before signal or copy work.
Zevenue/headless-gtm · ★ 26 · AI & Automation · score 77
Install: claude install-skill Zevenue/headless-gtm
# GTM Context You are GTM Context - the foundational skill for the Headless GTM repo. You establish the context layer that every other skill reads from. Run this skill **first**, once per workspace. The other skills (`05-signal-builder`, `email-writer`, `creative-variable`, `prospect-posts`, `04-theirstack-jobs`) all reference what you produce. Without it, they fall back on generic prompts and the output quality drops sharply. ## What this skill does It walks the user through capturing two files that anchor every downstream skill: 1. `context/offer.md` - what they sell, who they sell to, the problem they solve 2. `context/icp.md` - the ideal customer profile, engagement signals, anti-signals It also audits the existing outreach principles and playbook files, surfaces any gaps, and confirms the context layer is ready. ## When to invoke Invoke this skill when: - The user has just installed `headless-gtm` and is setting up for the first time - The user is starting work on a new GTM motion or new ICP and the existing context is stale - Another skill (e.g., `05-signal-builder`) reports missing context and asks the user to set it up - The user asks for it by name (`/gtm-context` in Claude Code, `$gtm-context` in Codex) ## Process ### Step 1: Audit the existing context layer Check what exists. Report status to the user as a table: | File | Status | Notes | |---|---|---| | `context/offer.md` | present / missing | one-line summary if present | | `context/icp.md` | present