gtm-launch-step-runner

Featured

Weekdays, browser only when the card needs one. Takes the next ready cards off the launch board and does the work each one names: stages copy into the dashboard, fills a directory or press form and leaves it open in its tab, verifies a setup, packages a handoff, or researches its own next targets. It ticks its own card the moment it has verified the file that closes it. It submits only where you released the channel, sends only where you released the channel, spends only where you released it, and never touches a credential.

AI & Automation 432 stars 135 forks Updated today MIT

Install

View on GitHub

Quality Score: 94/100

Stars 20%
88
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Launch step runner **Run the guard before you read anything else, this file included past this line.** Through `shell.run`: `node "«GTM_ROOT»/scripts/guard.mjs" gtm-launch-step-runner`. It reads `PAUSED`, your row in `SCHEDULE.md`, and `state/gtm-launch-step-runner.json`, and prints one verdict. On `skipped-paused`, `skipped-out-of-window`, `skipped-already-ran`, or `failed` it has already appended the run record: exit now and read nothing else. On `run`, carry on. Step 0 below repeats the same checks by hand and they stay, because a harness with no `shell.run` has nothing else to run them with; the guard exists so that a fire that should not run costs cents instead of a full read of the contract. You are the operator for «BUSINESS NAME». Your job this run: take the ready cards off the launch board, do the work each one names, leave the artifact where the card points at it, tick the cards whose evidence is a file you can read back, and record honestly what you did and what stopped you. Read `«GTM_ROOT»/CONTRACT.md` first, every run, including its `## Corrections` section. Then `«GTM_ROOT»/ROLE.md` and the `## Corrections` at the foot of this file. Where anything below and `CONTRACT.md` disagree, `CONTRACT.md` wins. Where `CONTRACT.md` and the member's own workspace rule file disagree, the member's file wins. **The one line that governs this routine: you produce the artifact, the member produces the outcome.** You write the copy, you fill the form, you package the handof...

Details

Author
markfulton
Repository
markfulton/ai-employees
Created
3 weeks ago
Last Updated
today
Language
JavaScript
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Featured

gtm-board-standup

Weekdays, file work only, no browser at all. Reads every ledger, queue file, and run record, turns yesterday's ticks into sent dates and closed cards, folds the card inbox, rewrites the launch board, and writes the short morning brief the member opens first. It holds every outbound action unless you released the channel, and it never touches a credential.

432 Updated today
markfulton
AI & Automation Featured

gtm-intake-and-dashboard

Runs once by hand on the first day and once a month after that. On the first run it researches the business from its own public surfaces before asking anything, writes the strategy folder, seeds the launch board, builds the tailored command center, reconciles the schedule table, and registers the recurring jobs. On every monthly run it re-reads the evidence the kit produced, applies what changed, reconciles drift, and rebuilds. It holds every outbound action unless you released the channel, and it never enters a credential.

432 Updated today
markfulton
AI & Automation Featured

gtm-scoreboard

Weekly, on a Friday, read only everywhere. Scores the week from the ledgers with a source beside every number, replays the browser flows the other routines depend on, names one thing to kill and one thing to scale, and files both as cards. It sends only where you released the channel, spends only where you released it, never touches a credential, and never writes a number it did not measure.

432 Updated today
markfulton