Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/erphq/skills/user-onboardingnpx skills add erphq/skills --skill user-onboardinggit clone --depth 1 https://github.com/erphq/skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/erphq/skills/user-onboarding)<a href="https://agentmods.dev/skills/erphq/skills/user-onboarding"><img src="https://agentmods.dev/badge/skills/erphq/skills/user-onboarding.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00039 | $0.09628 |
| Opus 5 | $0.00019 | $0.04814 |
| Sonnet 5 | $0.00008 | $0.01926 |
| Haiku 4.5 | $0.00004 | $0.00963 |
Grade A, and why
user-onboarding scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 566 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Onboarding
Size-Tier Scope
This variant scales the operating pattern for organizations under 100 people. Keep the controls lightweight, favor owner-led approvals, and introduce automation only where it removes recurring manual work without adding governance overhead.
Purpose
An enterprise application delivers zero value until users adopt it. Onboarding is not a one-time event -- it is a structured program that takes users from awareness through competency to proficiency. The gap between a technically correct system and a successfully adopted system is almost always a training and change management gap, not a technology gap.
Use this skill when a builder needs to:
- Analyze training needs by role, process, and change impact
- Design and produce training content (guides, videos, walkthroughs, quick reference cards)
- Integrate with a Learning Management System (LMS)
- Track adoption and measure time-to-competency
- Build a super-user / champion network
- Design contextual in-app help and knowledge base structure
- Address change resistance proactively
Key Concepts
Training Needs Analysis
A structured assessment that determines what each user group needs to learn, how much change they face, and what training format will be most effective.
Dimensions of analysis:
- By role: Different roles use different parts of the system. An AP clerk needs deep training on invoice processing; a department manager needs training on approvals and reports. Map each role to the specific modules, screens, and processes they will use.
- By process: Each business process touches multiple roles. Map the end-to-end process (e.g., procure-to-pay) and identify every role that participates. Training should follow process flow, not module boundaries.
- By change impact: Assess how much each role's daily work changes. Roles with high change (entirely new process, new tool, new data) need more intensive training. Roles with low change (same process, new interface) need orientation and quick reference.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 5d ago First seen · 566 lines · 39 tokens per session scan A daa946e2845b
user-onboarding is a skill published in the GitHub repository erphq/skills (2 stars, last pushed 16d ago), licensed MIT. It adds 39 tokens to every session and 9,628 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
skill-library-mission
Build a project skill library in .claude/skills/ via discovery, parallel authoring, and review. Use when packaging tribal knowledge. Do not use for one skill.
tutorial-patterns
Tutorial and how-to guide patterns for progressive learning experiences. Covers Diátaxis tutorial/how-to structure, quickstart design, step-by-step walkthrough writing, anti-patterns, and progressive disclosure. Use proactively when writing tutorials, how-to guides, getting-started docs, or README files.
cdc-clear-communication
Draft, rewrite, or audit evidence-based public-health communication using an independently expressed interpretation of the CDC Clear Communication Index. Use for patient explanations, health campaigns, risk and emergency messages, public-safety notices, and educational health material that must make one message and…
absolute-docs
Diátaxis-driven documentation for AI coding agents: write, improve, or audit tutorials, how-tos, reference, explanation, and developer docs (README, CONTRIBUTING, ADRs). Detects the docs stack; gates on the outline before writing prose; verifies every claim against the code before it ships. Triggers on "absolute…
com.googleapis.developerknowledge-mcp-mcp
Provides access to Google's public developer documentation.
seeds-regenerative-inquiry-cycle
Design a SEEDS regenerative inquiry cycle connecting place-based learning to ecological awareness for young learners. Use when building early childhood or primary inquiry around ecosystems and community.