Skip to main content
Agent skill

Hr Onboarding

A new-hire onboarding plan as a single page — first week schedule, buddy + manager intro, learning track, equipment checklist, and "you're set when…" outcomes. Use when the brief mentions "onboarding", "new hire", "first week plan", or "入职".

Get started

Get the complete skill folder, including its scripts and reference files.

When to use this skill

Use Hr Onboarding when an AI agent needs a reusable SKILL.md workflow for this job: A new-hire onboarding plan as a single page — first week schedule, buddy + manager intro, learning track, equipment checklist, and "you're set when…" outcomes. Use when the brief mentions "onboarding", "new hire", "first week plan", or "入职".

When not to use it

Skip Hr Onboarding when the task is outside the creativity category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.

How to install

Where will you use it?

Install scope
Claude Code folder setup
mkdir -p ~/.claude/skills/hr-onboarding
# Save SKILL.md to ~/.claude/skills/hr-onboarding/SKILL.md
  1. Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/hr-onboarding/SKILL.md. For a shared project, commit the folder at .claude/skills/hr-onboarding/ instead.
  2. Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
  3. For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.

Full install guide for Claude, Cursor, and Codex →

Try a starter prompt

After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.

Starter prompt
Use the Hr Onboarding skill for this task: Read the active DESIGN.md. Confirm any required inputs or files before making changes.

What supports this recommendation?

74/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.

Documentation
82/100
Practical detail
74/100
Source evidence
63/100
Source signals
70/100
Model compatibility evidence
  • claudeuntested

    No model-specific signal or recorded compatibility test was found.

  • chatgptuntested

    No model-specific signal or recorded compatibility test was found.

  • geminiuntested

    No model-specific signal or recorded compatibility test was found.

  • copilotuntested

    No model-specific signal or recorded compatibility test was found.

  • llamauntested

    No model-specific signal or recorded compatibility test was found.

  • perplexityuntested

    No model-specific signal or recorded compatibility test was found.

  • mistraluntested

    No model-specific signal or recorded compatibility test was found.

  • grokuntested

    No model-specific signal or recorded compatibility test was found.

Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.

What this skill does

# HR Onboarding Skill

Produce a single-screen onboarding plan in HTML.

## Workflow

1. Read the active DESIGN.md. 2. Identify the role + tenure expectations from the brief. Default to a 30/60/90-day shape if unspecified. 3. Layout: - Cover banner: name placeholder, role, start date, manager + buddy. - "Day 1" panel with the literal schedule (kickoff time, lunch, 1:1 slot). - First-week timeline (Mon → Fri, two activities per day). - 30 / 60 / 90 day milestone cards with three concrete outcomes each. - Resource list: handbook, Slack channels, key dashboards, payroll setup. - "You're set when…" checklist — five outcomes with checkboxes. 4. Single inline `<style>`, semantic HTML.

## Output contract

``` <artifact identifier="onboarding-plan" type="text/html" title="Onboarding Plan"> <!doctype html>...</artifact> ```

Intended uses

  • Read the active DESIGN.md.
  • Identify the role + tenure expectations from the brief. Default to a
  • Layout:
  • Cover banner: name placeholder, role, start date, manager + buddy.
  • "Day 1" panel with the literal schedule (kickoff time, lunch, 1:1 slot).
  • First-week timeline (Mon → Fri, two activities per day).
  • 30 / 60 / 90 day milestone cards with three concrete outcomes each.
  • Resource list: handbook, Slack channels, key dashboards, payroll setup.
  • "You're set when…" checklist — five outcomes with checkboxes.
  • Single inline <style>, semantic HTML.

Implementation notes

  • Review the source instructions and adapt inputs before running the workflow.

Try it, then tell us how it went

A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.