Onboarding Playbook Creation
seb1n/awesome-ai-agent-skills
Design structured customer onboarding workflows with phased checklists, email templates, success milestones, and ownership assignments.
Synthesised view of account health and activity for managers overseeing customer-facing teams (Sales, CS, Professional Services, Presales).
Install Customer Status
$ npx skills add techwolf-ai/ai-first-toolkit --skill customer-status -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install techwolf-ai/ai-first-toolkit customer-status --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/techwolf-ai/ai-first-toolkit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/people-management/skills/customer-status .claude/skills/customer-status && 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-status" agent skill from https://github.com/techwolf-ai/ai-first-toolkit/tree/main/plugins/people-management/skills/customer-status into .claude/skills/customer-status/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customer-status", 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/techwolf-ai/ai-first-toolkit/tree/main/plugins/people-management/skills/customer-statusType 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 techwolf-ai/ai-first-toolkit --skill customer-status -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install techwolf-ai/ai-first-toolkit customer-status --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/techwolf-ai/ai-first-toolkit.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/people-management/skills/customer-status .agents/skills/customer-status && 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-status" agent skill from https://github.com/techwolf-ai/ai-first-toolkit/tree/main/plugins/people-management/skills/customer-status into .agents/skills/customer-status/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customer-status", 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 techwolf-ai/ai-first-toolkit --skill customer-status -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install techwolf-ai/ai-first-toolkit customer-status --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/techwolf-ai/ai-first-toolkit.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/people-management/skills/customer-status .cursor/skills/customer-status && 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-status" agent skill from https://github.com/techwolf-ai/ai-first-toolkit/tree/main/plugins/people-management/skills/customer-status into .cursor/skills/customer-status/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customer-status", 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/techwolf-ai/ai-first-toolkit.git --path plugins/people-management/skills/customer-status--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 techwolf-ai/ai-first-toolkit --skill customer-status -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install techwolf-ai/ai-first-toolkit customer-status --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/techwolf-ai/ai-first-toolkit.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/people-management/skills/customer-status .gemini/skills/customer-status && 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-status" agent skill from https://github.com/techwolf-ai/ai-first-toolkit/tree/main/plugins/people-management/skills/customer-status into .gemini/skills/customer-status/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customer-status", 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 techwolf-ai/ai-first-toolkit customer-statusInstalls 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 techwolf-ai/ai-first-toolkit --skill customer-status -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/techwolf-ai/ai-first-toolkit.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/people-management/skills/customer-status .github/skills/customer-status && 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-status" agent skill from https://github.com/techwolf-ai/ai-first-toolkit/tree/main/plugins/people-management/skills/customer-status into .github/skills/customer-status/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customer-status", 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 techwolf-ai/ai-first-toolkit --skill customer-status -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install techwolf-ai/ai-first-toolkit customer-status --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/techwolf-ai/ai-first-toolkit.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/people-management/skills/customer-status .opencode/skills/customer-status && 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-status" agent skill from https://github.com/techwolf-ai/ai-first-toolkit/tree/main/plugins/people-management/skills/customer-status into .opencode/skills/customer-status/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customer-status", 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-status- GitHub stars
- 132
- Token cost
- ~1.2k tokens
- SKILL.md length
- 538 words
- Files
- 3 (incl. references)
- Skills in repo
- 29
- Repo updated
- First seen
- Licence
- MIT
At a glance
Synthesised view of account health and activity for managers overseeing customer-facing teams (Sales, CS, Professional Services, Presales).
- Works in 7 steps: Load Context → Identify Active Accounts → Scan Per Account → …
- Tasks that involve Customer success
- SKILL.md covers When to Use, Instructions and Important Notes
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Customer Status is an agent skill from techwolf-ai/ai-first-toolkit. Synthesised view of account health and activity for managers overseeing customer-facing teams (Sales, CS, Professional Services, Presales). Scans project channels, email threads, and Notion pages to surface status, risks, and upcoming milestones, without requiring the manager to trawl through individual channels. Supports proactive account management.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/operating-principles.md` and `references/output-template.md`).
It sits in Sales & Support, covering Customer success and Project management. It works with Notion. The repository describes itself as: Open-source Claude Code skills and Codex skills for AI-first work. Audit, re-engineer, and bootstrap projects with AI-first design principles. The licence is MIT.
When your agent uses it
- Tasks that involve Customer success
- Tasks that involve Project management
Example prompts
- “/customer-status”
Workflow steps
7 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 2ee7841. 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 Status loads about 1.2k tokens when it runs, and up to ~2k if it reads all its reference files. Until then it costs about 92 tokens; SKILL.md has 538 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 techwolf-ai/ai-first-toolkit at commit 2ee7841, republished under its MIT licence (© techwolf-ai). 538 words, ~1,228 tokens.
Download SKILL.mdSave it as
.claude/skills/customer-status/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- customer-status
- description
- Synthesised view of account health and activity for managers overseeing customer-facing teams (Sales, CS, Professional Services, Presales). Scans project channels, email threads, and Notion pages to surface status, risks, and upcoming milestones, without requiring the manager to trawl through individual channels. Supports proactive account management.
Customer Status Overview
Principle: "Narrow scope, high impact." One synthesised view across all accounts, so you can spot what needs attention without channel-hopping.
Produces a dashboard-style overview of active customer accounts and internal projects for the manager's team.
When to Use
- Weekly check-in on account health
- Before leadership meetings where customer status is discussed
- When the manager says "how are our accounts?", "customer status", "any customer risks?"
- Can be filtered: "customer status for [account]", "customer status for [team member]'s accounts"
Instructions
If any MCP connector is unavailable, follow the connector unavailability protocol in references/operating-principles.md.
1. Load Context
Read from manager-context/:
sources.md: customer/project channels, account mappingsmanager-profile.md: team members and their account assignmentsteam/: individual team member profiles and project assignments
If no manager-context exists:
⚠️ No manager context found. Run /setup first so I know which accounts and channels to monitor.
I can still search broadly, but results will be less targeted.2. Identify Active Accounts
From manager-context, get the list of active accounts/projects and their:
- Slack channels
- Key contacts (team member and customer-side)
- Notion project pages
- Current delivery phase (if documented)
If filtering by account or team member, narrow the scope.
3. Scan Per Account
For each active account, gather:
Slack (last 7 days):
- Recent messages in the project/customer channel
- Volume of activity (high/normal/low compared to usual)
- Any messages with escalation signals: "blocked", "risk", "delayed", "urgent", "escalate", "concerned"
- Any positive signals: "shipped", "live", "approved", "happy", "great feedback"
- Most recent message timestamp (to detect silent accounts)
Gmail (last 14 days):
- Email threads related to this customer
- Any emails with escalation or risk language
- Communication frequency
Notion:
- Project/customer status page (if documented in sources.md)
- Last updated date
- Any documented risks or decisions
Google Drive:
- Recent shared documents (SOWs, proposals, reports)
4. Assess Health Signal
For each account, determine a health signal based on evidence:
- 🟢 Healthy: Regular activity, positive signals, no escalations, milestones on track
- 🟡 Attention: Some risk signals, decreased activity, upcoming deadline, stale documentation
- 🔴 At Risk: Escalation language, blocked progress, customer complaints, silence for >5 days on active project
Important: These are signals, not diagnoses. Always show the evidence that led to the assessment.
Show full SKILL.md (213 more words)Show less
5. Produce the Overview
Read references/output-template.md for the full output template structure.
6. Sub-Agent Review
Spawn a sub-agent to review the customer status overview with fresh eyes. The reviewer should:
- Check that health signal assessments are evidence-based: every red/yellow rating should cite specific signals, not just absence of activity.
- Verify that silence is not over-interpreted: a quiet channel on a stable account is not the same as a quiet channel on an active delivery.
- Check for team member workload signals: if one person owns many flagged accounts, note it.
- Flag any accounts where the evidence is thin enough that the health signal might be misleading.
Incorporate the reviewer's feedback before presenting the final overview.
7. Present and Offer Follow-Up
Here's your customer status overview. Want me to:
- Dig deeper into any specific account?
- Prep for a conversation with [team member] about [account]?
- Check email threads for a specific customer?Important Notes
Read references/operating-principles.md for shared operating principles (data scope, DM flagging, signals vs diagnoses, connector unavailability).
Additional notes specific to this skill:
- Don't alarm unnecessarily. Silence on a channel might mean things are running smoothly. Combine multiple signals before flagging red.
- Recency matters. Flag any account where project docs haven't been updated in >2 weeks on active projects.
- Respect customer confidentiality. Summarise, don't reproduce customer communications verbatim. When surfacing DM content, flag it as
(from DM). - Team member context. If a team member owns multiple accounts, note that, they might be spread thin.
© techwolf-ai, 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 2 other files (references) in plugins/people-management/skills/customer-status of techwolf-ai/ai-first-toolkit.
- SKILL.md
- references/operating-principles.md
- references/output-template.md
Open the folder on GitHubat commit 2ee7841
Compare with similar skills
Customer Status 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 Status this skilltechwolf-ai/ai-first-toolkit | 132 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Onboarding Playbook Creationseb1n/awesome-ai-agent-skills | 206 | — | ~2.4k | 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 | |
| Integrationsbutterbase-ai/butterbase-skills | 534 | — | ~832 | Automated safety check: Pass | MIT | |
| Support Feedback Prioritizationamplitude/builder-skills | 159 | — | ~949 | Automated safety check: Pass | None |
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.
Integrations
butterbase-ai/butterbase-skills
Use BEFORE recommending or installing any third-party SaaS SDK for email (Resend, SendGrid, Postmark, Mailgun), SMS (Twilio), messaging (Slack), calendar (Google Calendar), CRM (HubSpot…
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.
More from techwolf-ai/ai-first-toolkit
All 29 skills in this repoTask Profile
techwolf-ai/ai-first-toolkit
Mine the user's Claude Code + Cowork session history into a structured task profile, what they do with AI, how often, how successfully where friction lives, then propose atomic skills that would…
Session Search
techwolf-ai/ai-first-toolkit
Find context from past Claude Code (CLI) and Claude Cowork (desktop) sessions on this Mac.
Token Doctor
techwolf-ai/ai-first-toolkit
Personal diagnosis of where your Claude Code + Cowork spend goes.
Write Blog Post
techwolf-ai/ai-first-toolkit
Write or develop a blog post. An agent skill from techwolf-ai/ai-first-toolkit.
Write Opinion
techwolf-ai/ai-first-toolkit
Write or develop an opinion piece (opiniestuk/op-ed). An agent skill from techwolf-ai/ai-first-toolkit.
AI Firstify
techwolf-ai/ai-first-toolkit
Analyze, re-engineer, or bootstrap projects to align with AI-first design principles.
Related
Works with
Questions about Customer Status
What does Customer Status do?
Synthesised view of account health and activity for managers overseeing customer-facing teams (Sales, CS, Professional Services, Presales). Customer Status is an agent skill from techwolf-ai/ai-first-toolkit. Synthesised view of account health and activity for managers overseeing customer-facing teams (Sales, CS, Professional Services, Presales).
When should I use Customer Status?
Customer Status fits situations like: tasks that involve Customer success; tasks that involve Project management.
How do I install Customer Status in Claude Code?
Run `npx skills add techwolf-ai/ai-first-toolkit --skill customer-status -a claude-code`. Or copy the skill folder (plugins/people-management/skills/customer-status in techwolf-ai/ai-first-toolkit) into .claude/skills/customer-status in your project. Claude Code loads it when a task matches its description.
How do I install Customer Status in Codex?
Run `npx skills add techwolf-ai/ai-first-toolkit --skill customer-status -a codex`. Or copy the skill folder (plugins/people-management/skills/customer-status in techwolf-ai/ai-first-toolkit) into .agents/skills/customer-status in your project. Codex loads it when a task matches its description.
Can I use Customer Status 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 techwolf-ai/ai-first-toolkit --skill customer-status -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-status, .gemini/skills/customer-status, .github/skills/customer-status and .opencode/skills/customer-status in your project.
What does Customer Status need to run?
SKILL.md names no scripts, command-line tools or credentials: Customer Status is instructions for the agent only.
Does Customer Status 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 Status 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 Status use?
Customer Status 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 Status use?
About 1.2k tokens (SKILL.md is roughly 4.9k 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 804 tokens, read only when the agent opens those files.
What are the alternatives to Customer Status?
Skills that share tags, products or a category with Customer Status: Onboarding Playbook Creation (seb1n/awesome-ai-agent-skills, 206 stars), HTML Ppt Zhangzara Daisy Days (nexu-io/open-design, 100k stars), Customer Success Plan (mohitagw15856/pm-claude-skills, 1.4k stars) and Integrations (butterbase-ai/butterbase-skills, 534 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Customer Status?
techwolf-ai (a GitHub organization) maintains it in techwolf-ai/ai-first-toolkit, which has 132 GitHub stars. The repository holds 29 skills in this directory. The repository was last updated on September 29, 2026.
Source: techwolf-ai/ai-first-toolkit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.