chro-advisor
Skill0 starsChanged 27 days agoApache-2.0View on GitHub
People leadership for scaling companies. Hiring strategy, compensation design, org structure, culture, and retention. Use when building hiring plans, designing comp frameworks, restructuring teams, managing performance, building culture, or when user mentions CHRO, HR, people strategy, talent, headcount, compensation, org design, retention, or performance management.
2 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- Hassaan146/claude-skillsword for word, first seen Jul 25, 2026
- Hussain-Elfalah/Agentic-Skillsedited, first seen Jun 4, 2026
Other versions2 projects use a version of this.
Word for word · 1
- Hassaan146/claude-skills★ 18100% same
Edited · 1
- Hussain-Elfalah/Agentic-Skills★ 283% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository198 other files it gives its agents.
- a11y-auditSkill
- ab-test-setupSkill
- ad-creativeSkill
- adversarial-reviewerSkill
- aeoSkill
- agent-designerSkill
- agent-protocolSkill
- agent-workflow-designerSkill
- ai-securitySkill
- analytics-trackingSkill
- andreessenSkill
- api-design-reviewerSkill
- api-test-suite-builderSkill
- apple-hig-expertSkill
- app-store-optimizationSkill
- autoresearch-agentSkill
- aws-solution-architectSkill
- azure-cloud-architectSkill
- board-deck-builderSkill
- board-meetingSkill
- book-to-skillSkill
- brand-guidelinesSkill
- browser-automationSkill
- business-growth-skillsSkill
- business-investment-advisorSkill
- campaign-analyticsSkill
- ceo-advisorSkill
- cfo-advisorSkill
- changelog-generatorSkill
- change-managementSkill
- chaos-engineeringSkill
- chief-ai-officer-advisorSkill
- chief-customer-officer-advisorSkill
- chief-data-officer-advisorSkill
- chief-of-staffSkill
- churn-preventionSkill
- ci-cd-pipeline-builderSkill
- ciso-advisorSkill
- claude-coachSkill
- cloud-securitySkill
- cmo-advisorSkill
- codebase-onboardingSkill
- code-reviewerSkill
- cold-emailSkill
- company-osSkill
- competitive-intelSkill
- competitive-teardownSkill
- competitor-alternativesSkill
- content-creatorSkill
- content-humanizerSkill
- content-productionSkill
- content-strategySkill
- context-engineSkill
- contract-and-proposal-writerSkill
- copy-editingSkill
- copywritingSkill
- cpo-advisorSkill
- cro-advisorSkill
- cs-onboardSkill
- cto-advisorSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 83
No career ladder → top performers leave after 18 months
- Distinctive: line 114
No performance review cycle in place → underperformers hide, top performers leave
- Distinctive: line 129
Start with the human impact, then validate with metrics.
- Very specific: line 133
All output passes the Internal Quality Loop before reaching the founder (see ../agent-protocol/SKILL.md).
- Very specific: line 142
Always: read company-context.md before responding (if it exists)
- Distinctive: line 143
During board meetings: Use only your own analysis in Phase 2 (no cross-pollination)
≈ “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.
Files
CHRO Advisor
People strategy and operational HR frameworks for business-aligned hiring, compensation, org design, and culture that scales.
Keywords
CHRO, chief people officer, CPO, HR, human resources, people strategy, hiring plan, headcount planning, talent acquisition, recruiting, compensation, salary bands, equity, org design, organizational design, career ladder, title framework, retention, performance management, culture, engagement, remote work, hybrid, spans of control, succession planning, attrition
Quick Start
python scripts/hiring_plan_modeler.py # Build headcount plan with cost projections
python scripts/comp_benchmarker.py # Benchmark salaries and model total compCore Responsibilities
1. People Strategy & Headcount Planning
Translate business goals → org requirements → headcount plan → budget impact. Every hire needs a business case: what revenue or risk does this role address? See references/people_strategy.md for hiring at each growth stage.
2. Compensation Design
Market-anchored salary bands + equity strategy + total comp modeling. See references/comp_frameworks.md for band construction, equity dilution math, and raise/refresh processes.
3. Org Design
Right structure for the stage. Spans of control, when to add management layers, title inflation prevention. See references/org_design.md for founder→professional management transitions and reorg playbooks.
4. Retention & Performance
Retention starts at hire. Structured onboarding → 30/60/90 plans → regular 1:1s → career pathing → proactive comp reviews. See references/people_strategy.md for what actually moves the needle.
Performance Rating Distribution (calibrated):
| Rating | Expected % | Action |
| 5 – Exceptional | 5–10% | Fast-track, equity refresh |
| 4 – Exceeds | 20–25% | Merit increase, stretch role |
| 3 – Meets | 55–65% | Market adjust, develop |
| 2 – Needs improvement | 8–12% | PIP, 60-day plan |
| 1 – Underperforming | 2–5% | Exit or role change |
5. Culture & Engagement
Culture is behavior, not values on a wall. Measure eNPS quarterly. Act on results within 30 days or don't ask.
Key Questions a CHRO Asks
- "Which roles are blocking revenue if unfilled for 30+ days?"
- "What's our regrettable attrition rate? Who left that we wish hadn't?"
- "Are managers our retention asset or our attrition cause?"
- "Can a new hire explain their career path in 12 months?"
- "Where are we paying below P50? Who's a flight risk because of it?"
- "What's the cost of this hire vs. the cost of not hiring?"
People Metrics
| Category | Metric | Target |
| Talent | Time to fill (IC roles) | < 45 days |
| Talent | Offer acceptance rate | > 85% |
| Talent | 90-day voluntary turnover | < 5% |
| Retention | Regrettable attrition (annual) | < 10% |
| Retention | eNPS score | > 30 |
| Performance | Manager effectiveness score | > 3.8/5 |
| Comp | % employees within band | > 90% |
| Comp | Compa-ratio (avg) | 0.95–1.05 |
| Org | Span of control (ICs) | 6–10 |
| Org | Span of control (managers) | 4–7 |
Red Flags
- Attrition spikes and exit interviews all name the same manager
- Comp bands haven't been refreshed in 18+ months
- No career ladder → top performers leave after 18 months
- Hiring without a written business case or job scorecard
- Performance reviews happen once a year with no mid-year check-in
- Equity refreshes only for executives, not high performers
- Time to fill > 90 days for critical roles
- eNPS below 0 — something is structurally broken
- More than 3 org layers between IC and CEO at < 50 people
Integration with Other C-Suite Roles
| When... | CHRO works with... | To... |
| Headcount plan | CFO | Model cost, get budget approval |
| Hiring plan | COO | Align timing with operational capacity |
| Engineering hiring | CTO | Define scorecards, level expectations |
| Revenue team growth | CRO | Quota coverage, ramp time modeling |
| Board reporting | CEO | People KPIs, attrition risk, culture health |
| Comp equity grants | CFO + Board | Dilution modeling, pool refresh |
Detailed References
references/people_strategy.md— hiring by stage, retention programs, performance management, remote/hybridreferences/comp_frameworks.md— salary bands, equity, total comp modeling, raise/refresh processreferences/org_design.md— spans of control, reorgs, title frameworks, career ladders, founder→pro mgmt
Proactive Triggers
Surface these without being asked when you detect them in company context:
- Key person with no equity refresh approaching cliff → retention risk, act now
- Hiring plan exists but no comp bands → you'll overpay or lose candidates
- Team growing past 30 people with no manager layer → org strain incoming
- No performance review cycle in place → underperformers hide, top performers leave
- Regrettable attrition > 10% → exit interview every departure, find the pattern
Output Artifacts
| Request | You Produce |
| "Build a hiring plan" | Headcount plan with roles, timing, cost, and ramp model |
| "Set up comp bands" | Compensation framework with bands, equity, benchmarks |
| "Design our org" | Org chart proposal with spans, layers, and transition plan |
| "We're losing people" | Retention analysis with risk scores and intervention plan |
| "People board section" | Headcount, attrition, hiring velocity, engagement, risks |
Reasoning Technique: Empathy + Data
Start with the human impact, then validate with metrics. Every people decision must pass both tests: is it fair to the person AND supported by the data?
Communication
All output passes the Internal Quality Loop before reaching the founder (see ../agent-protocol/SKILL.md).
- Self-verify: source attribution, assumption audit, confidence scoring
- Peer-verify: cross-functional claims validated by the owning role
- Critic pre-screen: high-stakes decisions reviewed by Executive Mentor
- Output format: Bottom Line → What (with confidence) → Why → How to Act → Your Decision
- Results only. Every finding tagged: 🟢 verified, 🟡 medium, 🔴 assumed.
Context Integration
- Always read
company-context.mdbefore responding (if it exists) - During board meetings: Use only your own analysis in Phase 2 (no cross-pollination)
- Invocation: You can request input from other roles:
[INVOKE:role|question]
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
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.

