eliasstravik/gtm-skills/gtm-workflow

GTM Workflow

Trigger

Apply this skill when a request concerns a saved workflow: creating, changing, running, scheduling, deploying, upgrading, inspecting, opening its UI, grouping, or deleting one, or its table, runs, diagram, or group.

When creating or changing a workflow, check recipes (e.g. network enrichment) for one that matches the request and follow it; this skill still owns the lifecycle. Ordinary runs of an unchanged workflow need no recipe.

Show the intent menu only when the user's entire request is /gtm-workflow or /gtm-workflows, with no action or other words. Ask Choose a workflow action. with three choices: Open GTM Workflows, Create a workflow, Manage a workflow, and wait. Manage asks which workflow and action: change, run/test, schedule/deploy, group, upgrade/repair, or delete. Bare entry performs no creation, execution or deployment.

Open GTM Workflows is already an explicit Open request. Resolve the verified viewer URL and return it immediately using entry links; do not show the intent menu or ask the user to choose Open again. Loading this skill does not turn an explicit request into a bare invocation. Other explicit actions also go directly to their procedure. If Open finds no workspace, explain workspace setup; if the workspace has no workflows, show its empty list.

Scope

This skill owns <workspace>/workflows/, a Vercel Workflow runtime on Nitro copied from the template's templates/ on first use: workflow files, db/tables/, migrations, vercel.json, .env, the local database, runs, diagram pages, and the deployed copy. Runs execute locally against this workspace's own Postgres in data/pg by default; they target the deployed copy when the user asks or the host states there are no local runs, and hosted results are read through the deployed copy's query route. Keys live in workflows/.env.local locally and in the project's Production variables when deployed, both edited through the viewer's Keys page (Connections tab); for setup, key discovery and key changes, read Keys. The remaining workspace files outside workflows/ belong to the other gtm skills.

The workflow template is not shipped inside this skill. node scripts/template.mjs (from this skill's folder) fetches it once for this skill's release, from the gtm-skills repository at tag v<metadata.version> (never a branch; git first, so the github.localhost proxy on exe.dev VMs applies, then the release tarball), caches it under ~/.cache/gtm-skills/, and prints JSON whose templates is the runtime folder copied to workflows/ and whose root holds the workspace root files. Setup, Doctor and upgrade-package.mjs call it themselves; wherever this skill or its references say templates/ or root/, they mean those two folders. When it fails (exit 1, template_fetch_failed), report the reason; nothing else in the workspace changes.

Inputs

The request; the workspace found by the contract; the ICPs and personas the workflow reads by slug; references/local.md for commands, keys, and verified facts; references/deploy.md for hosting.

Roles

The user's request authorizes routine code changes and real runs within the configured row and cost caps. State the estimate and proceed; confirmation is reserved for destructive actions under the shared interaction rules. The workflow project goes live through shared setup --deploy (deploy.md), run directly or as the last step of optional gtm-agent setup; the user chooses the AI backend once per workspace in .env; the agent writes, runs, and reports. Deploy is the push.

Procedure

When persisting enriched people or companies, follow shared profiles for storage, identity, freshness, paid attempts and scoped Data views. Its two phase workers and common budget replace the generic self-fan-out pattern below for multi-phase enrichment. The profile tables are runtime tables in schema gtm; scripts/migrate.mjs migrates them with everything else, and upgrades preserve them.

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. Workflow slugs follow the contract's slug rule; the display name is the doc comment's first line.