Antigravity-awesome-skills employment-contract-templates

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

install
source · Clone the upstream repo
git clone https://github.com/sickn33/antigravity-awesome-skills
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/sickn33/antigravity-awesome-skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/plugins/antigravity-awesome-skills/skills/employment-contract-templates" ~/.claude/skills/sickn33-antigravity-awesome-skills-employment-contract-templates-092f88 && rm -rf "$T"
manifest: plugins/antigravity-awesome-skills/skills/employment-contract-templates/SKILL.md
source content

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.