CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

people-report

Generate headcount, attrition, diversity, or org health reports. Use when pulling a headcount snapshot for leadership, analyzing turnover trends by team, preparing diversity representation metrics, or assessing span of control and flight risk across the org.

Quality

79%

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

Fix and improve this skill with Tessl

tessl review fix ./human-resources/skills/people-report/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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-organized, token-efficient instruction skill with concrete report definitions and a strong output template. Its main weakness is workflow clarity — the analysis workflow lacks validation checkpoints and specifies no concrete statistical methods per report type.

Suggestions

Add validation checkpoints to the Approach workflow, e.g., after identifying data: verify date ranges, confirm which terminations count as voluntary, and check denominator definitions (average headcount vs. period-end) before computing attrition.

Replace "Analyze with appropriate statistical methods" with per-report-type specifics, e.g., attrition rate = leavers ÷ average headcount over the period, broken out by team and quarter for trend analysis.

Trim the redundant second intro sentence ("Analyze workforce data to surface trends, risks, and opportunities.") since it restates the first line.

DimensionReasoningScore

Conciseness

Metric sections are lean enumerations with no concept explanations Claude already knows, and the output template earns its tokens. Not 5 because the opening line "Analyze workforce data to surface trends, risks, and opportunities" partially restates the first sentence and a few list items could be tightened.

4 / 5

Actionability

Concrete guidance throughout: per-report-type definitions, a field checklist for input data, and a copy-paste markdown output template. Not 5 because "Analyze with appropriate statistical methods" and "Present findings with context and caveats" remain vague; not 3 since the template and checklists are executable-level guidance.

4 / 5

Workflow Clarity

The Approach lists a clear 5-step sequence but has no validation checkpoints — nothing verifies data completeness, date ranges, or metric denominators before reporting. Matches anchor 3 (sequence present, checkpoints missing/implicit); the Methodology output section is only an implicit transparency step.

3 / 5

Progressive Disclosure

Well-organized sections (Usage, Report Types, Key Metrics, Approach, Output, Connectors) with no nested references. Not 5 because the body is ~93 lines (above the under-50-line simple-skill exception) and the only reference, ../../CONNECTORS.md, is external to the bundle and unverifiable.

4 / 5

Total

15

/

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 strong description that clearly states what the skill does and when to use it, with concrete trigger phrases and good natural-language keyword coverage. Minor room to add synonyms like "retention" or "people analytics" and to sharpen distinctiveness from generic reporting skills.

DimensionReasoningScore

Specificity

Names four concrete report types ("headcount, attrition, diversity, or org health reports") — several specific actions. Not 5 because it omits inputs/analysis detail; not 3 because coverage goes beyond 1-2 actions.

4 / 5

Completeness

Explicitly answers both: "Generate headcount, attrition, diversity, or org health reports" (what) and a full "Use when..." clause with four concrete trigger scenarios (when). Matches the anchor-5 good example pattern exactly.

5 / 5

Trigger Term Quality

Includes natural HR terms users would say: "headcount snapshot", "turnover trends", "flight risk", "span of control", plus the attrition/turnover synonym pair. Not 5 because common variations like "retention", "people analytics", or "employee data" are missing.

4 / 5

Distinctiveness Conflict Risk

Clear HR/people-analytics niche with distinct triggers (headcount, attrition, flight risk). Not 5 because generic "generate reports" phrasing creates minor overlap risk with general reporting or data-analysis skills.

4 / 5

Total

17

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 1 suspicious

Warning

Total

14

/

16

Passed

Repository

anthropics/knowledge-work-plugins

Path

human-resources/skills/people-report/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.