Skill UI

Details the deployment, hardening, and operation of a resilient Command and Control (C2) infrastructure using the open-source Sliver framework. This guide covers advanced techniques including multi-protocol listeners (mTLS, HTTP/S, DNS, WireGuard), deployable redirectors, and domain fronting, making it essential for authorized red-teaming and sophisticated adversary simulation.

This skill provides comprehensive methods to detect Cobalt Strike beacon command-and-control (C2) traffic. It uses advanced network forensics techniques, including analyzing default TLS certificates (e.g., serial 8BB00EE), JA3/JA3S fingerprints, HTTP malleable profiles, and beacon interval jitter, leveraging Zeek logs, Suricata rules, and Python PCAP analysis. It is essential for threat hunters and SOC analysts investigating sophisticated C2 communications.

Details how to implement robust API rate limiting and throttling using advanced techniques like Token Bucket, Sliding Window, and Fixed Window algorithms. Supports per-user, per-IP, and per-endpoint quotas, utilizing Redis for distributed counting. Essential for protecting APIs against brute force, credential stuffing, and resource exhaustion attacks, returning proper HTTP 429 responses.

This skill provides robust mechanisms to interact with the Clari API, specifically designed to handle rate limiting (HTTP 429 errors) and manage asynchronous bulk export jobs. It implements exponential backoff and sequential scheduling, ensuring reliable data retrieval and forecasting exports without hitting API limits. Ideal for automated data pipelines and background job processing.

Provides comprehensive guides on setting up ClickUp API v2 authentication. Learn how to implement both Personal API Tokens (for server-side use) and OAuth 2.0 (for multi-user applications). This skill covers secure credential management, making authenticated HTTP requests, and handling common API error codes, ensuring robust integration development.

This comprehensive guide serves as a quick reference for diagnosing and fixing common Flexport API v2 errors. It covers standard HTTP status codes (e.g., 401, 403, 422, 429, 5xx), detailing the causes and providing actionable fixes, including cURL examples and validation best practices. Essential for developers integrating supply chain solutions with Flexport.

A comprehensive guide for developers migrating between different versions of the Flexport API, specifically detailing changes from v1 to v2. It covers breaking changes in request headers, response parsing (e.g., _object to data), pagination formats, and error structures, ensuring smooth integration updates.

This guide provides a quick reference for diagnosing and fixing common errors encountered when using the Intercom API. It details specific HTTP status codes (e.g., 401, 404, 429), their root causes, and actionable solutions, including code snippets for secure API interaction and implementing backoff logic for rate limiting. Essential for developers troubleshooting integration failures.

A comprehensive developer resource for diagnosing and resolving common Canva Connect API errors and HTTP status codes. It details issues such as expired tokens (401), insufficient permissions (403), rate limiting (429), and validation failures (400), providing specific causes, error payloads, and code-level fixes for seamless integration development.

A comprehensive reference guide for diagnosing and fixing common Anthropic Claude API errors, categorized by HTTP status codes (400, 429, 500, etc.). Includes specific error JSON patterns, root causes (e.g., role alternation, rate limits), suggested fixes, and code examples in Bash and Python for effective troubleshooting.

This guide provides a comprehensive reference for diagnosing and resolving common integration errors encountered when using the AppFolio Stack API. It covers specific HTTP error codes (e.g., 401, 404, 409, 422, 429), detailing the root cause, recommended fixes, and best practices for robust error handling, such as implementing backoff strategies and re-authentication.

This guide provides comprehensive troubleshooting for common Attio REST API errors, detailing specific HTTP status codes (e.g., 400, 401, 429, 422). It explains the required error response format, common causes (like invalid scopes or rate limits), and actionable, proven fixes using code examples and best practices.