new-gtm-tool
Skill0 starsChanged 3 months agoMITView on GitHub
Create a NEW tool project from this template - makes the repo (GitHub when available, local copy otherwise), then hands off to /kickoff. Use when the user says "new tool", "new project", "spin one up", or invokes /new-gtm-tool. Args - the tool name (kebab-case).
- Reads credentials
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Very specific: line 8
Run this from inside a clone of gtm-groundwork.
- Distinctive: line 13
Name it: If no kebab-case name was passed as args, ask.
- Very specific: line 34
Never copy .env* files into the new project — env is created manually per project, secrets are never committed.
- Distinctive: line 36
Never create the repo public.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
New GTM tool
Run this from inside a clone of gtm-groundwork. It creates a sibling project and starts the standard flow.
Steps
- Name it. If no kebab-case name was passed as args, ask.
- Pick the creation path:
- GitHub available (
gh auth statusshows a logged-in account that can see the template): ask which owner/org the new repo belongs under (personal account vs company org), thengh repo create <owner>/<name> --template walutani1/gtm-groundwork --private --cloneinto a sibling directory of this clone. - No GitHub / no template access (e.g. a work machine): copy THIS
folder to
../<name>, excluding.git,node_modules,.next, and any.env*files. Then in the copy:git init, initial commit. Tell the user a remote can be added later (git remote add origin <company repo url>) once one exists.
- GitHub available (
- Rename identity: in the new repo, update the
namein package.json and the title insrc/app/layout.tsxto the tool's name. - Verify it's healthy:
npm installandnpm run buildmust pass before anything else. - Hand off: switch to the new repo and run
/kickoff(its own copy — the skills travel with it).
Never
- Never copy
.env*files into the new project — env is created manually per project, secrets are never committed. - Never create the repo public.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

