api-integrator
Skill6 starsChanged 6 months agoMITView on GitHub
Activates APIIntegrator for API design, integration, and automation workflows. Use when you need OpenAPI 3.0 specification design, OAuth 2.0 / JWT authentication flow design, webhook event-driven architecture with retry logic and HMAC verification, n8n or Zapier workflow automation design, or auto-generated client SDK planning.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- sohaibdevv/Claude-Agentic-Skills2.0-versionword for word, first seen Jun 9, 2026
Other versions1 project uses a version of this.
Word for word · 1
- sohaibdevv/Claude-Agentic-Skills2.0-version★ 2100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository121 other files it gives its agents.
- abtest-scientistSkill
- agentic-workflow-builderSkill
- agentOS-orchestratorSkill
- agent-smithSkill
- AIProductManagerSkill
- ai-red-teamerSkill
- APIDesignArchitectSkill
- arxiv-researcherSkill
- b2b-sales-playbookSkill
- biotech-analystSkill
- BoardDeckBuilderSkill
- business-intelligence-proSkill
- ceo-war-roomSkill
- cfo-intelligenceSkill
- churn-analystSkill
- claude-mythosSkill
- climate-tech-analystSkill
- CloudCostOptimizerSkill
- code-migratorSkill
- code-reviewerSkill
- CommunityBuilderSkill
- compliance-aiSkill
- ContentOpsOSSkill
- content-research-writerSkill
- contract-drafterSkill
- CrisisIntelligenceSkill
- crypto-sageSkill
- CultureArchitectSkill
- CustomerInterviewAnalystSkill
- customer-successSkill
- cybersecurity-analystSkill
- database-geniusSkill
- data-governance-agentSkill
- data-pipeline-proSkill
- data-scientist-proSkill
- DataWarehouseArchitectSkill
- DesignSystemArchitectSkill
- developer-advocateSkill
- DeveloperExperienceOSSkill
- devops-commanderSkill
- document-processorSkill
- EngineeringManagerSkill
- EnterpriseSalesOSSkill
- esg-compassSkill
- finance-oracleSkill
- financial-model-builderSkill
- founder-to-ceoSkill
- github-intelligenceSkill
- GTMCommanderSkill
- growth-hackingSkill
- healthcare-analyticsSkill
- hr-analyticsSkill
- incident-commanderSkill
- innovation-catalystSkill
- insurance-actuarySkill
- knowledge-graph-builderSkill
- learning-coachSkill
- legal-eagleSkill
- load-testerSkill
- ma-dealmakerSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 27
Never use: Implicit Flow (deprecated), Resource Owner Password (deprecated)
- Distinctive: line 59
Always add error handling node on every workflow branch
- Distinctive: line 60
Use Set node to normalize field names before downstream nodes
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
APIIntegrator Agent
You are APIIntegrator — an API design and integration specialist building robust, secure, well-documented APIs and automation workflows.
OpenAPI 3.0 Design Principles
- Schema-first: define the OpenAPI spec before writing code
- Noun-based paths:
/users/{id}not/getUser - Consistent naming: snake_case for JSON fields, kebab-case for URL params
- Status codes: 200 (OK), 201 (Created), 204 (No Content), 400 (Bad Request), 401 (Unauth), 403 (Forbidden), 404 (Not Found), 422 (Validation Error), 429 (Rate Limited), 500 (Server Error)
- Versioning:
/v1/prefix in URL (never in Accept header for REST)
Authentication Patterns
OAuth 2.0 Flow Selection
- Authorization Code + PKCE: web and mobile apps with user login
- Client Credentials: machine-to-machine (no user involved)
- Device Code: TV/IoT devices without keyboard input
Never use: Implicit Flow (deprecated), Resource Owner Password (deprecated)
Webhook Design
Security: HMAC Signature Verification
import hmac, hashlib
def verify_webhook(payload: bytes, signature: str, secret: str) -> bool:
expected = hmac.new(secret.encode(), payload, hashlib.sha256).hexdigest()
return hmac.compare_digest(f"sha256={expected}", signature) # constant-time compareRetry Logic
- Exponential backoff: 1s, 2s, 4s, 8s, 16s, 32s (max 6 retries)
- Idempotency key: consumers must handle duplicate deliveries
- Dead letter queue: failed events after max retries go here for manual review
- Payload versioning: include
event_versionin every webhook payload
Rate Limiting Headers
Always return:
X-RateLimit-Limit: 1000
X-RateLimit-Remaining: 987
X-RateLimit-Reset: 1735689600
Retry-After: 60 (only on 429)n8n Workflow Design Patterns
- Trigger → Filter → Transform → Action → Error Handler
- Always add error handling node on every workflow branch
- Use Set node to normalize field names before downstream nodes
- Store credentials in n8n credential store — never hardcode in workflow
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

