eliasstravik/gtm-skills/gtm-workspace

GTM Workspace

Trigger

Apply this skill when a request concerns a GTM workspace as a whole, its organization facts, or its members.

Scope

One workspace holds one organization's GTM context as Markdown under ~/.gtm/<org-slug>/, with git as its memory. This skill owns the workspace root, ORG.md, members/, and workspace health, and hosts the shared standards in references/. ICPs, personas, fit checks, and workflows/ belong to the other gtm skills; Doctor never inspects the internals of workflows/.

Workflow hosting and provider connections belong to gtm-workflow. Route standalone Local or Vercel setup to its shared scripts/setup.mjs; do not require GTM Agent or Slack. Workspace Doctor delegates connection health to that skill's Doctor.

Inputs

The request; the workspace found by the discovery order in the contract; facts from the user, the company's own public site, and other safe public sources, never invented; a member's email from the user or a source, never inferred.

Roles

The user approves every change through the host's write permission; the agent proposes, edits, commits, and reports.

Procedure

The first gtm skill used in a conversation checks once for a newer release, as updates says. Talk by the six rules in interaction; reproduce the dialogues.

Every save: one sentence on what will change, pull first when origin/main exists, edit through the host's write path, commit on main with a plain-language message, push when a remote exists, verify the commit (and that it reached origin/main when a remote exists), close with what was created, changed, or deleted.

Outputs

A workspace with the root shape in the contract, every change a commit on main, and, when shared, a private GitHub repository gtm-<slug>.

Exceptions

Several workspaces match and none is named: ask, never save a preference. A fact cannot be confirmed: write Unknown. A member without an email is not created. Asked to delete a whole workspace: the agent never does; say so, and that the user removes the folder, or the GitHub repository when shared. Legacy suborgs/ units become prose under ## Notes in ORG.md, or their own workspace when the user wants separate GTM context.

QC

• ORG.md has the 13 fields of company data in order, one line each; nested bullets only under Location, Products and services, and Tech stack.
• The root carries only what the contract lists; the pointer files and .gitignore match their templates byte for byte.
• Every slug follows the contract's rule; every member has an email.
• The closing statement of what changed follows a verified commit.

References

interaction rules; interactions dialogues; contract for slugs, discovery, root shape, sourcing, and sharing; company data and person data vocabularies; templates/ for AGENTS.md, CLAUDE.md, ORG.md, gitignore, and MEMBER.md.