Meeting Notes
outline/outline
Create meeting notes in Outline from a template; use when the user wants an agenda, notes, or a follow-up document for a meeting.
Build a smooth client-onboarding process that starts projects on the right foot — clear expectations, the info you need, and a professional first impression that prevents problems later.
Install Client Onboarding Kit
$ npx skills add mohitagw15856/pm-claude-skills --skill client-onboarding-kit -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills client-onboarding-kit --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/client-onboarding-kit .claude/skills/client-onboarding-kit && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "client-onboarding-kit" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/client-onboarding-kit into .claude/skills/client-onboarding-kit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "client-onboarding-kit", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/client-onboarding-kitType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mohitagw15856/pm-claude-skills --skill client-onboarding-kit -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills client-onboarding-kit --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/client-onboarding-kit .agents/skills/client-onboarding-kit && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "client-onboarding-kit" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/client-onboarding-kit into .agents/skills/client-onboarding-kit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "client-onboarding-kit", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill client-onboarding-kit -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills client-onboarding-kit --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/client-onboarding-kit .cursor/skills/client-onboarding-kit && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "client-onboarding-kit" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/client-onboarding-kit into .cursor/skills/client-onboarding-kit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "client-onboarding-kit", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mohitagw15856/pm-claude-skills.git --path skills/client-onboarding-kit--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mohitagw15856/pm-claude-skills --skill client-onboarding-kit -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills client-onboarding-kit --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/client-onboarding-kit .gemini/skills/client-onboarding-kit && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "client-onboarding-kit" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/client-onboarding-kit into .gemini/skills/client-onboarding-kit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "client-onboarding-kit", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mohitagw15856/pm-claude-skills client-onboarding-kitInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mohitagw15856/pm-claude-skills --skill client-onboarding-kit -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/client-onboarding-kit .github/skills/client-onboarding-kit && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "client-onboarding-kit" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/client-onboarding-kit into .github/skills/client-onboarding-kit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "client-onboarding-kit", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill client-onboarding-kit -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills client-onboarding-kit --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/client-onboarding-kit .opencode/skills/client-onboarding-kit && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "client-onboarding-kit" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/client-onboarding-kit into .opencode/skills/client-onboarding-kit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "client-onboarding-kit", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
client-onboarding-kit- GitHub stars
- 1.4k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 522 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Build a smooth client-onboarding process that starts projects on the right foot — clear expectations, the info you need, and a professional first impression that prevents problems later.
- Works in 6 steps: Welcome and reassure. A prompt, warm… → Gather everything up front. A structured… → Align expectations explicitly. Scope… → …
- Asked to onboard a new client
- SKILL.md covers What This Skill Produces, Required Inputs, Framework: Set The Frame… and Output Format, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Client Onboarding Kit is an agent skill from mohitagw15856/pm-claude-skills. Build a smooth client-onboarding process that starts projects on the right foot — clear expectations, the info you need, and a professional first impression that prevents problems later. Use when asked to onboard a new client, create an onboarding process, kick off a client project, or client welcome packet. Produces a welcome and kickoff flow, the intake you need to start, expectation-setting on scope/comms/timeline/payment, a kickoff-meeting agenda, and the templates to reuse — so onboarding is consistent, not…
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Productivity & Automation, covering Meeting notes and agendas. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Asked to onboard a new client
- Create an onboarding process
- Kick off a client project
- Client welcome packet
Example prompts
- “/client-onboarding-kit”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Welcome and reassure. A prompt, warm welcome after signing sets the tone and confirms they made the right choice.
- Gather everything up front. A structured intake for the info, access, assets, and decisions you need — so the work isn't stalled chasing…
- Align expectations explicitly. Scope (and what's out of scope), communication channels and cadence, timeline/milestones, revisions, and…
- Run a real kickoff. A structured kickoff meeting confirms goals, roles, and the plan, and gives the client confidence.
- Make it repeatable. Templatize the welcome, intake, and agenda so every client gets the same professional start with less effort each time.
- Prevent the usual problems. The clarity set here (especially scope and comms) is what heads off scope creep and friction later.
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Client Onboarding Kit loads about 1.1k tokens when it runs. Until then it costs about 155 tokens; SKILL.md has 522 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 522 words, ~1,122 tokens.
Download SKILL.mdSave it as
.claude/skills/client-onboarding-kit/SKILL.md (or your agent's skills folder).- name
- client-onboarding-kit
- description
- Build a smooth client-onboarding process that starts projects on the right foot — clear expectations, the info you need, and a professional first impression that prevents problems later. Use when asked to onboard a new client, create an onboarding process, kick off a client project, or client welcome packet. Produces a welcome and kickoff flow, the intake you need to start, expectation-setting on scope/comms/timeline/payment, a kickoff-meeting agenda, and the templates to reuse — so onboarding is consistent, not improvised, and prevents the scope and communication problems that sink projects.
Client-Onboarding Kit
How a project starts largely determines how it goes. Sloppy onboarding — unclear scope, missing info, mismatched expectations — is where most client problems are born. A clean, repeatable onboarding process sets expectations, gathers what you need, and signals professionalism from day one. This builds that flow so every new client starts the same, smooth way.
What This Skill Produces
- A welcome & kickoff flow — the sequence from signed deal to project start (welcome, intake, kickoff, first steps)
- The intake — the exact information, access, and assets you need to begin (so you're not chasing it later)
- Expectation-setting — clear alignment on scope, communication norms, timeline, milestones, and payment terms
- A kickoff-meeting agenda — a structured first meeting that aligns everyone and builds confidence
- Reusable templates — the welcome message, intake form, and kickoff agenda to reuse every time
- Problem-prevention — the boundaries (scope, comms cadence, revisions) set now that prevent disputes later
Required Inputs
Ask for these if not provided:
- Your service — what you deliver and a typical project shape
- Client type — size/sophistication (tunes formality)
- Current process — what you do now (or nothing)
- Pain points — where projects usually go wrong (scope, comms, delays, payment)
- Tools — what you use for comms, files, contracts, payments
Framework: Set The Frame Before The Work
- Welcome and reassure. A prompt, warm welcome after signing sets the tone and confirms they made the right choice.
- Gather everything up front. A structured intake for the info, access, assets, and decisions you need — so the work isn't stalled chasing details.
- Align expectations explicitly. Scope (and what's out of scope), communication channels and cadence, timeline/milestones, revisions, and payment terms — stated now, not assumed.
- Run a real kickoff. A structured kickoff meeting confirms goals, roles, and the plan, and gives the client confidence.
- Make it repeatable. Templatize the welcome, intake, and agenda so every client gets the same professional start with less effort each time.
- Prevent the usual problems. The clarity set here (especially scope and comms) is what heads off scope creep and friction later.
Show full SKILL.md (185 more words)Show less
Output Format
Client onboarding: [service] · client type [x]
Flow: signed → welcome → intake → kickoff → first steps. Welcome message: [warm, next-steps, what to expect]. Intake (gather up front): [info · access · assets · decisions needed]. Set expectations: scope (+ out of scope) · comms channel & cadence · timeline/milestones · revisions · payment terms. Kickoff agenda: [goals · roles · plan · Q&A · next steps]. Templates to reuse: [welcome · intake form · kickoff agenda].
Quality Checks
- Covers the full flow from signed to project start
- Includes a structured intake for everything needed to begin
- Sets explicit expectations on scope, comms, timeline, and payment
- Provides a kickoff-meeting agenda
- Produces reusable templates
- Ties the setup to preventing later scope/comms problems
Anti-Patterns
- Improvising onboarding differently each time.
- Starting work before gathering the needed info/access.
- Leaving scope and comms to assumption.
- No kickoff — diving in without alignment.
- One-off effort with nothing templatized.
Example Trigger Phrases
- "Help me create a client onboarding process."
- "Build me a welcome packet and kickoff flow for new clients."
- "What should I gather from a new client before starting?"
- "My projects start chaotically — help me onboard clients better."
- "Give me a kickoff meeting agenda for a new client project."
© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/client-onboarding-kit of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Client Onboarding Kit next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Client Onboarding Kit this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Meeting Notesoutline/outline | 41k | — | ~551 | Automated safety check: Pass | Custom licence | |
| Management Talkthananon/9arm-skills | 3.2k | — | ~3.2k | Automated safety check: Pass | None | |
| Challenge Baseline ModelAgibotTech/genie_sim | 1.4k | — | ~2.4k | Automated safety check: Pass | Custom licence | |
| Handwriting Stand Uplimin112/min-skill | 454 | — | ~2.5k | Automated safety check: Pass | None | |
| Daily Journalravila4/claude-adhd-skills | 158 | — | ~2.5k | Automated safety check: Pass | MIT |
Similar skills
Management Talk
thananon/9arm-skills
Rewrite engineer-to-engineer content for engineering-org leadership (VPs, directors, PMs, release managers, execs in an engineering-savvy company) and shape it for the channel it is going to — JIRA…
Challenge Baseline Model
AgibotTech/genie_sim
Provision and launch the Simulation Challenge baseline inference model end to end: clone the inference code from a given git repo/branch, download the checkpoints from ModelScope into the repo's…
Handwriting Stand Up
limin112/min-skill
Turn a screen recording of handwriting (or a photo of handwritten text) into a single-file HTML "continuation" — the recording plays, the ink lifts off the page as solid 3D letters, a short animated…
Daily Journal
ravila4/claude-adhd-skills
Draft, organize, or update development journal entries. An agent skill from ravila4/claude-adhd-skills.
Granola
ArtemXTech/claude-code-obsidian-starter
Query and sync Granola meetings to Obsidian vault. An agent skill from ArtemXTech/claude-code-obsidian-starter.
More from mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Related
Categories
Questions about Client Onboarding Kit
What does Client Onboarding Kit do?
Build a smooth client-onboarding process that starts projects on the right foot — clear expectations, the info you need, and a professional first impression that prevents problems later. Client Onboarding Kit is an agent skill from mohitagw15856/pm-claude-skills. Build a smooth client-onboarding process that starts projects on the right foot — clear expectations, the info you need, and a professional first impression that prevents problems later.
When should I use Client Onboarding Kit?
Client Onboarding Kit fits situations like: asked to onboard a new client; create an onboarding process; kick off a client project; client welcome packet.
How do I install Client Onboarding Kit in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill client-onboarding-kit -a claude-code`. Or copy the skill folder (skills/client-onboarding-kit in mohitagw15856/pm-claude-skills) into .claude/skills/client-onboarding-kit in your project. Claude Code loads it when a task matches its description.
How do I install Client Onboarding Kit in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill client-onboarding-kit -a codex`. Or copy the skill folder (skills/client-onboarding-kit in mohitagw15856/pm-claude-skills) into .agents/skills/client-onboarding-kit in your project. Codex loads it when a task matches its description.
Can I use Client Onboarding Kit in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill client-onboarding-kit -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/client-onboarding-kit, .gemini/skills/client-onboarding-kit, .github/skills/client-onboarding-kit and .opencode/skills/client-onboarding-kit in your project.
What does Client Onboarding Kit need to run?
SKILL.md names no scripts, command-line tools or credentials: Client Onboarding Kit is instructions for the agent only.
Does Client Onboarding Kit access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Client Onboarding Kit safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Client Onboarding Kit use?
Client Onboarding Kit is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Client Onboarding Kit use?
About 1.1k tokens (SKILL.md is roughly 4.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Client Onboarding Kit?
Skills that share tags, products or a category with Client Onboarding Kit: Meeting Notes (outline/outline, 41k stars), Management Talk (thananon/9arm-skills, 3.2k stars), Challenge Baseline Model (AgibotTech/genie_sim, 1.4k stars) and Handwriting Stand Up (limin112/min-skill, 454 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Client Onboarding Kit?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.