employment-contract-templates
Create employment contracts, offer letters, and HR policy documents following legal best practices. Use when drafting employment agreements, creating HR policies, or standardizing employment documentation.
71
57%
Does it follow best practices?
Impact
99%
1.20xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/hr-legal-compliance/skills/employment-contract-templates/SKILL.mdQuality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that clearly specifies concrete actions, includes natural trigger terms with good variation coverage, and explicitly addresses both what the skill does and when to use it. The HR/employment domain is well-defined, making it distinctive and unlikely to conflict with other skills. It follows the third-person voice convention and is concise without unnecessary padding.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Create employment contracts, offer letters, and HR policy documents following legal best practices.' These are distinct, well-defined document types with a clear qualifier about legal best practices. | 3 / 3 |
Completeness | Clearly answers both what ('Create employment contracts, offer letters, and HR policy documents following legal best practices') and when ('Use when drafting employment agreements, creating HR policies, or standardizing employment documentation') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'employment contracts', 'offer letters', 'HR policy documents', 'employment agreements', 'HR policies', 'employment documentation'. Good coverage of variations (e.g., 'contracts' vs 'agreements'). | 3 / 3 |
Distinctiveness Conflict Risk | Clearly occupies a distinct niche around HR/employment documentation. The specific document types (employment contracts, offer letters, HR policies) and domain (legal best practices for employment) make it unlikely to conflict with general document or legal skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
14%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an extremely verbose dump of boilerplate employment document templates that Claude could generate on its own. It lacks any workflow guidance, validation steps, or decision-making logic for when and how to customize templates. The content would benefit enormously from being restructured into a concise overview with referenced template files and a clear workflow for document creation.
Suggestions
Move the three large templates into separate referenced files (e.g., OFFER_LETTER.md, EMPLOYMENT_AGREEMENT.md, HANDBOOK.md) and keep SKILL.md as a concise overview with navigation links.
Add a clear workflow with steps: 1) Identify jurisdiction, 2) Select template type, 3) Customize required sections, 4) Review checklist for legal compliance, 5) Flag sections needing legal counsel review.
Replace the generic templates with decision logic and customization guidance—e.g., when to use at-will vs. fixed-term, which non-compete clauses are enforceable by state, and what sections are legally required vs. optional.
Remove the 'Core Concepts' table and tree diagram explaining employment document types and legal categories—Claude already knows these. Focus on jurisdiction-specific pitfalls and non-obvious requirements.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~400+ lines. The templates are full boilerplate that Claude already knows how to generate. The document explains basic concepts like employment types, document types, and legal considerations that Claude is well-versed in. The entire skill could be reduced to key patterns, jurisdiction-specific gotchas, and a brief example. | 1 / 3 |
Actionability | The templates are concrete and could be copy-pasted, which is good. However, they are generic placeholder-heavy templates rather than executable guidance. There's no instruction on how to customize them, no decision logic for choosing between at-will vs fixed-term, and no guidance on jurisdiction-specific adaptations beyond 'consult legal counsel.' | 2 / 3 |
Workflow Clarity | There is no workflow for creating employment documents. No sequencing of steps, no validation checkpoints, no review process. The 'Best Practices' section lists do's and don'ts but doesn't describe a process. For documents with legal implications, the absence of a review/validation workflow is a significant gap. | 1 / 3 |
Progressive Disclosure | Monolithic wall of text with three massive templates inline. The offer letter, employment agreement, and handbook policy sections should each be in separate referenced files. There are no external references or navigation aids. Everything is dumped into a single file. | 1 / 3 |
Total | 5 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (521 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
- Repository
- wshobson/agents
- Commit
91fe43e
- 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.