Skip to main content
AI/MLsickn33

employment-contract-templates

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

Stars
39,227
Source
sickn33/antigravity-awesome-skills
Updated
2026-05-30
Slug
sickn33--antigravity-awesome-skills--employment-contract-templates
View on GitHubRaw SKILL.md

// install — copy + paste into any project

mkdir -p .claude/skills && curl -fsSL https://raw.githubusercontent.com/sickn33/antigravity-awesome-skills/HEAD/plugins/antigravity-awesome-skills-claude/skills/employment-contract-templates/SKILL.md -o .claude/skills/employment-contract-templates.md

Drops the SKILL.md into .claude/skills/employment-contract-templates.md. Works with Claude Code, Cursor, and any agent that loads SKILL.md files from .claude/skills/.

Employment Contract Templates

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

Use this skill when

  • Drafting employment contracts
  • Creating offer letters
  • Writing employee handbooks
  • Developing HR policies
  • Standardizing employment documentation
  • Preparing onboarding documentation

Do not use this skill when

  • You need jurisdiction-specific legal advice
  • The task requires licensed counsel review
  • The request is unrelated to employment documentation

Instructions

  • Confirm jurisdiction, employment type, and required clauses.
  • Choose a document template and tailor role-specific terms.
  • Validate compensation, benefits, and compliance requirements.
  • Add signature, confidentiality, and IP assignment terms as needed.
  • If detailed templates are required, open resources/implementation-playbook.md.

Safety

  • These templates are not legal advice; consult qualified counsel before use.

Resources

  • resources/implementation-playbook.md for detailed templates and checklists.

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.