1.6K skills · sorted by relevance
Investigate software errors, version conflicts, and API questions across official documentation, GitHub, technical Q&A, and Chinese developer communities. Results distinguish matching errors, source authority, and reported environments, giving you documented leads and next checks for debugging.
Build a PDF from a LaTeX paper, diagnose compilation errors, and repair reference or citation problems. Check the resulting layout, page count, anonymity, and embedded fonts, then report fixes and remaining warnings.
Investigate service errors in Sentry by project, environment, and time period. Rank problems by event counts and affected users, compare releases or earlier periods, and report findings with links and a clear search scope.
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.
Investigate Convex production errors, prepare fixes on a branch, and verify them before opening a pull request for human review. After an approved deployment, check whether the same error recurs. Never automatically merge changes or deploy to production.
Write and review interface text, including button labels, errors, empty states, and confirmations. Match the product's established vocabulary and tone, explain actions clearly, and give people a useful next step when something goes wrong.
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.
Run multi-line Python scripts through run_shell when execute_code_sandbox repeatedly fails. The guide explains heredocs, a way to pass blocks of text to a command, with examples for PDF creation, data processing, and inspecting errors.
Troubleshoot CSV and XLSX processing when execute_code_sandbox fails. The workflow locates input files, saves processing code as a Python script, captures execution errors, checks dependencies and file access, and confirms output exists before reading it.
Resolve Unicode character errors when converting Markdown to PDF with pandoc. Follow a workflow to replace troublesome symbols with ASCII equivalents, regenerate and check the PDF, or consider another PDF engine when preserving characters matters.
Investigate unclear errors in Python PDF generation by displaying output immediately and inspecting error details. Use the resulting traceback, a record of where execution failed, to identify missing dependencies, font problems, or invalid file paths.
Audits arithmetic code for mixed units, decimal precision mistakes, and scaling errors. Adds comments identifying each value’s units and produces a summary of findings, unit definitions, and files reviewed.
Test and debug rendered web apps by reproducing interaction bugs, checking layouts and console errors, making focused fixes, and validating again. Results include screenshots, observed state changes, and a QA report explaining coverage and remaining gaps.
Investigate errors, crashes, and failures after updates using reproducible steps, logs, and runtime checks. Identify the root cause before making authorized fixes, then verify the result and check for the same problem elsewhere.
Inspect production errors recorded in Sentry through read-only API access. Summarize unresolved issues, recent crashes, occurrence counts, and event details to understand what happened and when each problem was last seen.
Inspect and control live Chrome pages to investigate display problems, console errors, failed requests, and slow loading. Capture screenshots, automate page interactions, and record performance traces to identify where delays or layout shifts occur.
Write and troubleshoot n8n expressions, the formulas that pass and transform data between workflow steps. Correct field references, read webhook inputs, format dates and text, and query nested JSON while checking for silently missing results.
Write JavaScript for n8n Code nodes to aggregate, filter, and transform workflow data. Guidance covers data access, output formats, execution modes, common errors, and performance choices when processing large numbers of records.
Build custom calculation and parsing tools that an n8n AI Agent can call. This skill covers JavaScript or Python inputs, structured arguments, string results, tool descriptions, and fixes for invocation and output errors.
Write and troubleshoot native Python in n8n Code nodes. Covers data filtering and transformation, migration from older Python code, valid return formats, and restricted execution environments, including cases where errors pass unprocessed input downstream.
Build an MCP integration skill using a template that reads server-specific reference notes before calling tools. The Sentry example gathers unresolved errors, groups them by likely root cause, and produces a report with investigation suggestions.
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.
XML sitemap audit — find and fix the sitemap problems that quietly waste crawl budget and slow indexing. Discovers the sitemap (robots.txt, /sitemap.xml, sitemap index), validates structure and size limits, and cross-checks the URLs it lists against reality: non-200 / redirected / noindex / canonicalized-away URLs that shouldn't be in a sitemap, plus indexable pages that are missing from it. Reviews lastmod accuracy, sitemap-index organization, and robots.txt reference. Use this skill whenever the user asks about sitemaps, sitemap errors in Search Console, "sitemap couldn't fetch / has errors", crawl budget, pages not getting indexed, or whether their sitemap is clean. Trigger on: "sitemap", "sitemap.xml", "XML sitemap", "sitemap errors", "sitemap audit", "couldn't fetch sitemap", "crawl budget", "pages not indexed sitemap", "sitemap index", "lastmod", "robots.txt sitemap", or any sitemap/crawl-coverage question. For a full-site SEO audit use /seo-analysis; for broken links use /broken-link-checker.
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.