How do I install the Onboard skill?

Run npx skillmds@latest add tranhieutt/onboard in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Onboard skill do?

--- It is listed under Coding & Dev Tools on SkillMD.

Is Onboard safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Onboard?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Onboard free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Onboard?

tranhieutt (@tranhieutt) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Onboard by tranhieutt — Agent Skill

Name: Onboard
Author: tranhieutt

File contents

--- name: onboard type: workflow description: "Generates a contextual onboarding document for a new contributor or agent joining the project, summarizing architecture, conventions, and current priorities. Use when onboarding a new team member, contributor, or agent." argument-hint: "[role|area]" user-invocable: true allowed-tools: Read, Glob, Grep, Write effort: 3 when_to_use: "When onboarding a new contributor or agent to the project for a specific role or area"

When this skill is invoked:

Read the CLAUDE.md for project overview and standards.
Read the relevant agent definition from .claude/agents/ if a specific role is specified.
Scan the codebase for the relevant area:
- For programmers: scan src/ for architecture, patterns, key files
- For designers: scan design/ for existing design documents
- For narrative: scan design/narrative/ for world-building and story docs
- For QA: scan tests/ for existing test coverage
- For production: scan production/ for current sprint and milestone
Read recent changes (git log if available) to understand current momentum.
Generate the onboarding document:

# Onboarding: [Role/Area]

## Project Summary
[2-3 sentence summary of what this product is and its current state]

## Your Role
[What this role does on this project, key responsibilities, who you report to]

## Project Architecture
[Relevant architectural overview for this role]

### Key Directories
| Directory | Contents | Your Interaction |
|-----------|----------|-----------------|

### Key Files
| File | Purpose | Read Priority |
|------|---------|--------------|

## Current Standards and Conventions
[Summary of conventions relevant to this role from CLAUDE.md and agent definition]

## Current State of Your Area
[What has been built, what is in progress, what is planned next]

## Current Sprint Context
[What the team is working on now and what is expected of this role]

## Key Dependencies
[What other roles/systems this role interacts with most]

## Common Pitfalls
[Things that trip up new contributors in this area]

## First Tasks
[Suggested first tasks to get oriented and productive]

1. [Read these documents first]
2. [Review this code/content]
3. [Start with this small task]

## Questions to Ask
[Questions the new contributor should ask to get fully oriented]

---name: onboarddescription: ---------name: onboardtype: workflowdescription: "Generates a contextual onboarding document for a new contributor or agent joining the project, summarizing architecture, conventions, and current priorities. Use when onboarding a new team member, contributor, or agent."argument-hint: "[role|area]"user-invocable: trueallowed-tools: Read, Glob, Grep, Writeeffort: 3when_to_use: "When onboarding a new contributor or agent to the project for a specific role or area"---When this skill is invoked:1. **Read the CLAUDE.md** for project overview and standards.2. **Read the relevant agent definition** from `.claude/agents/` if a specific role is specified.3. **Scan the codebase** for the relevant area: - For programmers: scan `src/` for architecture, patterns, key files - For designers: scan `design/` for existing design documents - For narrative: scan `design/narrative/` for world-building and story docs - For QA: scan `tests/` for existing test coverage - For production: scan `production/` for current sprint and milestone4. **Read recent changes** (git log if available) to understand current momentum.5. **Generate the onboarding document**:```markdown# Onboarding: [Role/Area]## Project Summary[2-3 sentence summary of what this product is and its current state]## Your Role[What this role does on this project, key responsibilities, who you report to]## Project Architecture[Relevant architectural overview for this role]### Key Directories| Directory | Contents | Your Interaction ||-----------|----------|-----------------|### Key Files| File | Purpose | Read Priority ||------|---------|--------------|## Current Standards and Conventions[Summary of conventions relevant to this role from CLAUDE.md and agent definition]## Current State of Your Area[What has been built, what is in progress, what is planned next]## Current Sprint Context[What the team is working on now and what is expected of this role]## Key Dependencies[What other roles/systems this role interacts with most]## Common Pitfalls[Things that trip up new contributors in this area]## First Tasks[Suggested first tasks to get oriented and productive]1. [Read these documents first]2. [Review this code/content]3. [Start with this small task]## Questions to Ask[Questions the new contributor should ask to get fully oriented]```

Frequently asked questions

Onboard