1.6K skills · sorted by relevance
Interpret n8n validation results and work through fixes for missing settings, broken references, and expression errors. Distinguishes blocking errors from advisory warnings, explains validation profiles, and guides review of automatic fixes and execution failures.
Check out a GitHub pull request, fix linting and TypeScript errors, and commit and push the changes. The workflow supports forked pull requests and repeats type checks to verify fixes while keeping changes focused on these errors.
Create PostHog error tracking suppression rules to drop high-volume, low-value errors at ingestion. Use when the user asks "stop capturing this error", "drop browser extension errors", "ignore ResizeObserver loops", "suppress bot-driven errors", or wants to reduce ingestion cost from noisy unactionable errors. Identifies suppression candidates, scopes the filter tightly, decides between full suppression and sampling, and confirms the rule before creating it. Suppressed errors are dropped permanently — this skill defaults to caution.
The English summary is being prepared. Showing the original description.
Investigate OpenSEO production errors in Cloudflare Workers Observability. Count worker invocations accurately, compare periods and deployment versions, and filter previously investigated noise to focus analysis on errors that need attention.
Review new and spiking Sentry errors, rank their impact, and check for existing GitHub issues. Create triage issues for the highest-impact untracked errors and post a Slack summary, while leaving Sentry error states and assignments unchanged.
Run TypeScript type checks when standard commands fail, then filter diagnostics to files involved in your task. Preserve the compiler’s exit status while reviewing relevant errors separately from existing project errors.
Recover document and PDF generation tasks when sandbox errors provide little detail. Checks Python libraries, runs generation through the shell, captures errors, and verifies output files, with alternative PDF tools and text output as fallback options.
Idiomatic Golang error handling — creation, wrapping with %w, errors.Is/As, errors.Join, custom error types, sentinel errors, panic/recover, the single handling rule, structured logging with slog, HTTP request logging middleware, and samber/oops for production errors. Built to make logs usable at scale with log aggregation 3rd-party tools. Apply when creating, wrapping, inspecting, or logging errors in Go code. For samber/oops specifics → See `samber/cc-skills-golang@golang-samber-oops` skill; for slog handler ecosystem → See `samber/cc-skills-golang@golang-samber-slog` skill.
The English summary is being prepared. Showing the original description.
Explains runtime errors and compilation failures with actionable debugging guidance. Use when Python or Java code throws runtime exceptions (NullPointerException, TypeError, AttributeError, etc.), compilation errors (syntax errors, type mismatches, import failures), or dependency issues. Analyzes error messages, stack traces, and code context to identify root causes and provide concrete fixes with examples. Distinct from test-related errors - focuses on errors during normal code execution and build processes.
The English summary is being prepared. Showing the original description.
Diagnose network errors and intermittent connections on routers, switches, and Linux hosts. Compare both ends of a link and changes in error counts to distinguish cable faults, congestion, and mismatched speed or communication settings.
Check a Rust project for compilation errors with cargo check, examine errors and warnings, and fix the issues found. An included command example also covers checking all project targets.
Write and troubleshoot n8n expressions, the formulas that pass and transform data between workflow steps. Covers field references, webhook inputs, dates, strings, and choosing between expressions and Code nodes for data transformations.
Build AI applications with Genkit in Node.js and TypeScript, including conversational agents, generation workflows, and tools. Use documentation, type checks, and execution traces—records of model inputs and tool calls—to verify behavior and troubleshoot errors.
Investigate crashes, out-of-memory errors, and device initialization failures on GKE TPU v6e nodes. The skill checks logs and custom metrics collection for conflicting operations, then guides temporary mitigation by disabling an identified collector.
Investigate 403 and 500 errors in Google Cloud Gemini Enterprise Agent Platform. Examine logs, registered destinations, agent identities, and authorization policies to produce a diagnostic report with evidence, recommended fixes, and verification steps.
Set up credentials and a development environment for your first Google Ads API request to retrieve campaigns. Choose from six official client libraries or direct HTTP requests, with guidance for account IDs, developer tokens, and common authorization errors.
Operate Chrome or Brave using signed-in browser sessions to verify deployed pages, reproduce bugs, inspect page structure, and examine errors or network traffic. An optional macOS bridge extends control to native applications and operating system input.
Capture production errors from Convex server functions and browser interfaces in your own deployment. Redact sensitive information before storage, inspect recent failures, monitor new events, and optionally route recurring errors into a workflow that opens fix pull requests.
Run TypeScript checks without generating output files, with a fallback when the usual commands fail. The workflow records existing errors, filters diagnostics to changed files, and repeats checks after fixes to assess the modified code.
Interpret validation errors and guide fixing them. Use when encountering validation errors, validation warnings, false positives, operator structure issues, or need help understanding validation results. Also use when asking about validation profiles, error types, the validation loop process, or auto-fix capabilities. Consult this skill whenever a validate_node or validate_workflow call returns errors or warnings — it knows which warnings are false positives and which errors need real fixes.
The English summary is being prepared. Showing the original description.
Use when hitting layout errors (RenderFlex overflow, unbounded constraints, RenderBox not laid out), scroll errors, or setState-during-build errors.
The English summary is being prepared. Showing the original description.
Investigate software errors by tracing code, reviewing recent changes, and reproducing symptoms. Test a specific cause before making a minimal fix, then verify the result with regression tests and a structured debug report.
Open web pages, follow navigation, and check form flows in a browser. Capture screenshots at different screen sizes, compare pages before and after actions, and collect console errors, the technical messages that can reveal page problems.
Review Caveman Cloud spending, latency, errors, and potential improvements using current reports and traces, or individual execution records. Produce findings tied to time windows and trace IDs, while keeping measured costs, estimated opportunities, and verified savings separate.