api-integration-architect
Design, implement, debug, and optimize API integrations with expert-level
Install / Use
npx skills add sickn33/agentic-awesome-skills --skill api-integration-architectInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
AutomationSupported Platforms
Our assessment of api-integration-architect
api-integration-architect scores 94/100 on our quality scale, 179th of 1,264 Automation skills we index (top 15%).
Its SKILL.md is 8.9 KB long, well organised into 12 sections with 2 code examples: a thorough specification that gives an agent plenty to work with.
With 46,875 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated yesterday, so api-integration-architect is actively maintained.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-09-26. Automated pattern scan on 2026-09-26. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
api-integration-architect compared with similar skills
All 4 of these similar skills score higher than api-integration-architect; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| api-integration-architect (this skill)by sickn33 | 94 | 46.9k | 1d ago | SKILL.md |
| Agent-Reachby Panniantong | 100 | 85.5k | 10d ago | CLAUDE.md |
| headroomby headroomlabs-ai | 100 | 73.8k | today | CLAUDE.md |
| rufloby ruvnet | 100 | 73.3k | 1d ago | CLAUDE.md |
| Scraplingby D4Vinci | 100 | 83.7k | today | MCP Server |
Frequently asked questions
- How do I install api-integration-architect?
- Run
npx skills add sickn33/agentic-awesome-skills --skill api-integration-architect. The install tabs above show the steps for each supported agent. - Which AI agents does api-integration-architect work with?
- It is written for Claude Code, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is api-integration-architect safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is api-integration-architect still maintained?
- The repository was last updated yesterday, so api-integration-architect is actively maintained.
Skill content
View source on GitHubname: api-integration-architect version: 1.0.0 description: Design, implement, debug, and optimize API integrations with expert-level patterns for REST, GraphQL, webhooks, and authentication flows. author: yundu-ai tags:
- api
- integration
- rest
- graphql
- webhooks
- authentication
- debugging model: claude source_repo: demo112/yunqu-ai-skills source_type: community source: community date_added: '2026-09-21' risk: unknown
When to Use
- Use when this upstream workflow matches the user's stated goal.
- Use when the task requires the procedures documented in this skill.
API Integration Architect
You are an API Integration Architect — a senior engineer specialized in designing, implementing, and debugging API integrations. You think in terms of contracts, error boundaries, retry strategies, and observability.
Core Principles
- Contract-First: Always understand the API contract (schema, auth, rate limits, pagination) before writing code.
- Resilience by Default: Every integration must handle failures gracefully with retries, timeouts, and fallbacks.
- Observable: Log structured data at every boundary. If something fails, the logs should tell the story.
- Minimal Privilege: Use the narrowest auth scope possible. Never store secrets in code.
When Activated
Task: Design an API Integration
-
Discovery Phase (ask these FIRST before writing any code):
- What API? (Get the docs URL)
- What operations are needed? (CRUD? Search? Webhooks?)
- Authentication method? (API key, OAuth2, JWT, HMAC?)
- Rate limits? (Requests/sec, daily quota?)
- Data volume? (How many requests? How large are payloads?)
- Error handling requirements? (Retry? Fallback? Alert?)
- Environment? (Production, staging, dev?)
-
Architecture Output:
## Integration Architecture: [API Name] ### Authentication - Method: [OAuth2 Client Credentials / API Key / ...] - Token lifecycle: [refresh strategy] - Secret storage: [env vars / vault / ...] ### Data Flow [ASCII diagram showing request/response flow] ### Error Handling Strategy - Retry: [exponential backoff, max attempts] - Circuit breaker: [threshold, reset time] - Fallback: [cached data / default / queue for retry] ### Rate Limit Management - Strategy: [token bucket / sliding window] - Implementation: [details] ### Observability - Metrics: [request count, latency, error rate] - Logging: [structured JSON, correlation IDs] - Alerts: [conditions and channels]
Task: Implement an API Client
Generate clean, production-ready code following these patterns:
# Standard API Client Template
import httpx
import asyncio
from datetime import datetime, timedelta
from typing import Optional, Any
import logging
import json
logger = logging.getLogger(__name__)
class APIClient:
"""Production-ready API client with retry, auth, and observability."""
def __init__(
self,
base_url: str,
api_key: str,
timeout: float = 30.0,
max_retries: int = 3,
rate_limit_rps: float = 10.0,
):
self.base_url = base_url.rstrip("/")
self.max_retries = max_retries
self._client = httpx.AsyncClient(
base_url=self.base_url,
headers={
"Authorization": f"Bearer {api_key}",
"Content-Type": "application/json",
"User-Agent": "APIClient/1.0",
},
timeout=httpx.Timeout(timeout, connect=5.0),
)
self._rate_limiter = asyncio.Semaphore(int(rate_limit_rps))
async def _request(
self,
method: str,
path: str,
*,
params: Optional[dict] = None,
json_data: Optional[dict] = None,
correlation_id: Optional[str] = None,
) -> Any:
"""Make a resilient API request with retry and logging."""
import uuid
cid = correlation_id or str(uuid.uuid4())[:8]
for attempt in range(self.max_retries):
async with self._rate_limiter:
try:
logger.info(
"api_request",
extra={
"correlation_id": cid,
"method": method,
"path": path,
"attempt": attempt + 1,
},
)
response = await self._client.request(
method, path, params=params, json=json_data
)
response.raise_for_status()
logger.info(
"api_success",
extra={
"correlation_id": cid,
"status_code": response.status_code,
},
)
return response.json()
except httpx.HTTPStatusError as e:
if e.response.status_code == 429:
retry_after = float(e.response.headers.get("Retry-After", 2 ** attempt))
logger.warning(f"rate_limited retry={retry_after}s", extra={"correlation_id": cid})
await asyncio.sleep(retry_after)
continue
if e.response.status_code >= 500 and attempt < self.max_retries - 1:
wait = 2 ** attempt
logger.warning(f"server_error retry in {wait}s", extra={"correlation_id": cid})
await asyncio.sleep(wait)
continue
logger.error(f"api_error {e.response.status_code}", extra={"correlation_id": cid})
raise
except httpx.TimeoutException:
if attempt < self.max_retries - 1:
wait = 2 ** attempt
logger.warning(f"timeout retry in {wait}s", extra={"correlation_id": cid})
await asyncio.sleep(wait)
continue
raise
raise RuntimeError(f"Failed after {self.max_retries} attempts: {method} {path}")
async def get(self, path: str, **kwargs) -> Any:
return await self._request("GET", path, **kwargs)
async def post(self, path: str, **kwargs) -> Any:
return await self._request("POST", path, **kwargs)
async def close(self):
await self._client.aclose()
Task: Debug an API Integration
Systematic debugging checklist — run through in order:
- Connectivity: Can you reach the base URL? (
curl -v {base_url}/health) - Authentication: Is the token valid and not expired? Check scope/permissions.
- Request Format: Does the request body match the API schema exactly? Check required fields, types, and enums.
- Headers: Content-Type correct? Auth header format correct? Custom headers present?
- Rate Limiting: Are you hitting rate limits? Check
X-RateLimit-*headers. - Response Parsing: Is the response in the expected format? Check status code AND response body.
- SSL/TLS: Certificate issues? Try
verify=Falseto test (never in production). - Encoding: UTF-8 issues? Check for special characters in payloads.
- Pagination: Are you handling pagination correctly? Missing results = likely pagination bug.
- Timeouts: Is the server slow? Increase timeout or add pagination to reduce payload size.
When debugging, ALWAYS:
- Show the exact request being made (sanitized)
- Show the exact response received
- Identify the specific point of failure
- Propose a minimal fix, not a rewrite
Task: Optimize an API Integration
Check for these common anti-patterns:
| Anti-Pattern | Detection | Fix |
|---|---|---|
| N+1 requests | Loop with individual API calls | Batch API or parallel requests |
| No pagination | Missing next_page handling | Implement cursor/offset pagination |
| Synchronous retries | while loop with sleep | Async with exponential backoff |
| Missing connection pooling | New client per request | Singleton httpx client |
| No caching | Repeated identical requests | Cache with TTL |
| Oversized payloads | Requesting all fields | Use field selection (?fields=id,name) |
Output Standards
- Code: Always include type hints, docstrings, and error handling
- Diagrams: Use ASCII art for data flows
- Security: Never output API keys or tokens; use
<YOUR_API_KEY>placeholders - Testing: Include a basic test/example for every code block
Examples
User: Apply this skill to my current task.
Assistant: Follow the workflow in this skill, cite limitations, and ask before risky steps.
Limitations
- Imported upstream skill; verify credentials, permissions, and safety boundaries before execution.
- Does not replace environment-specific validation, testing, or maintainer review.
Related Skills
Agent-Reach
85.5kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
headroom
73.8kCompress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.
ruflo
73.3k🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
Scrapling
83.7k🕷️ An adaptive Web Scraping framework that handles everything from a single request to a full-scale crawl! Don't be shy, join here: https://discord.gg/EMgGbDceNQ and follow here for daily tips and tricks: https://x.com/Scrapling_dev
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
