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 lengthy legal document templates with minimal instructional value. Claude already knows how to draft employment documents, so the skill should focus on project-specific conventions, jurisdiction-specific requirements, or decision frameworks rather than reproducing boilerplate. The massive inline templates destroy token efficiency and the lack of any workflow or customization guidance makes this more of a static reference than an actionable skill.
Suggestions
Move the full templates to separate referenced files (e.g., offer-letter-template.md, employment-agreement-template.md) and keep SKILL.md as a concise overview with navigation links.
Add a workflow for document creation: e.g., 1) Determine jurisdiction, 2) Select template, 3) Customize required sections, 4) Validate jurisdiction-specific requirements, 5) Flag sections needing legal review.
Replace the verbose templates with compact structural outlines showing required sections and key decision points (at-will vs. fixed term, exempt vs. non-exempt) rather than full boilerplate text.
Remove the 'Core Concepts' section and document type table — Claude already knows what offer letters and NDAs are. Focus on project-specific conventions or jurisdiction-specific gotchas instead.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~400+ lines. The templates are essentially full legal documents that Claude could generate on its own. The skill explains basic concepts like document types and employment relationships that Claude already knows. The table of document types, the 'When to Use This Skill' list, and the 'Core Concepts' section all add tokens without adding value. | 1 / 3 |
Actionability | The templates are concrete and could be copy-pasted, which is somewhat actionable. However, they are essentially fill-in-the-blank documents with [PLACEHOLDER] fields rather than executable guidance. There's no instruction on how to customize these templates based on specific inputs or how to make jurisdiction-specific decisions. | 2 / 3 |
Workflow Clarity | There is no workflow or process described. The skill provides static templates but no guidance on the sequence of steps for creating employment documents, no validation checkpoints (e.g., verifying jurisdiction-specific requirements are met), and no decision logic for choosing between template options or customizing sections. | 1 / 3 |
Progressive Disclosure | This is a monolithic wall of text with three massive templates inlined. The templates should be in separate referenced files, with the SKILL.md providing a concise overview and decision guidance. There are no references to external files, and the content is poorly organized 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
27a7ed9
- 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.