Loading...
Loading...
Found 821 Skills
Help users discover and install Claude Code skills. Use this skill when users ask "how to do X", "find a skill that can do X", "are there any skills that can..." or want to expand AI capabilities. Search, verify quality, and assist with installation through the skills.sh ecosystem.
Generate new screens from text prompts or images, edit existing screens with prompts and design system tokens, and generate design variants using Stitch MCP. Includes prompt enhancement pipeline, design mappings, professional UI/UX terminology, design tokens and theme system capabilities.
Design and implement workflow automation with task routing approval chains and SLA monitoring for securities operations. Use when building a new operational workflow for account opening maintenance transfers or corporate actions, implementing task routing logic based on type priority or capacity, designing multi-level approval chains with dollar thresholds and delegation of authority, defining escalation rules for aging work items approaching SLA breach, selecting a workflow engine or BPM platform like Camunda Pega or ServiceNow, modeling an operational process as a state machine with defined transitions, adding audit trail and logging for SEC Rule 17a-3 or FINRA supervisory obligations, migrating from email-and-spreadsheet tracking to a structured workflow system, or measuring cycle time throughput queue depth and rework rate.
Provides image recognition capabilities for non-multimodal models (such as pure text models like deepseek-v4-pro, GLM-5.1, mimo-v2.5-pro, etc.). This skill is automatically triggered when the main model cannot recognize images, when users send screenshots/design drafts/UI screenshots for analysis, or when users say 'Look at this image', 'Analyze this screenshot', 'What's wrong with this image'. It also applies to any scenario where users paste images but the current model does not support image input. Supports simultaneous recognition of multiple images, with primary-backup fallback achieved by configuring multiple image recognition models. It can also be manually triggered using the commands /skill:vision-support or /vision. Iron Rule: The models configured for this skill are only used for image content recognition and will never participate in main logical reasoning. Note: If the current model is itself a multimodal model (such as Claude Sonnet 4, GPT-4o, Gemini, etc. that can directly recognize images), do not use this skill; let the main model recognize directly.
Guides management consulting-style work—engagement framing, hypothesis-driven problem structuring, issue trees, business cases, operating model and capability design, strategic options analysis, workshop facilitation, and executive recommendations (not legal advice). Use when diagnosing a business problem, structuring a strategy or transformation initiative, building a business case for leadership, designing target operating models, preparing steerCo or board recommendations, or advising on build-vs-buy and portfolio priorities—not for detailed requirements/BRDs (business-analyst), multi-team delivery tracking (technical-program-manager), contract negotiation (commercial-counsel), revenue accounting (senior-revenue-accountant), applied AI architecture (applied-ai-architect-commercial-enterprise), or system ADRs (senior-system-architecture). Canvas/TAM: business-model-researcher. Comms: communication-lead. M&A closing: transaction-manager. M&A principal/IC: transaction-principal.
Give your AI agents capabilities through tools (function calling). Helps you identify what your AI needs to do, create tool definitions, and attach them to AI Config variations.
Comprehensive SAP Joule CLI (formerly sapdas CLI) assistant for managing digital assistants from the command line — compiling capabilities, deploying assistants, running BDD tests, linting, and troubleshooting errors. Use this skill whenever the user mentions "joule cli", "sapdas", "joule compile", "joule deploy", "joule test", "joule login", "joule lint", digital assistant deployment, capability compilation, DAAR files, RTA artifacts, or any task involving the Joule command line interface — even if they just say something like "deploy my assistant" or "how do I log in to Joule from the terminal". Also trigger when the user asks about testing Joule capabilities with Cucumber, linking AI assistants, managing deployed assistants, or automating Joule workflows in CI/CD pipelines.
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).
Maps architectural components in a codebase and measures their size to identify what should be extracted first. Use when asking "how big is each module?", "what components do I have?", "which service is too large?", "analyze codebase structure", "size my monolith", or planning where to start decomposing. Do NOT use for runtime performance sizing or infrastructure capacity planning.
Extend Pydantic AI agents with batteries-included capabilities from pydantic-ai-harness — currently Code Mode, which collapses many tool calls into one sandboxed Python execution. Use when the user mentions pydantic-ai-harness, CodeMode, Monty, code mode, or tool sandboxing, when they want an agent to run agent-written Python, or when a Pydantic AI agent would benefit from orchestrating multiple tool calls in a single sandboxed script.
Use when writing or reviewing Move smart contracts on Sui. Applies to naming structs, error constants, regular constants, events, getter functions, capability types, hot potato types, and dynamic field keys. Use whenever creating new types, functions, or constants in Move code.
Use when users need Rust quantitative SDK or TQSDK Rust capabilities: real-time market data/quote/market depth/K-line/tick, product/contract list, main continuous contract/continuous contract, option chain, contract specification, metadata/direct query, historical data download/cache/CSV/Greeks, trading account/order placement/order cancellation/order status, TargetPosTask/risk control/multi-account/strategy execution, low-latency trading desk, stream/fan-out, replay/backtest/live-sim-replay; also applicable when agents need real-time or historical quantitative data, transaction execution substrate, or trading desk capabilities, even if TQSDK is not explicitly mentioned.