Loading...
Loading...
Found 1,390 Skills
Triage Unity and Unreal Engine editor, build, package, cook, compile, and CI logs into the first actionable failure, likely subsystem, and next debugging steps. Use when a game project fails to build, cook, package, import assets, compile scripts/code, or throws noisy editor/runtime errors, even if the user only shares raw log text or says "Unity build failed", "Unreal cook error", "Editor.log", "UHT/UBT failed", or "packaging started breaking after asset moves".
Intercept and debug HTTP traffic from any CLI, service, or script using HTTP Toolkit. Use when you need to inspect LLM API calls, backend requests, auth flows, or debug network-level issues across any language or runtime.
Qualtrics XM platform help — CX surveys (NPS/CSAT/CES), Employee Experience (EX) pulse surveys, Strategy & Research, Experience Agents AI, XM Directory, dashboards, REST API v3, MCP servers. Use when surveys aren't getting responses, dashboards won't show the right data, API calls return errors, you're setting up Qualtrics for the first time, confused by XM Directory contact management, need to export response data, comparing Qualtrics vs Medallia, or Qualtrics is too complex and you need guidance. Do NOT use for general NPS/CSAT strategy across tools (use /sales-customer-feedback) or product review collection like Trustpilot or G2 (use /sales-customer-reviews).
Tactiq platform help — Chrome extension AI meeting note-taker with bot-free live transcription for Google Meet, Zoom, and MS Teams. Use when Tactiq transcription accuracy is poor with accents, AI credits running out too fast, setting up Tactiq workflows to push notes to Slack or Notion, connecting Tactiq to HubSpot or Salesforce via Zapier, figuring out which Tactiq plan to pick, or comparing Tactiq to Fathom or Fireflies. Do NOT use for choosing between note-takers generally (use /sales-note-taker) or reviewing a specific call for coaching (use /sales-call-review).
Use when building or testing OData queries with dxs odata execute: incremental query development, verifying $select/$expand/$filter clauses, or diagnosing query errors against a Footprint API connection.
Use when asked to debug, fix a bug, investigate an error, or do root cause analysis, and when users report errors, stack traces, unexpected behavior, or say something stopped working.
This skill should be used when debugging full-stack issues that span UI, backend, and database layers. It provides a systematic workflow to detect errors, analyze root causes, apply fixes iteratively, and verify solutions through automated server restarts and browser-based testing. Ideal for scenarios like failing schedulers, import errors, database issues, or API payload problems where issues originate in backend code but manifest in the UI.
Help set up and troubleshoot rendering for task files and glossary files. Use when the user asks about PlantUML, AsciiDoc, VS Code, JetBrains, preview rendering, Java, or Graphviz needed to review rendered task or glossary files.
Diagnose Harness pipeline executions via MCP. Analyzes any execution (failed or successful) to produce structured reports with stage/step breakdown, timing, bottlenecks, failure details, chained pipeline drill-down, and execution logs. Use when asked to debug a pipeline, investigate a failure, find out why a build failed, analyze pipeline errors, check execution logs, review execution performance, or find bottlenecks. Trigger phrases: debug pipeline, pipeline failed, why did my build fail, analyze failure, pipeline error, execution logs, fix pipeline, execution bottleneck, slow pipeline.
Root-cause investigation for bugs, regressions, suspicious runtime behavior, failed automations, and unexpected outcomes.
Generates Logging Query Language (LQL) queries for Google Cloud Logging from natural language. Use this skill when you need to query log data or when you are debugging issues. You can filter log data by Google Cloud service. Don't use this skill to query other databases, such as SQL or Spanner.
Use this skill for live web tasks where WebFetch or curl would fail or be insufficient: JavaScript-rendered pages, forms, screenshots, PDFs, login flows, CAPTCHA/bot-protection flows, and multi-step navigation. It runs a real Steel cloud browser through the Steel CLI. Use when the agent should visit, click, type, scrape, screenshot, or extract now. Do not use for writing reusable Steel SDK/API code; use steel-developer for code. If a live task fails, hand off to steel-session-debugging; if evidence points to bot detection, proxies, CAPTCHA, or identity, hand off to steel-reliability.