CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

87

1.04x
Quality

Does it follow best practices?

Impact

96%

1.04x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill delivers highly actionable, copy-paste-ready templates but is verbose and monolithic, inlining full templates and concepts Claude already knows. It lacks an explicit drafting/review workflow for a legally sensitive domain.

Suggestions

Move the three full templates into separate reference files (e.g., references/offer-letter.md, references/employment-agreement.md, references/handbook-policy.md) and keep SKILL.md as a concise overview with one-level-deep links, improving both conciseness and progressive disclosure.

Remove or shrink the Core Concepts ASCII tree explaining At-Will vs. Contract and Employee vs. Contractor, which restates knowledge Claude already has; replace with a pointer only if jurisdiction-specific nuance is needed.

Add a short multi-step drafting workflow with a validation checkpoint — e.g., select template → fill placeholders → confirm jurisdiction-specific requirements and at-will language → have legal counsel review before use.

DimensionReasoningScore

Conciseness

The ~520-line body inlines three full templates and includes a Core Concepts tree (At-Will vs. Contract, Employee vs. Contractor) that Claude already knows; valuable but could be tightened. Not a 3 because of the redundant explanatory scaffolding and verbatim boilerplate.

2 / 3

Actionability

Provides complete, copy-paste-ready templates with placeholders, a worked PTO accrual table, and concrete cause-for-termination definitions — fully actionable guidance. Not a 2 because it is not pseudocode or vague.

3 / 3

Workflow Clarity

Structure and document types are present, but there is no multi-step drafting workflow or validation/review checkpoint for legally sensitive documents. Capped at 2 because the missing review-before-finalize feedback loop matters in this domain.

2 / 3

Progressive Disclosure

A single monolithic SKILL.md with no bundle files inlines all three full templates instead of splitting them into one-level-deep references. Sections are organized (not level 1) but content that should be separate is inline.

2 / 3

Total

9

/

12

Passed

Description

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.

The description is specific, trigger-rich, and complete with explicit when-to-use guidance, hitting the top anchor on every dimension. It is concise and clearly distinguishes the skill's niche.

DimensionReasoningScore

Specificity

Names multiple concrete actions and deliverables — "employment contracts, offer letters, and HR policy documents" — matching the anchor for listing several specific actions rather than a single domain-plus-action.

3 / 3

Completeness

Explicitly answers both what (create contracts/offer letters/HR policy docs) and when via a clear "Use when drafting..." clause, satisfying the top anchor.

3 / 3

Trigger Term Quality

Covers natural phrasings a user would say ("employment contracts", "offer letters", "drafting employment agreements", "creating HR policies", "standardizing employment documentation") with good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

Occupies a distinct employment-documentation niche with specific triggers and third-person voice, making it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (528 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository
Dicklesworthstone/pi_agent_rust
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.