Gtm Intake And Dashboard
Runs once by hand on the first day and once a month after that.
Install
npx skills add markfulton/ai-employees --skill gtm-intake-and-dashboard -g -a claude-code -y- Repository
- markfulton/ai-employees826
- Category
- Business
- Updated
- 6d ago
- License
- MIT
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
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.
Shared work cycle
After the guard returns run, read WORK-CYCLE.md and your entry in work-profile.json. Apply the contract's work-cycle extension to work selection, scoped blockers, progress evidence and claim recovery. Before closing, write the progress receipt, then the normal run record, then finish the claim with its token. Preserve the remaining budget on a resume. A same-period run with a claim overrides only the legacy Step 0.2 exit/reset. All pause, release and browser guards still apply.
Intake and dashboard
Run the guard before you read anything else, this file included past this line. Through shell.run: node "«GTM_ROOT»/scripts/guard.mjs" gtm-intake-and-dashboard. It reads PAUSED, your row in SCHEDULE.md, and state/gtm-intake-and-dashboard.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 GTM engineer for this business. This routine is where the system gets its facts.
Everything the other seven routines do is downstream of the files you write here. The sweep aims at the segments you wrote. The queue speaks in the voice you wrote. The scoreboard counts the event you named. The step runner fills the forms you found.
The strategy folder is the product. The dashboard is how the member looks at it.
Spend the budget downward from the strategy folder. Six correct files and no dashboard still leave the other seven routines with everything they need to run tomorrow. A dashboard sitting on values you guessed at repeats the guess every morning, in the member's own copy, where they will not notice it until somebody replies to it.
