skills/team-onboarding-guide/SKILL.md
Template for onboarding a new teammate to a team's Claude Code setup, walking them through usage stats, setup checklists, MCP servers, skills, and team tips in a warm conversational style
npx skillsauth add mkusaka/ccskills team-onboarding-guideInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Based on [name]'s usage over the last [N] days:
Work Type Breakdown: [Category 1] [ascii bar] [N]% [Category 2] [ascii bar] [N]% [Category 3] [ascii bar] [N]% ...
Top Skills & Commands: [/command] [ascii bar] [N]x/month ...
Top MCP Servers: [Server] [ascii bar] [N] calls ...
TODO
TODO
<!-- INSTRUCTION FOR CLAUDE: A new teammate just pasted this guide for how the team uses Claude Code. You're their onboarding buddy — warm, conversational, not lecture-y. Open with a warm welcome — include the team name from the title. Then: "Your teammate uses Claude Code for [list all the work types]. Let's get you started." Check what's already in place against everything under Setup Checklist (including skills), using markdown checkboxes — [x] done, [ ] not yet. Lead with what they already have. One sentence per item, all in one message. Tell them you'll help with setup, cover the actionable team tips, then the starter task (if there is one). Offer to start with the first unchecked item, get their go-ahead, then work through the rest one by one. After setup, walk them through the remaining sections — offer to help where you can (e.g. link to channels), and just surface the purely informational bits. Don't invent sections or summaries that aren't in the guide. The stats are the guide creator's personal usage data — don't extrapolate them into a "team workflow" narrative. -->development
Shape-specific /design-sync instructions for syncing a React design system from Storybook stories and built package output
development
Skill definition for syncing a React design system to claude.ai/design, including project selection, source-shape detection, converter configuration, validation, upload planning, and self-check behavior
development
Shape-specific /design-sync instructions for syncing a React design system from a built package without Storybook
development
Skill instructions for answering Claude Code configuration questions by checking the running build, bundled references, and current documentation