AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Api Design

skill-omnigentx-jarvis-api-design · by omnigentx

>

No reviews yet
0 installs
34 views
0.0% view→install

Install

$ agentstack add skill-omnigentx-jarvis-api-design

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No 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 Used
  • 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.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-omnigentx-jarvis-api-design)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
2mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

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 →
Are you the author of Api Design? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

API DESIGN

Workflow

  1. Identify use cases from the BRD.
  2. Pick a pattern: REST / WebSocket / gRPC.
  3. Define endpoints.
  4. Write schemas (request/response types).
  5. Document error codes and edge cases.

REST API template

### [METHOD] /api/v1/resource

**Description**: what it does

**Request**:
- Headers: `Authorization: Bearer `
- Body:
  ```json
  { "field": "type", "description": "..." }
  ```

**Response 200**:
```json
{ "data": {...}, "message": "success" }

Error codes: | Code | Meaning | |------|---------| | 400 | Invalid request | | 401 | Unauthorized | | 404 | Not found |


## Rules
- Endpoint paths use plural nouns (`/users`, not `/user`).
- Versioning lives in the URL (`/api/v1/`).
- Always use a single, consistent error-response shape.
- Paginate list endpoints (`?page=1&limit=20`).

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [omnigentx](https://github.com/omnigentx)
- **Source:** [omnigentx/jarvis](https://github.com/omnigentx/jarvis)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.