Skill UI

Mandates Taskwarrior integration for every coding request by decomposing work into tracked tasks, starting them, syncing Timewarrior time tracking, and enforcing the full add→start→done lifecycle before writing code.

This skill provides comprehensive methods for building event-driven integrations with Apollo.io. Since Apollo lacks native webhooks, it covers advanced techniques like polling the Contacts API, tracking contact stage changes, monitoring sequence engagement, and automating follow-up tasks. Ideal for achieving real-time CRM data synchronization and workflow automation.

This skill provides comprehensive methods for building event-driven integrations with Apollo.io. Since Apollo lacks native webhooks, it covers advanced techniques like polling the Contacts API, tracking contact stage changes, monitoring sequence engagement, and automating follow-up tasks. Ideal for achieving real-time CRM data synchronization and workflow automation.

A comprehensive guide for diagnosing and fixing common integration errors with Customer.io. It covers critical topics such as API status codes (400, 401, 429), authentication failures, incorrect timestamp formatting, and best practices for event tracking and transactional message delivery. Use this resource when troubleshooting campaign failures or API calls failing.

This comprehensive guide identifies and explains the most common anti-patterns and mistakes when integrating with Customer.io. It covers crucial development topics, including proper API key usage, Unix timestamp formatting, ensuring correct event tracking order (Identify before Track), and optimizing API calls for performance. Use this as a definitive checklist for code review and developer onboarding.

Guides engineers through initializing MCUs, crafting RTOS-aware drivers, and tuning power/timing for STM32, ESP32, and bare-metal targets; covers constraint analysis, interrupt safety, resource tracking, and validation with static analysis and real-time debugging.

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 reference architecture guides the integration of OpenEvidence into clinical decision support systems (CDS). It is designed for healthcare platforms needing evidence-based query processing, deterministic citation tracking, and full audit logging. Key considerations include HIPAA compliance, optimizing for sub-second response times in point-of-care workflows, and establishing robust data models and event pipelines.

A comprehensive technical audit checklist designed to validate the production readiness of OpenRouter API integrations. It covers critical areas including security practices (e.g., secret management, key rotation), system reliability (e.g., fallbacks, retries, timeouts), and observability requirements (e.g., structured logging, cost tracking). Use this guide before launching or during major operational reviews to ensure robust, scalable, and compliant deployments.

This guide provides a comprehensive workflow for setting up a robust local development environment for PostHog integrations. It covers enabling debug mode for real-time event inspection, implementing mocking strategies for stable unit testing, and configuring integration tests using a dedicated development PostHog project. Use this when building or testing analytics tracking features with posthog-js or posthog-node to ensure fast, isolated development cycles.

This comprehensive guide provides methods for implementing deep observability for Replit deployments. It covers building detailed health check endpoints (tracking uptime, memory, and DB status), setting up structured JSON logging, detecting cold start events, and configuring external alerting mechanisms (e.g., UptimeRobot, Slack). Use this when building robust, production-grade applications that require continuous performance monitoring and reliability tracking.

This comprehensive guide provides a phased strategy for migrating error tracking services from legacy tools like Rollbar, Bugsnag, or New Relic to Sentry. It covers crucial steps including concept mapping between diverse providers, implementing safe parallel reporting (dual-write), validating data parity via API comparison, and performing the final cutover to ensure continuous monitoring and zero downtime.