CtrlK
BlogDocsLog inGet started
Tessl Logo

hr-pro

Professional, ethical HR partner for hiring, onboarding/offboarding, PTO and leave, performance, compliant policies, and employee relations.

56

Quality

63%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/hr-pro/SKILL.md

The canonical home for this skill is hr-pro in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

57%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, actionable HR instruction skill whose main weaknesses are repeated legal-disclaimer padding, implicit validation checkpoints, and a dangling reference to a missing file. Tightening these would lift conciseness and progressive disclosure.

Suggestions

Consolidate the legal disclaimer into one canonical block and reference it elsewhere instead of restating it three times.

Add explicit validation checkpoints to each playbook (e.g., 'Before finalizing a policy: confirm jurisdiction, review against local-law checklist, and escalate to counsel on high-risk items'), with a validate->fix->retry loop.

Either create the referenced 'resources/implementation-playbook.md' (or move it under a real 'references/' bundle) and signal it clearly with a dedicated section, or remove the dangling reference.

DimensionReasoningScore

Conciseness

Most content is domain-specific HR guidance Claude does not already know, but the 'not legal advice / consult counsel' message is repeated three times (disclaimer, Operating Principles, and Guardrails), which is more than minor padding and could be tightened.

3 / 5

Actionability

Concrete deliverable structures, specific placeholders ({{CompanyName}}, {{Jurisdiction}}), and playbook components (8-12 questions, 1-5 rubric anchors) give mostly executable guidance; it stops short of copy-ready templates, appropriate for an instruction-only skill.

4 / 5

Workflow Clarity

Sequences like hiring (role design -> JD -> interview -> decision) and the 6-part Deliverable Format are clear, but validation checkpoints are mostly implicit (soft 'ask before proceeding' gates) with no validate->fix->retry loops for legally consequential outputs.

3 / 5

Progressive Disclosure

Section structure is clear and well-organized, but the only reference ('resources/implementation-playbook.md') is buried in an Instructions bullet and points to a non-existent file, leaving references mis-signaled and unresolved.

3 / 5

Total

13

/

20

Passed

Description

70%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 specific, distinctive HR description with strong trigger-term coverage, weakened only by the absence of an explicit 'Use when...' trigger clause. Adding that clause would raise completeness.

Suggestions

Append an explicit 'Use when...' trigger clause, e.g. 'Use when the user needs HR deliverables such as job descriptions, interview kits, PTO/leave policies, performance reviews, PIPs, or employee-relations templates.'

Add a few natural synonyms (e.g., 'recruiting', 'time off', 'employee handbook') to broaden trigger-term coverage.

Reframe capability areas as concrete verbs (e.g., 'Draft, review, and standardize...') to strengthen the specificity anchor.

DimensionReasoningScore

Specificity

The description lists several concrete HR capability areas ('hiring, onboarding/offboarding, PTO and leave, performance, compliant policies, and employee relations'), but they are framed as role domains ('partner for') rather than discrete concrete actions, leaving minor gaps versus the comprehensive-actions anchor.

4 / 5

Completeness

It clearly answers 'what' (HR partner across listed domains) but provides no explicit 'when' / 'Use when...' trigger clause, so per the guideline completeness is capped at 3.

3 / 5

Trigger Term Quality

Natural user phrases like 'hiring', 'onboarding/offboarding', 'PTO and leave', 'performance', and 'employee relations' are present with good coverage, though common synonyms such as 'recruiting' or 'time off' are missing.

4 / 5

Distinctiveness Conflict Risk

It carves out a clear HR niche with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

16

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.