customer-onboarding SKILL.md skillA
customer-onboarding from trevhud/rote is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add trevhud/rote/customer-onboarding@git:20261020.d5cace8Pins git:20261020.d5cace8 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- trevhud/rote
- Path
examples/holdout/customer-onboarding/skill/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261020.d5cace8, committed Oct 20, 2026
- Size
- 2,404 bytes
- Repository stars
- 8
- License
- Apache-2.0
Onboard a new customer once their deal is closed-won in HubSpot. Pulls the deal, screens the company, checks the terms, gets the CS lead's sign-off, then provisions the workspace, invites the customer's admins, opens the Linear onboarding project and announces it in #cs-onboarding. Use when someone says "onboard <company>" or "deal <id> closed".
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 Input: the HubSpot deal id. ## 1. Pull the deal `hubspot_get_deal` (HubSpot MCP) with the deal id. It returns company name, plan, seats, discount %, payment terms (days), the special terms note, and the admin contacts. ## 2. Sanctions screen (MANDATORY) Run the company name through `screen_entity` on the compliance MCP. Every customer, no exceptions, before anything is provisioned. A hit doesn't stop onboarding by itself, but the CS lead has to see it in step 5. ## 3. Commercial terms Standard terms: - discount 20% or less - payment terms net 30 or shorter - seats within the plan cap: Starter 25, Growth 200, Enterprise no cap Anything outside that is non-standard. List each one. ## 4. Special terms note Read the deal's special terms note. Flag anything that changes our MSA: custom SLA, liability cap changes, data residency, termination for convenience, MFN pricing. Nothing in the note, or only scheduling notes (kickoff dates, contact preferences), means standard. ## 5. CS lead sign-off Send the CS lead the deal summary, the screen result, and the non-standard items from 3 and 4. Wait for approval. The CS lead can …
Read the whole file at its exact version.
How to install
mdr add trevhud/rote/customer-onboarding@sha256:8cfe717c853a3d92The line at the top of this page pins the label git:20261020.d5cace8, 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_l2sp6yu65z2vsugx)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 20, 2026.
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 (2404 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
trevhud/rote · 8 stars · license Apache-2.0 · pushed 2026-10-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_l2sp6yu65z2vsugx GET https://markdownregistry.com/api/v1/resolve?ref=trevhud/rote/customer-onboarding GET https://markdownregistry.com/api/v1/blob/8cfe717c853a3d926d573b77fd19116b6cee5cce8ab8d3f63da6e34b6fb5879d
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.