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.
Install with Tessl CLI
npx tessl i github:wshobson/agents --skill employment-contract-templates65
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 follows best practices. It uses third person voice, lists specific document types, includes a clear 'Use when...' clause with natural trigger terms, and carves out a distinct niche in HR/employment documentation that won't easily conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Create employment contracts, offer letters, and HR policy documents' with the qualifier 'following legal best practices'. This clearly describes what the skill does with specific document types. | 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 natural keywords users would say: 'employment contracts', 'offer letters', 'HR policy documents', 'employment agreements', 'HR policies', 'employment documentation'. Good coverage of terms someone in HR or management would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on HR/employment documentation. The specific document types (employment contracts, offer letters, HR policies) create distinct triggers 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 excessively verbose, embedding complete multi-page templates that consume significant token budget without providing proportional value. It lacks workflow guidance for the document creation process and fails to structure content appropriately—full templates should be referenced files, not inline content. The skill reads more like a static document repository than actionable guidance for Claude.
Suggestions
Move full templates to separate reference files (e.g., OFFER_LETTER_TEMPLATE.md, EMPLOYMENT_AGREEMENT.md) and keep only key patterns/snippets in the main skill
Add a clear workflow section with steps like: 1) Identify jurisdiction requirements, 2) Select appropriate template, 3) Customize required fields, 4) Flag sections needing legal review
Remove the 'Core Concepts' table explaining document types—Claude knows what offer letters and NDAs are
Add specific customization guidance: which clauses vary by state, what fields must be filled, and validation checkpoints before finalizing documents
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive template content that Claude could generate on demand. The 'Core Concepts' section explains basic document types Claude already knows, and the full templates consume excessive tokens when patterns/examples would suffice. | 1 / 3 |
Actionability | Provides concrete templates that are copy-paste ready, but they're static markdown documents rather than executable guidance. Missing specific instructions on how to customize templates for different jurisdictions or scenarios. | 2 / 3 |
Workflow Clarity | No clear workflow for creating employment documents. Lists 'When to Use' scenarios but provides no sequenced process for drafting, reviewing, or validating documents. Missing critical validation steps for legal document creation. | 1 / 3 |
Progressive Disclosure | Monolithic wall of text with three massive templates inline. Content that should be in separate reference files (full templates, policy sections) is embedded directly, making the skill unwieldy and difficult to navigate. | 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 | |
- 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.