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:Dicklesworthstone/pi_agent_rust --skill employment-contract-templates71
Quality
57%
Does it follow best practices?
Impact
96%
1.04xAverage score across 3 eval scenarios
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 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 minimizes conflict risk 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 full-length templates that consume significant tokens while providing minimal guidance on how to actually use them. It lacks workflow clarity for the document creation process and fails to leverage progressive disclosure by inlining everything rather than referencing separate template files. The content explains concepts Claude already knows and provides generic templates without jurisdiction-specific customization guidance.
Suggestions
Move full templates to separate referenced files (e.g., OFFER_LETTER.md, EMPLOYMENT_AGREEMENT.md) and keep only brief examples with key clauses in the main skill
Add a clear workflow: 1) Identify jurisdiction 2) Determine employment type 3) Select template 4) Customize required sections 5) Legal review checklist
Remove the 'Core Concepts' table and basic explanations - Claude knows what offer letters and NDAs are
Add specific guidance on jurisdiction-dependent clauses (e.g., 'California: non-competes generally unenforceable, omit Section 6.1')
| 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 a brief example with key clauses would suffice. | 1 / 3 |
Actionability | Provides concrete templates that are copy-paste ready, but they're generic placeholders rather than executable guidance. Missing specific instructions on how to customize templates for different jurisdictions or situations, and relies heavily on 'consult legal counsel' without actionable customization steps. | 2 / 3 |
Workflow Clarity | No clear workflow for creating employment documents. Missing steps like: assess jurisdiction requirements, select appropriate template, customize required sections, validate compliance. The 'Best Practices' section lists do's and don'ts but provides no sequenced process. | 1 / 3 |
Progressive Disclosure | Monolithic wall of text with three massive templates inline. All content is in one file when templates should be in separate referenced files. External resources are listed but internal content organization is poor. | 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 | |
Table of Contents
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.