client-onboarding SKILL.md skillA
client-onboarding from ericrisco/rsc-harness is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add ericrisco/rsc-harness/client-onboarding@git:20260729.3ecb845Pins git:20260729.3ecb845 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- ericrisco/rsc-harness
- Path
skills/client-onboarding/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260729.3ecb845, committed Jul 29, 2026
- First version recorded
- Jun 2, 2026
- Size
- 12,691 bytes
- Repository stars
- 236
- License
- MIT
Use when a deal closed or a user signed up and the first 30 days need an activation plan: sales→delivery handoff, one verifiable activation event, kickoff, and a 30/60/90 or day-0→14 plan with owners, dates and a measurable exit. NOT reactive ticket triage (that is `customer-support`), NOT renewals/churn past the onboarded gate (that is `retention`).
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Client onboarding You run the **post-signature activation sprint**: the window between "deal closed / account created" and "customer is live and has felt real value at least once." The deal is signed — now get this customer set up, to their first win, and formally **onboarded** before the trust they bought with their signature decays. You own four jobs: (1) take the sales→delivery handoff so nothing promised gets lost, (2) define **one verifiable activation event** and the shortest path to it, (3) run the kickoff (welcome packet, agenda, RACI), and (4) lay a phased plan with named owners, dates, and a measurable exit. Hand off explicitly: an inbound ticket from an existing customer → [`customer-support`](../customer-support/SKILL.md) (you are proactive first-30-days, not reactive triage); renewals, churn programs and health scoring → [`retention`](../retention/SKILL.md) (you **end** at the onboarded gate); the pre-signature proposal/SOW → [`proposals`](../proposals/SKILL.md); pre-close stages and forecasting → [`sales-pipeline`](../sales-pipeline/SKILL.md) (the handoff is the seam between you); kickoff invites → …
Read the whole file at its exact version.
How to install
mdr add ericrisco/rsc-harness/client-onboarding@sha256:b4ee3b9dee98a03cThe line at the top of this page pins the label git:20260729.3ecb845, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_hzl747wiopk63kzt)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Jun 2, 2026 and Jul 29, 2026, about one every 57 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260729.3ecb845 latest | 2026-07-29 | 3ecb845 | 12,691 B | A | view · diff |
| git:20260602.484d945 | 2026-06-02 | 484d945 | 13,511 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (12691 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
ericrisco/rsc-harness · 236 stars · license MIT · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_hzl747wiopk63kzt GET https://markdownregistry.com/api/v1/resolve?ref=ericrisco/rsc-harness/client-onboarding GET https://markdownregistry.com/api/v1/blob/b4ee3b9dee98a03c030c626b428cea3e4b0dd01c0dce10ee8186eb8d56bdf46f
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from ericrisco/rsc-harness
Every file in ericrisco/rsc-harness