[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79SJKPZ06BVASXK1PPPRS99":3,"skill-same:01M79SJKPZ06BVASXK1PPPRS99":52},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":32,"commitSha":33,"skillDirectory":34,"forksCount":13,"repositoryHtmlUrl":35,"repositoryHomepageUrl":6,"ownerHtmlUrl":36,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":37,"install":38,"resources":51},"01M79SJKPZ06BVASXK1PPPRS99","api-designer",null,"Use when designing REST or GraphQL APIs, creating OpenAPI specifications, or planning API architecture. Invoke for resource modeling, versioning strategies, pagination patterns, error handling standards.","Snuc1925\u002FSWE-AI-Agent","Snuc1925","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F87866086?v=4","01M79SEFKVJ24BEZS59RCHPNSX","01M79SEFMJFYTNK7S8WF299CWN",0,"MIT","https:\u002F\u002Fgithub.com\u002FSnuc1925\u002FSWE-AI-Agent\u002Fblob\u002Fmain\u002Fskill-library\u002Fapi-backend\u002Fapi-designer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: api-designer\ndescription: Use when designing REST or GraphQL APIs, creating OpenAPI specifications, or planning API architecture. Invoke for resource modeling, versioning strategies, pagination patterns, error handling standards.\nlicense: MIT\nmetadata:\n  author: https:\u002F\u002Fgithub.com\u002FJeffallan\n  version: \"1.1.0\"\n  domain: api-architecture\n  triggers: API design, REST API, OpenAPI, API specification, API architecture, resource modeling, API versioning, GraphQL schema, API documentation\n  role: architect\n  scope: design\n  output-format: specification\n  related-skills: graphql-architect, fastapi-expert, nestjs-expert, spring-boot-engineer, security-reviewer\n---\n\n# API Designer\n\nSenior API architect specializing in REST and GraphQL APIs with comprehensive OpenAPI 3.1 specifications.\n\n## Core Workflow\n\n1. **Analyze domain** — Understand business requirements, data models, and client needs\n2. **Model resources** — Identify resources, relationships, and operations; sketch entity diagram before writing any spec\n3. **Design endpoints** — Define URI patterns, HTTP methods, request\u002Fresponse schemas\n4. **Specify contract** — Create OpenAPI 3.1 spec; validate before proceeding: `npx @redocly\u002Fcli lint openapi.yaml`\n5. **Mock and verify** — Spin up a mock server to test contracts: `npx @stoplight\u002Fprism-cli mock openapi.yaml`\n6. **Plan evolution** — Design versioning, deprecation, and backward-compatibility strategy\n\n## Reference Guide\n\nLoad detailed guidance based on context:\n\n| Topic | Reference | Load When |\n|-------|-----------|-----------|\n| REST Patterns | `references\u002Frest-patterns.md` | Resource design, HTTP methods, HATEOAS |\n| Versioning | `references\u002Fversioning.md` | API versions, deprecation, breaking changes |\n| Pagination | `references\u002Fpagination.md` | Cursor, offset, keyset pagination |\n| Error Handling | `references\u002Ferror-handling.md` | Error responses, RFC 7807, status codes |\n| OpenAPI | `references\u002Fopenapi.md` | OpenAPI 3.1, documentation, code generation |\n\n## Constraints\n\n### MUST DO\n- Follow REST principles (resource-oriented, proper HTTP methods)\n- Use consistent naming conventions (snake_case or camelCase — pick one, apply everywhere)\n- Include comprehensive OpenAPI 3.1 specification\n- Design proper error responses with actionable messages (RFC 7807)\n- Implement pagination for all collection endpoints\n- Version APIs with clear deprecation policies\n- Document authentication and authorization\n- Provide request\u002Fresponse examples\n\n### MUST NOT DO\n- Use verbs in resource URIs (use `\u002Fusers\u002F{id}`, not `\u002FgetUser\u002F{id}`)\n- Return inconsistent response structures\n- Skip error code documentation\n- Ignore HTTP status code semantics\n- Design APIs without a versioning strategy\n- Expose implementation details in the API surface\n- Create breaking changes without a migration path\n- Omit rate limiting considerations\n\n## Templates\n\n### OpenAPI 3.1 Resource Endpoint (copy-paste starter)\n\n```yaml\nopenapi: \"3.1.0\"\ninfo:\n  title: Example API\n  version: \"1.1.0\"\npaths:\n  \u002Fusers:\n    get:\n      summary: List users\n      operationId: listUsers\n      tags: [Users]\n      parameters:\n        - name: cursor\n          in: query\n          schema: { type: string }\n          description: Opaque cursor for pagination\n        - name: limit\n          in: query\n          schema: { type: integer, default: 20, maximum: 100 }\n      responses:\n        \"200\":\n          description: Paginated list of users\n          content:\n            application\u002Fjson:\n              schema:\n                type: object\n                required: [data, pagination]\n                properties:\n                  data:\n                    type: array\n                    items: { $ref: \"#\u002Fcomponents\u002Fschemas\u002FUser\" }\n                  pagination:\n                    $ref: \"#\u002Fcomponents\u002Fschemas\u002FCursorPage\"\n        \"400\": { $ref: \"#\u002Fcomponents\u002Fresponses\u002FBadRequest\" }\n        \"401\": { $ref: \"#\u002Fcomponents\u002Fresponses\u002FUnauthorized\" }\n        \"429\": { $ref: \"#\u002Fcomponents\u002Fresponses\u002FTooManyRequests\" }\n  \u002Fusers\u002F{id}:\n    get:\n      summary: Get a user\n      operationId: getUser\n      tags: [Users]\n      parameters:\n        - name: id\n          in: path\n          required: true\n          schema: { type: string, format: uuid }\n      responses:\n        \"200\":\n          description: User found\n          content:\n            application\u002Fjson:\n              schema: { $ref: \"#\u002Fcomponents\u002Fschemas\u002FUser\" }\n        \"404\": { $ref: \"#\u002Fcomponents\u002Fresponses\u002FNotFound\" }\n\ncomponents:\n  schemas:\n    User:\n      type: object\n      required: [id, email, created_at]\n      properties:\n        id:    { type: string, format: uuid, readOnly: true }\n        email: { type: string, format: email }\n        name:  { type: string }\n        created_at: { type: string, format: date-time, readOnly: true }\n\n    CursorPage:\n      type: object\n      required: [next_cursor, has_more]\n      properties:\n        next_cursor: { type: string, nullable: true }\n        has_more:    { type: boolean }\n\n    Problem:                       # RFC 7807 Problem Details\n      type: object\n      required: [type, title, status]\n      properties:\n        type:     { type: string, format: uri, example: \"https:\u002F\u002Fapi.example.com\u002Ferrors\u002Fvalidation-error\" }\n        title:    { type: string, example: \"Validation Error\" }\n        status:   { type: integer, example: 400 }\n        detail:   { type: string, example: \"The 'email' field must be a valid email address.\" }\n        instance: { type: string, format: uri, example: \"\u002Fusers\u002Freq-abc123\" }\n\n  responses:\n    BadRequest:\n      description: Invalid request parameters\n      content:\n        application\u002Fproblem+json:\n          schema: { $ref: \"#\u002Fcomponents\u002Fschemas\u002FProblem\" }\n    Unauthorized:\n      description: Missing or invalid authentication\n      content:\n        application\u002Fproblem+json:\n          schema: { $ref: \"#\u002Fcomponents\u002Fschemas\u002FProblem\" }\n    NotFound:\n      description: Resource not found\n      content:\n        application\u002Fproblem+json:\n          schema: { $ref: \"#\u002Fcomponents\u002Fschemas\u002FProblem\" }\n    TooManyRequests:\n      description: Rate limit exceeded\n      headers:\n        Retry-After: { schema: { type: integer } }\n      content:\n        application\u002Fproblem+json:\n          schema: { $ref: \"#\u002Fcomponents\u002Fschemas\u002FProblem\" }\n\n  securitySchemes:\n    BearerAuth:\n      type: http\n      scheme: bearer\n      bearerFormat: JWT\n\nsecurity:\n  - BearerAuth: []\n```\n\n### RFC 7807 Error Response (copy-paste)\n\n```json\n{\n  \"type\": \"https:\u002F\u002Fapi.example.com\u002Ferrors\u002Fvalidation-error\",\n  \"title\": \"Validation Error\",\n  \"status\": 422,\n  \"detail\": \"The 'email' field must be a valid email address.\",\n  \"instance\": \"\u002Fusers\u002Freq-abc123\",\n  \"errors\": [\n    { \"field\": \"email\", \"message\": \"Must be a valid email address.\" }\n  ]\n}\n```\n\n- Always use `Content-Type: application\u002Fproblem+json` for error responses.\n- `type` must be a stable, documented URI — never a generic string.\n- `detail` must be human-readable and actionable.\n- Extend with `errors[]` for field-level validation failures.\n\n## Output Checklist\n\nWhen delivering an API design, provide:\n1. Resource model and relationships (diagram or table)\n2. Endpoint specifications with URIs and HTTP methods\n3. OpenAPI 3.1 specification (YAML)\n4. Authentication and authorization flows\n5. Error response catalog (all 4xx\u002F5xx with `type` URIs)\n6. Pagination and filtering patterns\n7. Versioning and deprecation strategy\n8. Validation result: `npx @redocly\u002Fcli lint openapi.yaml` passes with no errors\n\n## Knowledge Reference\n\nREST architecture, OpenAPI 3.1, GraphQL, HTTP semantics, JSON:API, HATEOAS, OAuth 2.0, JWT, RFC 7807 Problem Details, API versioning patterns, pagination strategies, rate limiting, webhook design, SDK generation\n\n[Documentation](https:\u002F\u002Fjeffallan.github.io\u002Fclaude-skills\u002Fskills\u002Fapi-architecture\u002Fapi-designer\u002F)\n","# API Designer\n\nSenior API architect specializing in REST and GraphQL APIs with comprehensive OpenAPI 3.1 specifications.\n\n## Core Workflow\n\n1. **Analyze domain** — Understand business requirements, data models, and client needs\n2. **Model resources** — Identify resources, relationships, and operations; sketch entity diagram before writing any spec\n3. **Design endpoints** — Define URI patterns, HTTP methods, request\u002Fresponse schemas\n4. **Specify contract** — Create OpenAPI 3.1 spec; validate before proceeding: `npx @redocly\u002Fcli lint openapi.yaml`\n5. **Mock and verify** — Spin up a mock server to test contracts: `npx @stoplight\u002Fprism-cli mock openapi.yaml`\n6. **Plan evolution** — Design versioning, deprecation, and backward-compatibility strategy\n\n## Reference Guide\n\nLoad detailed guidance based on context:\n\n| Topic | Reference | Load When |\n|-------|-----------|-----------|\n| REST Patterns | `references\u002Frest-patterns.md` | Resource design, HTTP methods, HATEOAS |\n| Versioning | `references\u002Fversioning.md` | API versions, deprecation, breaking changes |\n| Pagination | `references\u002Fpagination.md` | Cursor, offset, keyset pagination |\n| Error Handling | `references\u002Ferror-handling.md` | Error responses, RFC 7807, status codes |\n| OpenAPI | `references\u002Fopenapi.md` | OpenAPI 3.1, documentation, code generation |\n\n## Constraints\n\n### MUST DO\n- Follow REST principles (resource-oriented, proper HTTP methods)\n- Use consistent naming conventions (snake_case or camelCase — pick one, apply everywhere)\n- Include comprehensive OpenAPI 3.1 specification\n- Design proper error responses with actionable messages (RFC 7807)\n- Implement pagination for all collection endpoints\n- Version APIs with clear deprecation policies\n- Document authentication and authorization\n- Provide request\u002Fresponse examples\n\n### MUST NOT DO\n- Use verbs in resource URIs (use `\u002Fusers\u002F{id}`, not `\u002FgetUser\u002F{id}`)\n- Return inconsistent response structures\n- Skip error code documentation\n- Ignore HTTP status code semantics\n- Design APIs without a versioning strategy\n- Expose implementation details in the API surface\n- Create breaking changes without a migration path\n- Omit rate limiting considerations\n\n## Templates\n\n### OpenAPI 3.1 Resource Endpoint (copy-paste starter)\n\n```yaml\nopenapi: \"3.1.0\"\ninfo:\n  title: Example API\n  version: \"1.1.0\"\npaths:\n  \u002Fusers:\n    get:\n      summary: List users\n      operationId: listUsers\n      tags: [Users]\n      parameters:\n        - name: cursor\n          in: query\n          schema: { type: string }\n          description: Opaque cursor for pagination\n        - name: limit\n          in: query\n          schema: { type: integer, default: 20, maximum: 100 }\n      responses:\n        \"200\":\n          description: Paginated list of users\n          content:\n            application\u002Fjson:\n              schema:\n                type: object\n                required: [data, pagination]\n                properties:\n                  data:\n                    type: array\n                    items: { $ref: \"#\u002Fcomponents\u002Fschemas\u002FUser\" }\n                  pagination:\n                    $ref: \"#\u002Fcomponents\u002Fschemas\u002FCursorPage\"\n        \"400\": { $ref: \"#\u002Fcomponents\u002Fresponses\u002FBadRequest\" }\n        \"401\": { $ref: \"#\u002Fcomponents\u002Fresponses\u002FUnauthorized\" }\n        \"429\": { $ref: \"#\u002Fcomponents\u002Fresponses\u002FTooManyRequests\" }\n  \u002Fusers\u002F{id}:\n    get:\n      summary: Get a user\n      operationId: getUser\n      tags: [Users]\n      parameters:\n        - name: id\n          in: path\n          required: true\n          schema: { type: string, format: uuid }\n      responses:\n        \"200\":\n          description: User found\n          content:\n            application\u002Fjson:\n              schema: { $ref: \"#\u002Fcomponents\u002Fschemas\u002FUser\" }\n        \"404\": { $ref: \"#\u002Fcomponents\u002Fresponses\u002FNotFound\" }\n\ncomponents:\n  schemas:\n    User:\n      type: object\n      required: [id, email, created_at]\n      properties:\n        id:    { type: string, format: uuid, readOnly: true }\n        email: { type: string, format: email }\n        name:  { type: string }\n        created_at: { type: string, format: date-time, readOnly: true }\n\n    CursorPage:\n      type: object\n      required: [next_cursor, has_more]\n      properties:\n        next_cursor: { type: string, nullable: true }\n        has_more:    { type: boolean }\n\n    Problem:                       # RFC 7807 Problem Details\n      type: object\n      required: [type, title, status]\n      properties:\n        type:     { type: string, format: uri, example: \"https:\u002F\u002Fapi.example.com\u002Ferrors\u002Fvalidation-error\" }\n        title:    { type: string, example: \"Validation Error\" }\n        status:   { type: integer, example: 400 }\n        detail:   { type: string, example: \"The 'email' field must be a valid email address.\" }\n        instance: { type: string, format: uri, example: \"\u002Fusers\u002Freq-abc123\" }\n\n  responses:\n    BadRequest:\n      description: Invalid request parameters\n      content:\n        application\u002Fproblem+json:\n          schema: { $ref: \"#\u002Fcomponents\u002Fschemas\u002FProblem\" }\n    Unauthorized:\n      description: Missing or invalid authentication\n      content:\n        application\u002Fproblem+json:\n          schema: { $ref: \"#\u002Fcomponents\u002Fschemas\u002FProblem\" }\n    NotFound:\n      description: Resource not found\n      content:\n        application\u002Fproblem+json:\n          schema: { $ref: \"#\u002Fcomponents\u002Fschemas\u002FProblem\" }\n    TooManyRequests:\n      description: Rate limit exceeded\n      headers:\n        Retry-After: { schema: { type: integer } }\n      content:\n        application\u002Fproblem+json:\n          schema: { $ref: \"#\u002Fcomponents\u002Fschemas\u002FProblem\" }\n\n  securitySchemes:\n    BearerAuth:\n      type: http\n      scheme: bearer\n      bearerFormat: JWT\n\nsecurity:\n  - BearerAuth: []\n```\n\n### RFC 7807 Error Response (copy-paste)\n\n```json\n{\n  \"type\": \"https:\u002F\u002Fapi.example.com\u002Ferrors\u002Fvalidation-error\",\n  \"title\": \"Validation Error\",\n  \"status\": 422,\n  \"detail\": \"The 'email' field must be a valid email address.\",\n  \"instance\": \"\u002Fusers\u002Freq-abc123\",\n  \"errors\": [\n    { \"field\": \"email\", \"message\": \"Must be a valid email address.\" }\n  ]\n}\n```\n\n- Always use `Content-Type: application\u002Fproblem+json` for error responses.\n- `type` must be a stable, documented URI — never a generic string.\n- `detail` must be human-readable and actionable.\n- Extend with `errors[]` for field-level validation failures.\n\n## Output Checklist\n\nWhen delivering an API design, provide:\n1. Resource model and relationships (diagram or table)\n2. Endpoint specifications with URIs and HTTP methods\n3. OpenAPI 3.1 specification (YAML)\n4. Authentication and authorization flows\n5. Error response catalog (all 4xx\u002F5xx with `type` URIs)\n6. Pagination and filtering patterns\n7. Versioning and deprecation strategy\n8. Validation result: `npx @redocly\u002Fcli lint openapi.yaml` passes with no errors\n\n## Knowledge Reference\n\nREST architecture, OpenAPI 3.1, GraphQL, HTTP semantics, JSON:API, HATEOAS, OAuth 2.0, JWT, RFC 7807 Problem Details, API versioning patterns, pagination strategies, rate limiting, webhook design, SDK generation\n\n[Documentation](https:\u002F\u002Fjeffallan.github.io\u002Fclaude-skills\u002Fskills\u002Fapi-architecture\u002Fapi-designer\u002F)\n",{"name":5,"license":14,"metadata":23,"description":7},{"role":24,"scope":25,"author":26,"domain":27,"version":28,"triggers":29,"output-format":30,"related-skills":31},"architect","design","https:\u002F\u002Fgithub.com\u002FJeffallan","api-architecture","1.1.0","API design, REST API, OpenAPI, API specification, API architecture, resource modeling, API versioning, GraphQL schema, API documentation","specification","graphql-architect, fastapi-expert, nestjs-expert, spring-boot-engineer, security-reviewer","main","459326d435e3b6ae17300b946bd4b7458ecd2bae","skill-library\u002Fapi-backend\u002Fapi-designer","https:\u002F\u002Fgithub.com\u002FSnuc1925\u002FSWE-AI-Agent","https:\u002F\u002Fgithub.com\u002FSnuc1925","2026-07-29 09:46:52",{"source":8,"skillName":5,"commands":39,"prompt":49,"zipAvailable":50},[40,43,46],{"tool":41,"command":42},"npx","npx skills add Snuc1925\u002FSWE-AI-Agent --skill api-designer",{"tool":44,"command":45},"bunx","bunx skills add Snuc1925\u002FSWE-AI-Agent --skill api-designer",{"tool":47,"command":48},"pnpm","pnpm dlx skills add Snuc1925\u002FSWE-AI-Agent --skill api-designer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSnuc1925\u002FSWE-AI-Agent\u002Fblob\u002Fmain\u002Fskill-library\u002Fapi-backend\u002Fapi-designer\u002FSKILL.md",true,[],[53,62,70,78,85,93],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":57,"licenseFileUrl":58,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":18},"01M79T5E59T5HMWZVTFJA9QXN1","linear","Manage issues, projects & team workflows in Linear. Use when the user wants to read, create or updates tickets in Linear.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FSnuc1925\u002FSWE-AI-Agent\u002Fblob\u002Fmain\u002Fskill-library\u002Fworkflow-planning\u002Flinear\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FSnuc1925\u002FSWE-AI-Agent\u002Fblob\u002Fmain\u002Fskill-library\u002Fworkflow-planning\u002Flinear\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":57,"licenseFileUrl":66,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":18},"01M79T535TSDZ09RXZ2YPEE3TN","define-goal","Help the user define a concrete, measurable goal before starting work, especially when they ask to use the goal tool, create a goal, set an objective, clarify success criteria, or turn a fuzzy intention into a quantitative outcome. Use this skill for goal creation and goal refinement only; it does not manage durable snapshots, decision logs, or long-running execution artifacts.","https:\u002F\u002Fgithub.com\u002FSnuc1925\u002FSWE-AI-Agent\u002Fblob\u002Fmain\u002Fskill-library\u002Fworkflow-planning\u002Fdefine-goal\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FSnuc1925\u002FSWE-AI-Agent\u002Fblob\u002Fmain\u002Fskill-library\u002Fworkflow-planning\u002Fdefine-goal\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":57,"licenseFileUrl":74,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":18},"01M79T4TE9NAVN5REZVETVXBCN","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002FSnuc1925\u002FSWE-AI-Agent\u002Fblob\u002Fmain\u002Fskill-library\u002Ftesting\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FSnuc1925\u002FSWE-AI-Agent\u002Fblob\u002Fmain\u002Fskill-library\u002Ftesting\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":18},"01M79T4HSEDWY2NXVRDZ3RX7J4","test-master","Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation frameworks; analyzing coverage gaps; performance testing with k6 or Artillery; security testing with OWASP methods; debugging flaky tests; or working on QA, regression, test automation, quality gates, shift-left testing, or test maintenance.","https:\u002F\u002Fgithub.com\u002FSnuc1925\u002FSWE-AI-Agent\u002Fblob\u002Fmain\u002Fskill-library\u002Ftesting\u002Ftest-master\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":57,"licenseFileUrl":89,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":18},"01M79T43SW5P3Y37F6Y82T76EM","playwright","Use when the task requires automating a real browser from the terminal (navigation, form filling, snapshots, screenshots, data extraction, UI-flow debugging) via `playwright-cli` or the bundled wrapper script.","https:\u002F\u002Fgithub.com\u002FSnuc1925\u002FSWE-AI-Agent\u002Fblob\u002Fmain\u002Fskill-library\u002Ftesting\u002Fplaywright\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FSnuc1925\u002FSWE-AI-Agent\u002Fblob\u002Fmain\u002Fskill-library\u002Ftesting\u002Fplaywright\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":57,"licenseFileUrl":97,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":18},"01M79T3ZYPH547MMC5FFBY1APS","playwright-interactive","Persistent browser and Electron interaction through `js_repl` for fast iterative UI debugging.","https:\u002F\u002Fgithub.com\u002FSnuc1925\u002FSWE-AI-Agent\u002Fblob\u002Fmain\u002Fskill-library\u002Ftesting\u002Fplaywright-interactive\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FSnuc1925\u002FSWE-AI-Agent\u002Fblob\u002Fmain\u002Fskill-library\u002Ftesting\u002Fplaywright-interactive\u002FSKILL.md",[],[]]