05 Api GeneratorSAFE

From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.

04-api-generator/
├── SKILL.md                    # Main skill file
├── PATTERNS.md                 # Framework detection patterns
├── STANDARDS.md                # Documentation standards
├── EXAMPLES.md                 # Input/output examples
├── templates/
│   ├── index.md               # API index template
│   ├── endpoint.md            # Endpoint documentation template
│   └── openapi.yaml           # OpenAPI spec template
└── scripts/
├── detect_routes.py       # Route detection script
└── validate_openapi.sh    # OpenAPI validation script

Please document this Express route:
router.get('/users/:id', userController.getUser);

Scan the src/routes directory and generate API documentation for all endpoints.

Generate an OpenAPI 3.0 spec for the API defined in src/api.

# Detect all routes
python scripts/detect_routes.py src/

# Detect Express routes only
python scripts/detect_routes.py src/ --framework express

# Save to file
python scripts/detect_routes.py src/ -o routes.json

# Validate an OpenAPI spec
./scripts/validate_openapi.sh api-spec.yaml

The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.

---
name: api-generating
description: Generate API endpoint code and documentation from specifications. Use when the user wants to create new API endpoints, generate route handlers, scaffold REST APIs, or produce OpenAPI/Swagger specs from code.
allowed-tools:
  - Read
  - Grep
  - Glob
  - Write
  - Bash(python:*)
  - Bash(./scripts/*:*)
---

# API Documentation Generator

Generate comprehensive API documentation from source code.

## Quick Reference

| Task | Resource |
|------|----------|
| Identify framework | See `PATTERNS.md` |
| Documentation standards | See `STANDARDS.md` |
| Example outputs | See `EXAMPLES.md` |

## Process

### Step 1: Identify API Endpoints

Look for route definitions. For framework-specific patterns, see `PATTERNS.md`.

### Step 2: Extract Information

For each endpoint, extract:
- HTTP method (GET, POST, PUT, DELETE, etc.)
- Path/route
- Parameters (path, query, body)
- Request/response schemas
- Authentication requirements

### Step 3: Generate Documentation

Use the template in `templates/endpoint.md` for each endpoint.

### Step 4: Create Overview

Generate an index using `templates/index.md`.

## Output Formats

### Markdown (Default)
Generate markdown suitable for README or docs site.

### OpenAPI/Swagger
If requested, generate OpenAPI 3.0 spec. See `templates/openapi.yaml`.

## Automation

To auto-detect routes:
```bash
python scripts/detect_routes.py <source_directory>
```

To validate OpenAPI spec:
```bash
./scripts/validate_openapi.sh <spec_file>
```

SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.

What the source does

Filesystem

none-observed

Network

none-observed

Shell

none-observed

Dependencies

pinned

Secrets in source

none-found

Findings (1)

Gates applied: no_behavioural_pass, no_license.