Onboard
Automate repetitive workflows and reduce manual effort
Example: Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example: Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example: Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Time estimate: 15-45 minutes depending on use case complexity
Prerequisites
Submit your Claude Code skill and start earning
epx add Donchitos/Claude-Code-Game-Studios --skill onboardCompatible with
Supported agents
description: "Generates a contextual onboarding document for a new contributor or agent joining the project. Summarizes project state, architecture, conventions, and current priorities relevant to the
argument-hint: "[role|area]"
allowed-tools: Read, Glob, Grep, Write
| name | onboard |
| description | "Generates a contextual onboarding document for a new contributor or agent joining the project. Summarizes project state, architecture, conventions, and current priorities relevant to the specified role or area." |
| argument-hint | "[role|area]" |
| user-invocable | true |
| allowed-tools | Read, Glob, Grep, Write |
| model | haiku |
Read CLAUDE.md for project overview and standards.
Read the relevant agent definition from .claude/agents/ if a specific role is specified.
src/ for architecture, patterns, key filesdesign/ for existing design documentsdesign/narrative/ for world-building and story docstests/ for existing test coverageproduction/ for current sprint and milestoneRead recent changes (git log if available) to understand current momentum.
# Onboarding: [Role/Area]
## Project Summary
[2-3 sentence summary of what this game 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]
Present the onboarding document to the user.
Ask: "May I write this to production/onboarding/onboard-[role]-[date].md?"
If yes, write the file, creating the directory if needed.
Verdict: COMPLETE — onboarding document generated.
/sprint-status to show the new contributor current progress./help if the contributor needs guidance on what to work on next.AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiononboardExecute the skills CLI command in your project's root directory to begin installation:
epx add Donchitos/Claude-Code-Game-Studios --skill onboardFetches onboard from Donchitos/Claude-Code-Game-Studios and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
.cursor/skills/onboard
Restart Cursor to activate onboard. Access via /onboardin your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
quick-design
Donchitos/Claude-Code-Game-Studios · Game Dev Planning · same repo
prototype
Donchitos/Claude-Code-Game-Studios · Game Dev Skills · same repo
security-audit
Donchitos/Claude-Code-Game-Studios · Game Dev Code · same repo
soak-test
Donchitos/Claude-Code-Game-Studios · Game QA & Testing · same repo
seo-geo
whyashthakker/agent-skills-marketing · Marketing · 2 shared tags
caveman-review
JuliusBrussee/caveman · Marketing · 2 shared tags
Solid pick for teams standardizing on skills: onboard is focused, and the summary matches what you get after install.
onboard reduced setup friction for our internal harness; good balance of opinion and flexibility.
onboard has been reliable in day-to-day use. Documentation quality is above average for community skills.
onboard fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
onboard reduced setup friction for our internal harness; good balance of opinion and flexibility.
onboard has been reliable in day-to-day use. Documentation quality is above average for community skills.
I recommend onboard for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
onboard fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
We added onboard from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Keeps context tight: onboard is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 72