Loading...
Loading...
Found 1,344 Skills
Expert knowledge for Azure Cloud Services development including troubleshooting, best practices, decision making, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when managing Cloud Services (extended support), Guest OS versions, Key Vault certs, autoscale rules, or PowerShell automation, and other Azure Cloud Services related development tasks. Not for Azure Networking (use azure-networking), Azure Virtual Machines (use azure-virtual-machines), Azure Resource Manager (use azure-resource-manager), Azure Portal (use azure-portal).
Expert knowledge for Azure Payment Hsm development including troubleshooting, best practices, decision making, architecture & design patterns, security, and configuration. Use when designing Payment HSM VNets/FastPath, payShield Manager access, HA/DR topologies, SKUs, or traffic inspection, and other Azure Payment Hsm related development tasks. Not for Azure Dedicated HSM (use azure-dedicated-hsm), Azure Key Vault (use azure-key-vault), Azure Cloud Hsm (use azure-cloud-hsm), Azure Security (use azure-security).
Expert knowledge for Azure Lab Services development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when configuring lab plans, VM templates/schedules, VNet-integrated labs, GPU/nested virtualization, or Canvas/Teams integration, and other Azure Lab Services related development tasks. Not for Azure DevTest Labs (use azure-devtest-labs), Azure Virtual Machines (use azure-virtual-machines), Azure Virtual Desktop (use azure-virtual-desktop).
Query the official CrewAI documentation for answers. Use when the user has a CrewAI question that isn't fully covered by the getting-started, design-agent, design-task skills — e.g., specific API details, configuration options, advanced features, troubleshooting errors, enterprise features, tool references, or anything where the latest docs are the best source of truth.
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".
Expert knowledge for Chaos Studio development including troubleshooting, limits & quotas, security, configuration, and integrations & coding patterns. Use when defining ARM/Bicep experiments, deploying Chaos Agents, using CLI/REST, or integrating with Azure Monitor, and other Chaos Studio related development tasks. Not for Azure Monitor (use azure-monitor), Azure Resiliency (use azure-resiliency), Azure Reliability (use azure-reliability), Azure Site Recovery (use azure-site-recovery).
TranscribeMe platform help — human+AI hybrid transcription service with 99% accuracy guarantee on human-reviewed tiers, HIPAA compliance, and REST API. Use when uploading audio for human-edited transcription, choosing between Machine Express and human-reviewed tiers, integrating TranscribeMe API into a transcript pipeline, comparing TranscribeMe vs Rev vs GoTranscript vs Sonix for accuracy-critical transcription, troubleshooting slow turnaround or inconsistent punctuation, setting up HIPAA-compliant medical or legal transcription, or debugging chunked upload or OAuth token issues. Do NOT use for live meeting recording or real-time transcription (TranscribeMe is upload-only — use /sales-note-taker for live meeting tools).
Expert knowledge for Azure DevOps development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when managing Boards/work items, pipelines, repos, Analytics/OData/Power BI, or Azure DevOps Server deployments, and other Azure DevOps related development tasks. Not for Azure Boards (use azure-boards), Azure Pipelines (use azure-pipelines), Azure Repos (use azure-repos), Azure Test Plans (use azure-test-plans).
Use when the user needs to perform multi-step operations with the MetaMask Agentic CLI such as onboarding, login, swapping tokens, bridging across chains, opening/closing/modifying perpetual positions, prediction market trading, or troubleshooting CLI issues.
Automates codebase environment configuration, troubleshooting, and repair. When non-technical users (editors, business personnel, operations staff) get a repository and say things like "it won't run", "how to start", "how to configure the environment", "help me set up the codebase", "initialize the project", "commit code", "what to do about conflicts", it automatically reads ONBOARDING.md, diagnoses environment gaps, fixes dependencies, verifies runnability, and safely completes git operations. It is also used by technical users to quickly standardize the setup process for new repositories (SessionStart hook, PII Guard, history sanitization, project-isolated API keys). This skill is triggered whenever users mention terms like "environment", "configuration", "won't run", "setup", "start", "clone", "how to run", "dependencies", "is it installed", "commit code", "merge conflict", "push failed".
DDEV local development expertise. Use when working with DDEV projects, containers, configuration, or troubleshooting DDEV environments.
Enforce safe Frida 17 MCP operations with strict phase gating. Use when attaching/spawning sessions, writing or loading scripts, applying Java/native hooks, troubleshooting instrumentation failures, or interpreting Frida MCP output. Require docs-first usage and run the mandatory workflow: Idea -> Scripting -> Execution -> Notes.