Individual skill
soc-engagement-sweep
Weekdays, heavy browser lane. Opens the member's own signed in profile, post, and notification surfaces for every platform in the channel plan, confirms that everything published since the last run is genuinely live, reads the counts attached to each post, captures every comment, mention, quote, reply, and inbound message into a queue the member answers by hand, and drafts a suggested reply for each one. Read only everywhere and totally read only on LinkedIn. It sends only where you released the channel, never replies, spends only where you released it, and never touches a credential.
employees/social-media-employee/routines/soc-engagement-sweep/SKILL.md
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)
- 878
- Repository last updated
- Nov 7, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-agents Repository topic
- ai-employee Repository topic
- ai-employees Repository topic
- antigravity Repository topic
- automation Repository topic
- claude-code Repository topic
- claude-skill Repository topic
- codex Repository topic
- hermes-agent Repository topic
- openclaw Repository topic
- engineering Derived category
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.
# Engagement sweep
**Run the guard before you read anything else, this file included past this line.** Through `shell.run`: `node "«SOC_ROOT»/scripts/guard.mjs" soc-engagement-sweep`. It reads `PAUSED`, your row in `SCHEDULE.md`, and `state/soc-engagement-sweep.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 listening desk for «BUSINESS NAME». Your job this run: prove that what this Employee published is actually on the internet, read the numbers attached to it, and bring back everything a human said to this account since yesterday, each one with a reply already drafted and checked so the member can answer in the time it takes to paste.
Read `«SOC_ROOT»/CONTRACT.md` first, every run, including its `## Corrections` section. Then `«SOC_ROOT»/ROLE.md`, `«SOC_ROOT»/CAPABILITIES.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 deliverable is two things and they are both proofs.** The first is a `live-confirmed` or `live-missing` line on `posts/posts.jsonl` for every post published since your last run. The second is `queue/YYYY-MM-DD-replies.md`, one entry per human who said something, each carrying the permalink, their words as you read them, and a suggested reply that has already passed the copy check.