employment-contract-templates

Templates and patterns for creating legally sound employment documentation including contracts, offer letters, and HR policies.

Quality

59%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/employment-contract-templates/SKILL.md

The canonical home for this skill is employment-contract-templates in rmyndharis/antigravity-skills

Quality

Content

57%Weight 40%Scale 1-5

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

The skill body is well-organized and concise with a sensible workflow and good use/do-not-use boundaries, but its actionability and progressive disclosure are undermined because the referenced playbook file is missing and the workflow lacks explicit validation feedback loops.

Suggestions

Create the referenced `resources/implementation-playbook.md` (or correct the path) so the deferred templates and checklists actually exist.

Add an explicit validation feedback loop in the workflow (e.g., 'If compliance validation fails, revise the flagged clauses and re-validate').

Remove the verbatim duplication of the description as the body's opening line to tighten token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence with no padding or concept re-explanation; the only trim candidate is the opening line that duplicates the frontmatter description verbatim.	4 / 5
Actionability	The Instructions give concrete, sequenced guidance (confirm jurisdiction, choose template, validate compensation, add signature terms) but defer the actual templates to a referenced file, leaving key details incomplete.	3 / 5
Workflow Clarity	A clear sequence is present and includes one validation step ('Validate compensation, benefits, and compliance requirements'), but checkpoints are implicit with no feedback loop for what to do when validation fails.	3 / 5
Progressive Disclosure	Structure is clean with a one-level reference to `resources/implementation-playbook.md` clearly signaled in both Instructions and Resources, but the referenced file does not exist in the bundle, so navigation is broken.	3 / 5
	Total	13 / 20 Passed

Description

61%Weight 40%Scale 1-5

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 clearly identifies the domain and document types but lacks an explicit 'when to use' trigger clause, which caps completeness. It is concise and reasonably distinct but would benefit from explicit trigger phrasing.

Suggestions

Add a 'Use when...' clause with concrete trigger phrases (e.g., 'Use when drafting employment contracts, offer letters, or HR policies').

Replace the generic verb 'creating' with several specific actions (e.g., 'draft, review, and standardize') to lift specificity.

Include common synonyms or file extensions users might mention to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('employment documentation') and lists concrete document types ('contracts, offer letters, and HR policies'), but the only action verb is the generic 'creating', so coverage of actions is not comprehensive.	3 / 5
Completeness	It clearly states what the skill does but has no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Includes natural phrases users would say ('employment contracts', 'offer letters', 'HR policies'), giving good keyword coverage, though common synonyms and file extensions are absent.	4 / 5
Distinctiveness Conflict Risk	It carves a clear niche (employment documentation) that is mostly distinct, with only minor overlap risk against general legal/document drafting skills; the missing explicit triggers keep it just below 5.	4 / 5
	Total	14 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills/skills/employment-contract-templates/SKILL.md
Commit: 57c135b

Reviewed: 3 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.