customer-onboarding-and-implementation SKILL.md skillA
customer-onboarding-and-implementation from cbrock84/headcount is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add cbrock84/headcount/customer-onboarding-and-implementation@git:20260916.e72e404Pins git:20260916.e72e404 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- cbrock84/headcount
- Path
plugins/customer-experience/skills/customer-onboarding-and-implementation/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260916.e72e404, committed Sep 16, 2026
- First version recorded
- Sep 1, 2026
- Size
- 4,299 bytes
- Repository stars
- 2,543
- License
- MIT
Takes a new customer from signature to working — setting a definition of live that both sides agreed before the contract was signed, planning and staffing the implementation, running data migration and integration realistically, training the people who will actually use it, and handing over to the ongoing relationship. Use this to design an onboarding motion, rescue a stalled implementation, work out why customers who bought never went live, or scope the services a deal actually needs.
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
# Customer onboarding and implementation The period between signature and first real use is where the largest share of preventable churn is created, and where a customer's opinion of the product is formed permanently. ## Agree what live means before the contract is signed The most common implementation failure happens in the sales cycle: nobody wrote down what success would look like, so the project has no finish line and every party quietly holds a different one. Define the go-live criteria concretely — which teams, doing what, with what data in place — along with the date, who does what on each side, and what the customer must supply. Put it in the contract or an agreed plan before the deal closes, not after. **Sales commitments become implementation scope.** If a deal was won on something the product does not do yet, the implementation team inherits it. Route that decision back to whoever can make it rather than absorbing it silently. ## Plan the implementation as a project with a customer-side owner Nothing predicts implementation failure like the absence of a named, empowered owner on the …
Read the whole file at its exact version.
How to install
mdr add cbrock84/headcount/customer-onboarding-and-implementation@sha256:127770eca68b8c2fThe line at the top of this page pins the label git:20260916.e72e404, 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_2yk2uoltktpvgnqv)
6 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Sep 1, 2026 and Sep 16, 2026, about one every 15 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260916.e72e404 latest | 2026-09-16 | e72e404 | 4,299 B | A | view · diff |
| git:20260901.9844f9d | 2026-09-01 | 9844f9d | 3,960 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 (4299 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
cbrock84/headcount · 2,543 stars · license MIT · pushed 2026-10-18 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_2yk2uoltktpvgnqv GET https://markdownregistry.com/api/v1/resolve?ref=cbrock84/headcount/customer-onboarding-and-implementation GET https://markdownregistry.com/api/v1/blob/127770eca68b8c2f4fc4b91e388cc60070f537f1f8e736d9071d6cf2b543a8e8
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.