Loading...
Loading...
Found 2,152 Skills
Analyzes a single MLflow trace to answer a user query about it. Use when the user provides a trace ID and asks to debug, investigate, find issues, root-cause errors, understand behavior, or analyze quality. Triggers on "analyze this trace", "what went wrong with this trace", "debug trace", "investigate trace", "why did this trace fail", "root cause this trace".
Check Apideck connector API coverage before building integrations. Use when determining which operations a connector supports, comparing connector capabilities, or diagnosing why an API call fails with a specific connector. Teaches agents to query the Connector API for real-time coverage data.
Debug failing Power Automate cloud flows using the FlowStudio MCP server. Load this skill when asked to: debug a flow, investigate a failed run, why is this flow failing, inspect action outputs, find the root cause of a flow error, fix a broken Power Automate flow, diagnose a timeout, trace a DynamicOperationRequestFailure, check connector auth errors, read error details from a run, or troubleshoot expression failures. Requires a FlowStudio MCP subscription — see https://mcp.flowstudio.app
Remap the function_id:pc_index to the original source code position by provided debug info json file.
Use for authorized macOS and Mach-O reverse engineering including codesign, Objective-C/Swift recovery, endpoint security surfaces, and Apple platform malware analysis.
Used for front-end JavaScript reverse engineering with js-reverse-mcp, applicable to signature chain positioning, page observation and forensics, runtime sampling, local environment patching and reproduction, and evidence-based output. Prioritizes adaptation to js-reverse_* tools in the current environment; link with jshookmcp when stronger browser/CDP/Hook capabilities are required.
Develop and debug the MassGen Textual TUI with deterministic replay, snapshot regression tests, and targeted runtime checks.
Diagnose why AdMob ads are not showing in any Expo/React Native app. Use when the user reports real/test ads not displaying, asks why production ads have NO_FILL, whether the AdMob config/package/unit IDs are correct, how a TEST_ADS flag and UMP consent gate affect ads, or how to debug ads on a real device via adb logcat. Not project-specific — works for any app using react-native-google-mobile-ads.
Query a running Apache Spark History Server from Copilot CLI. Use this whenever the user wants to inspect SHS applications, jobs, stages, executors, SQL executions, environment details, or event logs, especially when they mention Spark History Server, SHS, event log history, benchmark runs, or application IDs.
Guidance for building and fixing Cython extensions, particularly for numpy compatibility issues. This skill should be used when tasks involve compiling Cython code, fixing deprecated numpy type errors, or resolving compatibility issues between Cython extensions and modern numpy versions (2.0+).
Deeply interviews the user about a bug before investigating or fixing it. Use this when the user says "interview me about [bug]", "I have a bug to report", "let's work on this bug", "found a bug", "there's a bug", or describes a bug they encountered. Asks probing questions about reproduction steps, environment, patterns, impact, and context that help isolate the root cause. Continues until the bug is well-understood, then writes a detailed investigation/fix plan.
CSS and UI animation patterns for responsive, polished interfaces. Use when implementing hover effects, tooltips, button feedback, transitions, or fixing animation issues like flicker and shakiness.