Loading...
Loading...
Found 491 Skills
Create an end-to-end customer journey map with stages, touchpoints, emotions, pain points, and opportunities. Use when mapping the customer experience, identifying friction points, improving onboarding, or visualizing the user journey.
Personalized setup and onboarding wizard. Use when setting up OrchestKit for a new project, configuring plugins, or generating a readiness score and improvement plan.
Review recent repository changes and decide whether AGENTS.md or other project-level documentation needs a high-level update. Use when finishing a feature, fix, refactor, or architectural change and you need to preserve repo-shaping guidance such as new patterns, constraints, workflows, validation rules, or onboarding-relevant gotchas without adding low-level implementation detail.
Generate a personalized SOUL.md through a warm, adaptive onboarding conversation. Trigger when the user wants to create, set up, or initialize their AI partner's identity — e.g., "create my SOUL.md", "bootstrap my agent", "set up my AI partner", "define who you are", "let's do onboarding", "personalize this AI", "make you mine", or when a SOUL.md is missing. Also trigger for updates: "update my SOUL.md", "change my AI's personality", "tweak the soul".
Register and configure an AI agent on OpenAnt. Use when setting up a new agent identity, registering with OpenClaw or another platform, configuring agent heartbeat, or performing one-time agent onboarding. Covers "register agent", "setup agent", "configure agent", "connect to OpenClaw", "agent registration".
Deep-dive into customer empathy and user journey thinking. Use when designing onboarding, improving UX, planning features, or trying to understand how to delight users faster.
Analyze an unfamiliar repository and explain what it does, how it runs, what architectural choices define it, where the important code lives, and what deserves deeper inspection next. Use this whenever a user has just cloned a repo, wants onboarding help, asks for a repo walkthrough, or needs a reliable first-pass architecture analysis.
WeChat Pay basic payment solution, covering payment, refund bills, profit sharing, merchant onboarding, and account opening willingness confirmation, providing five core capabilities: product selection, code examples, quick business reference, quality assessment, and troubleshooting. Use when user mentions "JSAPI payment", "APP payment", "H5 payment", "Native payment", Mini Program payment, payment code payment, combined payment, invoke payment, payment callback, order refund, download bill, account reconciliation, service provider mode, profit sharing, special merchant onboarding, account opening willingness confirmation, or asks to "recommend payment method", "provide payment interface code examples", "troubleshoot payment or refund issues".
Founder onboarding interview that captures company context across 7 dimensions. Invoke with /cs:setup for initial interview or /cs:update for quarterly refresh. Generates ~/.claude/company-context.md used by all C-suite advisor skills.
First onboarding and scaffolding creator for cheat-on-content. Unified process - all users follow the same 5-stage closed-loop, with the only difference being that users who have posted videos will have an extra step during init: fetch existing videos to build historical context (used for subsequent cheat-seed to provide more tailored topic suggestions and more accurate baselines). Trigger phrases: "Initialize" / "init" / "First use" / "I'm a new user" / "setup cheat-on-content". **Must be executed during the user's first session; other sub-skills will automatically route to this when .cheat-state.json does not exist.**
Legacy-project style inheritance skill. Use when the user types /inherit-legacy-style, or when onboarding an AI coding agent onto a hand-written legacy project and you need to prevent "style drift" (the model imposing its pretrained mainstream idioms onto the project). Language- and framework-agnostic — it aligns meta-architecture only, not syntax. Once run, it becomes a behavioral constraint on all subsequent coding tasks. Do NOT use for pure research or one-off questions unrelated to code-style alignment.
Plan user journeys, onboarding flows, engagement strategies, and day-to-day workflows for digital health products.