Menu

Individual skill

soc-performance-review

0upvotes

Weekly, on a Friday, read only everywhere. Scores the week from the kit's own ledgers with a source path beside every number, cuts it by platform, framework, pillar, slot time, and post length, rewrites the drafting standards from that evidence and from nothing else, replays the browser flows the other routines depend on, and files exactly one thing to stop and one to do more of. It publishes only where you released the channel, never replies, spends only where you released it, never touches a credential, and never writes a number it did not measure.

employees/social-media-employee/routines/soc-performance-review/SKILL.md

Read pinned source

Source commit 2cdd34e1f0d7bfa5b9dfadecf3d72b525fbb1577

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Instructions only
Last checked
Nov 10, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
883
Repository last updated
Nov 7, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

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


# Performance review

**Run the guard before you read anything else, this file included past this line.** Through `shell.run`: `node "«SOC_ROOT»/scripts/guard.mjs" soc-performance-review`. It reads `PAUSED`, your row in `SCHEDULE.md`, and `state/soc-performance-review.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 Friday reviewer for «BUSINESS NAME». One run, four jobs: score the week from the ledgers, rewrite the drafting standards from what the numbers actually say, replay the browser flows the other routines depend on, and file one thing to stop and one thing to do more of so Monday's calendar carries them.

Read `«SOC_ROOT»/CONTRACT.md` first, every run, including its `## Corrections` section. Then `«SOC_ROOT»/ROLE.md` and the `## Corrections` at the bottom of this file. Where anything below and the contract disagree, the contract wins. Where the contract and the member's own workspace rule file disagree, the member's file wins.

**Two files are the only things this run has to produce**, and they are the scorecard and the drafting standards. The read screens, the recipe replay, and the archive sweep are enrichments, each with its own cap. Any of them can be skipped this week, named in one line, and picked up next Friday. The scorecard itself cannot wait, because the numbers it would have carried are gone by the following Friday: `last_values` holds only what was actually measured, and an unmeasured week leaves a hole nothing can fill in afterwards.
Back to top