Plugin skills
Each skill in gtme's Claude Code plugin, its slash command, and when it fires, generated from plugin/skills
What you'll learn
You use gtme from Claude Code and want to know which slash command does what, or when a skill fires on its own.
- each skill's slash command
- when each skill fires
- where the plugin install is documented
The 4 skills in the gtme plugin for Claude Code, from each plugin/skills/*/SKILL.md. Claude Code fires a skill on its own when a request matches its description, and you can call it by its slash command.
| Command | Skill | Fires when |
|---|---|---|
/gtme:analyze | analyze | Use when someone asks what gtme did, what it cost, what the cache saved, why a record was dropped or not contacted, what is known about a person or company and where each fact came from, who is in a group, or wants a number from past runs. |
/gtme:create-adapter | create-adapter | Use when a pipeline needs a vendor, API, or data source gtme does not ship — "gtme doesn't have X", "add Hunter/Clearbit/our CRM", a custom endpoint — or when the records are not people or companies (posts, jobs, events, repos) and need a new entity type. |
/gtme:create-pipeline | create-pipeline | Use when someone describes an outreach or go-to-market goal in their own words and wants it built with gtme — a list to work, people to find or qualify, notes to write, a campaign or CRM to fill — before any pipeline file exists. |
/gtme:run-pipeline | run-pipeline | Use when a gtme pipeline file or bundle exists and someone wants it run, tested, rehearsed, sent, or "just shipped" — including "run it", "send it", "get the leads into the campaign", "does this work", or a re-run after an edit. |
Install
For agents has the plugin install.
See also
Used in
- For agents: Each plugin skill's trigger, procedure, and the commands it runs