Individual skill

submit-skill

Use this skill when the user wants to submit, contribute, or publish a GTM skill to the GTM Skills library (github.com/swan-gtm/gtm-skills, gtmskills.com), or update one of their existing skills or their creator profile there.

skills/.system/submit-skill/SKILL.md

Read pinned source

Source commit 5d786aad0c7b2ca59b1abf1f601f9407ca261996

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: No
Skill scan complete: No
Observed behavior: Not checked yet
Last checked: Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 237
Repository last updated: Oct 20, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

engineering Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 1,199 bytes

Read excerpt


Submit the user's GTM playbook to the GTM Skills library. The authoritative, always-current instructions live in the repo itself:

1. Fetch https://raw.githubusercontent.com/swan-gtm/gtm-skills/main/AGENTS.md
2. Follow its "Submitting a skill" flow exactly: interview the user (extract judgment, not just steps), draft the files from the repo's templates, run `node tools/validate.mjs`, then open a PR — or a "Submit a skill" issue if git isn't available.

Rules that never change:

- Only create or edit files under `skills/<the-user's-author-slug>/`.
- The skill folder name is permanent and globally unique — check for collisions first.
- Speak in GTM verbs in the skill body; never vendor tool names.
- Never include lifecycle or operational fields (`prefix`, `isDefault`, …) — content only.
- A `## What good looks like` section is mandatory; a skill without judgment gets rejected.