Api Doc StandardsSAFE
Overview
An agent skill published by revfactory.
459e1bb8f76eOBSERVED · 2026-10-12Host compatibility
What the documentation claims. We have not run a compatibility test.
| Host | Status | Notes |
|---|---|---|
| cursor | mentioned |
What it tells the agent
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-doc-standards
description: "API document writing tablelevel and pattern library. doc-writer agent REST/GraphQL/gRPC API document writingto do when reference tablelevel. 'API document tablelevel', 'API reference writing' request when usage. However, OpenAPI Spec specialist creation API test execution scope outside."
---
# API Doc Standards — API document writing tablelevel
doc-writer agent API document quality tablelevel and pattern.
## REST API document required section
```
1. overview — API purpose, target user, basic URL
2. authentication — authentication method, /
3. — request/ format, degree, error code
4. endpoint reference — by CRUD
5. error processing — error code ,
6. change capability — versionby changematters
```
## endpoint document template
```markdown
## POST /api/v1/users
user creation.
### request
****
| | | required |
|------|-----|------|
| Authorization | Bearer {token} | O |
| Content-Type | application/json | O |
**body text**
| | type | required | description | constraintcondition |
|------|------|------|------|---------|
| email | string | O | email | RFC 5322, 254specialist |
| name | string | O | name | 2~50specialist |
| role | string | X | role | admin/user/viewer, basic: user |
###
**nature (201 Created)**
{ "id": "usr_abc123", "email": "...", "name": "..." }
**error**
| status | code | description |
|------|------|------|
| 400 | INVALID_EMAIL | email |
| 409 | DUPLICATE_EMAIL | during email |
| 422 | VALIDATION_ERROR | nature |
```
## error tablelevel
```json
{
"error": {
"code": "RESOURCE_NOT_FOUND",
"message": "requestKorean number .",
"details": [{ "field": "user_id", "reason": "re-degree " }],
"request_id": "req_xyz789"
}
}
```
## HTTP status code mapping
| scope | un- | usage code |
|------|------|----------|
| 2xx | nature | 200, 201, 204 |
| 4xx | error | 400, 401, 403, 404, 409, 422, 429 |
| 5xx | from error | 500, 502, 503 |
## degree document tablelevel
### from based (recommended)
| un- | type | basic | description |
|---------|------|-------|------|
| limit | integer | 20 | item number (1~100) |
| cursor | string | - | next degree from |
: `has_more`, `next_cursor`
### based
| un- | type | basic | description |
|---------|------|-------|------|
| page | integer | 1 | degree |
| per_page | integer | 20 | item number |
| sort | string | created_at | standard |
| order | string | desc | direction |
## authentication section tablelevel
```markdown
## authentication
all API request Bearer needed.
### : POST /auth/token
### usage: Authorization: Bearer {access_token}
### : POST /auth/refresh ( when)
| status code | cause | action |
|----------|------|------|
| 401 | / | re-grade |
| 403 | authority insufficient | role confirm |
```
## Rate Limiting document tablelevel
| | limitation | |
|------|------|------|
| Free | 100 | minute |
| Pro | 1,000 | minute |
| Enterprise | 10,000 | minute |
: `X-RateLimit-Limit`, `X-RateLimit-Remaining`, `X-RateLimit-Reset`
exceeding when: 429 + `Retry-After`
## document tablelevel
- URL version: `/api/v1/`, `/api/v2/`
- exchange: /endpoint/option un- addition
- exchange impossible: deletion, structure change, required un- addition → version needed
- basis example: minimum 6months before
## document quality checklist
| item | standard |
|------|------|
| examplewhen | all endpoint request++error |
| type | string, integer, boolean, array, object |
| required/optional | all un- tablewhen |
| constraintcondition | , , pattern |
| authentication | endpointby needed authority |
| SDK example | cURL + 1items or more |
| change capability | date + change + impact scope |Trust audit
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.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | NA |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (0)
No findings outside the package's declared scope.
Gates applied: no_behavioural_pass.
459e1bb8f76efull audit observations/trust-audit/skill/revfactory__api-doc-standards.json · Report an issue / request a re-scanAudit history
Every audit this skill has had.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-12 | 459e1bb8f76e | SAFE | B | 89 | first audit |
Questions
Is Api Doc Standards safe to install?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.
What can Api Doc Standards access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
Which assistants does Api Doc Standards work with?
Its documentation mentions cursor. That is what the text claims, not a compatibility test we ran.
How current is this page?
The grade is for one exact copy of the source (459e1bb8f76e), read on 2026-10-12. The repository is watched, and a new audit runs when it changes — this is the first audit.