skills sourced live from GitHub · all skills listed are free · each skill is provided under its author's license.
home / Business & Operations / GTM Operating Cadence Skill by @github
The skill is the skills/gtm-operating-cadence folder inside that repository. Copy it into the folder your agent loads skills from; check your agent's documentation for where that is.
Designs a company's meeting rhythm, metric reporting and quarterly planning so decisions keep up with growth.
Describes a five-level meeting structure, a weekly dashboard meant to surface problems early and a quarterly planning process that guards against drift. Aimed at companies where alignment worsens as headcount rises.
The original SKILL.md is organised into these sections:
Written and maintained by @github. It is published under the MIT license, which allows reuse with attribution. See the author profile. SkillDirectory does not claim authorship: this page adds our own review and links back to the original, and the skill's text belongs to its author.
# Operating Cadence The meeting structure that worked at 30 people collapses at 100. What worked at 100 collapses at 300. The failure mode is always the same: too many people in too many meetings making too few decisions. ## When to Use **Triggers:** - "Our meetings don't produce decisions" - "We're growing but alignment is getting worse" - "How often should we meet?" - "Nobody knows what's happening across functions" - "Decisions take forever" - "Leadership is in meetings all day" **Context:** - Companies scaling from 20 to 300+ people - Post-PMF through growth stage - Distributed / remote teams - Any stage where "we need to talk about this" has become the default --- ## Core Frameworks ### 1. The Five-Level Meeting Architecture **The Pattern:** Different meetings serve different purposes. Conflating them creates either inefficiency (too much time) or confusion (unclear decisions). Separate meetings by function, frequency, and decision authority. …
Excerpt only, quoted from the author's repository. Open the repository for the complete file.