Loading...
Loading...
Found 5,557 Skills
Evidence-first live messaging workflow for ECC. Use when the user wants to read texts or DMs, recover a recent one-time code, inspect a thread before replying, or prove which message source was actually checked.
Activate to orchestrate multi-phase design projects, set briefs, enforce quality gates, and sequence specialist work.
Use the open-source free `ReportGenerator` tool for turning .NET coverage outputs into HTML, Markdown, Cobertura, badges, and merged reports. Use when raw coverage files are not readable enough for CI or human review.
Apply case study research design (Yin) to investigate how and why questions within real-life contexts using single or multiple case designs and triangulation. Use this skill when the user needs to choose between single and multiple case designs, apply holistic versus embedded units of analysis, triangulate evidence from multiple sources, or when they ask 'how should I structure a case study', 'single or multiple cases', or 'how do I ensure validity in case research'.
Comprehensive psychoeducation on mental health conditions, therapy modalities, evidence-based coping techniques, psychiatric medications, and self-assessment frameworks. Educational resource only — not medical advice, diagnosis, or treatment. Use when learning about mental health concepts, understanding therapy options, exploring coping strategies, or recognizing when to seek professional help. Trigger on "mental health", "therapy types", "coping strategies", "anxiety", "depression", "ADHD", "psychiatric medication", "when should I see a therapist".
Find branch coverage gaps in changed code and fix them by writing missing tests. Two analysis layers: Source ↔ Test (logic branches vs test cases) and Spec ↔ Test (requirement scenarios vs test cases, when a spec file is provided). Use when verifying test completeness after implementing a feature or fixing a bug, when auditing whether tests match a spec, or when suspecting untested branches.
Sets up a 3D CAD model viewer in a Dune app using Cognite Reveal via @cognite/dune-industrial-components/reveal. Use this skill whenever the user mentions 3D viewer, 3D visualization, reveal, CAD model, RevealProvider, RevealCanvas, Reveal3DResources, FDM 3D mapping, asset 3D model, loading a 3D model, or wants to display any Cognite 3D content in a Dune application — even if they don't explicitly say 'Reveal' or '3D viewer'. Do NOT manually wire up RevealProvider, RevealCanvas, or model-loading hooks without consulting this skill first.
Kuikly Exposure & Visibility Event Development Assistant (Kuikly DSL). It guides how to use five visibility events including didAppear, didDisappear, willAppear, willDisappear, and appearPercentage to implement functions such as component exposure reporting, visibility percentage monitoring, list item exposure statistics, etc. It is used when users need to implement scenarios like exposure reporting, visibility monitoring, list item exposure statistics, visibility percentage calculation in Kuikly.
Acts as a Senior Staff Engineer to enforce high-quality software development standards. Use this skill when the user asks for code implementation, architectural review, debugging, or technical design. It ensures all code is production-ready, typed, and architecturally sound.
Read market data for a known Kalshi prediction market on DFlow — orderbook, trades, top-of-book prices, candlesticks, forecast-percentile history, and Kalshi in-game live data — via one-shot REST snapshots, historical ranges, or live WebSocket streams. Use when the user asks "show me the orderbook for X", "get last hour of trades", "build a live price ticker", "stream orderbook depth", "pull 1-minute candles for the last day", "watch in-game scores for this sports market", or "alert me when the orderbook moves". Do NOT use to discover markets matching a criterion (use `dflow-kalshi-market-scanner`), to place orders (use `dflow-kalshi-trading`), or to read a user's own positions/P&L (use `dflow-kalshi-portfolio`).
Operate Notion Public API through UXC with a curated OpenAPI schema for search, block traversal, page reads, content writes, and data source/database inspection. Use when tasks need recursive reads or structured writes that Notion MCP does not expose directly.
Vitally platform help — Health Scores, Playbooks, Projects, Automation, AI copilot, NPS, Dashboards, REST API. Use when health scores aren't reflecting reality, playbook automations aren't triggering, Salesforce or HubSpot sync is broken, onboarding projects are stalling, NPS surveys aren't reaching users, Vitally AI summaries seem off, custom traits aren't updating via API, or dashboards show stale data. Do NOT use for general customer success strategy (use /sales-customer-success) or survey design methodology (use /sales-customer-feedback).