audit-external-apis

Audit external API integrations for HTTP timeouts, retries, and error handling.

Updated Feb 26, 2026
One-click install
npx skills add https://github.com/ElPoot/contabilidad --skill audit-external-apis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit-external-apis
Source: https://github.com/ElPoot/contabilidad/tree/main/.agents/skills/audit-external-apis
Command: npx skills add https://github.com/ElPoot/contabilidad --skill audit-external-apis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you audit integrations with external governmental and catalog APIs (Hacienda, ATV, CABYS) to reduce failures caused by missing timeouts, incorrect retry behavior, weak error handling, or mishandling credentials.

Core Features & Use Cases

  • HTTP call mapping: Scans the codebase for HTTP requests (requests.get/post/put/patch/delete), timeout configuration, and retry logic.
  • Resilience verification: Checks HTTP error handling for rate limiting (429), server errors (5xx), and network exceptions (ConnectionError/Timeout), including backoff behavior.
  • Credential safety audit: Verifies keyring usage and ensures there is no credential leakage via logging or hardcoded secrets.
  • Use case: When the accounting system stops correctly validating fiscal status due to an API outage or throttling, run this audit to confirm the integration layer fails safely and securely.

Quick Start

Ask the auditor to review gestor_contable/core/xml_manager.py, gestor_contable/core/atv_client.py, and gestor_contable/core/cabys_manager.py for timeouts, retries, HTTP error handling, and credential handling, then produce an explicit findings report.

Frequently Asked Questions about audit-external-apis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit external API calls for missing timeouts and retry behavior?

To audit external API calls, scan your codebase for HTTP requests and inspect their timeout configuration, retry backoff logic, and network exception handling. This verifies whether your integration layer fails safely during outages.

What is the best way to handle HTTP rate limiting and 5xx server errors in Python integrations?

Handling HTTP rate limiting and 5xx server errors requires implementing explicit retry and backoff policies. You must inspect your request methods to verify they catch 429 and 5xx responses and apply appropriate delays before retrying.

How do I map all HTTP requests in my codebase to verify error handling?

Mapping HTTP requests involves scanning your source files for methods like requests.get, post, put, patch, and delete. You then trace these calls to confirm they have explicit timeout settings and proper exception handling.

When do I need to audit my API integration layer for HTTP resilience?

You need to audit your API integration layer for HTTP resilience when external service outages or throttling cause your system to fail. Verifying timeout and retry policies ensures your application degrades gracefully under network stress.