New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Head Of Pmo

by cbrock84 in cbrock84/headcount

The EPMO lead's remit — what the PMO governs, what it must never become, and how it earns standing rather than compliance.

MITAuto-check passedProduct & Project Management

Install Head Of Pmo

skills CLI
$ npx skills add cbrock84/headcount --skill head-of-pmo -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install cbrock84/headcount head-of-pmo --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/pmo/skills/head-of-pmo .claude/skills/head-of-pmo && rm -rf skills-src

Use ~/.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/

Facts

Skill name
head-of-pmo
GitHub stars
2k
Token cost
~1.3k tokens
SKILL.md length
782 words
Files
2 (incl. references)
Skills in repo
178
Repo updated
First seen
Licence
MIT

At a glance

The EPMO lead's remit — what the PMO governs, what it must never become, and how it earns standing rather than compliance.

  • Tasks that involve Meeting notes and agendas
  • SKILL.md covers The two failure modes, What it governs, Reporting line, and why it… and Earning standing, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Head Of Pmo is an agent skill from cbrock84/headcount. 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.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/sources.md`).

It sits in Product & Project Management, covering Meeting notes and agendas. 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.

When your agent uses it

  • Tasks that involve Meeting notes and agendas

Example prompts

  • “/head-of-pmo”

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

Head Of Pmo loads about 1.3k tokens when it runs, and up to ~1.6k if it reads all its reference files. Until then it costs about 76 tokens; SKILL.md has 782 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~76
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.6k

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). 782 words, ~1,339 tokens.

Download SKILL.mdSave it as .claude/skills/head-of-pmo/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
head-of-pmo
description
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.

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
  • pmo:estimating-and-contingency — how a defensible number is produced, and how much reserve the portfolio actually needs
  • pmo:schedule-development-and-analysis — building a schedule from logic rather than dates, and interrogating one you inherited
  • pmo:dependency-and-risk-management — the seams between teams, where programs actually fail
  • pmo:benefits-realization — whether the value claimed at approval ever appeared
  • pmo:change-and-adoption — whether anyone uses what was delivered

Benefits and adoption are the two that make a PMO worth funding. A PMO that governs intake but never checks outcomes has only made the front door more expensive.

Reporting line, and why it matters

The EPMO reports to the COO, not into any function whose work it governs. A PMO housed inside the largest delivery organization will, over time, prioritize that organization's work — not through bad faith but through proximity.

It has no write surface over the departments it governs. Its authority is procedural: it runs the gate, it holds the capacity number, and it publishes what was decided.

Earning standing

A PMO is obeyed when it is useful and circumvented when it is ceremony. What makes it useful:

  • Say no visibly, and say why. A gate that has never stopped anything is a gate nobody respects.
  • Hold the capacity number and defend it. The PMO is usually the only function that can see the organization is committed past what it can deliver, and saying so is most of the job.
  • Kill things. Stopping a dead project releases capacity the whole portfolio needs, and organizations are structurally bad at it — see pmo:portfolio-governance.
  • Make reporting cost less than it returns. Every status template is a tax on delivery. Ask for what changes a decision and nothing else.
Show full SKILL.md (342 more words)Show less

Green until it is red

The standard status report fails in a specific way: projects report green until the week they cannot, then go straight to red. Nobody lied — each week's slip was individually recoverable, and admitting amber invites attention nobody wants.

Fix it by asking for facts rather than colors. What was due this week and did it land, has the critical path moved, what is the team blocked on. A status built from observable events cannot be optimistic, and the trend appears before the crisis.

Make amber cheap. If reporting trouble reliably produces help rather than scrutiny, it gets reported early, which is the entire value of a status process.

Estimates and the padding equilibrium

Teams pad when estimates are treated as commitments and used against them; leaders discount because they know it is padded; teams pad more. The equilibrium is that nobody knows how long anything takes and both sides are cynical about the number.

Break it by separating the estimate from the commitment. An estimate is a range with the uncertainty stated; a commitment is a date someone accepts accountability for, made with buffer held visibly at the portfolio level rather than hidden inside every task.

Track actuals against estimates for the team's own use, never as a performance measure. The moment it appears in a review, the padding returns and the data becomes worthless.

Sources

references/sources.md in this skill lists the outside authorities that settle the questions here — what each one is authoritative for, and what you may do with it. Check them before answering on anything they cover, and cite what you used. Most are free to read and not free to reproduce; the use note on each is binding.

Never

  • Collect status that feeds no decision.
  • Take a delivery decision that belongs to the team doing the work.
  • Run a portfolio gate that has never stopped anything.
  • Let the PMO report into the function whose work it governs.
  • Accept a status color without the facts that produced it.
  • Use estimate accuracy as a performance measure.

© 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

SKILL.md and 1 other file (references) in plugins/pmo/skills/head-of-pmo of cbrock84/headcount.

  • SKILL.md
  • references/sources.md

Open the folder on GitHubat commit 98d1c17

Compare with similar skills

Head Of Pmo 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.

Head Of Pmo compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Head Of Pmo this skillcbrock84/headcount2k—~1.3kAutomated safety check: PassMIT
Gitea Workflowjwynia/agent-skills170—~3.8kAutomated safety check: PassMIT
Status Update Writeraakashg/pm-claude-skills112—~2.5kAutomated safety check: PassMIT
Daily Meeting Updatedavila7/claude-code-templates33k2 repos~3kAutomated safety check: PassMIT
Foundation Meeting Synthesizeproduct-on-purpose/pm-skills716—~2.4kAutomated safety check: PassApache-2.0
Agile Workflowjwynia/agent-skills170—~3.5kAutomated safety check: PassMIT

Similar skills

  • Gitea Workflow

    jwynia/agent-skills

    Orchestrate agile development workflows for Gitea repositories using the tea CLI.

    170 GitHub stars~3.8k tokensUpdated 7 mo ago
    Product & Project ManagementAuto-check passed

  • Status Update Writer

    aakashg/pm-claude-skills

    A skill your agent uses when the user asks to write a status update, weekly or monthly update, stakeholder update, project update, standup, status report, or QBR.

    112 GitHub stars~2.5k tokensUpdated 2 mo ago
    Product & Project ManagementAuto-check passed

  • Daily Meeting Update

    davila7/claude-code-templates

    Interactive daily standup/meeting update generator. An agent skill from davila7/claude-code-templates.

    33k GitHub starsUsed in 2 repos~3k tokens
    Product & Project ManagementAuto-check passed

  • Foundation Meeting Synthesize

    product-on-purpose/pm-skills

    Cross-meeting archaeology skill. An agent skill from product-on-purpose/pm-skills.

    716 GitHub stars~2.4k tokensUpdated 3 days ago
    Product & Project ManagementAuto-check passed

  • Agile Workflow

    jwynia/agent-skills

    Orchestrate agile development workflows by invoking commands in sequence with checkpoint-based flow control.

    170 GitHub stars~3.5k tokensUpdated 7 mo ago
    Product & Project ManagementAuto-check passed

  • Pmstudio Comms

    coco-research/coco

    Generate templated stakeholder communications from project context.

    513 GitHub stars~1.2k tokensUpdated yesterday
    Product & Project ManagementAuto-check passed

More from cbrock84/headcount

All 178 skills in this repo

  • Agent 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…

    2k GitHub stars~1.2k tokensUpdated 24 days ago
    Auto-check passed

  • Access And Identity

    cbrock84/headcount

    Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process.

    2k GitHub stars~1.1k tokensUpdated 24 days ago
    Auto-check passed

  • 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…

    2k GitHub stars~1.2k tokensUpdated 24 days ago
    Auto-check passed

  • 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.

    2k GitHub stars~865 tokensUpdated 24 days ago
    Auto-check passed

  • 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.

    2k GitHub stars~1k tokensUpdated 24 days ago
    Auto-check passed

  • 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.

    2k GitHub stars~916 tokensUpdated 24 days ago
    Auto-check passed

Categories

Questions about Head Of Pmo

What does Head Of Pmo do?

The EPMO lead's remit — what the PMO governs, what it must never become, and how it earns standing rather than compliance. Head Of Pmo is an agent skill from cbrock84/headcount. The EPMO lead's remit — what the PMO governs, what it must never become, and how it earns standing rather than compliance.

When should I use Head Of Pmo?

Head Of Pmo fits situations like: tasks that involve Meeting notes and agendas.

How do I install Head Of Pmo in Claude Code?

Run `npx skills add cbrock84/headcount --skill head-of-pmo -a claude-code`. Or copy the skill folder (plugins/pmo/skills/head-of-pmo in cbrock84/headcount) into .claude/skills/head-of-pmo in your project. Claude Code loads it when a task matches its description.

How do I install Head Of Pmo in Codex?

Run `npx skills add cbrock84/headcount --skill head-of-pmo -a codex`. Or copy the skill folder (plugins/pmo/skills/head-of-pmo in cbrock84/headcount) into .agents/skills/head-of-pmo in your project. Codex loads it when a task matches its description.

Can I use Head Of Pmo 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 head-of-pmo -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/head-of-pmo, .gemini/skills/head-of-pmo, .github/skills/head-of-pmo and .opencode/skills/head-of-pmo in your project.

What does Head Of Pmo need to run?

SKILL.md names no scripts, command-line tools or credentials: Head Of Pmo is instructions for the agent only.

Does Head Of Pmo 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 Head Of Pmo 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 Head Of Pmo use?

Head Of Pmo 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 Head Of Pmo use?

About 1.3k tokens (SKILL.md is roughly 5.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 224 tokens, read only when the agent opens those files.

What are the alternatives to Head Of Pmo?

Skills that share tags, products or a category with Head Of Pmo: Gitea Workflow (jwynia/agent-skills, 170 stars), Status Update Writer (aakashg/pm-claude-skills, 112 stars), Daily Meeting Update (davila7/claude-code-templates, 33k stars) and Foundation Meeting Synthesize (product-on-purpose/pm-skills, 716 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Head Of Pmo?

cbrock84 (a GitHub user) maintains it in cbrock84/headcount, which has 2,022 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.