Individual skill

onboarding-buddy

Builds a dated first-fortnight plan for a new joiner from the team's own documents, meetings and systems, naming who they meet and what they read on which day. Use when the user asks to plan an onboarding, prepare for a new starter, build a first-week plan, or says someone is joining the team.

packs/people-hr/onboarding-buddy/skill/SKILL.md

Read pinned source

Source commit d10af7a3e2da1bdc54d72e6a4af870c2e1212464

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Not checked yet
Last checked: Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 18
Repository last updated: Nov 5, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

agent-skills Repository topic
ai-governance Repository topic
copilot Repository topic
copilot-cowork Repository topic
cowork Repository topic
m365 Repository topic
microsoft-365-copilot Repository topic
microsoft365 Repository topic
skill-md Repository topic
engineering Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 2,709 bytes
references/config.mddoc · 344 bytes

Read excerpt


# Onboarding Buddy

Turns "they start Monday" into a dated plan built from what the team actually has.

## Inputs
- **Enterprise Search** for the team's existing material: handbooks, architecture notes, runbooks
- **Calendar Management** for who is available in the first fortnight
- `references/config.md` for the role templates and the standing first-week items

## Procedure
1. **Establish** the start date, the role and the team. Missing any of these, ask once and stop.
2. **Find the real material.** Search for what this team has written: onboarding notes, decision
   records, runbooks, recent all-hands. Record what exists and, importantly, what does not.
3. **Find the people** the role should meet, evidenced by who owns the systems and documents the