Loading...
Loading...
Found 11,972 Skills
Adversarial robustness engineering for ML/AI—evasion, poisoning, extraction, membership-inference threat models; robust training, sanitization, detectors; ASR/certified evals; lab model attacks; data-pipeline integrity; production I/O guardrails (classical ML and LLM/multimodal). Use for adversarial examples, robustness suites, poison audits, deploy guardrails—not LLM app red team (ai-redteam), governance (ai-risk-governance), safety classifier R&D (ml-research-engineer-safeguards), safeguard serving (ml-infrastructure-engineer-safeguards), privacy research (privacy-research-engineer-safeguards), AppSec pentest (penetration-tester).
Guides organizational and business storytelling—narrative structure (setup, tension, resolution), audience-tailored stories for executives, customers, boards, and teams, honest data and metrics framing, product and strategy narratives, incident and postmortem storytelling, and actuarial or insurance risk narratives for non-technical audiences. Covers story spine, key messages, and visual or slide narrative outlines. Use when the user says "tell the story", "storytelling", "narrative for executives", "data story", "board presentation narrative", "explain with a story", "story arc", "key message", "compelling narrative", "pitch story", or "incident story"—not cross-department reframing only (cross-department-translation), company-wide comms cadence and crisis wording packs (communication-lead), long-form creative fiction or screenwriting, brand copy without strategy context, or technical documentation and API reference (tech-writer-researcher).
Create, update, and repair local Shiplight YAML E2E tests. Use for Shiplight test projects, including project setup, specs, environments, auth fixtures, YAML implementation, validation, and test maintenance.
Plan a migration onto MotherDuck. Use when moving from Snowflake, Redshift, PostgreSQL, dbt-heavy stacks, or lakehouse tooling and the key decisions are target pattern, cutover slices, validation, rollback, and native-versus-DuckLake posture.
Builds Moran's I spatial autocorrelation workflows in CARTO. Triggers when the user mentions spatial autocorrelation, Moran's I, spatial dependency, spatial correlation, spatial outliers, HH HL LH LL quadrants, high-high clusters, low-low clusters, spatial weight matrix, "is there clustering", "are values spatially correlated", local indicators of spatial association, LISA, spatial randomness test, or wants to determine whether a variable exhibits spatial clustering, dispersion, or randomness across a gridded dataset. Also relevant when the user needs to classify locations into cluster types (HH, HL, LH, LL) rather than just identifying hotspots and coldspots.
Render an ad-hoc interactive map inline in the chat from a deck.gl declarative spec via the CARTO MCP server's view_map tool. Use whenever the user asks to map, visualize, or show the geographic distribution of points, polygons, hexagons, quadbins, clusters, density (heatmaps), or raster — and the map is exploratory or throwaway, not meant to be saved as a permanent CARTO Builder map. Triggers on "show me X on a map", "visualize Y", "make a heatmap of Z", "render the points/clusters/raster of W". Distinct from carto-create-builder-maps (CLI authoring of permanent maps), carto-preview-builder-map (loading an existing saved Builder map), and carto-develop-app (writing a from-scratch deck.gl app in TypeScript / JavaScript).
Find a specific CRM record by ID, email, domain, or name fragment, and traverse associations for the full account picture.
Deploys and manages Laravel applications on Laravel Cloud using the `cloud` CLI. Use when the user wants to deploy an app, ship to cloud, create/manage environments, databases, caches, domains, instances, background processes, or any Laravel Cloud infrastructure. Triggers on deploy, ship, cloud management, environment setup, database provisioning, and similar cloud operations.
Host modded Minecraft servers (CurseForge, Modrinth).
Pre-commit review: security scan, quality gates, auto-fix.
Mastodon automation — fediverse engagement, content-warned posts, instance-aware community participation, and boost-driven amplification.
Enforce allowed and forbidden conversation topics using semantic embedding similarity with session-aware drift detection