C-Level Advisory CHROPeopleHiring

CHRO Advisor

Hiring strategy, compensation design, org structure, and retention.

$skillfish add ~skills/chro-advisor

What This Skill Can Do

Concrete capabilities you get when you install this skill.

Design talent strategy, leveling frameworks, and compensation philosophy

Build performance management systems that drive accountability and growth

Diagnose and address retention risks, attrition patterns, and org dysfunction

Structure the people function and HR team as the company scales

Navigate workforce reductions, restructurings, and compliance requirements

Design culture measurement, engagement programs, and DEI initiatives

Real Conversations

See how the CHRO Advisor skill responds to actual requests. These are representative examples of what your AI agent will produce.

You

We've lost 8 engineers in the last 12 months out of a team of 20. Exit interviews say 'better opportunity' and 'compensation' but I think it's our CTO. He's technically brilliant but dismissive in design reviews and takes over PRs without explanation. HR is minimal — it's just me and a recruiter. How do I fix this?

Agent

40% engineering attrition is a leadership problem with a compensation story layered on top. Exit interviews almost never surface the real reason — "better opportunity" is what people say when they don't want to burn a bridge. The CTO pattern you're describing (PR takeovers, dismissive in reviews) is a classic technical authority + poor psychological safety combination. Here's how to address it.

Step 1: Verify the diagnosis before confronting the CTO. Run a skip-level survey with your remaining engineers — 5 anonymous questions: psychological safety, clarity of technical direction, quality of feedback, career growth confidence, and one open-ended. If 60%+ of responses reflect the CTO behavior pattern, you have data. Without data, a confrontation with a brilliant but defensive technologist goes nowhere.

Step 2: Have the direct conversation with the CTO using the data. Not "people don't like you" — that's personal. Use: "We've lost 8 engineers in 12 months. Our engineering attrition is 3x industry benchmark. I've identified a pattern in exit feedback that I need your help solving." Frame it as a shared business problem, not a behavioral critique. Attach the cost: each mid-level engineer loss costs $60–90K in recruiting + ramp time. 8 losses = $480–720K in replacement cost.

Step 3: Structural changes that help regardless:

  • Code review norms document: Written standards for how PRs get reviewed and commented on. Takes the CTO's behavior from personal preference to policy deviation.
  • Tech lead role: Designate 1–2 senior engineers as technical leads who own design reviews. Diffuses the single-point-of-failure dynamic.
  • Stay interviews: Quarterly 30-minute conversations with each engineer asking "what would make you consider leaving, and what would make you stay?" Better than exit interviews because the person is still there.

On compensation: Audit your comp against Levels.fyi for your market. If you're more than 15% below median, you're creating conditions where any frustration with culture becomes a financial decision to leave. Fix both.

Get Started

How to install and use this skill in your preferred environment.

Skills are designed for AI coding agents (Claude Code, Cursor, Windsurf) and IDE-based workflows where the agent can read files, run scripts, and act on your codebase. Web-based AI can use the knowledge and frameworks, but won't have tool access.

Models & Context

Which AI models and context windows work best with this skill.

Recommended Models

Best
Claude Opus 4 Claude Sonnet 4 GPT-4.1 Gemini 2.5 Pro Grok 3 Kimi K2
Good
Claude Haiku 4.5 GPT-4.1 mini Gemini 2.5 Flash Grok 3 mini

Larger models produce more detailed, production-ready outputs.

Context Window

This skill's SKILL.md is typically 3–10 KB — fits in any modern context window.

8K Skill only
32K+ Skill + conversation
100K+ Skill + references + codebase

All current frontier models (Claude, GPT, Gemini) support 100K+ context. Use the full window for complex multi-service work.

Pro tips for best results

1

Be specific

Include numbers — users, budget, RPS — so the skill can size the architecture.

2

Share constraints

Compliance needs, team size, and existing stack all improve the output.

3

Iterate

Start with a high-level design, then ask follow-ups for IaC, cost analysis, or security review.

4

Combine skills

Pair with companion skills below for end-to-end coverage.

Ready to try CHRO Advisor?

Install the skill and start getting expert-level guidance in your workflow — any agent, any IDE.

$skillfish add ~skills/chro-advisor
← Browse all 169 skills