Loading...
Loading...
Found 2,028 Skills
Guides FinOps analysis on AWS, GCP, and Azure—cost visibility and allocation, tagging and showback/chargeback models, rightsizing and waste removal, RI/Savings Plan/CUD recommendations, budgets and forecasts, anomaly detection, unit economics (cost per service/customer), and FinOps cadence with engineering accountability. Use when optimizing cloud spend, analyzing CUR/billing exports, building cost dashboards, explaining bill spikes, or improving allocation—not for GL mapping, capex, depreciation, or month-end ledger close (compute-accounting-manager), enterprise EA negotiation (enterprise-cloud-architect), hands-on resource provisioning (cloud-engineer), or hardware supply efficiency (data-center-compute-supply-efficiency).
Use this skill whenever building, reviewing, or refactoring React components that fetch data from APIs — especially at scale (recommender carousels, infinite feeds, pages with many parallel fetches, dashboards). Covers request orchestration (parallelism, batching, deduplication), cache strategy (keys, normalization, staleTime, SWR), backend protection (concurrency caps, debounce/throttle, jittered retries, circuit breakers), prefetching (route loaders, hover/intent, idle, server hydration), failure resilience (AbortController, timeouts, error boundaries, stale fallback, idempotent mutations), and feed/carousel patterns (virtualization, cursor pagination, summary/detail split). Trigger even if the user doesn't explicitly mention "performance" or "scale" — any non-trivial React data-fetching code benefits from these patterns. Includes 5 ready-to-use scaffolding templates (resource query hook, carousel data loader, infinite feed, hover-prefetch link, request collapser).
Discover, choose, install, and learn iii workers from the worker registry. Use when the task needs a worker-backed capability such as harness, shell, sandbox, database, storage, MCP, ACP, image processing, or future workers published to workers.iii.dev.
Fast, zero-friction capture of technical findings from the current conversation to the wiki's _raw/ staging area. Use this skill when the user says "/wiki-quick-chat-capture", "quick capture", "capture this finding", "save this bug fix", "capture this gotcha", "drop this to raw", "quick save to wiki", or wants to capture a non-obvious discovery mid-session without a full wiki-ingest run. Writes one _raw/ file per topic cluster in under 60 seconds — no subagents, no QMD updates, no manifest writes. Run /wiki-ingest or /data-ingest later to promote raw files to proper wiki pages.
Certification coach for Flows apps. Captures the app name, value case, persona, problem, and design intent through a structured conversation and writes App-Brief.md at the repo root. This is the FIRST step of the Flows app certification flow — run it immediately after `npx @cognite/cli apps create`, before building. Use when the user asks to start an app brief, run the certification coach, fill out the app brief, or run flows-app-brief.
Implements Syncfusion .NET MAUI Sunburst Chart (SfSunburstChart) for hierarchical data visualization using a radial, multi-level circular layout. Use this for sunburst charts, radial hierarchical charts, multi-level pie charts, or hierarchical data visualization with drill-down capabilities. Ideal for visualizing organizational structures, file systems, or nested categorical data.
Use after zanahoria-multi-assumptions has filed N parallel issue variants AND @coderabbitai has responded to all of them — closes the family by extracting the load-bearing assumption, naming a winner, capturing the decision as an ADR, and cleanly closing the rejected variants with cross-referenced reasoning. Triggers on close-the-family, pick-a-winner, commit-the-decision, decide-variants, after-CR-responds, zanahoria-decisions.
SOP for Vehicle Entry/Exit Operation Process of AIKE Smart Parking Open Platform (End-to-end Orchestration for Entry/Exit). This skill is applicable when users want to complete the full entry/exit of a vehicle, simulate the real physical entry/exit process, run through the entire link of 'Supplement/Capture Entry → Correction' or 'Exit Capture → Correction → Fee Inquiry → Payment', or ask questions like 'How does a vehicle enter/exits the parking lot?', 'Entry/exit process', 'Entry/exit SOP', 'How to move a vehicle into/out of the parking lot', 'Simulate vehicle entry/exit', or encounter stuck/debugging issues during entry/exit (e.g., vehicle fails to enter after capture or correction, capture returns error code 908, unsure how to proceed to the next step). This skill is a cross-domain orchestration layer that connects multiple commands from parking (supplement/correction/inventory), device (capture), and trade (fee inquiry/payment), and clarifies cross-command hard constraints (paired exit, capture device, channel release mode, token validity) and failure handling. Boundary: For querying a single record, checking on-site vehicles, locking vehicles, or calling a single command, please directly use the corresponding domain skills openydt-record / openydt-device / openydt-billing instead of this process skill.
Use when the user wants to find businesses, software, service providers, or partners for a specific industry, workflow, pain point, capability, or job to be done. Also use when the agent needs to programmatically purchase or consume a service. Use Stripe Directory to build a short relevant shortlist, even if the user does not mention Stripe Directory explicitly.
Build a Salesforce LWC that uses native mobile device capabilities — barcode scanner, biometrics, location, NFC, calendar, contacts, document scanner, geofencing, AR space capture, app review, and payments. Use this skill when the user asks for an LWC that scans a barcode, captures a photo of a document, reads location or geofences, prompts for biometrics, reads/writes the device calendar or contacts, taps NFC, takes a payment, prompts for an app review, or scans an AR space. Also triggers on "lightning/mobileCapabilities", "mobile capability", "Nimbus", "device capability". Do not use for mobile offline / Komaci priming reviews (use `mobile-platform-offline-validate`) or for picking generic Lightning base components (use a generic Lightning base components skill).
Amazon OpenSearch Service and Serverless across five capabilities — migration (Solr/ES/self-managed OpenSearch into AOS/AOSS, schema/query translation, sizing, cutover); provisioning (domain + AOSS lifecycle, upgrades, storage tiers, FGAC, monitoring); search (vector / semantic / hybrid / RAG with Bedrock connectors); log-analytics (PPL, OSI ingestion, anomaly detection, OpenSearch Dashboards, Splunk/Datadog alternatives); trace-analytics (OTel spans, service maps, Data Prepper). Triggers on OpenSearch, AOS, AOSS, Elasticsearch, ELK, Solr, Lucene, vector / k-NN / semantic / hybrid / neural search, RAG, ELSER, log analytics, observability, Kibana, OSI, OCU, PPL, trace analytics, BM25, eDisMax, schema.xml, ILM, ISM, FAISS, HNSW, Migration Assistant for Amazon OpenSearch Service, Historical Data Migration, Live Traffic Migration, UltraWarm, OR1, Splunk/Datadog alternative, moving off Solr. Picks ONE capability per ask, names instance class + count + shard math, ships query DSL examples.
WeCom Smart Document (formerly known as Smart Homepage, smartpage) management skill. Provides capabilities for creating Smart Documents (publishing local Markdown files as Smart Documents) and exporting content (asynchronously exporting to Markdown). Applicable scenarios: (1) Create one or more local Markdown files as Smart Documents (2) Asynchronously export Smart Document content to Markdown. Supports locating documents via docid or document URL. This skill is triggered when the user explicitly mentions "Smart Document" or "Smart Homepage", or when the link is in the format `https://doc.weixin.qq.com/smartpage/xxx`. Note: For regular documents (`/doc/*`), use `wecomcli-doc`; for online spreadsheets (`/sheet/*`), use `wecomcli-sheet`; for smart spreadsheets (`/smartsheet/*`), use `wecomcli-smartsheet`.