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.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

57%

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

The body is a well-organized overview with clean progressive disclosure to a real reference file, but it is light on concrete in-line guidance and lacks an explicit drafting workflow with validation steps for a legally sensitive task.

Suggestions

Remove or condense the 'When to Use This Skill' list since those triggers already appear verbatim in the description, freeing the body for more concrete drafting guidance.

Add a short sequenced drafting workflow (e.g., select document type -> pull template from references/details.md -> customize jurisdiction-specific clauses -> legal review) with an explicit validation/review checkpoint before use.

Move at least one compact, copy-ready template excerpt inline so the body is actionable without requiring the reference file, while keeping the full library in references/details.md.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient, but the 'When to Use This Skill' list and the opening sentence restate triggers already in the description, and could be tightened to avoid redundant tokens.	2 / 3
Actionability	The document-type table, legal-considerations tree, and do/don't list give some concrete guidance, but the actual executable templates are deferred to references/details.md and the inline guidance ('Be clear and specific', 'Don't make promises') stays fairly abstract.	2 / 3
Workflow Clarity	Content is organized into labeled sections, but there is no sequenced drafting workflow and no validation/review checkpoint for a consequential legal-document task, so it does not reach the top anchor.	2 / 3
Progressive Disclosure	The body is a concise overview that clearly signals a single one-level-deep reference ('Full template library and detailed worked examples live in references/details.md'), and that referenced file exists, matching the top anchor.	3 / 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 concise, third-person, and clearly states both capabilities and explicit trigger conditions. It lists concrete actions and natural trigger terms with minimal risk of skill conflict.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('Create employment contracts, offer letters, and HR policy documents following legal best practices') rather than vague language, matching the top anchor.	3 / 3
Completeness	Explicitly answers both what ('Create employment contracts, offer letters, and HR policy documents') and when ('Use when drafting employment agreements, creating HR policies, or standardizing employment documentation') with an explicit trigger clause.	3 / 3
Trigger Term Quality	Covers natural terms users would say — 'employment contracts', 'offer letters', 'HR policies', 'employment agreements', 'employment documentation' — with good variation rather than jargon.	3 / 3
Distinctiveness Conflict Risk	Targets a clear niche (employment/HR documentation) with distinct triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: wshobson/agents
Commit: 5cc2549

Reviewed: 10 days ago

Table of Contents

Discovery Implementation Validation

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.