A new hire’s first week is expensive when answers are scattered. One person asks IT for logins, another asks a busy manager for the same checklist, and a third guesses how a task should be done. The result is slow starts, repeated questions, and small mistakes that could have been avoided with one clear source of truth.
An agent skill can turn that scattered onboarding material into a reusable assistant. Anthropic describes Agent Skills as folders of instructions, scripts, and resources that an agent discovers and loads when they are relevant to a task. For onboarding, that folder can hold your checklists, standard operating procedures, tool login guidance, first-week tasks, and frequently asked questions, so a new hire gets the same approved answer every time.
This tutorial shows you how to build a small, safe onboarding skill for a small business. You do not need to be a developer. You need one approved set of onboarding documents, a named owner for updates, and a test run before the skill reaches a real new hire.
Before you start
Gather these items before you write anything. Start with the approved onboarding checklist, the standard operating procedures for the new hire’s first tasks, and a list of tools the role actually uses. Add the name of the person who approves each document, and note which documents are already out of date. If a procedure is disputed, leave it out until the owner confirms it.
- Approved checklist: The tasks a new hire must complete in week one.
- Current procedures: Short, step-by-step guides for the first real tasks.
- Tool list: Every tool the role uses, with its official help page.
- One owner: A named person who reviews the skill each month.
- No secrets: No passwords, tokens, or private keys in the skill.
Step 1: Collect the onboarding material
Start by collecting the material new hires actually ask about. Ask recent hires which questions they asked most in week one, and ask managers which tasks took longest to explain. Put the answers in one folder, and remove duplicates, expired links, and drafts that nobody approved.
Step 2: Write the SKILL.md file
Create one folder for the skill and add a SKILL.md file inside it. Anthropic’s documentation explains that a skill’s name and description go in the frontmatter of that file, and the description is what helps an agent decide when the skill is relevant. Write a short description that names the audience and the job, for example: onboarding help for new hires in a small business. Tell the agent to use the approved checklists first, to ask for missing information instead of guessing, and to point to the source document for each answer.
Step 3: Package checklists and procedures
Turn each approved document into a short checklist the agent can follow in order. Break long procedures into numbered steps, name the tool for each step, and state what a finished task looks like. Keep the language plain, and keep each step to one action. If a procedure needs a screenshot or a template, add it as a resource file in the same skill folder and refer to it by name. This keeps the skill self-contained, so the agent does not have to search the whole company drive for a missing file.
Step 4: Add safe tool login guidance
New hires lose the most time on tool access, so give clear login guidance without ever putting secrets in the skill. For each tool, list its purpose, its official sign-in page, and who to contact if access is missing. Explain the order in which accounts are created, and what a new hire should do if an invitation has not arrived. Point people to your password manager or IT process for actual credentials, and never paste a password, token, or shared login into SKILL.md or any resource file.
Step 5: Build the first-week task plan
Add a day-by-day plan for week one, with one clear outcome for each day. Day one can cover introductions, account checks, and reading the core checklist. Later days can add one real task at a time, each with a reviewer and a place to ask questions. End each day with a short check: what was completed, what is still blocked, and what happens next. This structure helps a manager see progress without hovering, and it helps a new hire know when a task is truly finished.
Step 6: Add FAQs from real questions
Collect the questions new hires actually ask, and answer each one in two or three sentences with a link or reference to the source document. Cover start times, dress code or remote working rules, who to contact for IT help, how to request time off, and where completed work is stored. Do not invent an answer when the source is unclear. Write that the agent should say so and name the person who can confirm it. A short, honest answer builds trust faster than a confident guess.
Step 7: Test, audit, and share the skill
Before a real new hire uses the skill, test it with a fake employee scenario. Ask it the ten most common questions, follow one checklist end to end, and check every answer against the approved source documents. Fix anything that is vague, outdated, or missing a source. Then run a short safety check: confirm the skill contains no secrets, no customer data, and no permission it does not need. Read our guide that explains how to audit an agent skill before your team uses it. Then add the finished skill to your small business skill library so everyone uses the same version.
Tips for small teams
- Keep it short: If a checklist is longer than one screen, split it into smaller tasks.
- Name one owner: One person should approve changes and review the skill each month.
- Update on change: When a tool or procedure changes, update the skill the same week and test it again.
Frequently asked questions
Do new hires need to use Claude to benefit from an onboarding skill?
The skill format described here follows Anthropic’s Agent Skills documentation, so the team needs an agent that supports skills to run it as a skill. Even without that setup, the same checklists, procedures, and FAQs remain useful as a shared onboarding document, because the value starts with approved, organised content.
Should an onboarding skill contain passwords or login details?
No. Keep credentials in your password manager or IT process, and use the skill only to explain which tool to open, what access to request, and who to contact. If you find a secret in a skill file, remove it at once and change the credential.
How long does a first onboarding skill take to build?
As an editorial estimate, a small team can build a useful first version in one focused afternoon if the approved documents already exist. Allow extra time for testing, because checking answers against source documents is what makes the skill safe to share.
Sources
Source: Anthropic, Agent Skills.



