Skill Detail

Install Claude Code department workflows with headcount

Use headcount to install focused Claude Code department plugins and invoke repeatable specialist workflows across business, engineering, security, finance, product, and operations work.

Templates & WorkflowsClaude Code
Templates & Workflows Claude Code Security Reviewed
โญ 743 GitHub stars
COPY SKILL INSTRUCTIONS (OPTIONAL)
npx skills add agentskillexchange/skills --skill install-claude-code-department-workflows-with-headcount Copy
Uses the third-party skills CLI, not an ASE-owned installer. Check your agent’s compatibility. This copies instructions; complete the upstream tool setup below separately.
At a glance
Tools required
Claude Code plugin marketplace, headcount department plugins
Install & setup
/plugin marketplace add cbrock84/headcount /plugin install security@headcount
Author
cbrock84
Publisher
Community
Last updated
Aug 31, 2026
Quick brief

## What it does

How it works

What this skill actually does

headcount is an installable Claude Code skill and plugin organization structured as company departments. Instead of loading one broad prompt library, an operator installs only the departments a project needs, then invokes individual skills such as `security:threat-modeling`, `finance:unit-economics`, `technology:implementation-planning`, or `demand-generation:landing-page-cro-expert`.

Use it when a Claude Code session needs a repeatable specialist lens or a cross-functional operating flow, not when you only want to browse the repository. The upstream docs describe single-skill invocation, independently installable departments, reviewer-class departments, and multi-department situations such as SOC 2 readiness, incident response, diligence prep, stalled growth diagnosis, contract review, and hiring planning.

## When to use it

Invoke this skill when an agent/operator wants to:

– Install a specific Claude Code department rather than a full skill collection.
– Route a business, product, engineering, security, finance, legal, marketing, or operations question to a named specialist workflow.
– Delegate a department as a subagent with its own charter and bounded surface.
– Work through a situation that crosses departments while preserving reviewer-class stops for security or legal risk.
– Keep Claude Code skills addressable as `department:skill` names so they do not collide.

## Scope boundary

This is not a generic product, SDK, or Claude Code listing. The repeatable unit is the operator workflow: choose a department, install it, invoke a named skill or cross-department use case, and keep the agent’s advice inside that department’s charter. The boundary is Claude Code department workflow execution; it should not be presented as a general company-management platform or as a replacement for qualified legal, tax, security, or financial counsel.

## Source-backed installation

“`
/plugin marketplace add cbrock84/headcount
/plugin install security@headcount
“`

Install additional departments as needed, then invoke skills by prompt matching or directly by department-qualified name, for example `/finance:financial-modeling`.