用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt;运行前请先检查来源。
npx skills add https://github.com/sujian666666com-glitch/kk-skill --skill api-doc-writer命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地?可下载 SkillsMP 当前能够提供的文件。
Discover and filter 15,330 The Graph subgraphs by domain, network, protocol type, or natural language goal. Each result includes an x402 query URL — $0.01 USDC on Base per call, no API key required.
Audit and reduce AI agent runtime spend in dollars. Use for AI costs, agent spend, token waste, runtime attribution, detector coverage, and FinOps. Works with OpenClaw, Hermes, QM, Claude Code, Cursor, and generic event ingest.
Use this skill whenever the user is troubleshooting a VMware/vSphere problem — a reported error, an exception, a log dump, a slow or failed VM, a host that went sideways — and needs help locating the root cause. It is the diagnostic brain of the VMware family: it drives a systematic investigation, pulls the right signals from the other skills, correlates events into one timeline, ranks root-cause hypotheses, and tells you what to check next even when you don't know where to start. Always use this skill for "diagnose this VMware issue", "why is my VM slow", "troubleshoot this vSphere error", "what does this log mean", "help me figure out what broke" when the context is explicitly VMware/vSphere/ESXi/NSX. It is READ-ONLY: it never changes anything. Do NOT use it to execute fixes — single fixes go to vmware-aiops, multi-step gated remediation goes to vmware-pilot. Do NOT use it for routine inventory or health checks with no problem to solve — use vmware-monitor.
基于 SOC 职业分类
正在显示 SKILL.md
| name | api-doc-writer |
| description | API接口文档助手。用于编写REST API文档、定义接口规范、生成接口说明。当需要编写API文档、接口规范时触发。 |
# API接口文档
版本:V1.0
更新日期:YYYY-MM-DD
维护人:XXX
---
## 接口概览
| 模块 | 接口数 | 负责人 |
|------|--------|--------|
| 用户模块 | 5 | @xxx |
| 订单模块 | 8 | @xxx |
| 支付模块 | 4 | @xxx |
---
## 通用说明
### 认证方式
Authorization: Bearer
### 请求格式
Content-Type: application/json
### 响应格式
```json
{
"code": 0,
"message": "success",
"data": {}
}
| 状态码 | 说明 |
|---|---|
| 0 | 成功 |
| 1001 | 参数错误 |
| 2001 | 未授权 |
| 3001 | 资源不存在 |
| 5001 | 服务器错误 |
接口地址
GET /api/v1/users/{id}
请求参数
| 参数名 | 类型 | 位置 | 必填 | 说明 |
|---|---|---|---|---|
| id | long | path | 是 | 用户ID |
请求示例
GET /api/v1/users/123
响应示例
{
"code": 0,
"message": "success",
"data": {
"id": 123,
"name": "张三",
"email": "zhangsan@example.com",
"phone": "13800138000",
"created_at": "2024-01-01 10:00:00"
}
}
错误示例
{
"code": 3001,
"message": "用户不存在",
"data": null
}
接口地址
POST /api/v1/users
请求参数
| 参数名 | 类型 | 必填 | 说明 |
|---|---|---|---|
| name | string | 是 | 用户名 |
| string | 是 | 邮箱 | |
| phone | string | 否 | 手机号 |
| password | string | 是 | 密码 |
请求示例
{
"name": "张三",
"email": "zhangsan@example.com",
"phone": "13800138000",
"password": "123456"
}
响应示例
{
"code": 0,
"message": "success",
"data": {
"id": 123,
"name": "张三"
}
}
接口地址
GET /api/v1/orders
请求参数
| 参数名 | 类型 | 位置 | 必填 | 说明 |
|---|---|---|---|---|
| page | int | query | 否 | 页码,默认1 |
| page_size | int | query | 否 | 每页数量,默认20 |
| status | string | query | 否 | 订单状态 |
请求示例
GET /api/v1/orders?page=1&page_size=10&status=paid
响应示例
{
"code": 0,
"message": "success",
"data": {
"total": 100,
"page": 1,
"page_size": 10,
"list": [
{
"id": "ORD202401010001",
"user_id": 123,
"amount": 100.00,
"status": "paid",
"created_at": "2024-01-01 10:00:00"
}
]
}
}
| 版本 | 日期 | 变更内容 | 变更人 |
|---|---|---|---|
| V1.0 | YYYY-MM-DD | 初始版本 | @xxx |
| V1.1 | YYYY-MM-DD | 新增xxx接口 | @xxx |
## 接口设计原则
### RESTful规范
| 方法 | 用途 | 示例 |
|------|------|------|
| GET | 查询 | GET /users |
| POST | 创建 | POST /users |
| PUT | 完整更新 | PUT /users/1 |
| PATCH | 部分更新 | PATCH /users/1 |
| DELETE | 删除 | DELETE /users/1 |
### URL命名规范
```markdown
- 使用名词复数:/users
- 使用小写:/user-info
- 使用连字符分隔:/order-details
- 避免动词:不用 /getUser
| 类别 | 状态码 | 说明 |
|---|---|---|
| 1xx | 信息 | 接收的请求正在处理 |
| 2xx | 成功 | 请求正常处理完毕 |
| 3xx | 重定向 | 需要附加操作完成请求 |
| 4xx | 客户端错误 | 请求有语法错误 |
| 5xx | 服务器错误 | 服务器处理出错 |