CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

nex-employee-handbook-us

Builds multi-state US employee handbooks using a core plus supplement model and NLRB-compliant conduct policies. Use when: Structure multi-state handbooks using the core plus supplement model; Audit conduct rules against the NLRB Stericycle standard; Draft federal policy modules based on specific employee headcount.

Quality

60%

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 ./skills/nex-employee-handbook-us/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

28%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.

The body reads as a product landing page rather than operational skill guidance: it markets capabilities and answers FAQ-style questions but provides no executable drafting logic, workflow, or reference materials. Its only real strengths are clear section organization and honest limitation disclosures.

Suggestions

Replace the marketing and FAQ sections with an explicit drafting workflow (e.g., 1. collect headcount and employee states, 2. draft the universal core with at-will disclaimers, 3. generate EEO/ADA/FMLA/PUMP modules per headcount thresholds, 4. build state supplements for CA/NY/IL, 5. run the Stericycle audit pass, 6. require attorney review before distribution).

Add concrete reference files with actual content, such as a state-by-state trigger table (sick leave, pay transparency, final paycheck timing, marijuana protections), federal module templates keyed to headcount thresholds, and a Stericycle audit checklist for conduct and social media policies.

Cut the 'Why this beats prompting it yourself' section, the FAQ that restates the description, and the promotional links to reclaim token budget for operational content.

DimensionReasoningScore

Conciseness

Marketing sections like 'Why this beats prompting it yourself', a FAQ that largely restates the description, and promotional links are padding that adds no operational value; time-sensitive claims ('Compliant with 2026 US Federal standards') further bloat the body.

2 / 5

Actionability

The body only describes capabilities ('Drafts a "Core + Supplement" architecture', 'Performs a "Stericycle pass"') without instructing how to execute anything — no drafting procedure, policy templates, module contents, or enumerated thresholds beyond passing mentions like the 50-employee rule.

2 / 5

Workflow Clarity

No sequenced workflow exists; the implied order (core document, headcount-based modules, state supplements, Stericycle audit, attorney review) is scattered across bullets and FAQ answers with no explicit steps or validation checkpoints.

2 / 5

Progressive Disclosure

Section headers are clear, but the substantive material that should live in reference files (state law trigger tables, policy module templates, Stericycle audit checklist) is entirely absent — the body itself states the original scripts and templates 'are not in this folder'.

3 / 5

Total

9

/

20

Passed

Description

71%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.

The description is specific, third-person, and clearly differentiated, with an explicit 'Use when:' clause covering both what and when. Its main weakness is trigger phrasing that mirrors the capability list instead of using natural user language, which limits keyword coverage.

Suggestions

Rewrite the 'Use when' triggers as natural user phrasings, e.g. 'Use when the user asks to draft, review, or update an employee handbook, policy manual, or HR policies for a multi-state or remote team'.

Add commonly spoken keywords and synonyms such as 'FMLA', 'paid sick leave', 'pay transparency', 'state supplements', and 'HR compliance' to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

Lists several concrete actions ('Builds multi-state US employee handbooks using a core plus supplement model', 'Audit conduct rules against the NLRB Stericycle standard', 'Draft federal policy modules based on specific employee headcount') with only minor gaps such as state supplements and acknowledgment forms.

4 / 5

Completeness

Both a clear 'what' ('Builds multi-state US employee handbooks...') and an explicit 'Use when:' clause with three triggers are present, but the when-clause restates capabilities in imperative form ('Structure multi-state handbooks...') rather than giving natural, distinct trigger conditions.

4 / 5

Trigger Term Quality

Relevant keywords like 'employee handbooks', 'multi-state', and 'NLRB Stericycle' appear, but 'Stericycle' is jargon most users would not naturally say, and common variations like 'HR policies', 'FMLA', 'sick leave', or 'policy manual' are missing.

3 / 5

Distinctiveness Conflict Risk

The niche is highly specific (multi-state US employee handbooks, NLRB Stericycle conduct compliance) with distinct trigger terms and minimal overlap risk with other skills.

5 / 5

Total

16

/

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

NexaiGuy/nex-ai-skills

Path

skills/nex-employee-handbook-us/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.