operating-cadence skillA
operating-cadence is agent-read markdown (skill) from cbrock84/headcount: Designs the rhythm an organization runs on — which reviews happen weekly, monthly and quarterly, what each one decides, who owns the numbers presented, and how a signal at the front line reaches the people who can act on it. Use this to set up a management operating system, fix a meeting calendar that produces no decisions, work out where a recurring problem keeps failing to surface, or cut a review structure that has grown past what it informs..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Operating cadence Every organization has a cadence. Most have one that accumulated — a meeting added after each incident, none ever removed — rather than one that was designed. The symptom is familiar: full calendars, thorough reporting, and decisions that still take six weeks. ## Give every recurring meeting a decision it exists to make A review that only shares information is a document pretending to be a meeting. Before a meeting recurs, answer three questions: what decision does this forum make, who in the room can make it, and what would have to be true for the answer to be no. If a forum has made no decision in a quarter, either it is the wrong forum or the decision is being made elsewhere. Both are worth knowing. ## Separate the three time horizons, and do not let them merge - **Weekly — execution.** What is off track, what is blocking it, who is unblocking it by when. Short, operational, no strategy. Fifteen items at five minutes each, not five at fifteen. - **Monthly — performance.** Results against plan, with the variance explained by a driver rather than restated. This is where a trend gets caught while it is still cheap. …
Read the whole file at its exact version.
How to install
mdr add cbrock84/headcount/operating-cadence@git:20260901.0f7b645mdr add cbrock84/headcount/operating-cadence@sha256:802e2b7b940737d7Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_uhsc2ufuuxjx33qo)
1 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (3769 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
cbrock84/headcount · 1,664 stars · license MIT · pushed 2026-09-17 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_uhsc2ufuuxjx33qo GET https://markdownregistry.com/api/v1/resolve?ref=cbrock84/headcount/operating-cadence GET https://markdownregistry.com/api/v1/blob/802e2b7b940737d74ce5bf48cc552a34b81aab4f9b5182c19b518e940fec181c
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.