Customer Status
techwolf-ai/ai-first-toolkit
Synthesised view of account health and activity for managers overseeing customer-facing teams (Sales, CS, Professional Services, Presales).
Design structured customer onboarding workflows with phased checklists, email templates, success milestones, and ownership assignments.
Install Onboarding Playbook Creation
$ npx skills add seb1n/awesome-ai-agent-skills --skill onboarding-playbook-creation -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install seb1n/awesome-ai-agent-skills onboarding-playbook-creation --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/seb1n/awesome-ai-agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/customer-success/onboarding-playbook-creation .claude/skills/onboarding-playbook-creation && 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 "onboarding-playbook-creation" agent skill from https://github.com/seb1n/awesome-ai-agent-skills/tree/main/customer-success/onboarding-playbook-creation into .claude/skills/onboarding-playbook-creation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "onboarding-playbook-creation", 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/seb1n/awesome-ai-agent-skills/tree/main/customer-success/onboarding-playbook-creationType 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 seb1n/awesome-ai-agent-skills --skill onboarding-playbook-creation -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install seb1n/awesome-ai-agent-skills onboarding-playbook-creation --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/seb1n/awesome-ai-agent-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/customer-success/onboarding-playbook-creation .agents/skills/onboarding-playbook-creation && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "onboarding-playbook-creation" agent skill from https://github.com/seb1n/awesome-ai-agent-skills/tree/main/customer-success/onboarding-playbook-creation into .agents/skills/onboarding-playbook-creation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "onboarding-playbook-creation", 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 seb1n/awesome-ai-agent-skills --skill onboarding-playbook-creation -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install seb1n/awesome-ai-agent-skills onboarding-playbook-creation --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/seb1n/awesome-ai-agent-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/customer-success/onboarding-playbook-creation .cursor/skills/onboarding-playbook-creation && 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 "onboarding-playbook-creation" agent skill from https://github.com/seb1n/awesome-ai-agent-skills/tree/main/customer-success/onboarding-playbook-creation into .cursor/skills/onboarding-playbook-creation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "onboarding-playbook-creation", 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/seb1n/awesome-ai-agent-skills.git --path customer-success/onboarding-playbook-creation--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 seb1n/awesome-ai-agent-skills --skill onboarding-playbook-creation -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install seb1n/awesome-ai-agent-skills onboarding-playbook-creation --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/seb1n/awesome-ai-agent-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/customer-success/onboarding-playbook-creation .gemini/skills/onboarding-playbook-creation && 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 "onboarding-playbook-creation" agent skill from https://github.com/seb1n/awesome-ai-agent-skills/tree/main/customer-success/onboarding-playbook-creation into .gemini/skills/onboarding-playbook-creation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "onboarding-playbook-creation", 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 seb1n/awesome-ai-agent-skills onboarding-playbook-creationInstalls 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 seb1n/awesome-ai-agent-skills --skill onboarding-playbook-creation -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/seb1n/awesome-ai-agent-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/customer-success/onboarding-playbook-creation .github/skills/onboarding-playbook-creation && 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 "onboarding-playbook-creation" agent skill from https://github.com/seb1n/awesome-ai-agent-skills/tree/main/customer-success/onboarding-playbook-creation into .github/skills/onboarding-playbook-creation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "onboarding-playbook-creation", 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 seb1n/awesome-ai-agent-skills --skill onboarding-playbook-creation -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install seb1n/awesome-ai-agent-skills onboarding-playbook-creation --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/seb1n/awesome-ai-agent-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/customer-success/onboarding-playbook-creation .opencode/skills/onboarding-playbook-creation && 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 "onboarding-playbook-creation" agent skill from https://github.com/seb1n/awesome-ai-agent-skills/tree/main/customer-success/onboarding-playbook-creation into .opencode/skills/onboarding-playbook-creation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "onboarding-playbook-creation", 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
onboarding-playbook-creation- GitHub stars
- 206
- Token cost
- ~2.4k tokens
- SKILL.md length
- 1,110 words
- Files
- 1
- Skills in repo
- 101
- Repo updated
- First seen
- Licence
- MIT
At a glance
Design structured customer onboarding workflows with phased checklists, email templates, success milestones, and ownership assignments.
- Works in 4 steps: Welcome (Day 0-3) → Setup (Day 4-10) → First Value (Day 11-20) → …
- The user requests onboarding playbook creation
- SKILL.md covers Workflow, Usage, Examples and Best Practices, plus 1 more section
- Calls go
What it does
Onboarding Playbook Creation is an agent skill from seb1n/awesome-ai-agent-skills. Design structured customer onboarding workflows with phased checklists, email templates, success milestones, and ownership assignments. Use when the user requests onboarding playbook creation or provides relevant inputs for this workflow.
Its SKILL.md is about 2.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Sales & Support, covering Customer success, Project management and Transactional email. The repository describes itself as: 103 ready-to-use AI agent skills for Claude Code, OpenAI Codex, Gemini CLI, Cursor, GitHub Copilot, Windsurf, and other Agent Skills-compatible tools. Complete SKILL.md… The licence is MIT.
When your agent uses it
- The user requests onboarding playbook creation
- Provides relevant inputs for this workflow
Example prompts
- “/onboarding-playbook-creation”
Requirements
- Node.js
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 75865a5. 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
Shell commands in SKILL.md call:
go
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
Onboarding Playbook Creation loads about 2.4k tokens when it runs. Until then it costs about 67 tokens; SKILL.md has 1,110 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 seb1n/awesome-ai-agent-skills at commit 75865a5, republished under its MIT licence (© seb1n). 1,110 words, ~2,431 tokens.
Download SKILL.mdSave it as
.claude/skills/onboarding-playbook-creation/SKILL.md (or your agent's skills folder).- name
- onboarding-playbook-creation
- description
- Design structured customer onboarding workflows with phased checklists, email templates, success milestones, and ownership assignments. Use when the user requests onboarding playbook creation or provides relevant inputs for this workflow.
- license
- MIT
- metadata.author
- community
- metadata.version
- 1.0
Onboarding Playbook Creation
Build comprehensive onboarding playbooks that guide new customers from signup to first value and sustained adoption. This skill produces phased workflows with explicit milestones, task checklists, communication templates, and clear ownership so that every customer follows a repeatable path to success regardless of which CSM is assigned.
Workflow
Define success milestones — Identify the 3-5 concrete outcomes that signal a customer has been successfully onboarded. These should be measurable product actions, not vague goals. Examples: "first report generated," "3+ team members active," "integration with primary data source complete." Tie each milestone to a business outcome the customer cares about to maintain alignment with their goals throughout the process.
Map onboarding phases — Structure the journey into distinct phases, each with a clear entry criteria, exit criteria, and expected duration. A standard B2B framework uses four phases: Welcome (Day 0-3) — account setup and introductions. Setup (Day 4-10) — technical configuration and data import. First Value (Day 11-20) — achieving the initial "aha moment" with the product. Adoption (Day 21-30) — expanding usage across the team and embedding into workflows.
Create task checklists per phase — Break each phase into specific, actionable tasks with owners (CSM, customer, SE, product). Each task should have an estimated duration, dependencies on prior tasks, and a definition of done. Include both internal tasks (create customer Slack channel, schedule kickoff) and customer-facing tasks (invite team members, connect data source).
Design communication templates — Write email and in-app message templates for each phase transition and key touchpoint. Include: welcome email, kickoff meeting agenda, mid-onboarding check-in, milestone celebration, risk alert (if a milestone is missed), and graduation email. Each template should have personalization tokens and conditional blocks based on customer segment.
Set timeline and ownership — Assign every task to a specific role and set due dates relative to the onboarding start date (Day 0). Create escalation rules for overdue tasks: 2 days overdue triggers a CSM nudge, 5 days overdue triggers a manager alert, 10 days overdue triggers a playbook reassessment call. Build in buffer for enterprise accounts that require procurement and security reviews.
Usage
Describe your product, customer segment, and onboarding goals. The agent will produce a complete playbook with phases, tasks, templates, and timelines.
Create a 30-day onboarding playbook for our B2B analytics platform. Target
segment is mid-market (50-500 employees). Key success milestones: connect a
data source, build first dashboard, share with 3+ team members.Examples
Example 1: 30-day B2B SaaS onboarding playbook
Input: B2B analytics platform, mid-market segment, 30-day onboarding window.
Output:
Phase 1: Welcome (Day 0-3)
| Task | Owner | Duration | Done When |
|---|---|---|---|
| Send welcome email with login credentials and quickstart guide | CSM | 15 min | Email delivered, customer opens |
| Create internal customer channel (#cs-acme-corp) | CSM | 5 min | Channel exists with team added |
| Schedule kickoff call for Day 2-3 | CSM | 10 min | Calendar invite accepted |
| Conduct kickoff call: align on goals, introduce support channels, confirm timeline | CSM + Customer | 45 min | Meeting notes shared, milestones agreed |
| Customer completes account profile and invites admin user | Customer | 20 min | Admin user active in product |
Phase 2: Setup (Day 4-10)
| Task | Owner | Duration | Done When |
|---|---|---|---|
| Connect primary data source (guided walkthrough) | Customer + SE | 1-2 hours | Data source shows "connected" status, initial sync complete |
| Verify data integrity — spot-check 3 metrics against source | SE | 30 min | Metrics match within 2% tolerance |
| Configure SSO/SAML if enterprise | SE | 1 hour | Team can login via company identity provider |
| Send Day 7 check-in email: "How's setup going?" | CSM (automated) | — | Email sent, reply monitored |
| Troubleshoot any integration blockers | SE | Varies | All blockers resolved, customer unblocked |
Phase 3: First Value (Day 11-20)
| Task | Owner | Duration | Done When |
|---|---|---|---|
| Build first dashboard using template library | Customer + CSM | 45 min | Dashboard created with live data |
| CSM reviews dashboard and suggests improvements | CSM | 30 min | Customer confirms dashboard meets their needs |
| Customer shares dashboard with 3 team members | Customer | 10 min | 3+ users have viewed the shared dashboard |
| Send milestone email: "You built your first dashboard!" | CSM (automated) | — | Email delivered with next steps |
| 15-minute adoption check-in call | CSM + Customer | 15 min | Usage patterns reviewed, expansion opportunities identified |
Show full SKILL.md (467 more words)Show less
Phase 4: Adoption (Day 21-30)
| Task | Owner | Duration | Done When |
|---|---|---|---|
| Customer creates 2 additional dashboards independently | Customer | Self-paced | 3+ total dashboards exist |
| Enable scheduled report delivery | Customer + CSM | 20 min | At least 1 scheduled report active |
| Conduct graduation call: review milestones, transition to ongoing CS | CSM + Customer | 30 min | Customer confirms self-sufficiency, success plan created |
| Internal handoff to ongoing CSM (if different from onboarding CSM) | CSM → CSM | 30 min | Handoff doc complete, new CSM introduced |
| Send graduation email with advanced resources and community invite | CSM (automated) | — | Email delivered |
Example 2: Developer tool self-serve onboarding checklist
Input: Developer CLI tool, self-serve motion, no CSM involvement.
Output:
In-App Onboarding Checklist (shown in dashboard sidebar)
Welcome to DevTool! Complete these steps to get up and running.
□ Install the CLI
Run: npm install -g @devtool/cli
Verify: devtool --version shows v3.x
□ Authenticate your account
Run: devtool auth login
Opens browser → approve → token saved locally
□ Connect your first repository
Run: devtool init in your project root
Creates .devtool.yml config file
□ Run your first scan
Run: devtool scan
View results at app.devtool.com/results
□ Fix your first issue
Click any finding → follow the suggested fix
Re-run devtool scan to verify
□ Invite a teammate
Go to Settings → Team → Invite
Enter their email to share project access
□ Set up CI integration
Add devtool scan to your CI pipeline
See: docs.devtool.com/ci for GitHub Actions, GitLab CI, and Jenkins examples
✓ You're all set! Explore advanced features →Companion email sequence (automated):
- Signup +0h: Welcome email with install instructions and link to interactive tutorial
- Signup +24h: "Did you run your first scan?" — re-engagement if install step incomplete
- Signup +72h: "Here's what teams like yours find most valuable" — use case inspiration
- Signup +7d: "Invite your team" — social proof of team adoption stats
- Signup +14d: "Ready for CI?" — guide to pipeline integration with ROI calculator
Best Practices
- Optimize for time-to-first-value above all else — every task that doesn't directly contribute to the customer's first success moment should be deferred to post-onboarding.
- Build separate playbook variants per segment (SMB self-serve, mid-market guided, enterprise high-touch) rather than one generic playbook with conditional branches.
- Instrument every milestone as a product event so you can measure onboarding completion rates, identify drop-off points, and trigger automated interventions.
- Include "what good looks like" benchmarks for each phase — e.g., "80% of customers connect a data source by Day 7" — so CSMs know when an account is falling behind.
- Review and update the playbook quarterly based on completion rate data, customer feedback, and product changes.
- Assign a playbook owner (usually a CS Ops lead) who is accountable for maintaining the playbook, training new CSMs, and iterating on it.
Edge Cases
- Customer goes dark during onboarding — If no response to 2 consecutive outreach attempts, trigger a "re-engagement" branch: peer CSM tries alternate contact, AE reaches out to economic buyer, final "we're here when you're ready" email at Day 25.
- Customer wants to skip phases — Technical customers who have already self-configured should be able to fast-track. Validate their setup meets the milestone criteria and advance them to the appropriate phase.
- Multi-product onboarding — When a customer purchases multiple products, stagger onboarding to avoid overwhelming them. Complete Product A onboarding before starting Product B, with a 1-week buffer.
- Champion leaves mid-onboarding — Immediately identify a new point of contact. Offer to restart the kickoff call with the replacement to rebuild context and alignment.
- Onboarding takes longer than planned — If Phase 2 (Setup) extends beyond its window due to technical complexity, do not compress Phase 3 and 4. Extend the total timeline and communicate the revised schedule to all stakeholders.
© seb1n, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in customer-success/onboarding-playbook-creation of seb1n/awesome-ai-agent-skills.
Open the folder on GitHubat commit 75865a5
Compare with similar skills
Onboarding Playbook Creation 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 |
|---|---|---|---|---|---|---|
| Onboarding Playbook Creation this skillseb1n/awesome-ai-agent-skills | 206 | — | ~2.4k | Automated safety check: Pass | MIT | |
| Customer Statustechwolf-ai/ai-first-toolkit | 132 | — | ~1.2k | Automated safety check: Pass | MIT | |
| HTML Ppt Zhangzara Daisy Daysnexu-io/open-design | 100k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Customer Success Planmohitagw15856/pm-claude-skills | 1.4k | — | ~2.6k | Automated safety check: Pass | MIT | |
| Support Feedback Prioritizationamplitude/builder-skills | 159 | — | ~949 | Automated safety check: Pass | None | |
| Statement Of Workmohitagw15856/pm-claude-skills | 1.4k | — | ~980 | Automated safety check: Pass | MIT |
Similar skills
HTML Ppt Zhangzara Daisy Days
nexu-io/open-design
A customer-success workshop onboarding users to a project-management app — the first-value path and the habits that retain.
Customer Success Plan
mohitagw15856/pm-claude-skills
Build a joint customer success plan for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Support Feedback Prioritization
amplitude/builder-skills
Pull Intercom tickets and Slack support messages from the past 7 days, classify each signal, enrich with CRM data (ARR, plan, renewal), score by customer value and churn risk, and output a tiered…
Statement Of Work
mohitagw15856/pm-claude-skills
Write a tight Statement of Work (SOW) that prevents scope creep and payment disputes.
Research Proposal Development
hashgraph-online/awesome-codex-plugins
Develop research proposals with solicitation alignment, reviewer-focused logic, evidence-bounded preliminary results, milestones, risks, and compelling figures.
More from seb1n/awesome-ai-agent-skills
All 101 skills in this repoAgent Red Teaming
seb1n/awesome-ai-agent-skills
Plan, execute, document, and retest authorized security assessments of AI agents and multi-agent workflows using safe adversarial cases, synthetic identities, canaries, and evidence-based findings.
Eu AI Act Readiness
seb1n/awesome-ai-agent-skills
Build a preliminary, evidence-based EU AI Act readiness assessment across AI-system inventory, territorial scope, operator roles, prohibited-practice screening, risk classification, transparency…
Human In The Loop
seb1n/awesome-ai-agent-skills
Design and verify auditable human oversight, approval gates, escalation paths, and safe state transitions for AI agent workflows.
MCP Server Building
seb1n/awesome-ai-agent-skills
Design, implement, harden, and verify Model Context Protocol (MCP) servers with precise tool contracts, least-privilege authorization, safe transports, structured errors, and interoperability tests.
PDF Processing
seb1n/awesome-ai-agent-skills
Inspect, extract, OCR, create, merge, split, reorder, rotate, annotate, fill, redact, compress, secure, and verify PDF documents while preserving source files and visual fidelity.
Skill Supply Chain Audit
seb1n/awesome-ai-agent-skills
Audit agent skills, plugins, prompts, manifests, scripts, dependencies, and bundled assets for provenance, prompt-injection, permission, execution, exfiltration, persistence, and update risk.
Related
Questions about Onboarding Playbook Creation
What does Onboarding Playbook Creation do?
Design structured customer onboarding workflows with phased checklists, email templates, success milestones, and ownership assignments. Onboarding Playbook Creation is an agent skill from seb1n/awesome-ai-agent-skills. Design structured customer onboarding workflows with phased checklists, email templates, success milestones, and ownership assignments.
When should I use Onboarding Playbook Creation?
Onboarding Playbook Creation fits situations like: the user requests onboarding playbook creation; provides relevant inputs for this workflow.
How do I install Onboarding Playbook Creation in Claude Code?
Run `npx skills add seb1n/awesome-ai-agent-skills --skill onboarding-playbook-creation -a claude-code`. Or copy the skill folder (customer-success/onboarding-playbook-creation in seb1n/awesome-ai-agent-skills) into .claude/skills/onboarding-playbook-creation in your project. Claude Code loads it when a task matches its description.
How do I install Onboarding Playbook Creation in Codex?
Run `npx skills add seb1n/awesome-ai-agent-skills --skill onboarding-playbook-creation -a codex`. Or copy the skill folder (customer-success/onboarding-playbook-creation in seb1n/awesome-ai-agent-skills) into .agents/skills/onboarding-playbook-creation in your project. Codex loads it when a task matches its description.
Can I use Onboarding Playbook Creation 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 seb1n/awesome-ai-agent-skills --skill onboarding-playbook-creation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/onboarding-playbook-creation, .gemini/skills/onboarding-playbook-creation, .github/skills/onboarding-playbook-creation and .opencode/skills/onboarding-playbook-creation in your project.
What does Onboarding Playbook Creation need to run?
Going by SKILL.md and its folder, Onboarding Playbook Creation needs the command-line tools its instructions call (go). Our summary lists: Node.js.
Does Onboarding Playbook Creation 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 Onboarding Playbook Creation 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 Onboarding Playbook Creation use?
Onboarding Playbook Creation is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Onboarding Playbook Creation use?
About 2.4k tokens (SKILL.md is roughly 9.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Onboarding Playbook Creation?
Skills that share tags, products or a category with Onboarding Playbook Creation: Customer Status (techwolf-ai/ai-first-toolkit, 132 stars), HTML Ppt Zhangzara Daisy Days (nexu-io/open-design, 100k stars), Customer Success Plan (mohitagw15856/pm-claude-skills, 1.4k stars) and Support Feedback Prioritization (amplitude/builder-skills, 159 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Onboarding Playbook Creation?
seb1n (a GitHub user) maintains it in seb1n/awesome-ai-agent-skills, which has 206 GitHub stars. The repository holds 101 skills in this directory. The repository was last updated on August 9, 2026.
Source: seb1n/awesome-ai-agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.