1.7K skills · sorted by relevance
This skill should be used when the user encounters "var-annotated" mypy errors, asks to "fix var-annotated errors", "add type annotations to variables", or mentions "Need type annotation for" errors. Provides workflow for fixing missing variable type annotations while respecting forbidden type constraints (no Any, dict[str, Any], list[Any], etc.).
The English summary is being prepared. Showing the original description.
Diagnoses and fixes issues in Atlassian Forge apps. Use this skill whenever a Forge app has errors, crashes, shows blank UI, fails to deploy, doesn't appear after installation, has permission issues, or produces unexpected output. Trigger on any mention of forge logs, forge deploy errors, resolver errors, blank panels, missing scopes, Custom UI not rendering, production vs dev discrepancies, or any Jira/Confluence app that "stopped working". Also trigger when the user asks to debug, troubleshoot, investigate, or fix a Forge app issue — even if they haven't used the word "Forge" but describe a Jira panel or Confluence macro acting up.
The English summary is being prepared. Showing the original description.
Diagnoses and fixes bugs, type/lint errors, CI failures, and runtime errors, root-cause first. NOT for investigation without a fix (mk:investigate) or build-only compile errors (mk:build-fix).
The English summary is being prepared. Showing the original description.
Diagnoses and fixes bugs, type errors, lint failures, CI/CD issues, and runtime errors via root-cause-first investigation. Use for defect remediation. NOT for investigation without a fix (see mk:investigate); NOT for build-only compilation errors (see mk:build-fix).
The English summary is being prepared. Showing the original description.
Complete Flutter SDK installation, IDE configuration, and troubleshooting guide for Linux, macOS, and Windows. Use for installing Flutter SDK from scratch, configuring PATH environment variables across platforms, setting up VS Code/Android Studio/IntelliJ IDEA with Flutter plugins, resolving 'flutter command not found' errors, fixing flutter doctor warnings and errors, troubleshooting Android SDK/NDK installation issues, configuring Xcode and CocoaPods on macOS, installing Visual Studio C++ build tools on Windows, resolving PATH conflicts and SDK path issues, fixing network/proxy setup problems, debugging IDE plugin activation, configuring emulators and simulators, handling platform-specific build errors, resolving dependency conflicts, fixing certificate and signing issues, troubleshooting hot reload failures, and verifying successful installation with flutter doctor diagnostics.
The English summary is being prepared. Showing the original description.
Use when doing ANY task involving Supabase. Triggers: Supabase products (Database, Auth, Edge Functions, Realtime, Storage, Vectors, Cron, Queues); client libraries and SSR integrations (supabase-js, @supabase/ssr) in Next.js, React, SvelteKit, Astro, Remix; auth issues (login, logout, sessions, JWT, cookies, getSession, getUser, getClaims, RLS); Supabase CLI or MCP server; schema changes, migrations, declarative schemas, security audits, Postgres extensions (pg_graphql, pg_cron, pg_vector); debugging and troubleshooting errors or unexpected behavior on Supabase projects (HTTP errors, Postgres errors, RLS surprises, permission denied, schema cache issues, timeouts, Edge Function crashes, Realtime drops, Storage failures) and reading or querying logs (Logs Explorer, ClickHouse).
The English summary is being prepared. Showing the original description.
DEBUGGING SKILL — Read and analyze Cocos Creator project.log for runtime errors, warnings, and stack traces. USE FOR: any bug report, crash, UI glitch, TypeError, null reference, missing asset, CompositePanel mount fail, ChildPanel route fail, or screen spec wiring error. Load this skill FIRST before any runtime debugging session. DO NOT USE FOR: compile errors (use get_errors tool instead).
The English summary is being prepared. Showing the original description.
Cleanup and triage of the task ledgers FOUND_DEFECTS.md, CURRENT_ERRORS.md, .matrx/AGENT_TASKS.md, .matrx/ARMAN_TASKS.md. Use when invoked as /task-hygiene <step>, cleaning up tasks, defects, or errors, triaging an error dump, promoting defects, or bootstrapping these files.
The English summary is being prepared. Showing the original description.
Doctrine for fixing TypeScript errors against generated types (database.types.ts, api-types.ts). Use when fixing tsc or type-check failures or a type-errors batch, writing supabase .rpc()/.from() calls or DB shape guards, errors mention Json/unknown/Database, or you are tempted to cast or suppress.
The English summary is being prepared. Showing the original description.
Guidelines for fixing unhandled errors from the VS Code error telemetry dashboard. Use when investigating error-telemetry issues with stack traces, error messages, and hit/user counts. Covers tracing data flow through call stacks, identifying producers of invalid data vs. consumers that crash, enriching error messages for telemetry diagnosis, and avoiding common anti-patterns like silently swallowing errors.
The English summary is being prepared. Showing the original description.
Guide Swift 6.2 migration and concurrency design using MainActor, which keeps related work on the main actor. Address data-race compiler errors, protocol conformance, and explicit background execution for heavy computations through @concurrent.
Create and repair C++ tests, configure GoogleTest and CTest, and investigate failures or inconsistent results. The workflow also covers measuring which code tests exercise and using runtime checks to detect memory errors and race conditions.
Configure Hermes to run AI models through Actual Computer on your own hardware. Set up either the hosted relay or a local connection, select models, verify responses, and troubleshoot request errors or empty output.
Explore a web app in the browser to find functional, visual, and usability issues. The skill organizes screenshots, console errors, and reproduction steps into a Markdown bug report, with findings grouped by severity and category.
Fix Python type checking failures found locally or in CI, the automated checks run on code changes. It identifies affected files, applies targeted fixes to type declarations and checks, then reruns validation.
Build MCP servers that let AI access actions and data using mcp-use. The guide covers project setup, reusable prompts, interactive React interfaces, authentication, error handling, and deployment, with reference files for each area.
Investigate software errors and unexpected behavior through four stages: investigation, analysis, hypothesis, and implementation. It requires identifying the root cause before making fixes and distinguishes evidence from code inspection, tests, and live runs when reporting findings.
Monitor a live app after deployment for console errors, slower performance, and page failures. Periodic screenshots and comparisons with pre-deployment baselines help identify anomalies and check whether the release is behaving as expected.
Use a real browser to verify web pages and apps through short, supervised interactions. Capture screenshots, inspect errors and network requests, and document reproducible steps for UI bugs or expected behavior checks.
Set up or check claude-mem memory syncing with cmem.ai Pro. Follow installer-based sign-in, verify the cloud connection, and review device details, pending writes, the last successful upload, and errors without sharing tokens in chat.
Improve the MCP server that connects claude-flow v3 to tools. It guides connection reuse, faster tool lookup, request distribution, and communication changes, with monitoring to evaluate response times, errors, memory use, and cache performance.
Investigate WorldMonitor production errors using Sentry event details and source code. Classify issues as noise, already fixed, product bugs, ingestion problems, or needing human review, with tested fixes when code changes are requested.
Inspect OmniRoute connection restrictions, usage quotas, and retry delays from the command line. Reset stuck providers and adjust failure thresholds, cooldowns, and recovery timing to manage how connections respond to errors.
Summarizes recorded system metrics for a chosen period, including completed tasks, errors, memory use, and token consumption. It compares values with historical baselines and flags unusual changes to help assess agent team health.