Api Generator

API code generator. Generate RESTful endpoints, GraphQL schemas, OpenAPI/Swagger docs, API clients, mock servers, authentication, rate limiting.

Security Scan

The skill is internally coherent for an API scaffolding/generator: its files and instructions match the claimed functionality and it does not request unrelated credentials or perform network exfiltration.

Purpose & Capability

Name/description (API code generator for REST/GraphQL/Swagger/clients/mocks/auth/rate-limiting/tests) align with the included scripts and templates. The two provided scripts produce the claimed outputs and suggested tooling (npm/pip) is only referenced in templates or usage hints — nothing appears unrelated to API generation.

Instruction Scope

SKILL.md directs the agent to run scripts/apigen.sh which generates templates to stdout; that stays within the stated purpose. Note: scripts/script.sh also provides a CLI-like helper that creates a per-user data directory and logs actions (history.log). Templates include references to environment variables (e.g., JWT_SECRET) as placeholders; the skill does not attempt to read arbitrary system files or external secrets.

Install Mechanism

No install spec is provided (instruction-only) and the included code is local shell/Python template generation. No downloads, third-party registries, or archive extraction are performed by the skill itself.

Credentials

The skill declares no required environment variables or credentials. References to env vars appear only in generated template snippets (e.g., JWT_SECRET) which are normal for auth examples and not requested/consumed by the skill at runtime.

Persistence & Privilege

always is false and the skill does not request elevated privileges. However, scripts/script.sh will create a data directory (default: ${APIGEN_DIR:-${XDG_DATA_HOME:-$HOME/.local/share}/api-generator}) and append to $DATA_DIR/history.log — local persistence in the user's home directory. This is reasonable for a scaffolding tool but worth noting to users who expect no filesystem writes.

Assessment

This skill appears to do what it claims: generate API scaffolds and example code. Before running, review the bundled scripts (scripts/apigen.sh and scripts/script.sh). They are local template generators and do not make network calls, but script.sh will create ~/.local/share/api-generator (or $APIGEN_DIR/XDG_DATA_HOME) and append a history.log — if you prefer no writes, set APIGEN_DIR to a tmp path or inspect output without running stateful commands. Also review generated auth templates (they reference secrets like JWT_SECRET with 'change-me-in-production') and audit any generated code before using in production. If you need extra assurance, run the scripts in an isolated environment or container.

Generate production-ready API code scaffolds from zero. REST, GraphQL, auth, tests — all in one tool.

Usage

bash scripts/apigen.sh <command> <resource_name> [options]

Commands

Core Generation

• rest <name> — RESTful CRUD endpoints (Express.js)
• graphql <name> — GraphQL Type + Query + Mutation schema
• swagger <name> — OpenAPI 3.0 specification document

Utilities

• client <name> — Python API client class
• mock <name> — Mock API server with in-memory store
• auth <type> — Auth code (jwt / oauth / apikey)
• rate-limit <type> — Rate limiter (token-bucket / sliding-window)
• test <name> — Jest + Supertest API test suite

Examples

bash scripts/apigen.sh rest user          # RESTful user endpoints
bash scripts/apigen.sh graphql product    # GraphQL product schema
bash scripts/apigen.sh auth jwt           # JWT authentication
bash scripts/apigen.sh test order         # Order API tests

Output

All code prints to stdout. Copy or redirect into your project files. Generated code includes full comments and can serve as a project starting point.

💬 Feedback & Feature Requests: https://bytesagain.com/feedback Powered by BytesAgain | bytesagain.com