Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
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…
Install Customer Onboarding And Implementation
$ npx skills add cbrock84/headcount --skill customer-onboarding-and-implementation -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install cbrock84/headcount customer-onboarding-and-implementation --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/customer-experience/skills/customer-onboarding-and-implementation .claude/skills/customer-onboarding-and-implementation && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "customer-onboarding-and-implementation" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/customer-experience/skills/customer-onboarding-and-implementation into .claude/skills/customer-onboarding-and-implementation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customer-onboarding-and-implementation", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/cbrock84/headcount/tree/main/plugins/customer-experience/skills/customer-onboarding-and-implementationType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add cbrock84/headcount --skill customer-onboarding-and-implementation -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install cbrock84/headcount customer-onboarding-and-implementation --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/customer-experience/skills/customer-onboarding-and-implementation .agents/skills/customer-onboarding-and-implementation && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "customer-onboarding-and-implementation" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/customer-experience/skills/customer-onboarding-and-implementation into .agents/skills/customer-onboarding-and-implementation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customer-onboarding-and-implementation", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add cbrock84/headcount --skill customer-onboarding-and-implementation -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install cbrock84/headcount customer-onboarding-and-implementation --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/customer-experience/skills/customer-onboarding-and-implementation .cursor/skills/customer-onboarding-and-implementation && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "customer-onboarding-and-implementation" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/customer-experience/skills/customer-onboarding-and-implementation into .cursor/skills/customer-onboarding-and-implementation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customer-onboarding-and-implementation", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/cbrock84/headcount.git --path plugins/customer-experience/skills/customer-onboarding-and-implementation--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add cbrock84/headcount --skill customer-onboarding-and-implementation -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install cbrock84/headcount customer-onboarding-and-implementation --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/customer-experience/skills/customer-onboarding-and-implementation .gemini/skills/customer-onboarding-and-implementation && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "customer-onboarding-and-implementation" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/customer-experience/skills/customer-onboarding-and-implementation into .gemini/skills/customer-onboarding-and-implementation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customer-onboarding-and-implementation", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install cbrock84/headcount customer-onboarding-and-implementationInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add cbrock84/headcount --skill customer-onboarding-and-implementation -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/customer-experience/skills/customer-onboarding-and-implementation .github/skills/customer-onboarding-and-implementation && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "customer-onboarding-and-implementation" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/customer-experience/skills/customer-onboarding-and-implementation into .github/skills/customer-onboarding-and-implementation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customer-onboarding-and-implementation", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add cbrock84/headcount --skill customer-onboarding-and-implementation -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install cbrock84/headcount customer-onboarding-and-implementation --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/customer-experience/skills/customer-onboarding-and-implementation .opencode/skills/customer-onboarding-and-implementation && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "customer-onboarding-and-implementation" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/customer-experience/skills/customer-onboarding-and-implementation into .opencode/skills/customer-onboarding-and-implementation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customer-onboarding-and-implementation", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
customer-onboarding-and-implementation- GitHub stars
- 2k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 588 words
- Files
- 2 (incl. references)
- Skills in repo
- 178
- Repo updated
- First seen
- Licence
- MIT
At a glance
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…
- Tasks that involve Customer success
- SKILL.md covers Agree what live means before…, Plan the implementation as a…, Sequence for early value, not… and Data and integrations are…, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Customer Onboarding And Implementation is an agent skill from cbrock84/headcount. 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.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/sources.md`).
It sits in Sales & Support, covering Customer success. The repository describes itself as: An agent organization structured as a company — 15+ departments, 125+ skills, each independently installable, citing the standards and regulators that settle the question. Runs… The licence is MIT.
When your agent uses it
- Tasks that involve Customer success
Example prompts
- “Use the customer-onboarding-and-implementation skill to take a new customer from signature to working — setting a definition of live that both sides…”
- “/customer-onboarding-and-implementation”
What it can do on your machine
Read from SKILL.md and the folder at commit 98d1c17. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Customer Onboarding And Implementation loads about 1.1k tokens when it runs, and up to ~1.3k if it reads all its reference files. Until then it costs about 132 tokens; SKILL.md has 588 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from cbrock84/headcount at commit 98d1c17, republished under its MIT licence (© cbrock84). 588 words, ~1,070 tokens.
Download SKILL.mdSave it as
.claude/skills/customer-onboarding-and-implementation/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- customer-onboarding-and-implementation
- description
- 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.
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 customer side. They need authority to make decisions and time genuinely allocated. If the customer cannot name that person, the project is at risk before it starts, and saying so early is a service.
Set a cadence from the beginning and hold it — a stalled implementation almost never announces itself; the calls quietly stop being attended.
Sequence for early value, not for completeness
Get one team doing one useful thing quickly, then widen. A phased approach produces a customer who has seen the product work, which changes every subsequent conversation.
The alternative — configure everything, migrate everything, launch to everyone — pushes all the value past a long window during which nothing works and the sponsor is defending the purchase.
Data and integrations are where the time actually goes
Both are routinely under-scoped because both depend on the customer's environment rather than
yours. Profile their data early; expect it to be worse than described. For the mechanics of moving
it, technology:data-migration covers the discipline.
Integration work depends on the customer's other vendors, their change windows, and their security review — none of which you control. Establish those constraints in week one rather than discovering them in week six.
Show full SKILL.md (212 more words)Show less
Train for the job, not for the product
Feature training teaches people what the buttons do. Task training teaches them how to do their actual work in the new system, and only the second changes behavior.
Train close to go-live, not months before, and train the people who will use it rather than only the project team. Leave behind material they can use without you.
Hand over deliberately
An implementation that ends when the project ends leaves the account with nobody. Hand over with context — what was configured and why, what was deferred, what is fragile, who the people are — and confirm the receiving side has it rather than assuming.
Sources
references/sources.md in this skill lists the outside authorities that settle the questions
here — what each one is authoritative for, and what you may do with it. Check them before
answering on anything they cover, and cite what you used. Most are free to read and not free
to reproduce; the use note on each is binding.
Never
- Start an implementation without written go-live criteria both sides agreed.
- Proceed without a named, empowered owner on the customer side.
- Discover the customer's integration and security constraints after committing to a date.
- Close an implementation on configuration complete rather than on people using it.
© cbrock84, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (references) in plugins/customer-experience/skills/customer-onboarding-and-implementation of cbrock84/headcount.
- SKILL.md
- references/sources.md
Open the folder on GitHubat commit 98d1c17
Compare with similar skills
Customer Onboarding And Implementation next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Customer Onboarding And Implementation this skillcbrock84/headcount | 2k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Cs Health Scorecardmohitagw15856/pm-claude-skills | 1.4k | — | ~2.4k | Automated safety check: Pass | MIT | |
| Youtube SearchZeroPointRepo/youtube-skills | 1k | 1 repos | ~1.8k | Automated safety check: Pass | MIT | |
| YtZeroPointRepo/youtube-skills | 1k | 1 repos | ~951 | Automated safety check: Pass | MIT | |
| Loki Modedavila7/claude-code-templates | 33k | 7 repos | ~7.1k | Automated safety check: Warn | MIT | |
| Account Researchexplorium-ai/gtm-skills | 185 | — | ~2.8k | Automated safety check: Pass | MIT |
Similar skills
Youtube Search
ZeroPointRepo/youtube-skills
A skill your agent uses when the user wants to find YouTube content on any topic: searching for videos or channels, finding creators who cover a subject, discovering tutorials, talks, or expert…
Yt
ZeroPointRepo/youtube-skills
A skill your agent uses when YouTube is relevant: pasted video links or IDs, @handles, quick video lookups, summaries, channel latest uploads, topic search, or any request involving YouTube content…
Loki Mode
davila7/claude-code-templates
Multi-agent autonomous startup system for Claude Code. An agent skill from davila7/claude-code-templates.
Account Research
explorium-ai/gtm-skills
Account research skill for Claude Code and Codex: generate a high-signal company intelligence brief including firmographics, technographics, funding history, hiring signals, business events, recent…
Expansion Retention
tech-leads-club/agent-skills
When the user wants to reduce churn, build expansion revenue, automate customer success, or optimize net revenue retention.
More from cbrock84/headcount
All 178 skills in this repoAgent Hierarchy
cbrock84/headcount
Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a…
Access And Identity
cbrock84/headcount
Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process.
Account Based Marketing
cbrock84/headcount
Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group…
Activation
cbrock84/headcount
Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone becomes a user or a lapsed account.
AI ML Governance
cbrock84/headcount
Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire.
AI Research Analyst
cbrock84/headcount
Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit.
Related
Categories
Questions about Customer Onboarding And Implementation
What does Customer Onboarding And Implementation do?
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…. Customer Onboarding And Implementation is an agent skill from cbrock84/headcount. 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.
When should I use Customer Onboarding And Implementation?
Customer Onboarding And Implementation fits situations like: tasks that involve Customer success.
How do I install Customer Onboarding And Implementation in Claude Code?
Run `npx skills add cbrock84/headcount --skill customer-onboarding-and-implementation -a claude-code`. Or copy the skill folder (plugins/customer-experience/skills/customer-onboarding-and-implementation in cbrock84/headcount) into .claude/skills/customer-onboarding-and-implementation in your project. Claude Code loads it when a task matches its description.
How do I install Customer Onboarding And Implementation in Codex?
Run `npx skills add cbrock84/headcount --skill customer-onboarding-and-implementation -a codex`. Or copy the skill folder (plugins/customer-experience/skills/customer-onboarding-and-implementation in cbrock84/headcount) into .agents/skills/customer-onboarding-and-implementation in your project. Codex loads it when a task matches its description.
Can I use Customer Onboarding And Implementation in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add cbrock84/headcount --skill customer-onboarding-and-implementation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/customer-onboarding-and-implementation, .gemini/skills/customer-onboarding-and-implementation, .github/skills/customer-onboarding-and-implementation and .opencode/skills/customer-onboarding-and-implementation in your project.
What does Customer Onboarding And Implementation need to run?
SKILL.md names no scripts, command-line tools or credentials: Customer Onboarding And Implementation is instructions for the agent only.
Does Customer Onboarding And Implementation access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Customer Onboarding And Implementation safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Customer Onboarding And Implementation use?
Customer Onboarding And Implementation is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Customer Onboarding And Implementation use?
About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 251 tokens, read only when the agent opens those files.
What are the alternatives to Customer Onboarding And Implementation?
Skills that share tags, products or a category with Customer Onboarding And Implementation: Cs Health Scorecard (mohitagw15856/pm-claude-skills, 1.4k stars), Youtube Search (ZeroPointRepo/youtube-skills, 1k stars), Yt (ZeroPointRepo/youtube-skills, 1k stars) and Loki Mode (davila7/claude-code-templates, 33k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Customer Onboarding And Implementation?
cbrock84 (a GitHub user) maintains it in cbrock84/headcount, which has 2,022 GitHub stars. The repository holds 178 skills in this directory. The repository was last updated on September 17, 2026.
Source: cbrock84/headcount on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.