Individual skill
onboarding-guide-generator
Generates a new-engineer onboarding guide from a codebase's actual structure - setup steps, architecture overview, key files, and where to start. Use when a project has no onboarding doc or an outdated one.
skills/productivity/onboarding-guide-generator/SKILL.md
Source commit d0a9928d24afb7df0fad2f2f35f65d3938a6926a
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 5, 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)
- 27
- Repository last updated
- Aug 20, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude-code Repository topic
- ai Repository topic
- ai-agents Repository topic
- ai-coding Repository topic
- ai-skill Repository topic
- ai-skill-enhancement Repository topic
- ai-skills Repository topic
- ai-skills-analysis Repository topic
- ai-skills-fest Repository topic
- ai-skills-manager 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
README.mddoc · 1,247 bytesSKILL.mdcore · 2,409 bytesexamples/example.mddoc · 1,993 bytes
Read excerpt
## Purpose
Generate an onboarding guide for a new engineer joining a project — grounded in the codebase's actual structure and setup, not a generic checklist — so a newcomer can get from "cloned the repo" to "made a first meaningful change" with less hand-holding.
## When to Use
- A project has no onboarding doc, or an outdated one that no longer matches the codebase.
- Preparing for a new hire or new contributor joining.
- The user asks for "onboarding docs" or "getting started" documentation for a codebase.
## What to Analyze / Do
1. **Determine real setup steps** — from the actual package manifest/README/scripts, not assumed commands. Don't invent steps that aren't verifiable from the source.
2. **Summarize the architecture** — the major components/services and how they relate, at a level a newcomer needs before diving into any one file.