Skill UI

Automated help for npm script workflows inside DevOps Basics, offering guided best practices, production-ready configs, and validation for CI/CD or infrastructure requests.

Automates oauth callback handler tasks for API integrations, offering best-practice guidance, production-ready code/config, and validation when you mention oauth callbacks, integrations, or request implementation help.

Guides developers through OAuth2 Flow Helper tasks within Security Fundamentals by providing best-practice instructions, generating production-ready code/configs, and validating outputs for authentication, validation, and secure coding.

This comprehensive workflow guides users through building a complete Obsidian plugin from an empty directory. It covers all necessary components, including the core Plugin class, settings panel, command definitions, ribbon icons, manifest configuration, and production build setup using esbuild and TypeScript. It is essential for developers starting a new plugin project or learning the entire Obsidian plugin lifecycle.

Master the art of building complex, production-grade user interfaces for Obsidian plugins. This guide covers implementing custom sidebar views (ItemView), interactive modal dialogs (for forms and confirmations), context menus, status bar widgets, and advanced editor commands. Learn how to interact with the Obsidian Vault API for file manipulation, significantly enhancing your plugin's functionality and user experience.

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 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.

This guide provides essential, production-ready architectural patterns for building highly reliable Obsidian plugins. It addresses common development pitfalls such as managing typed settings with versioned migration, implementing safe vault operations (check-before-act), and handling event listeners to prevent memory leaks. Use these patterns when hardening your plugin for public release or refactoring for maximum stability.

Automates OpenAPI specification work by guiding API developers through best practices, generating production-ready code/configs, and validating outputs for REST, GraphQL, and authentication design patterns.

This skill provides a complete guide to deploying a containerized OpenEvidence clinical evidence integration service using Docker. It establishes a HIPAA-conscious production environment, enabling secure connections to the OpenEvidence API. Users can query clinical evidence, retrieve summarized medical literature, and validate treatment recommendations, all while maintaining audit logging and data-at-rest encryption compliance. Includes setup for health checks and rolling updates.

This guide outlines the strict multi-environment setup for the OpenEvidence clinical AI system, crucial for maintaining HIPAA compliance. It details how to configure and validate separate environments (Development, Staging, Production) to manage different data classifications—synthetic, de-identified, and full PHI. The process emphasizes environment validation checks, BAA adherence, and robust audit logging to prevent regulatory violations and PHI exposure.