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
96%
1.04xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./tests/ext_conformance/artifacts/agents-wshobson/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 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, HR) 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 static template library pasted into a single massive file, with no workflow guidance, no decision logic, and no progressive disclosure. While the templates themselves are reasonably complete, they are extremely token-inefficient for a skill file — Claude can generate standard employment contract boilerplate without needing hundreds of lines of verbatim text. The skill would be far more effective as a concise set of instructions on how to draft these documents, with key customization points and jurisdiction-specific considerations highlighted.
Suggestions
Replace full verbatim templates with concise structural outlines listing required sections and key clauses, letting Claude generate the prose. Move full templates to separate referenced files if needed.
Add a clear workflow: 1) Determine document type needed, 2) Gather key inputs (jurisdiction, employment type, compensation details), 3) Draft using appropriate template structure, 4) Verify jurisdiction-specific requirements, 5) Add disclaimer.
Add a decision tree or selection criteria for choosing between document types (offer letter vs. employment agreement vs. handbook section) based on user needs.
Split templates into separate referenced files (OFFER_LETTER.md, EMPLOYMENT_AGREEMENT.md, HANDBOOK.md) and keep SKILL.md as a concise overview with navigation links.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~400+ lines. The document types table, legal considerations tree, and best practices sections explain concepts Claude already knows. The full-length templates with every boilerplate clause are massively token-inefficient — Claude can generate standard employment contract language without being shown every section verbatim. | 1 / 3 |
Actionability | The templates are concrete and copy-paste ready with clear placeholder syntax ([COMPANY NAME], [DATE], etc.), which is good. However, the skill lacks executable guidance on *how* to use these templates — there's no instruction on how to customize them, what questions to ask the user, or how to adapt for different jurisdictions. It reads more like a static document library than actionable instructions for Claude. | 2 / 3 |
Workflow Clarity | There is no workflow or sequencing for how Claude should approach creating employment documents. No decision tree for which template to use, no steps for gathering requirements from the user, no validation checkpoints (e.g., confirming jurisdiction, verifying required clauses). The 'When to Use' section is just a bullet list with no process guidance. | 1 / 3 |
Progressive Disclosure | Everything is dumped into a single monolithic file — three massive templates are fully inlined rather than referenced as separate files. The content would benefit enormously from a brief overview in SKILL.md with links to individual template files (e.g., OFFER_LETTER.md, EMPLOYMENT_AGREEMENT.md, HANDBOOK_POLICIES.md). | 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 (528 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
- Repository
- Dicklesworthstone/pi_agent_rust
- Commit
6e3d68c
- 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.