Loading...
Loading...
Found 10,838 Skills
Use when an ops leader (Director of CX, Head of Support, VP Ops, Head of BizOps, Head of IT ops, Head of Finance ops) is sizing ops capacity, building a headcount plan, modeling utilization risk, planning Q3 capacity or annual support capacity, or designing CS coverage — and needs Erlang-C queueing math, P90 demand sizing, shrinkage-adjusted FTE, manager-trigger thresholds, and a quarterly hiring sequence with ramp + attrition. Apply when sustained team utilization is above 80% or when the team is growing >50% in 12 months. Run before committing the headcount budget. This is NOT engineering capacity (see vpe-advisor for DORA + cycle time) and NOT strategic 3-year workforce planning (see chro-advisor).
Use when the agent wants to define, list, inspect, or execute GUI macros via the MacroCLI CLI. Macros are parameterized, CLI-callable workflows — the agent invokes `macro run <name>` and the system handles backend routing (plugin, file transform, accessibility, compiled GUI replay).
Feishu Real-time Event Subscription (WebSocket). Use `event list` to view supported EventKeys; `event schema` to check event payload/scope; `event consume` to start long-connection subscription, where event streams are written to stdout in NDJSON format (blocking, one process subscribes to one EventKey); `event status` to view active local consume processes; `event stop` to terminate consume processes by PID / EventKey / --all. Supports over 22 EventKeys (including IM message receive/read/recall/reaction, group member changes, contact employee changes, calendar changes, cloud disk title/collaborator changes, approval instances and tasks, VC meeting start/end). Status files: ~/.feishu-cli/events/<app_id>/bus.json + flock file lock + WebSocket auto-reconnect. This skill is applicable when users request "listen to Feishu events", "real-time message event reception", "approval callback subscription", "event stream", "WebSocket long-connection listening", "event consume", "event list / schema / status / stop", "AI Agent bot real-time response". Note: This skill only handles subscription; for event webhook business logic (pushing to Feishu messages/writing to multidimensional tables), please use with feishu-cli-msg / feishu-cli-bitable.
Google search MCP server with academic PDF extraction, no API key required, CAPTCHA recovery, and parallel search capabilities
Configure worker RBAC, filtered discovery, FORBIDDEN errors, registration hooks, auth functions, and safe browser/public worker-manager listeners in iii. Use when configuring permissions, tenant isolation, exposed functions, browser-safe worker access, or denied invocation behavior.
Analyze cloud costs, find optimization opportunities, and track anomalies using Harness CCM via MCP. Use when user says "cloud costs", "analyze costs", "cost optimization", "reduce spending", "cost report", or asks about cloud bills.
Official Roblox Studio MCP server tools reference. What each tool does, how to use it, reliability patterns, and workflows for script editing, building, playtesting, and debugging. Use when the AI has an MCP connection to Roblox Studio.
Comet — OpenSpec + Superpowers Binary Star Development Workflow. Initiate with /comet, which automatically detects phases and distributes to subcommands. Five phases: Open → Deep Design → Plan & Build → Verify & Finalize → Archive.
Knowledge comics (知识漫画): educational, biography, tutorial.
Use when planning and synthesizing product/user research as a method-and-repository discipline — selecting the right method for the goal (generative interviews vs usability test vs concept test vs validation), computing method-based saturation/sample size with an explicit confidence level, or synthesizing coded observations into insights while flagging single-source anecdotes. Never fabricates user insight; an insight requires recurrence across independent participants. Distinct from product-team/ux-researcher-designer (persona/journey artifacts), product-discovery (discovery-sprint planning), and experiment-designer (live A/B) — this is the research-ops method + insight-repository layer.
Identify sector rotation, capital switching and style migration directions, help judge the current market main line, compensatory growth directions and rotation sustainability. Suitable for market style observation, sector comparison, post-market review and next-stage main line judgment.
When the user wants to build or improve a sales bot's ability to avoid making claims that create liability. Also use when the user mentions "compliance," "legal risk," "claim avoidance," "regulated industries," or "liability prevention."