Gtm Operating Cadence
github/awesome-copilot
Design meeting rhythms, metric reporting, quarterly planning, and decision-making velocity for scaling companies.
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…
MITAuto-check passed
Install Operating Cadence
$ npx skills add cbrock84/headcount --skill operating-cadence -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install cbrock84/headcount operating-cadence --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/operations/skills/operating-cadence .claude/skills/operating-cadence && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "operating-cadence" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/operations/skills/operating-cadence into .claude/skills/operating-cadence/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "operating-cadence", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/cbrock84/headcount/tree/main/plugins/operations/skills/operating-cadenceType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add cbrock84/headcount --skill operating-cadence -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install cbrock84/headcount operating-cadence --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/operations/skills/operating-cadence .agents/skills/operating-cadence && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "operating-cadence" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/operations/skills/operating-cadence into .agents/skills/operating-cadence/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "operating-cadence", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add cbrock84/headcount --skill operating-cadence -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install cbrock84/headcount operating-cadence --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/operations/skills/operating-cadence .cursor/skills/operating-cadence && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "operating-cadence" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/operations/skills/operating-cadence into .cursor/skills/operating-cadence/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "operating-cadence", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/cbrock84/headcount.git --path plugins/operations/skills/operating-cadence--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add cbrock84/headcount --skill operating-cadence -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install cbrock84/headcount operating-cadence --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/operations/skills/operating-cadence .gemini/skills/operating-cadence && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "operating-cadence" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/operations/skills/operating-cadence into .gemini/skills/operating-cadence/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "operating-cadence", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install cbrock84/headcount operating-cadenceInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add cbrock84/headcount --skill operating-cadence -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/operations/skills/operating-cadence .github/skills/operating-cadence && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "operating-cadence" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/operations/skills/operating-cadence into .github/skills/operating-cadence/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "operating-cadence", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add cbrock84/headcount --skill operating-cadence -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install cbrock84/headcount operating-cadence --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/operations/skills/operating-cadence .opencode/skills/operating-cadence && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "operating-cadence" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/operations/skills/operating-cadence into .opencode/skills/operating-cadence/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "operating-cadence", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
operating-cadence- GitHub stars
- 2k
- Token cost
- ~939 tokens
- SKILL.md length
- 543 words
- Files
- 1
- Skills in repo
- 178
- Repo updated
- First seen
- Licence
- MIT
At a glance
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…
- SKILL.md covers Give every recurring meeting a…, Separate the three time…, One set of numbers, owned by… and Design the escalation path…, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Operating Cadence is an agent 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.
Its SKILL.md is about 940 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: An agent organization structured as a company — 15+ departments, 125+ skills, each independently installable, citing the standards and regulators that settle the question. Runs… The licence is MIT.
Example prompts
- “Use the operating-cadence skill to design the rhythm an organization runs on — which reviews happen weekly, monthly and quarterly, what each one…”
- “/operating-cadence”
What it can do on your machine
Read from SKILL.md and the folder at commit 98d1c17. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Operating Cadence loads about 939 tokens when it runs. Until then it costs about 117 tokens; SKILL.md has 543 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from cbrock84/headcount at commit 98d1c17, republished under its MIT licence (© cbrock84). 543 words, ~939 tokens.
Download SKILL.mdSave it as
.claude/skills/operating-cadence/SKILL.md (or your agent's skills folder).- name
- operating-cadence
- description
- 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.
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.
- Quarterly — direction. Whether the plan is still the right plan, resource reallocation, and the deliberate stopping of things.
The common failure is a monthly review that fills with weekly firefighting, so nobody ever looks up. The fix is not discipline in the room; it is a functioning weekly meeting that leaves nothing urgent for the monthly one to absorb.
One set of numbers, owned by name
The same metric presented two ways in two forums will be argued about in both. Each metric needs a single definition, a single source, and one named owner who is accountable for the number rather than for the outcome it measures — those are different people surprisingly often, and the distinction stops reporting from becoming advocacy.
Publish the pack before the meeting and expect it read. A review that spends its first half being presented to has cut its own decision time in half.
Show full SKILL.md (200 more words)Show less
Design the escalation path deliberately
Most organizations can describe how information flows up. Far fewer can describe how long it takes, and the duration is the part that matters. A problem visible on Monday at the front line that reaches a decision-maker at the monthly review has lost three weeks to structure.
Define what jumps the cadence: thresholds that trigger immediate escalation regardless of the calendar, and who can pull that lever without asking permission. Then check that it has been used. An escalation path nobody has ever invoked is either a very healthy operation or a dead letter, and the second is more common.
Prune on a schedule
Add a review and it lives forever; the calendar only grows. Review the cadence itself once a year: what each forum decides, whether it still decides it, and what could be merged or ended. Expect to remove something every time.
Never
- Let a meeting recur without naming the decision it makes.
- Present a number whose definition differs from the one used in another forum.
- Escalate through the calendar when the problem is moving faster than the calendar.
- Add a review to fix a problem that a clear owner would have fixed.
© cbrock84, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in plugins/operations/skills/operating-cadence of cbrock84/headcount.
Open the folder on GitHubat commit 98d1c17
Compare with similar skills
Operating Cadence next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Operating Cadence this skillcbrock84/headcount | 2k | — | ~939 | Automated safety check: Pass | MIT | |
| Gtm Operating Cadencegithub/awesome-copilot | 40k | 1 repos | ~4k | Automated safety check: Pass | MIT | |
| Design Systemaffaan-m/ECC | 276k | — | ~698 | Automated safety check: Pass | MIT | |
| Design Guidepaperclipai/paperclip | 99k | 1 repos | ~3.1k | Automated safety check: Pass | MIT | |
| Design Audit Against Rams' Principlesthedotmack/claude-mem | 99k | — | ~4.6k | Automated safety check: Pass | Apache-2.0 | |
| Figma Design to Codewarpdotdev/warp | 65k | 4 repos | ~2.9k | Automated safety check: Pass | AGPL-3.0 |
Similar skills
- Official
Design System
affaan-m/ECC
Generate a design system from an existing codebase or audit one for visual consistency: extract tokens (colors, typography, spacing, shadows) into design-tokens.json and CSS custom properties with…
Design Guide
paperclipai/paperclip
Paperclip UI design system guide for building consistent, reusable frontend components.
Design Audit Against Rams' Principles
thedotmack/claude-mem
Audits a design against Dieter Rams' ten principles of good design, scores each with evidence, and hands off a make-plan prompt for a new, refined or redesigned outcome.
Figma Design to Code
warpdotdev/warp
Turns a Figma frame or component into production code that matches the design, using the Figma MCP server and the project's own design system.
Design Consultation
garrytan/gstack
Learns about your product, studies the landscape and writes a DESIGN.md with a full design system covering type, color, layout, spacing and motion.
More from cbrock84/headcount
All 178 skills in this repoAgent Hierarchy
cbrock84/headcount
Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a…
Access And Identity
cbrock84/headcount
Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process.
Account Based Marketing
cbrock84/headcount
Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group…
Activation
cbrock84/headcount
Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone becomes a user or a lapsed account.
AI ML Governance
cbrock84/headcount
Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire.
AI Research Analyst
cbrock84/headcount
Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit.
Questions about Operating Cadence
What does Operating Cadence do?
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…. Operating Cadence is an agent 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.
How do I install Operating Cadence in Claude Code?
Run `npx skills add cbrock84/headcount --skill operating-cadence -a claude-code`. Or copy the skill folder (plugins/operations/skills/operating-cadence in cbrock84/headcount) into .claude/skills/operating-cadence in your project. Claude Code loads it when a task matches its description.
How do I install Operating Cadence in Codex?
Run `npx skills add cbrock84/headcount --skill operating-cadence -a codex`. Or copy the skill folder (plugins/operations/skills/operating-cadence in cbrock84/headcount) into .agents/skills/operating-cadence in your project. Codex loads it when a task matches its description.
Can I use Operating Cadence in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add cbrock84/headcount --skill operating-cadence -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/operating-cadence, .gemini/skills/operating-cadence, .github/skills/operating-cadence and .opencode/skills/operating-cadence in your project.
What does Operating Cadence need to run?
SKILL.md names no scripts, command-line tools or credentials: Operating Cadence is instructions for the agent only.
Does Operating Cadence access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Operating Cadence safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Operating Cadence use?
Operating Cadence is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Operating Cadence use?
About 939 tokens (SKILL.md is roughly 3.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Operating Cadence?
Skills that share tags, products or a category with Operating Cadence: Gtm Operating Cadence (github/awesome-copilot, 40k stars), Design System (affaan-m/ECC, 276k stars), Design Guide (paperclipai/paperclip, 99k stars) and Design Audit Against Rams' Principles (thedotmack/claude-mem, 99k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Operating Cadence?
cbrock84 (a GitHub user) maintains it in cbrock84/headcount, which has 2,016 GitHub stars. The repository holds 178 skills in this directory. The repository was last updated on September 17, 2026.
Source: cbrock84/headcount on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.