Events
coreyhaines31/marketingskills
When the user wants to plan, run, sponsor, speak at, or get pipeline from events — webinars, conferences, trade shows, meetups, dinners, workshops, virtual summits, or user conferences.
A skill your agent uses when operationalizing regional/field events with consistent playbooks and follow-up motions.
$ npx skills add gtmagents/gtm-agents --skill field-playbooks -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install gtmagents/gtm-agents field-playbooks --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/gtmagents/gtm-agents.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/event-marketing/skills/field-playbooks .claude/skills/field-playbooks && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "field-playbooks" agent skill from https://github.com/gtmagents/gtm-agents/tree/main/plugins/event-marketing/skills/field-playbooks into .claude/skills/field-playbooks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "field-playbooks", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/gtmagents/gtm-agents/tree/main/plugins/event-marketing/skills/field-playbooksType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add gtmagents/gtm-agents --skill field-playbooks -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install gtmagents/gtm-agents field-playbooks --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gtmagents/gtm-agents.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/event-marketing/skills/field-playbooks .agents/skills/field-playbooks && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "field-playbooks" agent skill from https://github.com/gtmagents/gtm-agents/tree/main/plugins/event-marketing/skills/field-playbooks into .agents/skills/field-playbooks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "field-playbooks", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add gtmagents/gtm-agents --skill field-playbooks -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install gtmagents/gtm-agents field-playbooks --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gtmagents/gtm-agents.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/event-marketing/skills/field-playbooks .cursor/skills/field-playbooks && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "field-playbooks" agent skill from https://github.com/gtmagents/gtm-agents/tree/main/plugins/event-marketing/skills/field-playbooks into .cursor/skills/field-playbooks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "field-playbooks", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/gtmagents/gtm-agents.git --path plugins/event-marketing/skills/field-playbooks--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add gtmagents/gtm-agents --skill field-playbooks -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install gtmagents/gtm-agents field-playbooks --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gtmagents/gtm-agents.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/event-marketing/skills/field-playbooks .gemini/skills/field-playbooks && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "field-playbooks" agent skill from https://github.com/gtmagents/gtm-agents/tree/main/plugins/event-marketing/skills/field-playbooks into .gemini/skills/field-playbooks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "field-playbooks", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install gtmagents/gtm-agents field-playbooksInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add gtmagents/gtm-agents --skill field-playbooks -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/gtmagents/gtm-agents.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/event-marketing/skills/field-playbooks .github/skills/field-playbooks && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "field-playbooks" agent skill from https://github.com/gtmagents/gtm-agents/tree/main/plugins/event-marketing/skills/field-playbooks into .github/skills/field-playbooks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "field-playbooks", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add gtmagents/gtm-agents --skill field-playbooks -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install gtmagents/gtm-agents field-playbooks --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gtmagents/gtm-agents.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/event-marketing/skills/field-playbooks .opencode/skills/field-playbooks && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "field-playbooks" agent skill from https://github.com/gtmagents/gtm-agents/tree/main/plugins/event-marketing/skills/field-playbooks into .opencode/skills/field-playbooks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "field-playbooks", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
field-playbooksA skill your agent uses when operationalizing regional/field events with consistent playbooks and follow-up motions.
Field Playbooks is an agent skill from gtmagents/gtm-agents. Use when operationalizing regional/field events with consistent playbooks and follow-up motions.
Its SKILL.md is about 310 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Production-ready collection of GTM agents and specialized skills for claude code. Covers sales, marketing, customer success, and revenue operations workflows. The licence is Apache-2.0.
5 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 78e0419. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Field Playbooks loads about 314 tokens when it runs. Until then it costs about 28 tokens; SKILL.md has 131 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from gtmagents/gtm-agents at commit 78e0419, republished under its Apache-2.0 licence (© gtmagents). 131 words, ~314 tokens.
.claude/skills/field-playbooks/SKILL.md (or your agent's skills folder).© gtmagents, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in plugins/event-marketing/skills/field-playbooks of gtmagents/gtm-agents.
Open the folder on GitHubat commit 78e0419
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in gtmagents/gtm-agents, which our catalogue first saw on October 7, 2026.
Field Playbooks next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Field Playbooks this skillgtmagents/gtm-agents | 414 | 1 repos | ~314 | Automated safety check: Pass | Apache-2.0 | |
| Eventscoreyhaines31/marketingskills | 54k | — | ~3k | Automated safety check: Pass | MIT | |
| Events And Field Marketingcbrock84/headcount | 2k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Event Sourcing Architectdavila7/claude-code-templates | 33k | 4 repos | ~659 | Automated safety check: Pass | MIT | |
| Event Store Designwshobson/agents | 40k | 9 repos | ~828 | Automated safety check: Pass | MIT | |
| Esign Field Placementaffaan-m/ECC | 277k | — | ~2.6k | Automated safety check: Pass | MIT |
coreyhaines31/marketingskills
When the user wants to plan, run, sponsor, speak at, or get pipeline from events — webinars, conferences, trade shows, meetups, dinners, workshops, virtual summits, or user conferences.
cbrock84/headcount
Plans and runs events that produce pipeline — conferences, trade shows, webinars, field programs, and measuring whether any of it worked.
davila7/claude-code-templates
Expert in event sourcing, CQRS, and event-driven architecture patterns.
wshobson/agents
Designs event stores for event-sourced systems: requirements, a comparison of EventStoreDB, PostgreSQL, Kafka, DynamoDB and Marten, and stream and versioning practices.
affaan-m/ECC
Deterministic method for placing signature, date, and text fields in a web e-signature composer through a browser automation session, using a fixed signature page, numeric Location panel coordinates…
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing scripts, client components, bundles, or runtime behavior related to Use event delegation for dynamic content.
gtmagents/gtm-agents
Chooses and orders data providers for email, phone, company and intent enrichment, with waterfall sequences and credit-saving tactics across 150+ sources.
gtmagents/gtm-agents
Writes personalized B2B cold emails from prospect research, using a gated workflow, a quality rubric and follow-up sequences.
gtmagents/gtm-agents
Structures sales discovery calls with a PREP routine, a five-part call flow, a question bank, a qualification scorecard and a follow-up recap email.
gtmagents/gtm-agents
Frames marketing automation around lifecycle stages, signals, touches and SLAs, with worksheets for onboarding, expansion, renewal and churn-prevention journeys.
gtmagents/gtm-agents
A skill your agent uses when engaging prospects through LinkedIn, communities, and social channels to spark warm conversations and meetings.
gtmagents/gtm-agents
A skill your agent uses when you need to map sequenced nurture flows with pacing, storytelling arcs, and value ladders.
A skill your agent uses when operationalizing regional/field events with consistent playbooks and follow-up motions. Field Playbooks is an agent skill from gtmagents/gtm-agents. Use when operationalizing regional/field events with consistent playbooks and follow-up motions.
Field Playbooks fits situations like: operationalizing regional/field events with consistent playbooks and follow-up motions.
Run `npx skills add gtmagents/gtm-agents --skill field-playbooks -a claude-code`. Or copy the skill folder (plugins/event-marketing/skills/field-playbooks in gtmagents/gtm-agents) into .claude/skills/field-playbooks in your project. Claude Code loads it when a task matches its description.
Run `npx skills add gtmagents/gtm-agents --skill field-playbooks -a codex`. Or copy the skill folder (plugins/event-marketing/skills/field-playbooks in gtmagents/gtm-agents) into .agents/skills/field-playbooks in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add gtmagents/gtm-agents --skill field-playbooks -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/field-playbooks, .gemini/skills/field-playbooks, .github/skills/field-playbooks and .opencode/skills/field-playbooks in your project.
SKILL.md names no scripts, command-line tools or credentials: Field Playbooks is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Field Playbooks is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 314 tokens (SKILL.md is roughly 1.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Field Playbooks: Events (coreyhaines31/marketingskills, 54k stars), Events And Field Marketing (cbrock84/headcount, 2k stars), Event Sourcing Architect (davila7/claude-code-templates, 33k stars) and Event Store Design (wshobson/agents, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
gtmagents (a GitHub user) maintains it in gtmagents/gtm-agents, which has 414 GitHub stars. The repository holds 121 skills in this directory. The repository was last updated on April 3, 2026.
Source: gtmagents/gtm-agents on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.