←Leaderboard/Business/headcount
Last commit on September 16, 2026·Created on August 28, 2026

cbrock84/headcount

“A strategic framework for multi-year portfolio choices and capital allocation”
Combined rank
#216
across all skills
In Business
#7
category rank
Stars
2.1k
+2.5% in last 7d
Forks
318
+0.6% in last 7d
Watchers
15
+7.1% in last 7d
Traction scoreGitHub stars can be faked, so popularity alone can be misleading. Traction Score looks for broader signs of recent attention, adoption, and active maintenance.
TL;DR

This skill provides a structured approach for corporate strategy executives managing long-horizon bets. It assists in determining market entry, evaluating build-buy-partner decisions, and framing strategic partnerships under uncertainty.

By focusing on corporate development and target screening, the skill helps clarify deal theses and valuation framing for business line allocation.

WHO IT'S FOR
Corporate strategy executives
planning multi-year portfolio choices and capital allocation
Corporate development teams
running deal thesis and acquisition diligence
Business development managers
evaluating new market entry and demand sizing
AI agent / automation builders
deploying structured organizational skills to AI agents
Compatible AgentsThe repository documents support for these agents. The skills may also work with other agents that can load SKILL.md files, but they may need some setup or small changes.

Use this skill collection

Follow the documented setup, then try a first task.

I’m using

Install the security department in Claude Code

Installs: Complete `security` department plugin. The department is installed independently from the other headcount departments. · Claude Code

Before you start
  • Claude Code
  1. In a Claude Code agent session, add the headcount marketplace. This is an agent-session command, not a terminal command.

    /plugin marketplace add cbrock84/headcount
  2. In the Claude Code agent session, install the security department.

    /plugin install security@headcount
README.md ↗ · Checked Oct 12, 2026docs/GETTING-STARTED.md ↗ · Checked Oct 12, 2026

Give it something to do.

Suggested first task

Explore approaches for a small feature

Uses solution-exploration

  • Proposed feature or behavior change
  • Desired outcome and current problem
  • Affected users or systems
  • Known constraints and explicit exclusions

Make sure solution-exploration is installed in your agent before trying this task.

Use the solution-exploration skill to examine this proposed feature before any code is written. Clarify the desired outcome, current problem, affected users, explicit exclusions, and observable success condition. Then present three genuinely different approaches—including the smallest workable approach and one requiring no new moving parts—with costs, tradeoffs, and necessary assumptions. Recommend one approach, explain why the others lost, and identify the assumption on which the recommendation depends most heavily.
Suggested first task

Synthesize a small set of customer interviews

Uses customer-research

  • Decision the research must inform
  • Raw interview notes or transcripts
  • Any relevant participant or segment labels

Make sure customer-research is installed in your agent before trying this task.

Use the customer-research skill to synthesize these interview notes for the stated decision. For each supported finding, report the claim, how many independent participants expressed it, one verbatim quote, and what decision would change if it is true. Clearly separate what participants said, what they did, and what you inferred. Do not treat a single interview as a general finding.
Suggested first task

Assess a programmatic SEO opportunity

Uses programmatic-seo

  • Repeating query pattern and available demand evidence
  • Description or sample of the dataset
  • Examples of how individual pages would differ
  • Examples of current ranking pages or their relevant strengths

Make sure programmatic-seo is installed in your agent before trying this task.

Use the programmatic-seo skill to assess whether this repeating search pattern is viable before building or publishing pages. Evaluate whether there is verified demand across many instances, sufficient quality data, genuine per-page value, and a defensible reason to outperform current results. Identify the minimum data threshold for generating a page and conclude with either a small validation step or a recommendation to create fewer, better pages.