Skill UI

A comprehensive guide for developers to diagnose and fix the six most common errors encountered when building Obsidian plugins. It covers critical technical issues such as null pointer exceptions, manifest loading failures, incorrect CSS paths, command registration timing, and state persistence bugs, ensuring reliable and stable plugin functionality.

This runbook provides systematic procedures for diagnosing and resolving critical failures within the Obsidian knowledge base. It guides users through recovering from plugin crashes, vault corruption, sync conflicts, and performance degradation using advanced command-line tools and developer console access. Essential for advanced users and technical support.

This deep-dive tool automates the complex process of migrating notes and knowledge bases from various platforms (such as Notion, Evernote, Roam, etc.) into Obsidian. It handles critical conversions like stripping platform-specific UUIDs, converting internal links to optimized Obsidian wikilinks ([[...]]), and correctly formatting attachments and YAML frontmatter, ensuring a seamless transition and preserving the structural integrity of your knowledge base.

This comprehensive checklist guides developers through the pre-release verification process for Obsidian community plugins. It covers critical technical areas such as validating manifest structure, ensuring clean production builds (e.g., removing sourcemaps), identifying potential memory leaks, and verifying cross-platform readiness, ensuring a high-quality user experience upon submission.

A comprehensive guide for developers migrating and upgrading Obsidian plugins across major API versions. It covers critical steps such as auditing plugin compatibility, implementing version-aware settings migration logic (for user data persistence), replacing deprecated API calls (e.g., Vault, Editor, FileManager), and updating configuration files like manifest.json to ensure stability on new Obsidian releases.

Automates the Continuous Integration and Continuous Deployment (CI/CD) process for OpenEvidence clinical decision support integrations. This setup ensures that unit tests (using mocked evidence queries and citations) and live API connectivity tests are run automatically on every pull request and merge to main. It validates critical functions like query formatting, evidence parsing, citation extraction, and response quality scoring, maintaining high reliability for medical AI applications.

Provides comprehensive observability for OpenEvidence, a system delivering critical clinical evidence queries. It monitors key metrics such as query response latency (p95), evidence freshness, citation accuracy, and compliance audit logs (HIPAA). Essential for ensuring timely, accurate, and regulatory-compliant patient care information retrieval.

This comprehensive checklist guides the secure and compliant deployment of OpenEvidence, a clinical decision support system. It covers critical requirements for handling Protected Health Information (PHI), including HIPAA-grade security, robust API integration best practices, mandatory monitoring setup, and resilience testing. Use this guide to ensure your healthcare-adjacent system meets the highest standards of compliance and reliability.

This guide demonstrates how to implement robust rate limiting and retry logic for critical healthcare APIs using a token bucket pattern. It covers managing specific service limits (e.g., clinical queries, evidence synthesis) and implementing strategies like exponential backoff and batch processing to ensure graceful degradation and reliable data retrieval in clinical decision support systems.

This guide provides a comprehensive roadmap for migrating and upgrading integrations with the OpenEvidence clinical AI platform. It addresses critical API changes, such as schema restructuring (e.g., flat answers to structured evidence), version detection, and updated citation formats. Developers can use this knowledge to implement robust migration logic, ensuring that downstream clinical applications maintain high levels of accuracy and safety when accessing evolving medical evidence.

A comprehensive guide on implementing failover and fallback mechanisms for Large Language Models (LLMs) when using OpenRouter. This skill covers native model fallbacks, provider routing strategies, and advanced client-side fallback chains. Use this pattern when building mission-critical or highly resilient systems that must maintain service availability even if a primary model or an entire provider goes offline. It ensures robust API integration and graceful degradation.

A comprehensive guide detailing common real-world mistakes and pitfalls when integrating with the OpenRouter API. Covers critical best practices for robust LLM deployment, including correct model ID formatting, cost control via max_tokens, secure API key management, handling rate limits, and optimizing client connection reuse. Essential for developers building multi-provider AI applications.