Menu

Individual skill

onboard

0upvotes

Onboard a new member onto a project team: the access list, the environment setup verified by a command that actually runs, a map of the codebase by ownership, the team's working agreements, and a first-week plan ending in a real contribution the team reviews. Use when someone joins the project, moves between teams, or returns after a long absence. Triggers on: "onboarding", "onboard", "người mới", "hướng dẫn thành viên mới", "new joiner", "getting started for the team", "オンボーディング", "新メンバー", "ramp up", "/atk:onboard".

plugins/atk/skills/onboard/SKILL.md

Read pinned source

Source commit 55481d2e4ae3cec8e2050c160303c751bbf20173

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
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)
12
Repository last updated
Nov 9, 2026
License
MIT

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

Files and excerpt

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

Browse files
Read excerpt

# Team Onboarding (`atk:onboard`)

Produces the document that gets a new member to a real, reviewed contribution in their first week.
Every setup step is verified against the repository, so the guide does not send a new joiner to a
script that no longer exists.

## Scope

Handles: deriving setup from the actual repository, listing access and accounts with who grants
them, mapping the codebase by area and owner, recording team working agreements, and building a
first-week plan with a real starter task.

Does NOT handle: granting access, writing the conventions themselves (`atk:convention`), setting the
project up for the kit (`atk:init`, which runs once per project rather than once per joiner), or
Back to top