Claude Skill

api-engineer

Read OpenAPI specs, call APIs, validate responses, and draft connectors. Use for integration work, contract testing, and client generation.

LLM Mart · 0 points · 0 0 0

Virus-scanned Reviewed automatically before listing.

Full trust report

Download navinspire-ia-navin-navin_skills_api-engineer-e9c73a3.zip · 0 KB

navinspire-ia/navin 31 4 forks AGPL-3.0 Updated 4d ago

Part of navinspire-ia/navin — 182 skills

Install

skills CLI npx skills add https://github.com/Navinspire-ia/navin/tree/main/navin/skills/api-engineer

Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install navinspire-ia-navin@llmmart

Git git clone https://github.com/Navinspire-ia/navin.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole navinspire-ia/navin collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

API Engineer

Overview

Treat OpenAPI/Swagger as the contract. Explore safely, then automate.

Workflow

Locate the spec (openapi.yaml, Swagger URL).
Map auth (bearer, basic, OAuth) - pull secrets from env.
Smoke-call read endpoints first (web_fetch / exec curl / dedicated tools).
Validate status codes and schema fields the user cares about.
When building a Navin tool/connector: small surface, clear errors, no secret logging.

Rules

Never commit tokens.
Prefer idempotent GETs for exploration.
Document rate limits and pagination when found.

Files (navin)

SKILL.md 823 B

---
name: api-engineer
description: Read OpenAPI specs, call APIs, validate responses, and draft connectors. Use for integration work, contract testing, and client generation.
metadata: {"navin":{"emoji":"🔌","category":"devops"}}
---

# API Engineer

## Overview

Treat OpenAPI/Swagger as the contract. Explore safely, then automate.

## Workflow

1. Locate the spec (`openapi.yaml`, Swagger URL).
2. Map auth (bearer, basic, OAuth) - pull secrets from env.
3. Smoke-call read endpoints first (`web_fetch` / `exec curl` / dedicated tools).
4. Validate status codes and schema fields the user cares about.
5. When building a Navin tool/connector: small surface, clear errors, no secret logging.

## Rules

- Never commit tokens.
- Prefer idempotent GETs for exploration.
- Document rate limits and pagination when found.