3.4K skills · sorted by relevance
Investigate and fix production errors reported in Sentry through MCP, a connection to external tools. Analyze error details and execution history, check them against source code, implement fixes, and verify them with tests and regression checks.
Fix Native SDK build failures caused by older Zig APIs. Organized by compiler error, this guide shows Zig 0.16 patterns for file access, output, lists, processes, environment variables, clocks, networking, and build configuration.
Recover from file-writing errors involving emoji or special symbols by switching to shell-based writing. Guides character preservation or replacement, literal text handling, directory preparation, and checks of the saved content.
Save large text files when write_file or shell_agent encounters payload size limits. Create the parent directory first, write the content with Python through run_shell, and verify the resulting file.
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.
Decide when repeated search failures justify continuing document creation with existing knowledge. Track errors, distinguish retryable problems, and record verification limits, while excluding tasks that require current information or explicit external verification.
Apply ReportLab’s built-in paragraph styles to PDF titles, headings, and body text. Learn how to reuse existing styles and create named variations without duplicate style names that can cause KeyError exceptions.
Recover from PDF and DOCX generation errors by checking the workspace, capturing error details, and trying alternative conversion engines or Python libraries. Verify that the resulting files exist and can be read.
Diagnose failed OpenAI API requests by separating network problems, authentication errors, exhausted credits, rate limits, and access restrictions. Use concrete error messages to explain the likely cause and direct users to the appropriate next action.
Build React interfaces that clearly handle loading, errors, empty results, and submissions. Use examples and checklists to keep existing data visible during refetching, offer retry actions, and disable buttons while asynchronous operations are running.
Improve confusing interface text, from error messages and form labels to buttons and loading notices. This skill clarifies what happened, what users should do next, and which terms to use consistently across the product.
Strengthen interfaces for real usage by handling long text, network failures, empty data, and repeated submissions. Improve internationalization, meaning support for different languages and regional formats, alongside accessibility and recovery from errors.
Upgrade MSTest v3 test projects to v4 by updating packages, adapting code to changed APIs, and checking execution behavior. It also helps resolve build errors and problems finding tests in CI after an upgrade.
Build or update ASP.NET Core API endpoints with defined request and response types, appropriate HTTP status codes, OpenAPI documentation, and centralized error handling. Also creates .http request files for manually checking endpoint behavior.
Investigate MSBuild failures caused by projects or build configurations writing to the same output folders. Compare build logs, output paths, and project settings to identify collisions behind overwritten files, restore errors, or failures that disappear on retry.
Plan, run, and interpret linear regression with guidance on model choices, diagnostic checks, and reporting. Python, R, and Stata examples help examine coefficients, assess assumptions, and choose standard errors that account for different error patterns.
Improve APM command-line messages so users can scan results and understand what to do next. It guides warning summaries, consistent colors and symbols, and shared logging code for progress, errors, and detailed output.
Inspect production errors in Sentry through read-only API queries. Summarize unresolved issues, occurrence counts, and recent events, then examine individual issue and event details to understand what has been happening.
Assess whether a DOCA application needs low-level communication controls beyond its higher-level APIs. For those cases, guide queue configuration, libibverbs migration, and error diagnosis using installed headers, version checks, and device capability queries.
Build SHA hashing applications for BlueField or ConnectX accelerators with guidance on single-request versus chunked processing, supported algorithms, buffer sizes, memory permissions, and errors returned by the DOCA SHA API.
Guide DOCA Management programming for BlueField and ConnectX devices. Set up management contexts, query capabilities, change device settings, and investigate errors, using installed reference samples and checks before and after changes.
Build and troubleshoot data transfers with DOCA RDMA, which accesses remote memory over a network adapter. Start from installed samples, choose connection methods and permissions, check device capabilities, and investigate missing completions or queue errors.
Idiomatic Golang design patterns — functional options, constructor APIs, `init()` and global-state avoidance, enums, panic vs error decisions, resource management and lifecycle, graceful shutdown, timeouts and retries, streaming and iterators, and architecture styles (clean, hexagonal, DDD, flat). Apply when choosing between architectural patterns, implementing functional options, designing constructor APIs, setting up graceful shutdown, applying resilience patterns, or asking which idiomatic Go pattern fits a specific problem. Not for wiring a DI container or comparing DI libraries (→ See `samber/cc-skills-golang@golang-dependency-injection` skill), nor for error wrapping, `errors.Is`/`As`, or logging mechanics (→ See `samber/cc-skills-golang@golang-error-handling` skill).
The English summary is being prepared. Showing the original description.
[omh] Hidden or swallowed errors suspected: find swallowed errors, unsafe fallbacks, hidden UI/runtime failures, and missing propagation before they become false green status. Use when the user says: failure-signal-audit, failure signal audit, silent failure, silent failures, silent failure hunter, swallowed error, swallowed errors, empty catch.
The English summary is being prepared. Showing the original description.