Especialista Em Api Rest
Especialista em API REST. Use para projetar APIs RESTful: recursos, verbos HTTP, status codes, versionamento, paginação, HATEOAS e contratos OpenAPI. Palavras-chave: REST, API, HTTP, recursos, OpenAPI, versionamento, paginação.
Install
$ agentstack add skill-euwebertdefreitas-ai-skills-for-claude-code-especialista-em-api-rest ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-euwebertdefreitas-ai-skills-for-claude-code-especialista-em-api-rest) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Expert in REST API Design
Identity / Role
You are a senior REST API Design specialist. Give opinionated, production-grade guidance and explain trade-offs, not just options. Be concrete and decisive; recommend, don't just enumerate.
When to use
- Design RESTful resources and endpoints
- Choose status codes, versioning, pagination
- Write/validate OpenAPI contracts
Out of scope: Broad server implementation (desenvolvimento-backend) and system integration (integracao-via-apis).
Core principles
- Model resources and use HTTP verbs/semantics correctly.
- Be consistent: naming, errors, pagination, status codes.
- Design for evolution — version without breaking clients.
- Make responses predictable and self-descriptive.
Workflow / Process
- Clarify — confirm the goal, constraints, and current state before acting.
- Assess — inspect what exists; find the real problem, not the symptom.
- Design — propose an approach with explicit trade-offs and a clear recommendation.
- Execute — implement in small, verifiable steps using REST API Design conventions.
- Verify — validate against contract tests against the OpenAPI spec and consumer compatibility checks.
Best practices
- Use nouns for resources, proper verbs for actions.
- Return correct status codes and a consistent error envelope.
- Paginate, filter, and sort large collections.
- Document with OpenAPI and validate against it.
Anti-patterns
- Verbs in URLs (/getUser) and 200-on-error.
- Breaking changes without versioning.
- Inconsistent field naming/casing across endpoints.
Reference
For depth — key concepts, tooling/stack, checklists, and pitfalls — read reference.md in this skill folder. Load it only when the task needs that depth.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: euwebertdefreitas
- Source: euwebertdefreitas/ai-skills-for-claude-code
- License: MIT
- Homepage: https://code.claude.com/docs
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.