Loading...
Loading...
Found 1,678 Skills
Structured workflows for investigating production issues in Honeycomb — the sequence of tool calls (context priming, broad query, BubbleUp, trace analysis, verification) and how to chain results between steps to reach root causes. Trigger phrases: "investigate production issue", "debug latency spike", "find root cause", "use BubbleUp", "analyze traces", "debug an outage", "why is my API slow", "errors are increasing", "health check", "SLO burning", or any request to investigate or debug production problems.
Investigate why a Duvo Job failed or produced the wrong outcome. Use when the user shares a failed Job, asks "why did this Job fail", or wants to fix a recurring failure on an Assignment. Reads the Job's transcript and the Build that was active for it via the Duvo public API, names the root cause from a fixed failure-mode taxonomy, and proposes one concrete fix — handing off to sop-writer for any SOP rewrite.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Remap the function_id:pc_index to the original source code position by provided debug info json file.
Diagnose and resolve Claude Code plugin and skill issues. This skill should be used when plugins are installed but not showing in available skills list, skills are not activating as expected, or when troubleshooting enabledPlugins configuration in settings.json. Triggers include "plugin not working", "skill not showing", "installed but disabled", or "enabledPlugins" issues.
Debugs issues users encounter with Tuist-generated projects by reproducing the scenario locally, building Tuist from source when needed, and triaging whether it is a bug, misconfiguration, or something that needs team input. Use when users report generation failures, build errors after generation, or unexpected project behavior.
Use when given a Sentry issue URL and you need to fetch exception details, stacktrace, and request context using sentry-cli (and Sentry API fallback when needed).
Debug React component issues including TypeScript types, props, state management, hooks, and rendering problems. Use when troubleshooting component not rendering, prop errors, state not updating, hook issues, or TypeScript type mismatches.
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.
Operate and evolve agent-memory-workbench with replay-first memory, minimal JSON edits, and a strict two-branch policy (normal + human-verification).
Diagnoses and fixes Aptos Move compilation, runtime, and deployment errors. Triggers on: 'error', 'fix this', 'debug', 'troubleshoot', 'why is this failing', error codes like 'EOBJECT_DOES_NOT_EXIST', 'ABORTED', 'RESOURCE_NOT_FOUND', 'Type mismatch', 'ability constraint'.
Obsidian 插件开发指南，提供项目初始化模板、配置文件、常见问题解决方案和 API 使用示例。当需要开发 Obsidian 插件、解决 Obsidian 插件开发问题、或查询 Obsidian API 用法时使用。触发场景：(1) 创建新的 Obsidian 插件项目，(2) 配置 esbuild/TypeScript 构建环境，(3) 解决 Node.js 模块加载问题，(4) 使用 Obsidian API（文件操作、frontmatter、UI 组件、命令注册、事件监听），(5) 调试 Obsidian 插件。