eliasstravik/gtm-skills · Archived
Triggers when a user asks to create, define, refine, update, delete, or doctor a buyer or stakeholder persona file in a connected GTM workspace, including choosing which organization owns it.
npx skills add eliasstravik/gtm-skills --skill gtm-persona
This repository is archived — consider an actively maintained alternative.
Triggers when a user asks to create, define, refine, update, delete, or doctor an ideal custome…
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 installsRelated neighbors and high-traction skills in the same topics — useful to compare before installing.
Coordinate projects — track tasks, schedule meetings, and share docs.
28.5K installsOrganize research — manage references, notes, and collaboration.
28.1K installsManage an executive's schedule, inbox, and communications.
27.9K installsCreate, organize, and distribute content across Workspace.
27.6K installsLead a team — run standups, coordinate tasks, and communicate.
27.4K installsAdminister IT — monitor security and configure Workspace.
27.1K 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,589 B
SUMMARY.md
420 B
Apply this Lifecycle SOP when the requested outcome creates, updates, repairs, or retires a buyer or stakeholder persona owned by an organization node in an existing GTM workspace.
Own node-local, freeform Markdown personas at personas/<persona-slug>/PERSONA.md across creation, refinement, deletion, and repo-wide persona integrity repair. Create and fully research personas with the shared person-data contract, interpreted as desired or accepted person criteria. Read legacy personas/<persona-slug>.md artifacts without requiring migration. Do not author ICP or member files, manage the workspace lifecycle, or classify/research leads against saved personas.
Contract
| Field | Public contract |
|---|---|
| Reads | Accepted persona facts and uncertainty, the root-to-owner ORG.md chain, owner-local personas, and safe supplied sources |
| Writes | Only the selected owner's canonical persona path, or scoped persona repairs during doctor |
| Outputs | An accepted node-owned persona 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 persona files in main Git history; no hidden coordination state |
| Handoff | gtm-workspace for repository structure or connections, gtm-icp for markets, and gtm-workflow for saved operational work |
Use the user's accepted persona facts and uncertainty, the hosting environment's connected-repo and durable-write declarations, the root-to-owner ORG.md chain, owner-local personas, and safe supplied sources.
The agent owns the selected persona 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 persona 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 persona |
| Update or refine is requested | Resolve one visible persona, preserve unrelated facts, preview complete before/after bytes, and save the accepted revision |
| Delete is requested | Resolve one visible persona, preview ownership and consequences, remove only the accepted target, and explain history recovery |
| Doctor is requested or persona artifacts seem malformed | Inspect persona placement and content repo-wide, preview one scoped repair set, save it once, and report resulting health |
Produce the accepted node-owned persona state and its qualified label, or a complete persona 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.PERSONA.md; preserve uncertainty and write Unknown instead of inventing or dropping unresolved criteria.main, stage only accepted persona paths, inspect the staged diff, and describe a verified durable result as “saved to history.”