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 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 full-length employment document templates with minimal instructional content. It is extremely verbose, consuming a massive token budget on boilerplate legal text that could be referenced from separate files. It lacks any workflow guidance for how to actually draft, customize, or validate employment documents, and the inline templates make the skill nearly unusable as a quick-reference guide.
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 decision guidance for which template to use.
Add a clear workflow with sequenced steps: 1) Identify document type needed, 2) Determine jurisdiction requirements, 3) Select and customize template, 4) Validate required clauses checklist, 5) Flag for legal review.
Replace the generic best practices and concept explanations with actionable decision trees—e.g., when to use at-will vs. fixed-term language, which clauses are required vs. optional by jurisdiction type.
Add a validation checklist for each document type listing must-have clauses and jurisdiction-specific considerations to check before finalizing.
| 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 three full-length templates are massive walls of boilerplate text that consume enormous token budget. Much of this could be condensed to key structural patterns and jurisdiction-specific gotchas. | 1 / 3 |
Actionability | The templates are concrete and copy-paste ready with clear placeholder syntax, which is good. However, they are static markdown 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 sequenced steps for drafting, reviewing, or customizing templates. No validation checkpoints (e.g., verify jurisdiction requirements, confirm required clauses are present, legal review step). The 'When to Use' section lists scenarios but provides no process for any of them. | 1 / 3 |
Progressive Disclosure | Monolithic wall of text with three enormous templates inline. The offer letter, employment agreement, and handbook policy section should each be in separate referenced files. External resource links at the bottom are generic URLs rather than structured references to companion skill files. | 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
47823e3
- 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.