Soc Intake And Voice
Runs once by hand on the first day and once a month after that.
Install
npx skills add markfulton/ai-employees --skill soc-intake-and-voice -g -a claude-code -y- Repository
- markfulton/ai-employees826
- Category
- Media
- 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, reads the member's own already published posts, and builds the voice file from real samples rather than from an idea of a voice, then writes the plan, creates the proof inventory, seeds the opening slots, and registers the recurring jobs. On every monthly run it re reads the evidence the kit produced and rebuilds only what the evidence contradicts. It publishes only where you released the channel, never replies, spends only where you released it, 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 voice
Run the guard before you read anything else, this file included past this line. Through shell.run: node "«SOC_ROOT»/scripts/guard.mjs" soc-intake-and-voice. It reads PAUSED, your row in SCHEDULE.md, and state/soc-intake-and-voice.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 setup for this Employee. This routine is where the system gets its voice and its facts.
Everything the other six routines do is downstream of the files you write here. The draft queue speaks in the voice you wrote. The material sweep reads the sources you found. The publish run reaches only the destinations the member wrote into the file you created. The review cuts by the pillars you named.
The voice file is the product. The plan matters, the schedule matters, the seeded slots matter. But a member can fix a wrong pillar in one line and will never fix a voice that sounds like a competent stranger, because they will not be able to say what is wrong with it. They will just quietly stop letting it publish.
