client-onboard
Skill1 starsChanged 5 months agoMITView on GitHub
Advance a client's onboarding through a fixed checklist in one resumable session. Reads a per-client onboarding.md (a 10-item checklist), walks it linearly, drafts each artifact (NDA, contract, letter of intent, welcome email, invoice setup, kickoff) into a per-client onboarding folder, fills the client's frontmatter fields, creates a follow-up task per sent item, and flips the client from prospect to active when the contract is signed. Idempotent and resumable: re-run any time; it skips checked items. Use when you say 'onboard <client>', 'advance onboarding', 'send the NDA', 'draft the LOI', 'set up invoicing for <client>', or 'activate <client>'.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- chriswestt/claude-skillstheir own version, first seen Oct 9, 2026
- waseemnasir2k26/skynetlabs-all-claude-codetheir own version, first seen Jun 9, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- waseemnasir2k26/skynetlabs-all-claude-code★ 2same name
- chriswestt/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository14 other files it gives its agents.
- brain-addSkill
- brain-add-videoSkill
- brain-checkSkill
- brain-digestSkill
- brain-processSkill
- brain-saveSkill
- brain-searchSkill
- consulting-deckSkill
- good-morningSkill
- harvestSkill
- logSkill
- taskSkill
- weekly-reviewSkill
- wrap-sessionSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 3 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 24
No fabricated content. Placeholder sections use italics or {{TK-…}} markers.
- Distinctive: line 25
Never invent legal text. Legal artifacts (NDA, contract) only receive placeholder substitution.
- Very specific: line 32
If the slug is omitted, scan <clients-dir>/*/ for clients whose status is prospect with onboarding still open, and present a multi-select …
- Very specific: line 38
If <slug> is provided, validate the folder exists.
- Very specific: line 57
Read the latest proposal. Extract pricing from a frontmatter pricing: block (preferred) or a ## Pricing section.
- Distinctive: line 61
If nothing parses, default to "skip" and warn in the report.
- Distinctive: line 90
Create a follow-up task in your task tracker for any "sent" or "requested" action.
- Very specific: line 91
If "Contract signed and filed" flips to checked this session, set a contract_just_signed flag for step 7.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/client-onboard
Advance a client's onboarding state through a fixed 10-item checklist. This skill advances state; it assumes the per-client folder and checklist already exist (see "Handoff contract" at the bottom). It is idempotent and resumable: run it as many times as you like; it skips items already checked and continues from the first open one.
Customize before use: replace
<clients-dir>(where your client folders live, e.g.clients/),<templates-dir>(your reusable artifact templates),[YOUR COMPANY], and[YOUR SIGNOFF]. SeeCUSTOMIZE.md.
Voice rules (apply to every drafted artifact and user-facing message)
- Active voice. The reader is the subject of the action.
- No fabricated content. Placeholder sections use italics or
{{TK-…}}markers. - Never invent legal text. Legal artifacts (NDA, contract) only receive placeholder substitution; clauses come from a reviewed template, never from the model.
- Sign emails off with
[YOUR SIGNOFF].
Argument
/client-onboard <slug> where <slug> is an existing <clients-dir>/<slug>/ folder.
If the slug is omitted, scan <clients-dir>/*/ for clients whose status is prospect
with onboarding still open, and present a multi-select via AskUserQuestion.
Steps
1. Parse argument
If <slug> is provided, validate the folder exists. If not, surface candidate slugs
via AskUserQuestion and let the user pick one.
2. Pre-flight
The one blocking failure is "no proposal found" for the client: halt with a clear, user-fixable message and stop. Lesser issues (a missing template stub, a missing onboarding folder) are auto-repaired with a one-line note in the final report.
3. Read context (one batch)
<clients-dir>/<slug>/README.md— frontmatter is the source of truth forname,slug,status,primary_contact,start_date, plus the nullable fields this skill fills:contract_path,nda_path,invoice_prefix,tools_access.<clients-dir>/<slug>/onboarding.md— current checklist state ([ ],[x],[~]).<templates-dir>/{nda,loi,welcome-email,contract}.md— carriers, not sources of legal text.- Latest proposal in
<clients-dir>/<slug>/proposals/*.md(pick by filename date descending; canonical namingYYYY-MM-DD-<version>.md).
4. Pricing load + confirm
Read the latest proposal. Extract pricing from a frontmatter pricing: block (preferred)
or a ## Pricing section. Capture price and payment_terms. Confirm via
AskUserQuestion: "Use pricing from <proposal-file>?" with options
[confirmed, override price, override terms, skip (use {{TK-confirm-pricing}})].
If nothing parses, default to "skip" and warn in the report.
5. Status report (print one block, no preamble)
Onboarding state for <client-name> (<slug>):
- Status: <current status>
- Complete: X of 10
- Walking: <unchecked item titles>
- Pricing: <resolved price + terms, or "manual fill">6. Linear walk
Fixed order, following onboarding.md:
- NDA sent
- NDA signed and filed
- Contract drafted
- Contract signed and filed
- Letter of intent sent
- Scope confirmation received
- Welcome email sent
- Invoice prefix assigned
- Kickoff meeting scheduled
- Tools provisioned
For each unchecked item in order:
- Draft the matching artifact into
<clients-dir>/<slug>/onboarding/where applicable (items 1-7 produce a draft; 8-10 are admin updates). - Apply the write: update
onboarding.mdinline ([x] <item>: <action> YYYY-MM-DD), and update the README frontmatter field where applicable. - Create a follow-up task in your task tracker for any "sent" or "requested" action.
- If "Contract signed and filed" flips to checked this session, set a
contract_just_signedflag for step 7. - On "skip": leave the item
[ ]and note it. Items 1-2 (NDA) accept "skip both" →[~]. - On user abort: stop the walk. Completed items keep their state; the half-processed item rolls back (no draft written, no checklist edit).
7. Activation prompt
Trigger only when contract_just_signed is true. On confirmation:
- Edit the README frontmatter
statusfromprospecttoactive. - Append a one-line entry to your activity log.
- Move the client from the prospect list to the active list in your client index.
8. Task closure sweep
For every item that flipped [ ] → [x] this session, find the matching open
follow-up task in your tracker and mark it done. Skip items with no matching task
(checked manually before the skill saw them).
9. Final report (print one block)
Session result for <client-name> (<slug>):
- Items advanced: <count> (<titles>)
- Items skipped: <count or "none"> (<titles + reason>)
- Drafts written: <paths under <clients-dir>/<slug>/onboarding/>
- Tasks created / closed: <counts>
- Activation triggered: <yes (prospect → active) | no>
- Next pending item: <title or "onboarding complete">
- Manual fill needed: <{{TK-…}} placeholders surfaced in drafts, if any>Edge cases
- Proposal missing: hard halt; suggest drafting one first.
- Multiple proposals: pick latest by filename date; confirm or override.
- Frontmatter field already filled: show current value, ask "keep or override?".
- Template stub is a heading only: use as-is, warn, and fill legal drafts with the placeholder map plus a "Legal body to source from a reviewed template before sending." line.
- A follow-up task already exists for the same item + client: skip; do not duplicate.
- Pricing not parseable: surface
{{TK-confirm-pricing}}; ask once at the start.
Handoff contract (assumed inputs)
This skill never creates new structure; it advances state. It assumes a prior setup
step has produced, for <slug>:
<clients-dir>/<slug>/README.mdwith the nullable fieldscontract_path,nda_path,invoice_prefix,tools_access.<clients-dir>/<slug>/onboarding.mdwith all 10 items unchecked.<clients-dir>/<slug>/onboarding/folder for drafts.<templates-dir>/{nda,loi,welcome-email,contract}.md(possibly stubs).- A proposal in
<clients-dir>/<slug>/proposals/.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

