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.
| 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 an explicit 'Use when...' clause. | 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 essentially a dump of three large employment document templates with minimal instructional value. It lacks workflow guidance, validation steps, and any process for Claude to follow when creating these documents. The extreme verbosity—mostly boilerplate legal text that could be in separate referenced files—makes it a poor use of context window, and the absence of actionable steps beyond 'fill in the blanks' limits its utility.
Suggestions
Extract the three full templates into separate referenced files (e.g., OFFER_LETTER.md, EMPLOYMENT_AGREEMENT.md, HANDBOOK_POLICIES.md) and keep SKILL.md as a concise overview with clear navigation links.
Add a clear workflow: 1) Determine document type needed, 2) Gather required information (with a checklist), 3) Select and customize template, 4) Validate jurisdiction-specific requirements, 5) Flag sections needing legal review.
Remove explanatory content Claude already knows (document type table, employment relationship taxonomy, generic best practices) and replace with specific, actionable customization guidance like jurisdiction-specific variations or common pitfalls.
Add validation checkpoints such as 'verify at-will language matches jurisdiction' or 'confirm non-compete enforceability in target state' to prevent legally problematic output.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~400+ lines. The table of document types, the 'Core Concepts' section explaining employment relationship categories, and the 'Best Practices' do's/don'ts are all things Claude already knows. The three full-length templates are massive walls of boilerplate text that consume enormous token budget. Much of this could be condensed dramatically. | 1 / 3 |
Actionability | The templates are concrete and could be copy-pasted, which is good. However, they are static markdown templates with placeholder brackets rather than executable code or dynamic generation logic. There's no guidance on how to programmatically generate, customize, or validate these documents—it's essentially a fill-in-the-blank exercise rather than actionable instructions for Claude. | 2 / 3 |
Workflow Clarity | There is no workflow or sequenced process for creating employment documents. No steps for how to gather requirements, select the right template, customize it, validate legal compliance, or review the output. The skill just presents raw templates with no process guidance, validation checkpoints, or error handling. | 1 / 3 |
Progressive Disclosure | Everything is dumped into a single monolithic file with no references to external files. Three massive templates are inlined when they should be separate files referenced from a concise overview. The content is a wall of text with no layered structure for discovery. | 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
08ded5e
- 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.