Employee Handbook Builder Skill for Claude

Build or modernize an employee handbook for a small business with no HR department -- interviews the owner for actual practices, drafts every core policy in plain English, flags the state-specific requirements that need local verification, and outputs a document employees might actually read.

943 tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

235

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/OneWave-AI/claude-skills --skill employee-handbook-builder

The instruction itself

4 sections, as written by the author

Employee Handbook Builder

Most small businesses run on unwritten rules until the first dispute, and then the absence of a handbook costs real money. Build one that documents how the business actually runs -- in plain English, not borrowed legalese -- and flag every spot where state law has an opinion. Drafting support, not legal advice: the deliverable is a strong draft for an employment attorney's review, which costs far less than having them write it from scratch.

Workflow

Interview. Ask what is actually true, section by section: employment basics (at-will status, classifications, probation practice), pay (schedule, overtime handling, timekeeping), time off (PTO or separate sick/vacation, accrual, carryover, holidays), conduct (attendance, dress, phone/social media, remote rules), benefits actually offered, discipline practice, and how people leave (notice, final pay, references). Accept an existing outdated handbook or scattered policy docs as input to mine.
Draft in plain English. Second person, short sentences, real examples over abstractions ("If you're going to be late, text your manager before your shift starts"). Every policy states what, why, and what happens if not. Required backbone sections included: EEO/anti-discrimination, anti-harassment with a reporting path that has two routes (never only "tell your manager" -- the manager may be the problem), safety, leave, and the at-will + not-a-contract disclaimers with the acknowledgment page.
Flag the jurisdiction layer. For the user's state(s): mark every section where state/local law commonly varies -- sick-leave mandates, final-paycheck timing, meal/rest breaks, pay-transparency, marijuana policy, non-compete enforceability, required postings -- as [STATE CHECK: what to verify]. Web-search the current landscape to make flags specific, but the flag says "verify with counsel/your state DOL," never "this is the law."
Consistency pass. The handbook must match reality: policies the owner admitted are not enforced get rewritten to what is enforced or removed -- a written policy the business ignores is a liability in disputes, worse than no policy.
Deliver. employee-handbook.md (hand to docx for the formatted document), the acknowledgment form, a one-page summary of the ten policies employees actually ask about, and the attorney-review punch list -- every [STATE CHECK] item collected with section references.

Rules

Never present the draft as legally sufficient. The attorney-review framing appears in the deliverable itself, not just the conversation.
Document the real business, not the aspirational one -- unenforced policies are landmines.
Plain English is a compliance feature: a handbook nobody reads protects nobody.
The anti-harassment reporting path always has at least two routes.
No policy theater: skip the 40 pages of borrowed corporate boilerplate; a 15-page handbook that fits the business beats a 60-page template.
Multi-state teams get the flag treatment per state, and remote employees count as their own state.

Quick Commands

"Build my handbook" -- full interview and draft
"Modernize [existing handbook]" -- gap analysis and rewrite
"Just the must-haves" -- the required-backbone minimum viable handbook
"What needs a lawyer?" -- the punch list from an existing draft

Other skills for the same job

different authors, same section of the catalogue

DOCX

by anthropics

vendor ×16

Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. When Claude needs to work with professional documents (.docx files) for: (1) Creating new documents, (2) Modifying or editing content, (3) Working with tracked changes, (4) Adding comments, or any other document tasks

Comprehensive PDF manipulation toolkit for extracting text and tables, creating new PDFs, merging/splitting documents, and handling forms. When Claude needs to fill in a PDF form or programmatically process, generate, or analyze PDF documents at scale.

Presentation creation, editing, and analysis. When Claude needs to work with presentations (.pptx files) for: (1) Creating new presentations, (2) Modifying or editing content, (3) Working with layouts, (4) Adding comments or speaker notes, or any other presentation tasks

Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.

Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.

Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.

Use this skill any time a .pptx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates, layouts, speaker notes, or comments. Trigger whenever the user mentions \"deck,\" \"slides,\" \"presentation,\" or references a .pptx filename, regardless of what they plan to do with the content afterward. If a .pptx file needs to be opened, created, or touched, use this skill.

Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax. Use when working with .md files in Obsidian, or when the user mentions wikilinks, callouts, frontmatter, tags, embeds, or Obsidian notes.

3k tokens

How to use it

Copy the folder

Take onewave-ai/employee-handbook-builder from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.