onboard

Name: onboard
Author: tobihagemann

3installs29forks

How to install onboard?

tobihagemann/turbo/onboard

$npx -y skills add tobihagemann/turbo --skill onboard

Installs into the current project.

Summary

Developer onboarding guide that composes architecture mapping, tooling review, and agentic setup review with setup, troubleshooting, and next-steps agents to produce a comprehensive guide at .turbo/onboarding.md and .turbo/onboarding.html. Use when the user asks to \"onboard me\"

Files · 1

View on GitHub

SKILL.md

1	# Onboard
2
3	Developer onboarding pipeline. Composes `/map-codebase`, `/review-tooling`, and `/review-agentic-setup` with inline agents, then synthesizes everything into `.turbo/onboarding.md` and `.turbo/onboarding.html`. Analysis-only.
4
5	## Task Tracking
6
7	At the start, use `TaskCreate` to create a task for each phase:
8
9	1. Launch all agents
10	2. Synthesize and generate markdown report
11	3. Generate HTML report
12
13	## Step 1: Launch All Agents
14
15	Use the Agent tool to launch all 6 agents below in a single assistant message so they run concurrently. Run them in the foreground so all their results return in this turn. Each Agent call uses `model: "opus"`. Each Composed Skills agent invokes its assigned skill via the Skill tool; each Inline Agent follows its exploration brief directly.
16
17	### Composed Skills
18
19	Launch one Agent tool call per row. Each agent's prompt instructs it to invoke its assigned skill via the Skill tool.
20
21	\| Skill \| Onboarding role \|
22	\|---\|---\|
23	\| `/map-codebase` \| Architecture understanding: structure, tech stack, entry points, patterns, data flow, dependencies, testing \|
24	\| `/review-tooling` \| Development workflow: linters, formatters, pre-commit hooks, test runners, CI/CD \|
25	\| `/review-agentic-setup` \| Agentic coding: CLAUDE.md, AGENTS.md, skills, MCP servers, hooks, cross-tool compatibility \|
26
27	### Inline Agents
28
29	Launch one Agent tool call each with the exploration brief below.
30
31	\| Agent \| Exploration Brief \|
32	\|---\|---\|
33	\| Prerequisites and Setup \| Read README.md, CONTRIBUTING.md, and package manager configs (package.json, Gemfile, Cargo.toml, go.mod, pyproject.toml, Package.swift, etc.). Extract: required language runtimes and versions, system dependencies, environment variables, database or service requirements, first-time setup steps (install, build, run, seed), and any bootstrap or setup scripts. \|
34	\| Troubleshooting \| Search for troubleshooting content in README.md, TROUBLESHOOTING.md, docs/ directory, FAQ files, and GitHub Discussions/Wiki if accessible. Extract common errors, known quirks, platform-specific gotchas, and debugging tips. If no troubleshooting docs exist, report that. \|
35	\| Next Steps \| Run `gh issue list --state open --json number,title,url,reactionGroups,comments,labels --limit 50`. Identify: (1) issues labeled `good-first-issue` or `good first issue`, (2) top 5 issues by engagement score (sum of reactions weighted 2x for thumbs-up, plus comment count). If `gh` is not available or not in a GitHub repo, skip and note that. \|
36
37	Each agent writes its findings as structured markdown.
38
39	## Step 2: Synthesize and Generate Markdown Report
40
41	After all agents complete:
42
43	1. Read all agent reports. Check if `.turbo/threat-model.md` exists; if so, read it for the Security Considerations section.
44	2. Reframe review skill outputs as documentation. `/review-tooling` findings become "Development Workflow" (what tools are used and how to run them). `/review-agentic-setup` findings become "AI-Assisted Development" (what's set up and how to use it). Focus on what exists, not what's missing. Strip severity labels, findings numbering, and gap framing from review skill outputs. Present detected tools and configurations as project conventions the new developer should know.
45	3. Write a brief welcome summary (3-5 sentences) capturing what the project is, who it's for, and the fastest path to a first contribution.
46	4. Write `.turbo/onboarding.md` using the report template. Output the welcome summary as text before writing the file.
47
48	### Report Template
49
50	```markdown
51	# Onboarding Guide
52
53	Date: <date>
54	Project: <project name>
55
56	## Welcome
57
58	<3-5 sentences: what this project is, who it's for, fastest path to a first contribution>
59
60	## Prerequisites and Setup
61
62	<from Prerequisites and Setup agent: language runtimes, dependencies, first-time setup steps, build/run commands>
63
64	## Architecture Overview
65
66	<from /map-codebase: condensed executive summary and key structural insights — not the full report, which lives at .turbo/codebase-map.md>
67
68	## Development Workflow
69
70	<from /review-tooling: reframed as "how to develop" — what linters/formatters to run, how to test, pre-commit hooks, CI/CD pipeline>
71
72	## AI-Assisted Development
73
74	<from /review-agentic-setup: reframed as "how to use AI coding tools" — what CLAUDE.md/AGENTS.md cover, installed skills, MCP servers, cross-tool compatibility>
75
76	## Security Considerations
77
78	<from .turbo/threat-model.md if present: key trust boundaries, security-sensitive areas, and what to be careful with — or omit this section if no threat model exists>
79
80	## Tr

People who liked this also viewed

6 picks

Type

onboard

3installs29forks

View on GitHub

How to install onboard?

tobihagemann/turbo/onboard

$npx -y skills add tobihagemann/turbo --skill onboard

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Onboard
2
3	Developer onboarding pipeline. Composes `/map-codebase`, `/review-tooling`, and `/review-agentic-setup` with inline agents, then synthesizes everything into `.turbo/onboarding.md` and `.turbo/onboarding.html`. Analysis-only.
4
5	## Task Tracking
6
7	At the start, use `TaskCreate` to create a task for each phase:
8
9	1. Launch all agents
10	2. Synthesize and generate markdown report
11	3. Generate HTML report
12
13	## Step 1: Launch All Agents
14
15	Use the Agent tool to launch all 6 agents below in a single assistant message so they run concurrently. Run them in the foreground so all their results return in this turn. Each Agent call uses `model: "opus"`. Each Composed Skills agent invokes its assigned skill via the Skill tool; each Inline Agent follows its exploration brief directly.
16
17	### Composed Skills
18
19	Launch one Agent tool call per row. Each agent's prompt instructs it to invoke its assigned skill via the Skill tool.
20
21	\| Skill \| Onboarding role \|
22	\|---\|---\|
23	\| `/map-codebase` \| Architecture understanding: structure, tech stack, entry points, patterns, data flow, dependencies, testing \|
24	\| `/review-tooling` \| Development workflow: linters, formatters, pre-commit hooks, test runners, CI/CD \|
25	\| `/review-agentic-setup` \| Agentic coding: CLAUDE.md, AGENTS.md, skills, MCP servers, hooks, cross-tool compatibility \|
26
27	### Inline Agents
28
29	Launch one Agent tool call each with the exploration brief below.
30
31	\| Agent \| Exploration Brief \|
32	\|---\|---\|
33	\| Prerequisites and Setup \| Read README.md, CONTRIBUTING.md, and package manager configs (package.json, Gemfile, Cargo.toml, go.mod, pyproject.toml, Package.swift, etc.). Extract: required language runtimes and versions, system dependencies, environment variables, database or service requirements, first-time setup steps (install, build, run, seed), and any bootstrap or setup scripts. \|
34	\| Troubleshooting \| Search for troubleshooting content in README.md, TROUBLESHOOTING.md, docs/ directory, FAQ files, and GitHub Discussions/Wiki if accessible. Extract common errors, known quirks, platform-specific gotchas, and debugging tips. If no troubleshooting docs exist, report that. \|
35	\| Next Steps \| Run `gh issue list --state open --json number,title,url,reactionGroups,comments,labels --limit 50`. Identify: (1) issues labeled `good-first-issue` or `good first issue`, (2) top 5 issues by engagement score (sum of reactions weighted 2x for thumbs-up, plus comment count). If `gh` is not available or not in a GitHub repo, skip and note that. \|
36
37	Each agent writes its findings as structured markdown.
38
39	## Step 2: Synthesize and Generate Markdown Report
40
41	After all agents complete:
42
43	1. Read all agent reports. Check if `.turbo/threat-model.md` exists; if so, read it for the Security Considerations section.
44	2. Reframe review skill outputs as documentation. `/review-tooling` findings become "Development Workflow" (what tools are used and how to run them). `/review-agentic-setup` findings become "AI-Assisted Development" (what's set up and how to use it). Focus on what exists, not what's missing. Strip severity labels, findings numbering, and gap framing from review skill outputs. Present detected tools and configurations as project conventions the new developer should know.
45	3. Write a brief welcome summary (3-5 sentences) capturing what the project is, who it's for, and the fastest path to a first contribution.
46	4. Write `.turbo/onboarding.md` using the report template. Output the welcome summary as text before writing the file.
47
48	### Report Template
49
50	```markdown
51	# Onboarding Guide
52
53	Date: <date>
54	Project: <project name>
55
56	## Welcome
57
58	<3-5 sentences: what this project is, who it's for, fastest path to a first contribution>
59
60	## Prerequisites and Setup
61
62	<from Prerequisites and Setup agent: language runtimes, dependencies, first-time setup steps, build/run commands>
63
64	## Architecture Overview
65
66	<from /map-codebase: condensed executive summary and key structural insights — not the full report, which lives at .turbo/codebase-map.md>
67
68	## Development Workflow
69
70	<from /review-tooling: reframed as "how to develop" — what linters/formatters to run, how to test, pre-commit hooks, CI/CD pipeline>
71
72	## AI-Assisted Development
73
74	<from /review-agentic-setup: reframed as "how to use AI coding tools" — what CLAUDE.md/AGENTS.md cover, installed skills, MCP servers, cross-tool compatibility>
75
76	## Security Considerations
77
78	<from .turbo/threat-model.md if present: key trust boundaries, security-sensitive areas, and what to be careful with — or omit this section if no threat model exists>
79
80	## Tr

People who liked this also viewed

6 picks

Type