api-dev
Build Production-Ready APIs
Teams need consistent patterns for fast, secure APIs. This skill provides reusable async, testing, documentation, caching, and deployment guidance.
This skill is part of a pack
Install the whole pack to get every skill the task needs, in one command.
Do not auto-install this skill.
The canonical policy requires operator review before any installation action.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "api-dev" from https://skillstore.io/skills/azeem-2-api-dev.md and its manifest at https://skillstore.io/api/skills/azeem-2-api-dev/manifest. Verify the artifact. Do not auto-install. Inspect the skill and report your findings, then wait for an operator or manual installation decision.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 "api-dev". I need a user profile API for a mobile app.
Expected outcome:
- A versioned endpoint plan for create, read, update, and delete operations.
- A standard error response model with validation and authorization cases.
- OpenAPI documentation notes for pagination, authentication, and rate limits.
Using "api-dev". My API slows down when external services fail.
Expected outcome:
- A circuit breaker strategy with failure thresholds and reset timing.
- Timeout, retry, and connection pool recommendations for async calls.
- Metrics to track latency, error rate, and dependency health.
Using "api-dev". I need tests for a new API workflow.
Expected outcome:
- A focused async test plan for create, read, update, and delete flows.
- Checks for pagination, hidden password fields, and rate limiting behavior.
- Mocking guidance for external services and integration boundaries.
Security Audit
CriticalMost static findings are false positives from Markdown code fences, placeholder URLs, request object names, and Redis URL parameters in examples. One critical issue is confirmed: the caching example deserializes Redis data with pickle.loads, which can enable code execution if cache data is controlled or poisoned. No prompt injection or malicious marketplace intent was found.
Confirmed security concerns (1)
Risk Factors
⚙️ External commands (15)
🌐 Network access (11)
🔑 Env variables (8)
Detected Patterns
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/azeem-2-api-dev/audits/9?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/azeem-2-api-dev?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/azeem-2-api-dev?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/azeem-2-api-dev/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/azeem-2-api-dev.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
Azeem-2. (2026). api-dev security audit report (audit version 9) [Author version unspecified]. Skillstore. https://skillstore.io/skills/azeem-2-api-dev/audits/9BibTeX citation
@techreport{azeem-2-azeem-2-api-dev-2026,
author = {Azeem-2},
title = {api-dev security audit report (audit version 9)},
institution = {Skillstore},
year = {2026},
number = {9},
url = {https://skillstore.io/skills/azeem-2-api-dev/audits/9},
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: "api-dev security audit report (audit version 9)"
version: "unspecified"
type: report
authors:
- name: "Azeem-2"
date-released: "2026-07-05"
url: "https://skillstore.io/skills/azeem-2-api-dev/audits/9"
identifiers:
- type: other
value: "skillstore:azeem-2-api-dev:audit:9"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Design a New API Service
Plan endpoints, versioning, error responses, and documentation before implementation starts.
Standardize Platform API Patterns
Create shared guidance for rate limits, caching, monitoring, and production configuration.
Build API Test Coverage
Draft async unit, integration, pagination, and rate limit tests for service workflows.
Try These Prompts
Use this skill to design a REST API for a small service. Include endpoints, status codes, error shapes, and OpenAPI notes.
Use this skill to review my API middleware plan for authentication, validation, logging, rate limiting, and error handling.
Use this skill to improve an async API client. Focus on connection pooling, timeouts, circuit breakers, caching, and observability.
Use this skill to audit my API for production readiness. Cover security headers, versioning, tests, monitoring, cache safety, and rollback risks.
Best Practices
- Adapt examples to your framework and verify security before deployment.
- Use explicit timeouts, connection limits, and structured error responses.
- Document versioning, rate limits, authentication, and deprecation rules.
Avoid
- Do not copy cache serialization examples without replacing unsafe pickle usage.
- Do not expose credentials or connection strings in logs, docs, or examples.
- Do not rely on tests alone without production monitoring and dependency health checks.