eliasstravik/gtm-skills · Archived
Triggers when a user asks to create, define, refine, update, delete, or doctor an ideal customer profile file in a connected GTM workspace, including choosing which organization owns it.
npx skills add eliasstravik/gtm-skills --skill gtm-icp
This repository is archived — consider an actively maintained alternative.
Triggers when a user asks to create, define, refine, update, delete, or doctor a buyer or stake…
14 installsTriggers when the user invokes `/gtm-workspace` or asks to create, import, update, delete, vali…
9 installsTriggers when a user wants to create, update, inspect, delete, run, approve, query, schedule, t…
9 installsTriggers when a user asks to classify, segment, route, or bucket companies against ICPs in a co…
7 installsOther skills from eliasstravik/gtm-skills · top by installs.
npx skills add eliasstravik/gtm-skills
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
main
Files included with this skill beyond the listing page.
SKILL.md
5,340 B
SUMMARY.md
376 B
Apply this Lifecycle SOP when the requested outcome creates, updates, repairs, or retires an ideal customer profile owned by an organization node in an existing GTM workspace.
Own node-local, freeform Markdown ICPs at icps/<icp-slug>/ICP.md across creation, refinement, deletion, and repo-wide ICP integrity repair. Create and fully research ICPs with the shared company-data contract, interpreted as desired or accepted account criteria. Read legacy icps/<icp-slug>.md artifacts without requiring migration. Do not author persona or member files, manage the workspace lifecycle, or classify/research accounts against saved ICPs.
Contract
| Field | Public contract |
|---|---|
| Reads | Accepted ICP facts and uncertainty, the root-to-owner ORG.md chain, owner-local ICPs, and safe supplied sources |
| Writes | Only the selected owner's canonical ICP path, or scoped ICP repairs during doctor |
| Outputs | An accepted node-owned ICP and qualified label, a complete health report, or a scoped handoff |
| Approval | The user accepts the complete bytes and exact path operation before any durable write or deletion |
| Persists | Accepted ICP files in main Git history; no hidden coordination state |
| Handoff | gtm-workspace for repository structure or connections, gtm-persona for buyers, and gtm-workflow for saved operational work |
Use the user's accepted ICP facts and uncertainty, the hosting environment's connected-repo and durable-write declarations, the root-to-owner ORG.md chain, owner-local ICPs, and safe supplied sources.
The agent owns the selected ICP lifecycle flow. The user accepts durable changes. gtm-workspace owns repository structure and connections; the hosting environment declares fixed connections and any replacement persistence mechanism.
| Condition | Owned flow |
|---|---|
| The requested outcome belongs to a sibling workflow | Hand off before workspace resolution or artifact reads; mutate nothing |
| No lifecycle verb is clear | Guide the ICP lifecycle menu and retain ownership of the selected flow |
| Create or define is requested | Resolve the workspace and owner node, ground a factual draft, check owner-local overlap, preview it, and save the accepted ICP |
| Update or refine is requested | Resolve one visible ICP, preserve unrelated facts, preview complete before/after bytes, and save the accepted revision |
| Delete is requested | Resolve one visible ICP, preview ownership and consequences, remove only the accepted target, and explain history recovery |
| Doctor is requested or ICP artifacts seem malformed | Inspect ICP placement and content repo-wide, preview one scoped repair set, save it once, and report resulting health |
Produce the accepted node-owned ICP state and its qualified label, or a complete ICP health report. A request owned by a sibling workflow produces only a scoped handoff and no artifact mutation.
If no valid workspace is connected or discoverable, stop without writing and direct workspace creation or connection to gtm-workspace. If a required reference is unavailable or the environment cannot durably save the accepted operation, keep the repo unchanged and use the prescribed recovery.
AskUserQuestion; put context and numbered choices below it, mark at most option 1 (Recommended), and end choices exactly Reply with a number, or type your answer.ICP.md; write Unknown instead of inventing or dropping unresolved criteria.main, stage only accepted ICP paths, inspect the staged diff, and describe a verified durable result as “saved to history.”