Skill Template

My skill name

by swan-gtm · MIT license · ★ 159 on GitHub · updated Sep 23

Use this skill when [the concrete trigger — a signal fires, a moment in the deal, a recurring cadence]. Produces [the concrete output].

---
name: my-skill-name
title: My skill name
description: |
  Use this skill when [the concrete trigger — a signal fires, a moment in the deal,
  a recurring cadence]. Produces [the concrete output]. [One or two more sentences
  dense with the phrases someone would actually say when they need this.]
category: Outreach
tags: [Sales]
metadata:
  internal: true # ← TEMPLATE ONLY — delete this metadata block in your copy
---

[One line: when this applies. One line: what it produces. Then delete every bracketed hint in this file.]

## The play

1. [First step — a GTM verb: "check the CRM", "load the ICP", "pull recent replies". Never a vendor tool name.]

Overview

[One line: when this applies. One line: what it produces. Then delete every bracketed hint in this file.]

Manual install (npx, ZIP)

Claude Codenpx skills add swan-gtm/gtm-skills --skill my-skill-name -g -a claude-code

Claude Code (manual)

mkdir -p ~/.claude/skills && curl -sL https://codeload.github.com/swan-gtm/gtm-skills/tar.gz/e65d97205fd2 \
  | tar -xz -C ~/.claude/skills --strip-components=2 gtm-skills-e65d97205fd2/templates/skill

Windows (PowerShell)

New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null; Invoke-WebRequest "https://m.agentalley.io/zip/c2865a0a0e81e2010468/skill.zip" -OutFile "$env:TEMP\skill.zip"; Expand-Archive "$env:TEMP\skill.zip" -DestinationPath "$HOME\.claude\skills" -Force

Claude.ai / desktopDownload the ZIP and upload it under Settings → Capabilities → Skills.

Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

SKILL.md1.3 KB
references/1 file · 1.1 KB

Read the files here

swan-gtm/e65d9722 files

SKILL.md1.3 KB

SKILL.md

Show the full text37 lines

skill-4/SKILL.md37 lines · 1.3 KB

PreviewCode

Outline

RawView on GitHub

[One line: when this applies. One line: what it produces. Then delete every bracketed hint in this file.]

The play

[First step — a GTM verb: "check the CRM", "load the ICP", "pull recent replies". Never a vendor tool name.]
[Next step.]
[If a step has depth worth its own page — a scoring rubric, worked examples, a channel variant — move it to references/<topic>.md and say here when to read it. Most skills worth installing ship 1–4 reference pages; see templates/skill/references/example-reference.md for the shape.]

What good looks like

[Mandatory section — this is the judgment that makes it a skill and not a checklist.]

[What the best operator notices first that others miss.]
[The common mistake — what the mediocre version looks like.]
[How you know the output is good, concretely.]

Rules

MUST [a hard rule].
NEVER [a hard failure mode].

1	---
2	name: my-skill-name
3	title: My skill name
4	description: \|
5	Use this skill when [the concrete trigger — a signal fires, a moment in the deal,
6	a recurring cadence]. Produces [the concrete output]. [One or two more sentences
7	dense with the phrases someone would actually say when they need this.]
8	category: Outreach
9	tags: [Sales]
10	metadata:
11	internal: true # ← TEMPLATE ONLY — delete this metadata block in your copy
12	---
13
14	[One line: when this applies. One line: what it produces. Then delete every bracketed hint in this file.]
15
16	## The play
17
18	1. [First step — a GTM verb: "check the CRM", "load the ICP", "pull recent replies". Never a vendor tool name.]
19	2. [Next step.]
20	3. [If a step has depth worth its own page — a scoring rubric, worked examples, a
21	channel variant — move it to references/<topic>.md and say here when to read it.
22	Most skills worth installing ship 1–4 reference pages; see
23	templates/skill/references/example-reference.md for the shape.]
24
25	## What good looks like
26
27	[Mandatory section — this is the judgment that makes it a skill and not a checklist.]
28
29	- [What the best operator notices first that others miss.]
30	- [The common mistake — what the mediocre version looks like.]
31	- [How you know the output is good, concretely.]
32
33	## Rules
34
35	- MUST [a hard rule].
36	- NEVER [a hard failure mode].
37