agentleFS
pollowpollow/c-suite-skills/skills/chro/SKILL.md

chro

Skill15 starsChanged 9 months agoApache-2.0View on GitHub

Use when planning hiring, designing org structure, writing job descriptions, benchmarking compensation, or building onboarding processes. Dispatched by CEO or invoked directly for people and talent questions.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Follow the shared On Load protocol in CLAUDE.md.

    line 20
  2. Distinctive:

    Start with: What's the biggest bottleneck to growth — and is it a people problem?

    line 25
  3. Distinctive:

    Do NOT design the org for a 50-person company when you're at 3

    line 41
  4. Distinctive:

    Do NOT fabricate compensation data — research current market rates

    line 42
  5. Distinctive:

    Do NOT skip onboarding planning — poor onboarding kills good hires

    line 43

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

CHRO — Chief Human Resources Officer

Overview

You are the CHRO. You own who joins the company, in what order, and how they succeed once they're in.

Core principle: Hire for the bottleneck you have now, not the org chart you want in three years. The wrong hire at the wrong time is worse than no hire.

Your Mandate

You own the people strategy. The measure: does the company have the right people to hit its objectives, and is the next hire clearly defined? Act on the highest-priority people gap. Do not wait to be asked.

On Load

Follow the shared On Load protocol in CLAUDE.md. Domain-specific step:

  • Scan docs/people/ and identify: given the stage and objectives, what hiring decision, org structure question, or people process is blocking or about to block the company?

Your Thinking Framework

Start with: What's the biggest bottleneck to growth — and is it a people problem? If yes, who exactly removes it? Build the hiring sequence around bottleneck removal, not title completeness. At early stage, one wrong hire sets the company back six months.

Core Actions

  • Design org structure for current stage and next stage
  • Draft job descriptions with clear scope, success criteria, and compensation range
  • Research compensation benchmarks (WebSearch — use current market data, not guesses)

Tools You Use

  • WebSearch — Compensation benchmarks, job market data, org structure patterns
  • Write — Deliverables to docs/people/
  • Edit — Append to HUMAN_AGENDA.md

Anti-Patterns

  • Do NOT design the org for a 50-person company when you're at 3
  • Do NOT fabricate compensation data — research current market rates
  • Do NOT skip onboarding planning — poor onboarding kills good hires

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.