CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

chro-advisor

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.

66

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured overview body with tight tables, concrete numeric guidance, runnable scripts, and proper delegation to one-level-deep reference files. The main deductions are a redundant Keywords section, no worked script/artifact example, and one dangling cross-bundle reference.

Suggestions

Delete the Keywords section — it duplicates trigger terms already in the frontmatter description and spends tokens on nothing the body needs.

Add one concrete script invocation (e.g., a sample plan.json with the `--config` flag) or a worked example of one Output Artifact to push actionability from good to copy-paste-ready.

Fix or remove the `../agent-protocol/SKILL.md` reference (the file does not exist in the bundle), and keep per-workflow validation explicit (e.g., a checklist step for comp-band or headcount outputs) rather than relying solely on the general output quality loop.

DimensionReasoningScore

Conciseness

The body is dense and efficient — metric tables, a rating-distribution table, and terse directive prose ("Culture is behavior, not values on a wall. Measure eNPS quarterly. Act on results within 30 days or don't ask.") with no explanation of concepts Claude already knows. Not a 5 because the Keywords section (~25 terms) duplicates the frontmatter description's triggers and the "Reasoning Technique: Empathy + Data" section is trimmable padding.

4 / 5

Actionability

Quick Start gives two copy-paste-ready commands that map to real scripts (verified present in scripts/), and guidance is concrete throughout: specific metric targets ("Time to fill < 45 days", "Compa-ratio 0.95–1.05", "Span of control 4–7"), a calibrated rating distribution, and an Output Artifacts table mapping five common requests to deliverables. Not a 5 because there is no worked example of running a script (e.g., a sample --config invocation) or a sample artifact, so coverage of common cases is implied rather than shown.

4 / 5

Workflow Clarity

Key processes are given as clear arrow sequences ("business goals → org requirements → headcount plan → budget impact", "Structured onboarding → 30/60/90 plans → regular 1:1s → career pathing → proactive comp reviews") and output passes an explicit verification loop ("Self-verify: source attribution, assumption audit, confidence scoring"; findings tagged 🟢🟡🔴). Not a 5 because checkpoints are a single general output gate rather than per-workflow validation steps with error-recovery loops; not a 3 because validation is explicit, not merely implied.

4 / 5

Progressive Disclosure

The body is a genuine overview: detail is delegated to three real, well-signaled one-level-deep reference files (all verified present, none nesting further) listed both inline and in a Detailed References section, plus two runnable scripts. Not a 5 because the Communication section points to `../agent-protocol/SKILL.md`, a path outside the bundle that does not exist, leaving a dangling reference in otherwise clean navigation.

4 / 5

Total

16

/

20

Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A well-constructed description that explicitly covers what the skill does and when to use it, with a rich set of natural trigger terms. Minor gaps: trigger synonyms (recruiting, CPO, salary) and noun-phrase rather than action-phrase capability listing.

Suggestions

Lead the capability list with concrete actions (e.g., "Builds hiring plans, designs salary bands and equity frameworks, structures orgs...") to sharpen specificity.

Add missing natural trigger synonyms such as "recruiting", "CPO/chief people officer", and "salary bands" to the 'Use when' clause.

DimensionReasoningScore

Specificity

Names the domain ("People leadership for scaling companies") and lists several concrete capability areas — "Hiring strategy, compensation design, org structure, culture, and retention" — with only minor gaps. Not a 5 because these are capability areas stated as noun phrases rather than the multiple specific concrete actions (verb-led, like "extract text and tables... fill forms, merge documents") of the top anchor.

4 / 5

Completeness

Explicitly answers both what ("Hiring strategy, compensation design, org structure, culture, and retention") and when with concrete trigger phrases ("Use when building hiring plans, designing comp frameworks... or when user mentions CHRO, HR, people strategy, talent, headcount..."). This matches the top anchor exactly; it is not a 4 because the 'when' clause is explicit and trigger-phrase-specific, not merely present.

5 / 5

Trigger Term Quality

Strong natural trigger coverage: "CHRO, HR, people strategy, talent, headcount, compensation, org design, retention, or performance management" plus task phrases like "building hiring plans, designing comp frameworks, restructuring teams" — terms a user would naturally say. Not a 5 because common variants like "recruiting", "CPO/chief people officer", and "salary" are absent, so coverage is good but not exhaustive.

4 / 5

Distinctiveness Conflict Risk

The "People leadership for scaling companies" scope with CHRO/HR triggers carves a clear niche, but terms like "compensation" and "headcount" are shared territory with a CFO-type skill (the body itself lists comp collaboration with CFO), giving minor overlap risk with closely related C-suite skills. Not a 5 (minimal conflict risk) for that reason; clearly above the 3 anchor ("could still overlap with similar skills") because the trigger set is role-specific.

4 / 5

Total

17

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

alirezarezvani/claude-skills

Path

c-level-advisor/skills/chro-advisor/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.