agentleFS
walutani1walutani1/gtm-groundwork/.claude/skills/new-gtm-tool/SKILL.md

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
  1. Very specific:

    Run this from inside a clone of gtm-groundwork.

    line 8
  2. Distinctive:

    Name it: If no kebab-case name was passed as args, ask.

    line 13
  3. Very specific:

    Never copy .env* files into the new project — env is created manually per project, secrets are never committed.

    line 34
  4. Distinctive:

    Never create the repo public.

    line 36

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

New GTM tool

Run this from inside a clone of gtm-groundwork. It creates a sibling project and starts the standard flow.

Steps

  1. Name it. If no kebab-case name was passed as args, ask.
  2. Pick the creation path:
    • GitHub available (gh auth status shows a logged-in account that can see the template): ask which owner/org the new repo belongs under (personal account vs company org), then gh repo create <owner>/<name> --template walutani1/gtm-groundwork --private --clone into 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.
  3. Rename identity: in the new repo, update the name in package.json and the title in src/app/layout.tsx to the tool's name.
  4. Verify it's healthy: npm install and npm run build must pass before anything else.
  5. 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.