899 skills · sorted by relevance
Design Azure infrastructure from plain language or visualize existing resources as interactive diagrams. Refine the architecture through conversation, then generate Bicep infrastructure code, review it, and validate changes before deployment.
Build MCP servers, which expose tools and data to AI agents, with mcp-use. The material covers server functions, reusable prompts, and interactive React widgets, but this skill is deprecated and points to mcp-app-builder as its replacement.
Use CloudFox to inspect AWS and Azure resources through read-only queries. Identify exposed endpoints, secrets, permissions, and role trust relationships, then organize findings into files for reviewing configuration weaknesses and potential paths to broader access.
Extract code and resources from installed Electron apps to inspect how they are built. Restore original files when source maps contain them, or format compressed JavaScript for easier reading. Supports app discovery on macOS and Windows.
Design and create custom cloud controls and frameworks for Google Cloud data boundary requirements that existing resources cannot meet. Receive prepared configuration fields for manual setup, or approve creation through the agent.
Create and manage custom Agent resources on Gemini Enterprise Agent Platform before running conversations. Prepare REST requests to configure instructions, attach files and skills, connect tools, track creation progress, and retrieve, update, or delete agents.
Manage NodeGroup resources in a KubeSphere environment, including creation, updates, and deletion. Bind or unbind nodes, namespaces, and workspaces, verify changes, and investigate synchronization problems or deployment settings using the bundled API script.
Operate FrontendIntegration resources from existing YAML definitions using kubectl, the Kubernetes command-line tool. Manage updates and enabled state, inspect build output, troubleshoot failures, and install or manage the frontend-forge extension.
Build infrastructure as code with Terraform across AWS, Azure, and GCP. Create reusable modules, manage state records that track resources, configure environments and providers, and validate proposed changes before applying an explicitly approved plan.
Adjust how AI agents generate workflows in cc-wf-studio by reviewing node descriptions, examples, and misleading constraints. The skill guides minimal schema edits, format regeneration, and testing to address biased node choices.
Model queues, production lines, logistics, and other systems that share limited resources in Python. Use discrete-event simulation, which advances through individual events, to measure waiting times, resource use, and throughput when comparing staffing or equipment levels.
Use this skill when the user is doing hands-on DOCA Flow DPA Provider work — exporting a `doca-flow` pipe or external resource (index-selector/memory) into BlueField DPA address space so a DPACC-built kernel can read counters, mutate hash-pipe entries, and update/read memory or index-selector resources inline with Flow. Covers per-port `doca_flow_dpa_ctx`, three queue types (general/resources-write/resources-read), the order-sensitive export handshake (`_export_prepare` → add entries → `_export` → `_get_device_addr`), and DPA-side device API. Trigger even when the user does not say "DOCA Flow DPA Provider" — implicit phrasings include "DPA kernel never sees entries in the exported pipe", "BAD_STATE from `_pipe_export`", "how do I disable a hash entry from a DPA kernel", "DPA memory read returns no value", or "DPA-side post keeps returning AGAIN". Refuse and route elsewhere for `doca-flow` pipe construction, generic host-side DPA (`doca-dpa`), or DPA-side kernel-writing — those belong to other skills.
The English summary is being prepared. Showing the original description.
Analyze Azure resource groups and generate detailed Mermaid architecture diagrams showing the relationships between individual resources. WHEN: create architecture diagram, visualize Azure resources, show resource relationships, generate Mermaid diagram, analyze resource group, diagram my resources, architecture visualization, resource topology, map Azure infrastructure.
The English summary is being prepared. Showing the original description.
Optimize existing Azure resources and analyze Reservations or Savings Plans. WHEN: "optimize Azure costs", "reduce cloud spending", "rightsize resources", "find idle resources", "orphaned disk", "deleted VM still charged", "public IP still charging", "reservation utilization", "Savings Plan coverage", "commitment recommendation", "why is pay-as-you-go still charged". DO NOT USE FOR: cost spikes, forecasts, pricing estimates, budgets, or governance.
The English summary is being prepared. Showing the original description.
Analyze Azure resource groups and generate detailed Mermaid architecture diagrams showing the relationships between individual resources. WHEN: create architecture diagram, visualize Azure resources, show resource relationships, generate Mermaid diagram, analyze resource group, diagram my resources, architecture visualization, resource topology, map Azure infrastructure.
The English summary is being prepared. Showing the original description.
Optimize existing Azure resources and analyze Reservations or Savings Plans. WHEN: "optimize Azure costs", "reduce cloud spending", "rightsize resources", "find idle resources", "orphaned disk", "deleted VM still charged", "public IP still charging", "reservation utilization", "Savings Plan coverage", "commitment recommendation", "why is pay-as-you-go still charged". DO NOT USE FOR: cost spikes, forecasts, pricing estimates, budgets, or governance.
The English summary is being prepared. Showing the original description.
Use when targeting the Annual Review of Environment and Resources or deciding whether an environment-and-resources synthesis fits this invited-review venue. Encodes the journal's invited-review fit, the authoritative-synthesis bar, structure expectations, official-submission re-check, and desk-reject heuristics.
The English summary is being prepared. Showing the original description.
Transfer app data to or from other platforms using AppMigrationKit. Use when implementing system-orchestrated one-time migration between iOS and Android or another platform, building an AppMigrationExtension, packaging transportable resources with ResourcesArchiver, importing resources on the destination device, reporting import progress, handling migration errors and app group cleanup, checking MigrationStatus, or testing migration code with AppMigrationTester.
The English summary is being prepared. Showing the original description.
Implement Terraform provider ephemeral resources with the Plugin Framework: the Open/Renew/Close lifecycle, ephemeral schema design, registration via EphemeralResources, renewal for expiring credentials, and how ephemeral values flow into write-only attributes and provider configuration. Use when adding an ephemeral resource, exposing secrets/tokens/certificates that must never persist in state or plan, deciding between an ephemeral resource and a data source, or wiring short-lived credentials from one provider into another.
The English summary is being prepared. Showing the original description.
Create, update, and review Terraform provider documentation for Terraform Registry using HashiCorp-recommended patterns, tfplugindocs templates, and schema descriptions. Use when adding or changing provider configuration, resources, data sources, ephemeral resources, list resources, functions, actions, or guides; when validating generated docs; and when troubleshooting missing or incorrect Registry documentation.
The English summary is being prepared. Showing the original description.
Use when you need to apply Java exception handling best practices — including using specific exception types, managing resources with try-with-resources, securing exception messages, preserving error context via exception chaining, validating inputs early with fail-fast principles, handling thread interruption correctly, documenting exceptions with @throws, enforcing logging policy, translating exceptions at API boundaries, managing retries and idempotency, enforcing timeouts, attaching suppressed exceptions, and propagating failures in async/reactive code. This should trigger for requests such as Exception handling; Use try-with-resources in Java code; Create exception chaining in Java code; Apply fail-fast validation in Java code; Review Java exception taxonomy and propagation. Part of Plinth Toolkit
The English summary is being prepared. Showing the original description.
"Apply the Resource-Based View (Barney, 1991) and VRIO framework to evaluate whether a firm's resources and capabilities confer sustained competitive advantage. Use this skill when the user needs to assess internal resources for strategic value, determine if a competitive edge is sustainable, audit resource portfolios for VRIO criteria, or when they ask 'what makes our advantage sustainable', 'which resources matter most', or 'can competitors replicate this'.".
The English summary is being prepared. Showing the original description.
Use this skill when the user is working with an Aspire distributed application and needs to operate the AppHost or its resources through the Aspire CLI: start, restart, stop, or wait on the app; inspect resources, logs, traces, docs, or health; add integrations; manage secrets or config; publish, deploy, or rerun a named pipeline step; initialize Aspire in an existing app; recover missing `.modules` files in a TypeScript AppHost; discover the right frontend URL for Playwright from Aspire state; expose custom dashboard/resource commands; or understand unfamiliar Aspire AppHost APIs in C# or TypeScript. Use it even if they describe the task in terms of an AppHost, resources, dashboard, existing app bootstrap, missing generated modules, Playwright URL discovery, C# API understanding, or local distributed app workflow without explicitly naming Aspire. Do not use it for non-Aspire .NET apps, container-only repos with no AppHost, or ordinary build and test tasks.
The English summary is being prepared. Showing the original description.
Own the lifecycle of short-lived paid CPU/GPU hosts and attached resources, from bounded provisioning through verified permanent deletion. Use when renting, extending, retiring, or recovering billable remote resources; campaign scheduling belongs to run-ephemeral-hosts.
The English summary is being prepared. Showing the original description.