head-of-pmo SKILL.md skillA
head-of-pmo from cbrock84/headcount is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add cbrock84/headcount/head-of-pmo@git:20260916.e72e404Pins git:20260916.e72e404 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- cbrock84/headcount
- Path
plugins/pmo/skills/head-of-pmo/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260916.e72e404, committed Sep 16, 2026
- First version recorded
- Aug 29, 2026
- Size
- 5,379 bytes
- Repository stars
- 2,543
- License
- MIT
The EPMO lead's remit — what the PMO governs, what it must never become, and how it earns standing rather than compliance. Use this to stand up or reform a PMO, decide what it should and should not control, judge whether it is adding value or overhead, or work out why teams route around it.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Head of the PMO An enterprise PMO exists to make the organization's delivery capacity visible and to force the choices that capacity implies. It does not exist to collect status. ## The two failure modes Every PMO fails in one of two directions, and the remedy for each makes the other worse: - **The reporting PMO.** It aggregates status nobody acts on, and teams learn to write updates that survive review rather than updates that are true. Its meetings are attended and its findings ignored. This is the common one. - **The controlling PMO.** It owns delivery decisions that belong to the teams, becomes a queue everything waits in, and is routed around by anyone with the standing to do so. The line that holds: the PMO owns **which** work proceeds and **whether the organization can absorb it**. Teams own **how** the work gets done. ## What it governs - `pmo:portfolio-governance` — intake, prioritization against real capacity, stage gates that can stop things, and resource contention across projects - `pmo:program-management` and `pmo:project-delivery` — the delivery disciplines themselves …
Read the whole file at its exact version.
How to install
mdr add cbrock84/headcount/head-of-pmo@sha256:e913699eb1ff975bThe line at the top of this page pins the label git:20260916.e72e404, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_s7sqikks6gjd74gu)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Aug 29, 2026 and Sep 16, 2026, about one every 5 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260916.e72e404 latest | 2026-09-16 | e72e404 | 5,379 B | A | view · diff |
| git:20260903.cc4a2cd | 2026-09-03 | cc4a2cd | 5,040 B | A | view · diff |
| git:20260901.5eb7d2b | 2026-09-01 | 5eb7d2b | 5,052 B | A | view · diff |
| git:20260831.eaba5fa | 2026-08-31 | eaba5fa | 4,790 B | A | view · diff |
| git:20260829.4a2c133 | 2026-08-29 | 4a2c133 | 3,271 B | A | view |
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 (5379 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 · 2,543 stars · license MIT · pushed 2026-10-18 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_s7sqikks6gjd74gu GET https://markdownregistry.com/api/v1/resolve?ref=cbrock84/headcount/head-of-pmo GET https://markdownregistry.com/api/v1/blob/e913699eb1ff975bac2c33e4a9725abd99e99a38c32a7f31e53754c443b83372
Your AI assistant 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.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.