[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F2FQJ726537HJZ2R8SD6KA":3,"skill-same:01M7F2FQJ726537HJZ2R8SD6KA":52},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":30,"commitSha":31,"skillDirectory":32,"forksCount":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":6,"ownerDescription":36,"updatedAt":37,"install":38,"resources":51},"01M7F2FQJ726537HJZ2R8SD6KA","openapi-spec-generator",null,"Generate complete, production-ready OpenAPI 3.x and Swagger 2.0 specifications from natural language descriptions, code, or partial specs.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fopenapi-spec-generator\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: openapi-spec-generator\ndescription: \"Generate complete, production-ready OpenAPI 3.x and Swagger 2.0 specifications from natural language descriptions, code, or partial specs.\"\nrisk: critical\nsource: https:\u002F\u002Fgithub.com\u002FLambdaTest\u002Fagent-skills\u002Ftree\u002Fmain\u002Fapi-skill\u002Fopenapi-spec-generator\nsource_repo: LambdaTest\u002Fagent-skills\nsource_type: community\ndate_added: 2026-07-01\nlicense: MIT\nlicense_source: https:\u002F\u002Fgithub.com\u002FLambdaTest\u002Fagent-skills\u002Fblob\u002Fmain\u002FLICENSE\n---\n\n# OpenAPI \u002F Swagger Specification Generator\n## When to Use\n\nUse this skill when you need generate complete, production-ready OpenAPI 3.x and Swagger 2.0 specifications from natural language descriptions, code, or partial specs. Use this skill whenever the user mentions OpenAPI, Swagger, API spec, REST API documentation, YAML\u002FJSON API schema, endpoint documentation, API...\n\n\nGenerate complete, valid OpenAPI 3.x or Swagger 2.0 specifications from descriptions, code, or partial specs.\n\n## Workflow\n\n### Step 1 — Gather Context\n\nBefore writing any YAML\u002FJSON, ask (or infer from context) the following:\n\n| Question | Why it matters |\n|---|---|\n| OpenAPI 3.x or Swagger 2.0? | Different `info`, `servers`\u002F`host`, `components`\u002F`definitions` structure |\n| Output format: YAML or JSON? | YAML default unless user specifies JSON |\n| What does this API do? | Sets `info.title`, `info.description`, tags |\n| List of endpoints (or code to extract from)? | Core paths object |\n| Authentication type(s)? | `securitySchemes` — see reference |\n| Common data models or entities? | `components\u002Fschemas` \u002F `definitions` |\n| Any existing partial spec to extend? | Merge rather than overwrite |\n\nIf the user provides code (Express routes, FastAPI, Django URLs, Spring controllers, etc.), **extract endpoints automatically** — do not ask what the user already told you.\n\n### Step 2 — Build the Spec\n\nFollow the structure guide for the chosen version. Always produce a **complete, valid spec** — never leave placeholder comments like `# TODO: add schema`.\n\n#### OpenAPI 3.x Skeleton\n\n```yaml\nopenapi: \"3.1.0\"\ninfo:\n  title: \u003CAPI Title>\n  version: \"1.0.0\"\n  description: \u003CShort description>\n  contact:\n    name: \u003CTeam or Author>\n    email: \u003Ccontact@example.com>\nservers:\n  - url: https:\u002F\u002Fapi.example.com\u002Fv1\n    description: Production\n  - url: https:\u002F\u002Fstaging-api.example.com\u002Fv1\n    description: Staging\ntags:\n  - name: \u003CTag>\n    description: \u003CTag description>\npaths:\n  \u002Fresource:\n    get:\n      summary: List resources\n      operationId: listResources\n      tags: [\u003CTag>]\n      parameters: []\n      responses:\n        \"200\":\n          description: Success\n          content:\n            application\u002Fjson:\n              schema:\n                $ref: \"#\u002Fcomponents\u002Fschemas\u002FResourceList\"\n              example:\n                items: []\n                total: 0\n        \"401\":\n          $ref: \"#\u002Fcomponents\u002Fresponses\u002FUnauthorized\"\n        \"500\":\n          $ref: \"#\u002Fcomponents\u002Fresponses\u002FInternalError\"\n      security:\n        - BearerAuth: []\ncomponents:\n  schemas: {}\n  responses:\n    Unauthorized:\n      description: Authentication required\n      content:\n        application\u002Fjson:\n          schema:\n            $ref: \"#\u002Fcomponents\u002Fschemas\u002FError\"\n    InternalError:\n      description: Internal server error\n      content:\n        application\u002Fjson:\n          schema:\n            $ref: \"#\u002Fcomponents\u002Fschemas\u002FError\"\n  securitySchemes: {}\n```\n\n#### Swagger 2.0 Skeleton\n\n```yaml\nswagger: \"2.0\"\ninfo:\n  title: \u003CAPI Title>\n  version: \"1.0.0\"\n  description: \u003CShort description>\nhost: api.example.com\nbasePath: \u002Fv1\nschemes: [https]\nconsumes: [application\u002Fjson]\nproduces: [application\u002Fjson]\ntags: []\npaths: {}\ndefinitions: {}\nsecurityDefinitions: {}\n```\n\n### Step 3 — Schemas and Models\n\n- **Always use `$ref`** for any schema used in more than one place.\n- Include `example` or `examples` on every schema and response body.\n- Mark required fields with the `required` array.\n- Use `nullable: true` (OAS 3.0) or `x-nullable: true` (Swagger 2.0) for optional nullable fields.\n- Prefer `format` keywords: `int32`, `int64`, `float`, `date`, `date-time`, `uuid`, `email`, `uri`, `byte`, `binary`.\n\n**Common schema patterns:**\n\n```yaml\n# Pagination wrapper\nPagedResult:\n  type: object\n  required: [items, total, page, pageSize]\n  properties:\n    items:\n      type: array\n      items:\n        $ref: \"#\u002Fcomponents\u002Fschemas\u002FResource\"\n    total:\n      type: integer\n      format: int64\n      example: 100\n    page:\n      type: integer\n      format: int32\n      example: 1\n    pageSize:\n      type: integer\n      format: int32\n      example: 20\n\n# Standard error\nError:\n  type: object\n  required: [code, message]\n  properties:\n    code:\n      type: string\n      example: RESOURCE_NOT_FOUND\n    message:\n      type: string\n      example: The requested resource was not found.\n    details:\n      type: object\n      additionalProperties: true\n\n# Timestamps mixin (use allOf)\nTimestamps:\n  type: object\n  properties:\n    createdAt:\n      type: string\n      format: date-time\n    updatedAt:\n      type: string\n      format: date-time\n```\n\n### Step 4 — Security Schemes\n\nRead `reference\u002Fsecurity-schemes.md` for detailed patterns. Quick reference:\n\n| Scheme | OAS 3.x type | Notes |\n|---|---|---|\n| Bearer JWT | `http`, scheme `bearer` | Most common for REST APIs |\n| API Key (header) | `apiKey`, in `header` | e.g. `X-API-Key` |\n| API Key (query) | `apiKey`, in `query` | Avoid — leaks in logs |\n| OAuth 2 | `oauth2` | Use `flows` to define grant types |\n| Basic Auth | `http`, scheme `basic` | Only over HTTPS |\n| OpenID Connect | `openIdConnect` | Provide `openIdConnectUrl` |\n\nApply security **globally** at the root and **override per-operation** only where it differs (e.g., public endpoints use `security: []`).\n\n### Step 5 — Parameters\n\n**Path parameters** — always `required: true`:\n```yaml\nparameters:\n  - name: userId\n    in: path\n    required: true\n    schema:\n      type: string\n      format: uuid\n    example: 123e4567-e89b-12d3-a456-426614174000\n```\n\n**Query parameters** — document defaults and enums:\n```yaml\n  - name: status\n    in: query\n    schema:\n      type: string\n      enum: [active, inactive, pending]\n      default: active\n```\n\n**Headers** — include `X-Request-ID`, correlation IDs, etc. as common parameters defined under `components\u002Fparameters`.\n\n### Step 6 — Response Codes\n\nAlways include at minimum:\n\n| Code | When |\n|---|---|\n| `200` | Successful GET, PUT, PATCH |\n| `201` | Successful POST that creates a resource |\n| `204` | Successful DELETE (no body) |\n| `400` | Validation \u002F bad request |\n| `401` | Missing or invalid auth |\n| `403` | Authenticated but not authorized |\n| `404` | Resource not found |\n| `409` | Conflict (duplicate, state mismatch) |\n| `422` | Unprocessable entity (semantic errors) |\n| `429` | Rate limited |\n| `500` | Internal server error |\n\nUse `$ref` to `components\u002Fresponses` for `401`, `403`, `404`, `429`, `500` to avoid repetition.\n\n### Step 7 — Quality Checklist\n\nBefore delivering the spec, verify:\n\n- [ ] `openapi` or `swagger` version field present\n- [ ] Every path has at least one operation\n- [ ] Every operation has `operationId` (camelCase, unique)\n- [ ] Every operation has at least one `200`\u002F`201`\u002F`204` response\n- [ ] `4xx` and `5xx` responses defined for all operations\n- [ ] All `$ref` targets exist in `components\u002F` or `definitions\u002F`\n- [ ] Required fields listed in `required` array for all request\u002Fresponse bodies\n- [ ] Security schemes defined AND applied\n- [ ] At least one `example` per schema or response body\n- [ ] Tags defined at root level to match operation tags\n- [ ] No orphaned schemas (everything in `components\u002Fschemas` is referenced)\n\n### Step 8 — Output\n\n1. Emit the complete YAML (or JSON) spec in a code block labeled `yaml` or `json`.\n2. After the spec, provide a brief **summary table** of endpoints generated.\n3. Offer to:\n   - Export as `.yaml` \u002F `.json` file\n   - Validate against Spectral or swagger-parser\n   - Generate mock server config (Prism)\n   - Generate client SDK stubs (language of choice)\n\n---\n\n## Extracting from Code\n\nWhen the user provides source code, extract:\n\n**Express \u002F Koa \u002F Fastify (Node.js)**\n- Look for `.get()`, `.post()`, `.put()`, `.patch()`, `.delete()` calls\n- Route params `:param` → path parameter `{param}`\n- Middleware like `authenticate` → note security requirement\n- `req.body`, `req.query`, `req.params` usage → infer request schema\n\n**FastAPI \u002F Flask (Python)**\n- Decorators: `@app.get()`, `@router.post()`, etc.\n- Pydantic models → translate directly to JSON Schema\n- `Query()`, `Path()`, `Body()` → map to parameter location\n\n**Spring Boot (Java)**\n- `@GetMapping`, `@PostMapping`, etc.\n- `@PathVariable`, `@RequestParam`, `@RequestBody`\n- DTO classes → schemas\n\n**Django REST Framework**\n- `ViewSet` and `Router` → CRUD endpoints\n- `Serializer` fields → schema properties\n\n**Rails**\n- `routes.rb` resource routes → standard REST endpoints\n- Strong params → request body schema\n\n---\n\n## Reference Files\n\n- `reference\u002Fsecurity-schemes.md` — Detailed security scheme examples for all auth types\n- `reference\u002Fcommon-patterns.md` — Pagination, HATEOAS, problem+json, webhooks, file upload patterns\n\nRead these when the user asks about a specific pattern or when generating complex auth\u002Fpagination setups.\n\n\n---\n\n## After Completing the OpenAPI\u002FSwagger Specification design\n\nOnce the OpenAPI\u002FSwagger Specification output is delivered, ask the user:\n\n\"Would you like me to generate API test cases for this design? (yes\u002Fno)\"\n\nIf the user says **yes**:\n- Check if the API Test Case Generator skill is available in the installed skills list\n- If the skill **is available**:\n  - Read and follow the instructions in the API Test Case Generator skill\n  - Use the specification output above as the input\n- If the skill **is NOT available**:\n  - Inform the user: \"It looks like the API Documentation skill isn't installed.\n    You can install it and re-run.\n\nIf the user says **no**:\n- End the task here\n\n---\n\n## Limitations\n\n- Use this skill only when the task clearly matches its upstream source and local project context.\n- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.\n- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.\n","# OpenAPI \u002F Swagger Specification Generator\n## When to Use\n\nUse this skill when you need generate complete, production-ready OpenAPI 3.x and Swagger 2.0 specifications from natural language descriptions, code, or partial specs. Use this skill whenever the user mentions OpenAPI, Swagger, API spec, REST API documentation, YAML\u002FJSON API schema, endpoint documentation, API...\n\n\nGenerate complete, valid OpenAPI 3.x or Swagger 2.0 specifications from descriptions, code, or partial specs.\n\n## Workflow\n\n### Step 1 — Gather Context\n\nBefore writing any YAML\u002FJSON, ask (or infer from context) the following:\n\n| Question | Why it matters |\n|---|---|\n| OpenAPI 3.x or Swagger 2.0? | Different `info`, `servers`\u002F`host`, `components`\u002F`definitions` structure |\n| Output format: YAML or JSON? | YAML default unless user specifies JSON |\n| What does this API do? | Sets `info.title`, `info.description`, tags |\n| List of endpoints (or code to extract from)? | Core paths object |\n| Authentication type(s)? | `securitySchemes` — see reference |\n| Common data models or entities? | `components\u002Fschemas` \u002F `definitions` |\n| Any existing partial spec to extend? | Merge rather than overwrite |\n\nIf the user provides code (Express routes, FastAPI, Django URLs, Spring controllers, etc.), **extract endpoints automatically** — do not ask what the user already told you.\n\n### Step 2 — Build the Spec\n\nFollow the structure guide for the chosen version. Always produce a **complete, valid spec** — never leave placeholder comments like `# TODO: add schema`.\n\n#### OpenAPI 3.x Skeleton\n\n```yaml\nopenapi: \"3.1.0\"\ninfo:\n  title: \u003CAPI Title>\n  version: \"1.0.0\"\n  description: \u003CShort description>\n  contact:\n    name: \u003CTeam or Author>\n    email: \u003Ccontact@example.com>\nservers:\n  - url: https:\u002F\u002Fapi.example.com\u002Fv1\n    description: Production\n  - url: https:\u002F\u002Fstaging-api.example.com\u002Fv1\n    description: Staging\ntags:\n  - name: \u003CTag>\n    description: \u003CTag description>\npaths:\n  \u002Fresource:\n    get:\n      summary: List resources\n      operationId: listResources\n      tags: [\u003CTag>]\n      parameters: []\n      responses:\n        \"200\":\n          description: Success\n          content:\n            application\u002Fjson:\n              schema:\n                $ref: \"#\u002Fcomponents\u002Fschemas\u002FResourceList\"\n              example:\n                items: []\n                total: 0\n        \"401\":\n          $ref: \"#\u002Fcomponents\u002Fresponses\u002FUnauthorized\"\n        \"500\":\n          $ref: \"#\u002Fcomponents\u002Fresponses\u002FInternalError\"\n      security:\n        - BearerAuth: []\ncomponents:\n  schemas: {}\n  responses:\n    Unauthorized:\n      description: Authentication required\n      content:\n        application\u002Fjson:\n          schema:\n            $ref: \"#\u002Fcomponents\u002Fschemas\u002FError\"\n    InternalError:\n      description: Internal server error\n      content:\n        application\u002Fjson:\n          schema:\n            $ref: \"#\u002Fcomponents\u002Fschemas\u002FError\"\n  securitySchemes: {}\n```\n\n#### Swagger 2.0 Skeleton\n\n```yaml\nswagger: \"2.0\"\ninfo:\n  title: \u003CAPI Title>\n  version: \"1.0.0\"\n  description: \u003CShort description>\nhost: api.example.com\nbasePath: \u002Fv1\nschemes: [https]\nconsumes: [application\u002Fjson]\nproduces: [application\u002Fjson]\ntags: []\npaths: {}\ndefinitions: {}\nsecurityDefinitions: {}\n```\n\n### Step 3 — Schemas and Models\n\n- **Always use `$ref`** for any schema used in more than one place.\n- Include `example` or `examples` on every schema and response body.\n- Mark required fields with the `required` array.\n- Use `nullable: true` (OAS 3.0) or `x-nullable: true` (Swagger 2.0) for optional nullable fields.\n- Prefer `format` keywords: `int32`, `int64`, `float`, `date`, `date-time`, `uuid`, `email`, `uri`, `byte`, `binary`.\n\n**Common schema patterns:**\n\n```yaml\n# Pagination wrapper\nPagedResult:\n  type: object\n  required: [items, total, page, pageSize]\n  properties:\n    items:\n      type: array\n      items:\n        $ref: \"#\u002Fcomponents\u002Fschemas\u002FResource\"\n    total:\n      type: integer\n      format: int64\n      example: 100\n    page:\n      type: integer\n      format: int32\n      example: 1\n    pageSize:\n      type: integer\n      format: int32\n      example: 20\n\n# Standard error\nError:\n  type: object\n  required: [code, message]\n  properties:\n    code:\n      type: string\n      example: RESOURCE_NOT_FOUND\n    message:\n      type: string\n      example: The requested resource was not found.\n    details:\n      type: object\n      additionalProperties: true\n\n# Timestamps mixin (use allOf)\nTimestamps:\n  type: object\n  properties:\n    createdAt:\n      type: string\n      format: date-time\n    updatedAt:\n      type: string\n      format: date-time\n```\n\n### Step 4 — Security Schemes\n\nRead `reference\u002Fsecurity-schemes.md` for detailed patterns. Quick reference:\n\n| Scheme | OAS 3.x type | Notes |\n|---|---|---|\n| Bearer JWT | `http`, scheme `bearer` | Most common for REST APIs |\n| API Key (header) | `apiKey`, in `header` | e.g. `X-API-Key` |\n| API Key (query) | `apiKey`, in `query` | Avoid — leaks in logs |\n| OAuth 2 | `oauth2` | Use `flows` to define grant types |\n| Basic Auth | `http`, scheme `basic` | Only over HTTPS |\n| OpenID Connect | `openIdConnect` | Provide `openIdConnectUrl` |\n\nApply security **globally** at the root and **override per-operation** only where it differs (e.g., public endpoints use `security: []`).\n\n### Step 5 — Parameters\n\n**Path parameters** — always `required: true`:\n```yaml\nparameters:\n  - name: userId\n    in: path\n    required: true\n    schema:\n      type: string\n      format: uuid\n    example: 123e4567-e89b-12d3-a456-426614174000\n```\n\n**Query parameters** — document defaults and enums:\n```yaml\n  - name: status\n    in: query\n    schema:\n      type: string\n      enum: [active, inactive, pending]\n      default: active\n```\n\n**Headers** — include `X-Request-ID`, correlation IDs, etc. as common parameters defined under `components\u002Fparameters`.\n\n### Step 6 — Response Codes\n\nAlways include at minimum:\n\n| Code | When |\n|---|---|\n| `200` | Successful GET, PUT, PATCH |\n| `201` | Successful POST that creates a resource |\n| `204` | Successful DELETE (no body) |\n| `400` | Validation \u002F bad request |\n| `401` | Missing or invalid auth |\n| `403` | Authenticated but not authorized |\n| `404` | Resource not found |\n| `409` | Conflict (duplicate, state mismatch) |\n| `422` | Unprocessable entity (semantic errors) |\n| `429` | Rate limited |\n| `500` | Internal server error |\n\nUse `$ref` to `components\u002Fresponses` for `401`, `403`, `404`, `429`, `500` to avoid repetition.\n\n### Step 7 — Quality Checklist\n\nBefore delivering the spec, verify:\n\n- [ ] `openapi` or `swagger` version field present\n- [ ] Every path has at least one operation\n- [ ] Every operation has `operationId` (camelCase, unique)\n- [ ] Every operation has at least one `200`\u002F`201`\u002F`204` response\n- [ ] `4xx` and `5xx` responses defined for all operations\n- [ ] All `$ref` targets exist in `components\u002F` or `definitions\u002F`\n- [ ] Required fields listed in `required` array for all request\u002Fresponse bodies\n- [ ] Security schemes defined AND applied\n- [ ] At least one `example` per schema or response body\n- [ ] Tags defined at root level to match operation tags\n- [ ] No orphaned schemas (everything in `components\u002Fschemas` is referenced)\n\n### Step 8 — Output\n\n1. Emit the complete YAML (or JSON) spec in a code block labeled `yaml` or `json`.\n2. After the spec, provide a brief **summary table** of endpoints generated.\n3. Offer to:\n   - Export as `.yaml` \u002F `.json` file\n   - Validate against Spectral or swagger-parser\n   - Generate mock server config (Prism)\n   - Generate client SDK stubs (language of choice)\n\n---\n\n## Extracting from Code\n\nWhen the user provides source code, extract:\n\n**Express \u002F Koa \u002F Fastify (Node.js)**\n- Look for `.get()`, `.post()`, `.put()`, `.patch()`, `.delete()` calls\n- Route params `:param` → path parameter `{param}`\n- Middleware like `authenticate` → note security requirement\n- `req.body`, `req.query`, `req.params` usage → infer request schema\n\n**FastAPI \u002F Flask (Python)**\n- Decorators: `@app.get()`, `@router.post()`, etc.\n- Pydantic models → translate directly to JSON Schema\n- `Query()`, `Path()`, `Body()` → map to parameter location\n\n**Spring Boot (Java)**\n- `@GetMapping`, `@PostMapping`, etc.\n- `@PathVariable`, `@RequestParam`, `@RequestBody`\n- DTO classes → schemas\n\n**Django REST Framework**\n- `ViewSet` and `Router` → CRUD endpoints\n- `Serializer` fields → schema properties\n\n**Rails**\n- `routes.rb` resource routes → standard REST endpoints\n- Strong params → request body schema\n\n---\n\n## Reference Files\n\n- `reference\u002Fsecurity-schemes.md` — Detailed security scheme examples for all auth types\n- `reference\u002Fcommon-patterns.md` — Pagination, HATEOAS, problem+json, webhooks, file upload patterns\n\nRead these when the user asks about a specific pattern or when generating complex auth\u002Fpagination setups.\n\n\n---\n\n## After Completing the OpenAPI\u002FSwagger Specification design\n\nOnce the OpenAPI\u002FSwagger Specification output is delivered, ask the user:\n\n\"Would you like me to generate API test cases for this design? (yes\u002Fno)\"\n\nIf the user says **yes**:\n- Check if the API Test Case Generator skill is available in the installed skills list\n- If the skill **is available**:\n  - Read and follow the instructions in the API Test Case Generator skill\n  - Use the specification output above as the input\n- If the skill **is NOT available**:\n  - Inform the user: \"It looks like the API Documentation skill isn't installed.\n    You can install it and re-run.\n\nIf the user says **no**:\n- End the task here\n\n---\n\n## Limitations\n\n- Use this skill only when the task clearly matches its upstream source and local project context.\n- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.\n- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.\n",{"name":5,"risk":24,"source":25,"license":15,"date_added":26,"description":7,"source_repo":27,"source_type":28,"license_source":29},"critical","https:\u002F\u002Fgithub.com\u002FLambdaTest\u002Fagent-skills\u002Ftree\u002Fmain\u002Fapi-skill\u002Fopenapi-spec-generator",1782864000000,"LambdaTest\u002Fagent-skills","community","https:\u002F\u002Fgithub.com\u002FLambdaTest\u002Fagent-skills\u002Fblob\u002Fmain\u002FLICENSE","main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","05-技能与代理开发\u002Fopenapi-spec-generator",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":39,"prompt":49,"zipAvailable":50},[40,43,46],{"tool":41,"command":42},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill openapi-spec-generator",{"tool":44,"command":45},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill openapi-spec-generator",{"tool":47,"command":48},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill openapi-spec-generator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fopenapi-spec-generator\u002FSKILL.md",true,[],[53,60,65,72,79,86],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],{"skillNo":61,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]