Loading...
Loading...
Found 335 Skills
Dontbesilent Business Model Diagnosis. Two modes are available: Consultation (dissolve your problem) and Checkup (deconstruct your business model). Triggers include commands like /dbs-diagnosis, /consultation, and natural language phrases such as "Help me analyze my business model", "Diagnose my business", "I have a business question". This service provides business model diagnosis based on dontbesilent's ontological framework, with two core modes: consultation (dissolve your question) and checkup (analyze your business model). Triggers: /dbs-diagnosis, "diagnose my business model", "I have a business question"
Reference — all 20 Xcode MCP tools with parameters, return schemas, and examples
Эксперт по troubleshooting гайдам. Используй для создания диагностических процедур, FAQ и решения проблем.
Read-only drift detector. Diffs SPEC.md against current code and reports violations grouped by severity. Writes nothing — suggests remedies via the spec or build skills but never invokes them. Triggers when the user asks to check drift, audit the spec, verify invariants, or ask whether code still matches the spec. Phrasings: "check drift", "audit the spec", "does the code still match §V", "check invariants", "spec vs code".
Extract billable ICD-10-CM diagnosis codes from a clinical note the way a professional coder builds the claim. Use when users say "code this encounter", "assign ICD-10 codes", "what diagnosis codes apply", "code this chart", or when turning clinical documentation into claim-ready diagnosis codes.
Troubleshooting guide for GrepAI. Use this skill to diagnose and fix common issues.
Real-time monitoring of ClickHouse metrics, events, and asynchronous metrics. Use for load average, connections, queue monitoring, and resource saturation.
Diagnose and fix broken Goldsky Compose apps interactively. Triggers on: compose app in error state, crashlooping, not running, not processing tasks, cron not firing, HTTP trigger returning 500, onchain event listener missing events, wallet errors, gas sponsorship failures, 'No bundler provider available', manifest validation errors, bundling/esbuild failures, secret missing, 'You cannot use a smart wallet in local dev', 'Transaction Receipt failed with status'. Also use when the user mentions a Compose app name alongside a problem, even if they don't say 'compose' explicitly, if they're referring to `goldsky compose` commands (not `goldsky turbo` or `goldsky pipeline`). Runs `status`/`logs`/`secret list`/`wallet list` to identify root cause, and offers fixes. For building a new app from scratch, use /compose instead. For manifest field / CLI flag / API lookups without an active problem, use /compose-reference instead. Do NOT trigger on Turbo or Mirror pipeline problems.
Diagnose MCP validation dependencies (Brave Search, Chrome DevTools) and output exact setup snippets.
Use when code, integrations, automation, infrastructure, or runtime behavior is broken, unexpected, inconsistent, or probably misimplemented and the user wants diagnosis, root-cause analysis, or repair.
Diagnose and repair a broken Notte Function. Use when a deployed or scheduled Function has started failing or returning empty/wrong results - for example "my function fn_... returns empty now", "repair my scraper function", "the Indeed function broke after the site changed", "fix this failed function run", or "diagnose why my scheduled function stopped working". The user supplies the Function that is broken; this skill finds the root cause, re-explores the changed surface, verifies a fix in isolation, and promotes it behind a confirmation gate. Pairs with notte-functions-build, which builds Functions.
Diagnose and fix plugin registry issues including orphaned entries and project-scope conflicts (addresses Claude Code issue