Localized reading guide
smb-onboardPurpose, usage and source
Claude as the trainer. Walks an SMB owner through connecting their first two tools, runs one recipe to prove immediate value, interviews them about their business (industry, size, top three headaches), stores that context persistently so every other skill benefits, and sets a weekly check-in cadence. Use when the owner is getting started or says any of: "set me up," "setup," "help me get set up," "get started," "help me get started," "get me started," "what can you do," "I'm new to this," or is in their first session.
Source retrieved:
- Source repository
- anthropics/knowledge-work-plugins
- SKILL.md
small-business/skills/smb-onboard/SKILL.md- Repository stars
- 34,049
- Repository updated
- 2026-10-30
- Categories
- Business
- Last collected
License: Apache-2.0
Workflow excerpts are reading aids, not executable instructions from Codez. No third-party Skill was run to produce this page.
The purpose and workflow passages below are upstream material, organized and translated for reading. They are distinct from the separately labeled Codez editorial analysis.
What this Skill does
Claude as the trainer. Walks an SMB owner through connecting their first two tools, runs one recipe to prove immediate value, interviews them about their business (industry, size, top three headaches), stores that context persistently so every other skill benefits, and sets a weekly check-in cadence. Use when the owner is getting started or says any of: "set me up," "setup," "help me get set up," "get started," "help me get started," "get me started," "what can you do," "I'm new to this," or is in their first session.
How the upstream workflow works
Quick start
Four moves: connect two tools → run one recipe → capture business context → set a weekly rhythm. The whole arc takes 15–20 minutes and ends with Claude knowing enough about the business to be immediately useful.
Upstream passage · L16 ↗Workflow
Welcome and assess. Greet the owner briefly, then follow this decision order exactly — same inputs, same path, every time: Check memory for a ## Business context block first. If it exists, take the return-session path: show the existing profile, ask what's changed, update only the fields that changed, then go straight to the matched recipe or the cadence. Do not re-interview, and do not re-offer connector setup — if a useful connector is missing, mention the category in one line at most and move on. If the block predates the Country, Currency, and Financial year end fields, fill just those three (from the ledger if connected, otherwise one question) and nothing else. Run one recipe to prove value. Narrate what Claude is doing and why — this is the "aha" moment.
The business diagnostic
This extends the interview into a diagnostic that assembles the owner's stack, rather than just storing context. Three additions to the flow above. Diagnose, then recommend a stack. From the interview answers — industry, size, tools, growth goals — assemble the specific skills and commands this owner should start with, not the full catalog. A contractor gets proposal-builder and contract-review named first; a shop gets inventory-planner and the storefront leg of business-pulse; a consultancy gets speed-to-lead and crm-autopilot. Read the mapping in reference/onboard-checklist.md and name three to five, each with its trigger phrase. A 36-skill catalog read out loud is a wall; a five-skill starting stack is a plan.
User: "get me started"
→ Assess what's already connected; pick the best 2 tools to connect first
→ Guide connection of each tool (one at a time)
→ Run one recipe against live data to prove value
→ Ask the interview questions one at a time; store answers to persistent memory
→ "Each Monday, say 'weekly check-in' — I'll pull your numbers and flag anything urgent."Requirements and setup
No short requirements passage was selected from this file. This does not mean the Skill has no dependencies. Check the repository setup instructions and referenced files.
Limits and quality checks
No separate limits passage was selected from this file. This does not mean the Skill is safe for every input or environment. Review the complete source and validate your own result.
Start with a safe trial
- Check the supported host and the repository installation instructions. Keep the Skill directory and its referenced scripts, assets and documentation together; SKILL.md alone may omit dependencies.
- Give the agent your real input, desired output and acceptance criteria. Invocation syntax and available tools depend on the host; this site does not assume a universal install command.
- Try the source workflow in a disposable project or on a copy. Review operations that change files, remote services or billable resources before allowing them.
- Validate the output against the source quality checks and your own requirements. A successful trigger or a high repository Star count does not establish a correct result.
Read further in the source
Related Skills
Translation and scope
This reading guide selects passages from the pinned upstream SKILL.md. Translation is assisted. It is not a complete manual or a claim of tested compatibility. Read the original and its referenced files before use.
This introduction refers to the pinned version below; current repository activity and collection time are shown separately.
- Pinned source
- Read the original ↗
- Source retrieved
- Source commit
2574e29377c7173d0cecffef29a6ecbd7f8ccb5d- Source SHA-256
5402b710a91ae71994582ebe988dab203a6ac5b4f8bab0b5252568f9d9d42ac8