Skill UI

Automatically collects comprehensive diagnostic evidence for Mistral AI support tickets. This bundle includes environment details (OS, Node/Python versions), installed SDK versions, API connectivity test results, available models, and recent error logs. It is essential for reproducing and diagnosing persistent issues when contacting technical support.

Delivers end-to-end monitoring setups—structured logging, Prometheus/Grafana dashboards, alerting rules, distributed tracing, and load/profile testing—so teams can observe services, debug production issues, and plan capacity.

Guides you through diagnosing Next.js getServerSideProps, getStaticProps, and API route failures by checking terminal logs, adding explicit try-catch handling, and reviewing hosting logs or common causes like env vars, DB, or serialization issues.

This tool gathers comprehensive diagnostic evidence from an Obsidian vault. It collects details such as app versions, installed plugins, appearance settings, file statistics, and console errors into a structured markdown report. Use it when troubleshooting persistent issues or preparing detailed bug reports for developer support.

This guide establishes a comprehensive and rapid development loop for Obsidian plugins. It covers the entire workflow, from setup (cloning templates, symlinking) to advanced features, including running esbuild in watch mode, achieving hot-reloading (via Ctrl+R or automatic methods), deep debugging with Chrome DevTools, and running unit tests with vitest. Essential for developers seeking fast feedback and reliable plugin iteration.

This skill provides a comprehensive guide to setting up isolated development, testing, and production vaults within Obsidian. It covers advanced techniques like symlinking plugin sources for hot reloading, implementing environment-specific configuration logic (e.g., managing debug modes and feature flags), and creating standardized vault templates for team onboarding, ensuring a robust and scalable development lifecycle.

A comprehensive toolkit for implementing production-grade observability in Obsidian plugins. It provides structured logging with log levels and history, a robust metrics collector (supporting counters, gauges, and timers for performance tracking), and an error tracker with deduplication. Users can build a real-time debug panel to monitor plugin performance, diagnose issues, and set up comprehensive error reporting.

This guide provides comprehensive error handling and debugging steps for the OpenEvidence API. It covers common failure points—including authentication issues (401, 403), query validation errors (422), rate limiting (429), and service timeouts (408). Users can learn how to diagnose the root cause of connection failures and refine their clinical queries to maximize data retrieval accuracy.

This bundle collects comprehensive diagnostic evidence from the OpenEvidence clinical decision support API. It validates API credentials, checks query endpoint health, retrieves evidence citations, and captures model metadata. Use it to diagnose complex issues like query failures, missing references, or high latency without needing direct dashboard access.

This skill provides comprehensive, structured audit logging for OpenRouter API interactions. It automatically captures essential metadata like total cost, token usage, model details, latency, and status, while also performing PII redaction. The resulting audit trail is stored in an append-only SQLite database, making it ideal for building compliance-ready systems, detailed cost monitoring, and deep debugging of production environments.

This comprehensive guide helps users diagnose and fix common OpenRouter API errors, including authentication failures (401), rate limiting (429), and bad requests (400). It provides a complete reference table, detailed root causes, and executable code examples in Bash and Python to ensure stable API integration and robust error handling.

This bundle provides a structured mechanism for capturing comprehensive debug information when interacting with the OpenRouter API. It captures the full request parameters, response content, detailed error logs, generation metadata (such as cost, token usage, and provider), and the execution environment. This tool is essential for diagnosing failed API calls, unexpected behaviors, or performance/latency issues.