employment-contract-templates

Overview of employment-contract-templates skill

What employment-contract-templates does

The employment-contract-templates skill helps generate first-draft employment documents such as offer letters, employment contracts, employee handbooks, NDAs, non-competes, and onboarding policy language. Its value is not just “write a contract,” but giving an AI agent a structured legal-document drafting frame instead of relying on a generic prompt.

Who this skill is best for

This skill is best for HR, legal ops, founders, people teams, and operators who need a faster starting point for routine employment documentation. It is especially useful when you want consistency across recurring documents, need to adapt a draft for a specific role or employment type, or want an agent to cover common sections you might forget in an ad hoc prompt.

Real job-to-be-done

Most users are not looking for abstract legal theory. They want a usable first draft that reflects the employment relationship, document type, and practical constraints of hiring: jurisdiction, employee classification, compensation structure, confidentiality, termination terms, and policy alignment. The employment-contract-templates skill is most valuable when speed and completeness matter, but legal review still happens before use.

What makes it different from a normal prompt

A normal prompt often produces a plausible-looking contract that misses key distinctions such as at-will vs. fixed term, employee vs. contractor, exempt vs. non-exempt, or whether an offer letter is more appropriate than a full employment agreement. This employment-contract-templates skill is centered on those document choices and legal framing points, which reduces guesswork at the start.

Important adoption caveat

This skill is a drafting aid, not a law firm. It does not replace jurisdiction-specific legal review, and that limitation matters more here than in many other skills. If your team needs enforceable production-ready employment documents across multiple states or countries, treat the output as a reviewable draft, not final legal advice.

How to Use employment-contract-templates skill

Install context for employment-contract-templates

Install the skill from the wshobson/agents repository into your agent environment:

npx skills add https://github.com/wshobson/agents --skill employment-contract-templates

Because this skill appears to be delivered mainly through SKILL.md, you should expect prompt-guided usage rather than helper scripts or structured support files.

Read this file first

Start with:

• plugins/hr-legal-compliance/skills/employment-contract-templates/SKILL.md

That file contains the main logic: when to use the skill, document types, and the legal distinctions the agent should consider before drafting.

Know what the skill needs as input

The quality of employment-contract-templates usage depends heavily on the facts you provide. At minimum, give the agent:

• document type needed
• jurisdiction
• role title and duties
• employee classification
• compensation terms
• start date and term length
• at-will or fixed-term status
• confidentiality or IP requirements
• termination expectations
• company policy constraints

If you omit these, the agent will fill gaps with generic language, which is exactly where employment documents become risky or unusable.

Choose the right document before drafting

One of the biggest practical wins from this skill is choosing the right output form first:

• Offer letter for pre-hire summary terms
• Employment contract for a fuller binding agreement
• Employee handbook for policies and procedures
• NDA for confidentiality before access
• Non-compete for restricted post-employment activity where lawful

If your real need is “make hiring paperwork consistent,” the answer may be a document set, not a single contract.

Turn a rough request into a strong prompt

Weak prompt:

“Write an employment contract for a software engineer.”

Stronger prompt:

“Use the employment-contract-templates skill to draft a U.S. employment agreement for a full-time at-will Senior Software Engineer in California. Include salary, bonus eligibility, equity summary placeholder, invention assignment, confidentiality, arbitration placeholder, termination language, and exempt classification assumptions. Flag clauses that require California-specific legal review.”

The stronger version works better because it specifies the relationship type, jurisdiction, role, and review-sensitive clauses.

Prompt pattern that usually works well

A practical employment-contract-templates guide prompt looks like this:

1. identify the document type
2. state the jurisdiction
3. define worker classification and employment status
4. list required business terms
5. specify risky clauses to include or avoid
6. ask the agent to mark review points clearly

Example:

“Use employment-contract-templates for Legal drafting. Create an offer letter plus short-form NDA for a remote part-time marketing manager in New York. Include compensation, expected hours, probationary language if appropriate, confidentiality, return-of-property terms, and a section listing assumptions and clauses for counsel review.”

Suggested workflow for real teams

A practical workflow is:

1. Draft the first version with the skill.
2. Ask the agent to list assumptions and missing facts.
3. Revise the draft with company-specific policies.
4. Run a second pass focused only on legal-risk clauses.
5. Send to counsel or internal legal review.
6. Save the approved version as your future prompt baseline.

This workflow gets more value from the skill than asking for a one-shot “perfect” contract.

What the skill covers well

The skill is strongest when you need a structured starting point for:

• standard employment agreements
• offer documentation
• onboarding documents
• policy drafting
• confidentiality-related employment docs

It is also useful for forcing the agent to think in terms of employment-document categories rather than freeform prose generation.

What it does not solve by itself

The employment-contract-templates install decision should be easy if you understand its limits. It does not appear to include:

• jurisdiction-specific clause libraries
• automated compliance checks
• file-based policy references
• negotiation playbooks
• executable review scripts

So if you need deeply localized legal drafting, this skill is a framework, not a complete compliance system.

Practical tips that improve output quality

Ask the agent to do all of the following in one response:

• draft the document
• list assumptions
• flag legally sensitive clauses
• identify missing inputs
• provide optional variants for high-risk sections

That gives you a usable draft and an issue list at the same time, which is much more decision-useful than polished but unqualified text.

employment-contract-templates skill FAQ

Is employment-contract-templates good for beginners?

Yes, if your goal is to create a better first draft than a blank page or generic chatbot prompt. No, if you expect beginner-safe legal finalization. Beginners benefit most when they use the skill to organize document requirements and then route outputs to experienced HR or legal reviewers.

When should I use this instead of a generic legal prompt?

Use employment-contract-templates skill when document type and employment classification matter. A generic prompt may produce smooth language, but this skill is better aligned to common employment-document categories and the legal distinctions that shape them.

Is employment-contract-templates for Legal teams only?

No. employment-contract-templates for Legal is a strong fit, but HR, founders, recruiters, and operations teams can also use it to prepare structured drafts for review. It is especially helpful where non-lawyers need to gather complete inputs before sending a document to counsel.

Can it draft policies as well as contracts?

Yes. The source scope explicitly covers HR policy documents and employee handbook-style materials, not just contracts. That makes it useful when you need onboarding or standards documentation alongside individual employment agreements.

Does the skill handle jurisdiction-specific law?

Only partially. It surfaces that jurisdiction matters, but it does not replace local legal expertise. If your use case depends on state, national, or industry-specific enforceability, ask the agent to flag review points and treat those sections as provisional.

When is this skill a poor fit?

Skip it if you need:

• signed-ready legal documents without review
• complex multinational employment packages
• heavily negotiated executive agreements
• automated compliance validation
• a maintained clause database with local law coverage

In those cases, the skill can still help with first drafts, but it should not be your main system.

How to Improve employment-contract-templates skill

Give better factual inputs, not longer prompts

The fastest way to improve employment-contract-templates results is to provide complete hiring facts instead of broad instructions. A short prompt with role, jurisdiction, classification, pay structure, and policy constraints usually outperforms a long but vague request.

Ask the agent to separate assumptions from final text

A common failure mode is hidden assumptions. Prevent that by explicitly asking for:

• draft text
• assumptions list
• unresolved legal questions
• clauses needing jurisdiction review

This makes review much faster and reduces the chance of approving generic language by accident.

Provide your company standards up front

If your organization already has preferences on IP assignment, confidentiality, notice periods, probation, arbitration, remote work, or handbook alignment, include them before drafting. Otherwise the skill will default to generic patterns that may not match internal policy.

Use clause-level iteration after the first draft

Do not regenerate the whole document unless the structure is wrong. Better results usually come from targeted follow-ups such as:

• “Revise termination to match at-will employment.”
• “Replace non-compete with non-solicit language.”
• “Add manager-level confidentiality and inventions wording.”
• “Shorten the offer letter and move detailed terms to an attached agreement.”

That preserves good sections and improves the risky ones.

Improve employment-contract-templates usage with document bundles

If the hiring workflow involves more than one artifact, ask for a coordinated set: for example, offer letter plus NDA plus onboarding acknowledgments. This reduces inconsistent terms across separately generated documents.

Watch for the main quality risks

The biggest issues to catch in employment-contract-templates guide outputs are:

• wrong document type
• unclear worker classification
• missing jurisdiction assumptions
• overconfident legal language
• unenforceable restrictive covenants
• policy terms that conflict with the handbook
• compensation language that is too vague to operationalize

These are more important than style polishing.

Build a reusable intake template

If your team will use the skill often, create a standard intake form with fields for jurisdiction, role, classification, compensation, start date, manager, work location, confidentiality level, IP sensitivity, and termination assumptions. Reusing the same intake structure will improve consistency more than changing wording from prompt to prompt.

Pair the skill with legal review deliberately

The best long-term use of employment-contract-templates skill is as a drafting accelerator plus review prep tool. Ask the agent to produce a “counsel review summary” after each draft, including what changed, what assumptions remain, and which clauses deserve local-law review. That turns the skill from a text generator into a more reliable legal drafting workflow.