skills/c-level-advisor/chro-advisor/SKILL.md
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.
npx skillsauth add neekware/ehayeskills chro-advisorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
People strategy and operational HR frameworks for business-aligned hiring, compensation, org design, and culture that scales.
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
python scripts/hiring_plan_modeler.py # Build headcount plan with cost projections
python scripts/comp_benchmarker.py # Benchmark salaries and model total comp
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.
Market-anchored salary bands + equity strategy + total comp modeling. See references/comp_frameworks.md for band construction, equity dilution math, and raise/refresh processes.
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.
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 |
Culture is behavior, not values on a wall. Measure eNPS quarterly. Act on results within 30 days or don't ask.
| 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 |
| 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 |
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 mgmtSurface these without being asked when you detect them in company context:
| 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 |
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?
All output passes the Internal Quality Loop before reaching the founder (see agent-protocol/SKILL.md).
company-context.md before responding (if it exists)[INVOKE:role|question]tools
# ehAye Multimedia Use this skill for **video, audio, images, media conversion, previews, transcription, thumbnails, frame extraction, Spotter visual search, or FFmpeg-backed processing**. Core rule: use ehAye native media tools first. Do not reach first for shell `ffmpeg`, `ffprobe`, Python, or `mediainfo` when a native media tool can do the job. Native tools use bundled engines, show proper tool UI, respect cancellation/timeouts, integrate with Preview/Spotter, and avoid cross-platform shell
development
Test-driven development skill for writing unit tests, generating test fixtures and mocks, analyzing coverage gaps, and guiding red-green-refactor workflows across Jest, Pytest, JUnit, Vitest, and Mocha. Use when the user asks to write tests, improve test coverage, practice TDD, generate mocks or stubs, or mentions testing frameworks like Jest, pytest, or JUnit. Handles test generation from source code, coverage report parsing (LCOV/JSON/XML), quality scoring, and framework conversion for TypeScript, JavaScript, Python, and Java projects.
tools
Help a user set up Telegram for ehAye Dojo. Default to Personal private bots (recommended). Group setup is advanced for teams/observers/demos.
development
# Writing Skills ## Overview **Writing skills IS Test-Driven Development applied to process documentation.** **Personal skills live in agent-specific directories (`~/.claude/skills` for Claude Code, `~/.agents/skills/` for Codex)** You write test cases (pressure scenarios with subagents), watch them fail (baseline behavior), write the skill (documentation), watch tests pass (agents comply), and refactor (close loopholes). **Core principle:** If you didn't watch an agent fail without the ski