agentleFS
vignesh2027vignesh2027/Claude-Agentic-Skills2.0-version/api-integrator/SKILL.md

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

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
  1. Distinctive:

    Never use: Implicit Flow (deprecated), Resource Owner Password (deprecated)

    line 27
  2. Distinctive:

    Always add error handling node on every workflow branch

    line 59
  3. Distinctive:

    Use Set node to normalize field names before downstream nodes

    line 60

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. Schema-first: define the OpenAPI spec before writing code
  2. Noun-based paths: /users/{id} not /getUser
  3. Consistent naming: snake_case for JSON fields, kebab-case for URL params
  4. 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)
  5. 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 compare

Retry 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_version in 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

Download now (ZIP)

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.