Skill UI

Automates dockerfile authoring with best practices for DevOps basics, guiding users from containerization patterns to CI/CD-ready configurations while validating outputs against standards.

A comprehensive quick-reference guide to diagnosing and resolving common Documenso API errors. Covers status codes (400, 401, 413, etc.), authentication issues, payload validation, rate limits, and best practices for successful document lifecycle management and API integration.

This guide provides comprehensive instructions for setting up and authenticating the Documenso SDK and API. Users will learn how to install the SDKs (TypeScript and Python), generate secure API keys, and initialize the client connection for both v1 (legacy) and v2 (recommended) API versions. It covers best practices for secure credential management within development projects.

Provides expert .NET/C# backend work for ASP.NET Core 8+ APIs, covering EF Core data access, authentication/authorization, background services, performance tuning, and production-ready patterns for enterprise services.

This skill specializes in building robust, scalable, and cloud-native backend microservices using the latest .NET 8 and C# 12 features. It masters modern architectural patterns, including Clean Architecture, CQRS with MediatR, and minimal APIs. Expertise covers secure authentication (JWT), data persistence with Entity Framework Core, asynchronous programming best practices, and comprehensive unit/integration testing, ensuring highly maintainable and performant code.

Auto-activating skill that assists with API Etag handler tasks, guiding REST/GraphQL/OpenAPI/authentication patterns, generating production-ready code, and validating standards.

Implement robust Role-Based Access Control (RBAC) specifically for Evernote integrations. This guide covers multi-tenant architectures, handling Evernote Business accounts, defining granular permissions (READ, WRITE, FULL), and creating authorization middleware. Essential for building secure, enterprise-grade SaaS applications that manage shared corporate data.

This runbook provides comprehensive, step-by-step procedures for managing critical incidents involving Evernote integrations. It covers diagnosing API outages, resolving persistent rate limits, handling authentication failures, and recovering from data synchronization issues. Use this guide during production troubleshooting or service outages to ensure rapid and systematic incident response, including circuit breaker activation and graceful degradation strategies.

This guide provides a comprehensive walkthrough for setting up the Evernote SDK and implementing OAuth 1.0a authentication. It details the entire process, from acquiring API keys via the developer portal, installing the SDK (for Node.js or Python), configuring environment variables, to initializing the client. Use this skill when starting a new Evernote integration or needing to verify secure API connectivity to the Evernote Cloud.

This guide provides a comprehensive setup for an efficient local development workflow when integrating with the Evernote API. It covers establishing a proper project structure, configuring sandbox credentials, and implementing both Developer Token and full OAuth flows. Use this when setting up testing environments and ensuring reliable API connectivity.

This guide provides comprehensive best practices for securing Evernote API integrations. It covers essential topics like secure credential management using environment variables or vaults, implementing CSRF-protected OAuth flows, encrypting access tokens at rest using AES-256-GCM, rigorous input validation, and ensuring secure logging practices by redacting sensitive data. Use this when hardening your application against data breaches.

A comprehensive diagnostic tool designed for deep debugging of complex Exa system issues. It systematically checks multiple layers (DNS, Authentication, Neural Search, Content Retrieval, etc.) and provides detailed latency profiling (p50, p95) to pinpoint performance bottlenecks or intermittent failures. Use this when standard troubleshooting steps fail or when preparing detailed evidence for support escalation.