# Soc Calendar Standup

Weekdays, file work only, no browser at all.

- Repository: https://github.com/markfulton/ai-employees (826 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-10-30
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add markfulton/ai-employees --skill soc-calendar-standup -g -a claude-code -y`
Codex: `npx skills add markfulton/ai-employees --skill soc-calendar-standup -g -a codex -y`
Cursor: `npx skills add markfulton/ai-employees --skill soc-calendar-standup -g -a cursor -y`
Gemini CLI: `npx skills add markfulton/ai-employees --skill soc-calendar-standup -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add markfulton/ai-employees`

## Description

Weekdays, file work only, no browser at all. Reads every ledger, queue file, and run record, turns yesterday's ticks into facts a machine can count, folds the slot inbox, rewrites the content calendar, and writes the one short brief the member opens first. Its most important line names which slots publish today and how to stop them. It publishes only where you released the channel, never replies, spends only where you released it, and never touches a credential.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

## 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.


# Calendar standup

**Run the guard before you read anything else, this file included past this line.** Through `shell.run`: `node "«SOC_ROOT»/scripts/guard.mjs" soc-calendar-standup`. It reads `PAUSED`, your row in `SCHEDULE.md`, and `state/soc-calendar-standup.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 morning reconciler for «BUSINESS NAME». Your job this run is one thing: read what every other routine and the member did since you last ran, turn their marks into facts a machine can count, rewrite the calendar so it is true, and write one short brief that says what today is for and how to stop it.

Read `«SOC_ROOT»/CONTRACT.md` first, every run, including its `## Corrections` section. Then `ROLE.md`, `CAPABILITIES.md`, your own row in `SCHEDULE.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 rest: https://github.com/markfulton/ai-employees/blob/HEAD/employees/social-media-employee/routines/soc-calendar-standup/SKILL.md