Loading...
Loading...
Found 1,614 Skills
Build and operate predictive models for logistics networks—demand forecasting at SKU/location/lane granularity; inventory positioning and safety stock optimization interfaces; ETA and lead-time prediction; capacity and congestion signals; route and network flow forecasting at model-integration level; cold chain and perishables; promotion and seasonality; model monitoring, drift, and backtesting against operational KPIs (fill rate, OTIF, WMAPE/MAPE). Use for predictive logistics, demand forecasting logistics, ETA prediction, inventory positioning, safety stock optimization, OTIF forecast, lane demand, WMAPE, logistics ML, capacity forecasting logistics, or cold chain forecast—not pure OR/MIP without logistics domain (operations-research-algorithm-developer), supply chain strategy only (supply-chain-manager), WMS feature dev (wms-developer), fleet telematics ingestion (geospatial-telematics-developer), generic ML without logistics (data-scientist), or EDI document mapping (edi-engineer).
Monitors Certificate Transparency (CT) logs to detect unauthorized certificate issuance, discover subdomains via CT data, and alert on suspicious certificate activity for owned domains. Uses the crt.sh API and direct CT log querying based on RFC 6962 to build continuous monitoring pipelines that catch rogue certificates, track CA behavior, and map the external attack surface. Activates for requests involving certificate transparency monitoring, CT log auditing, subdomain discovery via certificates, or certificate issuance alerting.
Creates SLO-based alerts and operational dashboards with key charts, alert thresholds, and runbook links. Use for "alerting", "dashboards", "SLO", or "monitoring".
Build Celigo B2B Manager EDI integrations -- trading partner onboarding, EDI profiles, file definitions, X12/EDIFACT flow patterns, and transaction monitoring. Use when onboarding partners, editing EDI flows, setting up parsing rules, or monitoring document exchange.
Monitor Granola usage, analytics, and meeting insights. Use when tracking meeting patterns, analyzing team productivity, or building meeting analytics dashboards. Trigger with phrases like "granola analytics", "granola metrics", "granola monitoring", "meeting insights", "granola observability".
Full Sentry SDK setup for .NET. Use when asked to "add Sentry to .NET", "install Sentry for C#", or configure error monitoring, tracing, profiling, logging, or crons for ASP.NET Core, MAUI, WPF, WinForms, Blazor, Azure Functions, or any other .NET application.
Staged rollout orchestration and monitoring for Google Play releases. Use when implementing gradual release strategies.
Apply Agency Theory (Jensen and Meckling, 1976) to diagnose principal-agent problems — moral hazard, adverse selection — and design governance mechanisms to align interests. Use this skill when the user needs to analyze conflicts of interest between owners and managers, design incentive or monitoring structures, evaluate corporate governance effectiveness, or when they ask 'how do we ensure managers act in shareholders interest', 'why is this incentive plan failing', or 'what governance mechanisms reduce agency costs'.
Desktop GUI and CLI app for running and monitoring Quip Network nodes, built with Tauri v2 and Rust
Used for debugging communication of Modbus RTU (serial port) or Modbus TCP (network) devices, supporting register read/write, slave scanning, and continuous monitoring.
Collect search results from Instagram — matching posts, URLs, authors, engagement. Use when the user wants to collect content matching keywords for research or monitoring.
Diagnose, troubleshoot, and advise on any Qdrant deployment by loading the latest official Qdrant skills live from skills.qdrant.tech. Use this whenever someone raises a Qdrant problem or question — slow or degraded search, high or growing memory / OOM crashes, optimizer stuck or slow, indexing slowness, scaling and sharding decisions (node count, QPS, latency, multitenancy, vertical vs horizontal), poor or irrelevant search results, hybrid search and reranking, embedding-model migration, version upgrades and compatibility, monitoring and observability (Prometheus, Grafana, health checks, /metrics, /telemetry), deployment choices (local, Docker, self-hosted, Qdrant Cloud, embedded), or client-SDK questions (Python, TypeScript, Rust, Go, .NET, Java). Trigger especially when the context is clearly a Qdrant cluster, collection, or vector-search deployment. Always prefer this skill over answering from memory: it pulls current, authoritative guidance and only the relevant context.