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

Quality Management

by cbrock84 in cbrock84/headcount

Builds quality into operations — defining standards, catching defects at the right point, root cause analysis, and continuous improvement.

MITAuto-check passedDevelopment

Install Quality Management

skills CLI
$ npx skills add cbrock84/headcount --skill quality-management -a claude-code

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

GitHub CLI
$ gh skill install cbrock84/headcount quality-management --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/operations/skills/quality-management .claude/skills/quality-management && 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
quality-management
GitHub stars
2k
Token cost
~1k tokens
SKILL.md length
569 words
Files
2 (incl. references)
Skills in repo
178
Repo updated
First seen
Licence
MIT

At a glance

Builds quality into operations — defining standards, catching defects at the right point, root cause analysis, and continuous improvement.

  • Works in 4 steps: Prevent — make the defect impossible.… → Detect at source — the person doing the… → Detect downstream — the next step… → …
  • Tasks that involve Root cause analysis
  • SKILL.md covers Define quality as the customer…, Catch defects where they are…, Root cause, not first cause and Metrics that do not corrupt, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Quality Management is an agent skill from cbrock84/headcount. Builds quality into operations — defining standards, catching defects at the right point, root cause analysis, and continuous improvement. Use this to reduce a defect or error rate, design quality controls into a process, run a root cause analysis, respond to a customer quality complaint, or set up quality metrics that drive behavior.

Its SKILL.md is about 1k 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 Development, covering Root cause analysis and Design review and critique. 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 Root cause analysis
  • Tasks that involve Design review and critique

Example prompts

  • “Use the quality-management skill to build quality into operations — defining standards, catching defects at the right point, root cause analysis…”
  • “/quality-management”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Prevent — make the defect impossible. Constraints, defaults, required fields, fixtures.
  2. Detect at source — the person doing the work sees the error immediately.
  3. Detect downstream — the next step catches it. Slower, and adds rework.
  4. Detect at the customer — the most expensive possible option, and it costs trust as well.

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

Quality Management loads about 1k tokens when it runs, and up to ~1.5k if it reads all its reference files. Until then it costs about 89 tokens; SKILL.md has 569 words of instructions outside code blocks.

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

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). 569 words, ~1,011 tokens.

Download SKILL.mdSave it as .claude/skills/quality-management/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
quality-management
description
Builds quality into operations — defining standards, catching defects at the right point, root cause analysis, and continuous improvement. Use this to reduce a defect or error rate, design quality controls into a process, run a root cause analysis, respond to a customer quality complaint, or set up quality metrics that drive behavior.

Quality management

Inspection at the end sorts good from bad. It never makes anything good. Quality is decided by the process that produced the work, so that is where the effort belongs.

Define quality as the customer experiences it

A standard nobody outside the team recognizes is a preference. State quality in terms a customer would agree with: correct, on time, complete, usable — with a threshold, so conformance is a fact rather than an opinion.

Then distinguish:

  • Specification quality — does it match what was specified?
  • Fitness for purpose — does the specification serve the actual need?

A process can hit specification perfectly while producing something nobody wants. Only the second question protects against that.

Catch defects where they are cheap

Cost of correction rises steeply with distance from the point of creation. Order of preference:

  1. Prevent — make the defect impossible. Constraints, defaults, required fields, fixtures.
  2. Detect at source — the person doing the work sees the error immediately.
  3. Detect downstream — the next step catches it. Slower, and adds rework.
  4. Detect at the customer — the most expensive possible option, and it costs trust as well.

Every control pushed one step earlier is worth more than an additional control at the end.

Root cause, not first cause

"Human error" is where analysis stops, not where it should. Ask what made the error easy to make and hard to notice: an ambiguous form, an unenforced sequence, a target that rewarded speed.

Work backwards through the causal chain until you reach something you can change structurally. A corrective action that depends on people being more careful is not a corrective action — the same conditions will produce the same result with different people.

Verify the fix by watching the defect rate, not by confirming the action was completed.

Metrics that do not corrupt

Any quality metric attached to individual performance will be gamed, usually by reclassifying defects rather than preventing them. Measure at the process level, review trends rather than points, and pair any rate metric with a volume metric so improvement by doing less is visible.

Escaped defects — those the customer found — are the honest measure. Everything else is a proxy.

Show full SKILL.md (210 more words)Show less

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.

Tooling

A quality management system is a regulatory purchase before it is an operational one. Greenlight Guru, Qualio, MasterControl, ETQ and similar exist because regulated industries need document control, training records and corrective actions in an auditable system. Outside those industries a well-run issue tracker and a document repository cover the same ground.

Corrective and preventive action tracking is the part worth having in one place regardless of tool, because the recurring finding is always an action from last time that was never closed.

Statistical process control needs measurement more than software. A control chart in a spreadsheet built on real measurements beats a platform fed by nobody.

Never

  • Attribute a defect to carelessness and stop there.
  • Add an inspection step in place of fixing the process that produced the defect.
  • Set a quality target for an individual that they can meet by reclassifying.
  • Close a corrective action without evidence the rate moved.

© 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/operations/skills/quality-management of cbrock84/headcount.

  • SKILL.md
  • references/sources.md

Open the folder on GitHubat commit 98d1c17

Compare with similar skills

Quality Management 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.

Quality Management compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Quality Management this skillcbrock84/headcount2k—~1kAutomated safety check: PassMIT
Code Design Rationale Investigatorcursor/plugins10k9 repos~2.6kAutomated safety check: PassNone
OpenLogi macOS Permissions TriageAprilNEA/OpenLogi23k—~2.5kAutomated safety check: NotesApache-2.0
Bug Finder for daisyUIsaadeghi/daisyui43k—~2.3kAutomated safety check: PassMIT
Root Cause Debugginggarrytan/gstack136k—~1.4kAutomated safety check: PassMIT
Review PRapache/shardingsphere21k—~6.4kAutomated safety check: PassApache-2.0

Similar skills

  • Code Design Rationale Investigator

    cursor/plugins

    Official

    Digs into why code is shaped the way it is by checking git history, pull requests and connected tools in parallel, then reporting a cited read on the tradeoffs.

    10k GitHub starsUsed in 9 repos~2.6k tokens
    DevelopmentAuto-check passed

  • OpenLogi macOS Permissions Triage

    AprilNEA/OpenLogi

    Decides whether an OpenLogi device problem on macOS is a privacy-permission (TCC) problem, using agent log lines, and says which identity needs which grant.

    23k GitHub stars~2.5k tokensUpdated today
    DevelopmentAuto-check: notes

  • Bug Finder for daisyUI

    saadeghi/daisyui

    Investigates suspected bugs in the daisyUI monorepo through read-only analysis, then writes a decision-ready fix plan in tmp/bugs without changing any product code.

    43k GitHub stars~2.3k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Root Cause Debugging

    garrytan/gstack

    Investigates bugs, errors and stack traces in phases and requires a root-cause hypothesis to be confirmed before any fix is written.

    136k GitHub stars~1.4k tokensUpdated today
    DevelopmentAuto-check passed

  • Review PR

    apache/shardingsphere

    Review Apache ShardingSphere or user-authorized downstream pull requests and PR discussions from public or authorized repository evidence.

    21k GitHub stars~6.4k tokensUpdated today
    DevelopmentAuto-check passed

  • Graph-Based Bug Tracing

    tirth8205/code-review-graph

    Traces a bug through a code knowledge graph, following callers, callees and execution flow before opening source files, within a small token budget.

    32k GitHub starsUsed in 1 repo~287 tokens
    DevelopmentAuto-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 21 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 21 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 21 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 21 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 21 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 21 days ago
    Auto-check passed

Categories

Questions about Quality Management

What does Quality Management do?

Builds quality into operations — defining standards, catching defects at the right point, root cause analysis, and continuous improvement. Quality Management is an agent skill from cbrock84/headcount. Builds quality into operations — defining standards, catching defects at the right point, root cause analysis, and continuous improvement.

When should I use Quality Management?

Quality Management fits situations like: tasks that involve Root cause analysis; tasks that involve Design review and critique.

How do I install Quality Management in Claude Code?

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

How do I install Quality Management in Codex?

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

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

What does Quality Management need to run?

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

Does Quality Management 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 Quality Management 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 Quality Management use?

Quality Management 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 Quality Management use?

About 1k tokens (SKILL.md is roughly 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 448 tokens, read only when the agent opens those files.

What are the alternatives to Quality Management?

Skills that share tags, products or a category with Quality Management: Code Design Rationale Investigator (cursor/plugins, 10k stars), OpenLogi macOS Permissions Triage (AprilNEA/OpenLogi, 23k stars), Bug Finder for daisyUI (saadeghi/daisyui, 43k stars) and Root Cause Debugging (garrytan/gstack, 136k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Quality Management?

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.