Skill UI

Implement comprehensive observability for Apollo.io API integrations. This skill provides structured instrumentation covering Prometheus metrics (request count, latency, rate limits, credits used), structured logging with PII redaction, and OpenTelemetry tracing. It ensures reliable tracking of API health, performance, and resource consumption.

This comprehensive tool provides an automated, multi-stage checklist for deploying Apollo.io integrations to a production environment. It validates crucial aspects including secure authentication (API keys, headers), system resilience (rate limiting, retry logic), observability (PII redaction, structured logging), and financial controls (credit tracking). Use this checklist before going live or when performing production system audits to ensure full compliance and stability.

A comprehensive guide covering security best practices for integrating with the Apollo.io API. This includes secure key storage (using secret managers/env vars), implementing PII redaction for logging, adhering to the principle of least privilege (using standard vs. master keys), and performing key rotation procedures. Essential for building secure and compliant integrations.

This guide details security best practices for integrating with Clay. It covers securing API keys, validating webhook signatures, isolating provider credentials, and redacting sensitive PII data. Essential for maintaining compliance and data integrity in production environments.

Guide for automating Codacy tasks through Composio’s Rube MCP, highlighting connection setup, tool discovery, and execution patterns while always fetching schemas first.

This skill provides a comprehensive solution for implementing observability for Customer.io integrations. It covers setting up Prometheus metrics (latency, request counts, bounces), structured JSON logging with PII redaction, and OpenTelemetry tracing. Use it when building robust, production-grade monitoring dashboards and alerting systems for Customer.io APIs.

Implements best practices for secure audio transcription using Deepgram. This guide covers PII redaction (built-in and custom patterns), secure audio upload to S3 with encryption, managing data retention policies, and ensuring compliance with major regulations like GDPR and HIPAA. It provides a comprehensive pipeline for handling sensitive audio data in enterprise applications.

This skill provides a comprehensive and isolated setup for managing Deepgram API integrations across different deployment stages (Development, Staging, Production). It includes typed configuration management, a client factory pattern, and Docker Compose profiles, ensuring that each environment uses specific credentials, models, and feature settings (like diarization or PII redaction) without conflict. Ideal for robust, multi-stage application deployment.

A comprehensive checklist and guide for deploying Deepgram integrations into a production environment. It covers critical areas including robust authentication practices, system resilience design (e.g., backoff strategies, circuit breakers), performance optimization (singleton clients, audio preprocessing), security measures (PII redaction), and mandatory monitoring setup (Prometheus metrics and alert rules). Essential for any go-live phase.

A comprehensive guide detailing security best practices for Deepgram API integration. It covers critical topics such as implementing scoped API keys, key rotation strategies, enabling built-in PII redaction for sensitive data, generating temporary client-side keys, and validating audio URLs to prevent SSRF attacks. Use this when building robust, production-grade applications requiring high data security and compliance.

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.

This utility collects comprehensive diagnostic data for troubleshooting Firecrawl issues. It automatically checks environment variables, verifies API connectivity, captures SDK versions, gathers recent error logs, and runs diagnostic scrapes. This is essential for generating complete, redacted support tickets when encountering persistent or hard-to-reproduce bugs.