Automated summary
An onboarding guide template that introduces a new teammate to a team's Claude Code usage (usage stats, setup checklist, MCP servers, skills), with embedded instructions telling Claude to act as an onboarding buddy.
Strengths
- A complete, fill-in-ready structure: usage breakdown, codebase/MCP/skill checklists, team tips, and a starter task
- Built-in instructions steer Claude toward a warm tone and a step-by-step flow (check what's already set up, then work through unchecked items one at a time)
- Uses markdown checkboxes to show what the teammate already has versus what's missing
- Explicitly forbids inventing sections or spinning personal usage stats into a 'team workflow' narrative
Limitations
- The skeleton is full of placeholders ([Team Name], [repo-name]) and leaves Team Tips / Get Started as TODO
- Assumes the guide author already has N days of usage statistics to populate
- Tightly coupled to Claude Code (slash commands, MCP servers, skills) and not directly portable to other tools
When a team wants a personalized welcome guide that walks a new member through setting up Claude Code and learning internal conventions.
For onboarding documentation about tools other than Claude Code, or when you have no usage data yet to populate the guide with.
Security analysis
SafeThis is an onboarding template whose hidden directive only tells the assistant to act as a warm setup buddy, compare existing setup against a checklist, and help work through unchecked items. Nothing exfiltrates data or performs destructive actions, though the entry grants Bash/Write/Edit and carries a comment-embedded instruction block that warrants normal caution when template fields are filled with external content.
- •Declared allowed-tools (Read/Write/Edit/Bash) are broad, so the assistant could modify files or run setup commands while walking a new teammate through onboarding — powerful but exercised for legitimate setup purposes.
- •The operating instructions are embedded in an HTML comment, invisible in rendered markdown; a mild prompt-injection surface if a guide's placeholder fields are populated with untrusted text.
- •No destructive commands, no curl|sh or base64 payloads, no secret/token exfiltration, and no instruction to disable safety controls.
Examples
I just joined the team — here's the onboarding guide my teammate shared for how we use Claude Code. Can you check it against my current setup and help me get going?Use this onboarding template to create a guide for our team 'Platform Core': fill in the codebases, the MCP servers we need (Linear, Postgres), and the skills our team relies on.Based on the setup checklist in this onboarding guide, suggest concrete entries for the Team Tips and Get Started sections so a new teammate knows what to do on day one.name: 'Skill: Team onboarding guide' description: 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 ccVersion: 2.1.94 allowed-tools: Read Write Edit Bash license: BSD-3-Clause license metadata: skill-author: Lord1Egypt
Welcome to [Team Name]
How We Use Claude
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 ...
Your Setup Checklist
Codebases
- [ ] [repo-name] — [repo url] ...
MCP Servers to Activate
- [ ] [Server] — [what it's for]. [How to get access] ...
Skills to Know About
- [/command] — [what it does, when the team uses it] ...
Team Tips
TODO
Get Started
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. -->From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/team-onboarding-guide-for-claude-code-mryiqh0t/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/team-onboarding-guide-for-claude-code-mryiqh0t' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/team-onboarding-guide-for-claude-code-mryiqh0t/download' --output '.skill-downloads/team-onboarding-guide-for-claude-code-mryiqh0t/SKILL.md.part' && mv '.skill-downloads/team-onboarding-guide-for-claude-code-mryiqh0t/SKILL.md.part' '.skill-downloads/team-onboarding-guide-for-claude-code-mryiqh0t/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Tools declared by the author (check availability in your agent): Read Write Edit Bash
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.
Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/team-onboarding-guide-for-claude-code-mryiqh0t/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
Supabase Docs Authoring
Documentation
Write, edit, and review Supabase documentation content including guides, tutorials, reference docs, and partials. Follow style guides and MDX/TOML validation rules.
Create Architecture Decision Record
Documentation
Create a new Architecture Decision Record with sequential numbering, register it in the AgentDB graph, and link related ADRs.
Plan update with deep research
Documentation
Updates a plan document by launching parallel subagents to analyze a topic across all compiler passes, then consolidates findings into the plan doc.