backend-api
Design REST API Endpoints
Backend teams need consistent routes, status codes, and request patterns. This skill guides REST API design, endpoint changes, and documentation.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "backend-api" from https://skillstore.io/skills/eis-its-backend-api.md and its manifest at https://skillstore.io/api/skills/eis-its-backend-api/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "backend-api". Design endpoints for customer orders with pagination and status filters.
Expected outcome:
- A resource plan with collection and item routes.
- Recommended methods for listing, creating, updating, and deleting orders.
- Pagination and filtering guidance for order status and date ranges.
- Status code guidance for successful, invalid, unauthorized, and missing resources.
Using "backend-api". Review route naming for a versioned inventory API.
Expected outcome:
- A consistency review of route names and resource boundaries.
- Suggestions for version placement and nested resource depth.
- Notes about query parameters for sorting and filtering.
- Documentation updates needed for client teams.
Security Audit
SafeOne static finding was confirmed. SKILL.md instructs the agent to follow a relative link outside the skill directory, which creates an unsafe filesystem dependency. No evidence of prompt injection, network activity, command execution, or data exfiltration was found.
Capability review items (1)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Risk Factors
📁 Filesystem access (1)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/eis-its-backend-api/audits/10?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/eis-its-backend-api?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/eis-its-backend-api?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/eis-its-backend-api/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/eis-its-backend-api.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
EIS-ITS. (2026). backend-api security audit report (audit version 10) [Author version unspecified]. Skillstore. https://skillstore.io/skills/eis-its-backend-api/audits/10BibTeX citation
@techreport{eis-its-eis-its-backend-api-2026,
author = {EIS-ITS},
title = {backend-api security audit report (audit version 10)},
institution = {Skillstore},
year = {2026},
number = {10},
url = {https://skillstore.io/skills/eis-its-backend-api/audits/10},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "backend-api security audit report (audit version 10)"
version: "unspecified"
type: report
authors:
- name: "EIS-ITS"
date-released: "2026-07-09"
url: "https://skillstore.io/skills/eis-its-backend-api/audits/10"
identifiers:
- type: other
value: "skillstore:eis-its-backend-api:audit:10"
description: "Skillstore immutable audit report identifier"
Compare variants
2 installable variantsEach author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.
Why this variant is first
devanb-backend-api
2026-08-21
eis-its-backend-api
2026-08-21
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Plan a New Resource Endpoint
Define routes, methods, request fields, response behavior, and status codes for a new backend resource.
Standardize Existing Routes
Review route names, nesting, versioning, and query parameters for consistency across a service.
Prepare API Documentation
Turn endpoint behavior into clear documentation for client teams and OpenAPI specifications.
Try These Prompts
Design REST endpoints for a new resource named [resource]. Include routes, methods, status codes, and response behavior.
Review these API routes for REST consistency. Check naming, nesting, methods, query parameters, and versioning.
Propose middleware for authentication, validation, rate limiting, and usage tracking for this API surface.
Refactor this API contract for consistent resources, pagination, error responses, status codes, and documentation updates.
Best Practices
- Use resource nouns for URLs and reserve verbs for HTTP methods.
- Define status codes, error shapes, and pagination behavior before implementation.
- Document authentication, validation, rate limits, and response examples with each endpoint.
Avoid
- Do not mix action names into URLs when a resource model fits.
- Do not add nested routes that hide ownership or make authorization unclear.
- Do not ship endpoint changes without updating API documentation.