agentleFS
matthewdonsemail-labmatthewdonsemail-lab/log/.claude/skills/log-inbox-governor-reset/SKILL.md

log-inbox-governor-reset

Skill63 starsChanged 2 days agoMITView on GitHub

Resetting an account's governor count. A log play (docs/useCases/inbox/governorReset.md): Every platform account's governor counts what it sent today and refuses once the count is spent (\"daily cap reached (500/day)\"). When the owner says to, the count goes back to 0 so the work can carry on, on X, Discord, Slack, Instagram, Reddit, LinkedIn or Facebook alike. The reset is checked and kept in log.db, so it is never a hand edit nobody can see (rule 168).

The file

Files
SKILL.md

Resetting an account's governor count

This is the log play inbox/governorReset. Before anything else, call the log MCP tool getGuide({ useCase: "inbox/governorReset" }): it returns this page and makes it the session's play, so every log tool's answer says which step you are on and a send with no play loaded is refused (rules 157, 158). Then follow the steps in order.

Draft every message from that person's own thread and matt's real replies (voice with no text, search), never from memory, and never send two that read alike (sameAsSent).

Every platform account's governor counts what it sent today and refuses once the count is spent ("daily cap reached (500/day)"). When the owner says to, the count goes back to 0 so the work can carry on, on X, Discord, Slack, Instagram, Reddit, LinkedIn or Facebook alike. The reset is checked and kept in log.db, so it is never a hand edit nobody can see (rule 168).

How the owner asks for it: "reset the governor on X back to 0", "confirm it's in the db", "reset X to 0", "reset the limit back to 0 from 500", "reset the platforms count to 0"

Run it from a fresh context

Say: "go on docs/useCases/inbox/governorReset.md for <platform> <account or all>". The agent reads this page and runs the steps.

The steps

#StepToolDone when
1Read the countsgovernorShow { platform }each account's requests, writes, this hour and any cooldown
2Reset the accounts the owner named, back to 0governorReset { platform, account, by: "<owner>", reason: "<what the owner said>" }each account reads 0 and names its log.db ledger row
3Confirm it is in the dbgovernorShow { platform }each account shows 0 requests and its last reset as a ledger row
4Tell the owner the count before and after, and carry on with what was blockedthe reply to the ownerthe owner knows each account is back to 0

account: "all" resets every account on that platform. A cooldown after a block is kept: a blocked account resumes only when the owner says so (rule 94), and the platform's own answer still decides (rule 73).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.