[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6H4FF2W88WV9EQ4YR85SNZP":3,"skill-same:01M6H4FF2W88WV9EQ4YR85SNZP":102},{"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":30,"publishedAt":51,"linkOnly":52,"markdownContent":53,"markdownBody":54,"frontMatter":55,"refName":61,"commitSha":62,"skillDirectory":63,"forksCount":64,"repositoryHtmlUrl":65,"repositoryHomepageUrl":6,"ownerHtmlUrl":66,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":67,"install":68,"resources":81},"01M6H4FF2W88WV9EQ4YR85SNZP","generating-api-contracts",null,"Generate API contracts and OpenAPI specifications from code or design documents.\nUse when documenting API contracts and specifications.\nTrigger with phrases like \"generate API contract\", \"create OpenAPI spec\", or \"document API contract\".","micsapp\u002Fmicstec-skills","micsapp","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F82411001?v=4","01M6GWCFQ6D3PV8EHNY62NN5VW","01M6GWCFVE1PA5HG0DKC7AMFJ3",4,"MIT","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fapi-development\u002Fapi-contract-generator\u002Fskills\u002Fgenerating-api-contracts\u002FSKILL.md",[17,22,27],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":28,"categoryName":29,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000037","律师与法务",[31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50],"api","contracts","generating api contracts","use","specifications","with","trigger","io","contract","api contract","document","design","read","Bash","openapi","code","generate","create","documents","codex","2026-11-10 10:12:30",false,"---\nname: generating-api-contracts\ndescription: |\n  Generate API contracts and OpenAPI specifications from code or design documents.\n  Use when documenting API contracts and specifications.\n  Trigger with phrases like \"generate API contract\", \"create OpenAPI spec\", or \"document API contract\".\n  \nallowed-tools: Read, Write, Edit, Grep, Glob, Bash(api:contract-*)\nversion: 1.0.0\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\nlicense: MIT\ncompatible-with: claude-code, codex, openclaw\n---\n# Generating API Contracts\n\n## Overview\n\nGenerate OpenAPI 3.0\u002F3.1 specifications and consumer-driven contract tests from existing API implementations, design documents, or database schemas. Produce machine-readable contracts that serve as the single source of truth for code generation, documentation, testing, and gateway configuration, with Pact integration for consumer-driven contract verification.\n\n## Prerequisites\n\n- API implementation with route definitions and handler logic, or design requirements document\n- OpenAPI authoring tool: Swagger Editor, Stoplight Studio, or IDE with OpenAPI extension\n- Consumer-driven contract framework: Pact (polyglot), Spring Cloud Contract (Java), or Dredd (generic)\n- Schema validation tool: Spectral for OpenAPI linting\n- Version control for contract files with diff-based review process\n\n## Instructions\n\n1. Scan existing route handlers and controller files using Grep and Read to extract all endpoint paths, HTTP methods, request parameter names\u002Ftypes, and response body shapes.\n2. Generate OpenAPI 3.0 specification from the extracted data, including `info` (title, version, description), `servers` (environment URLs), `paths` (operations), and `components` (reusable schemas).\n3. Define request schemas with field-level constraints: `type`, `format`, `required`, `minimum\u002Fmaximum`, `pattern` (regex), `enum`, and `example` values for every property.\n4. Document all response status codes per endpoint with separate schemas: 200\u002F201 for success, 400 for validation errors (with field-level error array), 401\u002F403 for auth failures, and 404\u002F500.\n5. Add security scheme definitions (`bearerAuth`, `apiKey`, `oauth2`) and apply them to appropriate operations using the `security` field.\n6. Create Pact consumer contract tests that capture expected interactions from the API consumer perspective, defining expected request\u002Fresponse pairs per endpoint.\n7. Set up provider verification that replays Pact interactions against the actual API implementation, verifying the provider satisfies all consumer expectations.\n8. Generate contract artifacts: OpenAPI spec file, Postman collection, and consumer contract (Pact JSON), all versioned alongside the API source code.\n\nSee `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fimplementation.md` for the full implementation guide.\n\n## Output\n\n- `${CLAUDE_SKILL_DIR}\u002Fopenapi.yaml` - Complete OpenAPI 3.0\u002F3.1 specification\n- `${CLAUDE_SKILL_DIR}\u002Fcontracts\u002Fpact\u002F` - Consumer-driven contract definitions (Pact JSON)\n- `${CLAUDE_SKILL_DIR}\u002Fcontracts\u002Fpostman\u002F` - Generated Postman collection for API testing\n- `${CLAUDE_SKILL_DIR}\u002Ftests\u002Fcontract\u002Fconsumer\u002F` - Consumer contract test implementations\n- `${CLAUDE_SKILL_DIR}\u002Ftests\u002Fcontract\u002Fprovider\u002F` - Provider verification test suite\n- `${CLAUDE_SKILL_DIR}\u002Fscripts\u002Fgenerate-contract.sh` - Contract generation automation script\n\n## Error Handling\n\n| Error | Cause | Solution |\n|-------|-------|----------|\n| Spec-code divergence | API implementation changed without updating the OpenAPI spec | Add CI check that generates spec from code and diffs against committed spec |\n| Pact verification failure | Provider response does not match consumer expectation | Review consumer contract for correctness; update provider if contract is valid |\n| Missing operation ID | Endpoint has no `operationId`, preventing code generation | Generate deterministic operation IDs from method + path (e.g., `getUsers`, `createUser`) |\n| Circular schema reference | Components reference each other creating infinite recursion | Break cycles with `allOf` composition or introduce intermediate types |\n| Example\u002Fschema mismatch | Example values do not validate against their own schema | Auto-validate all examples during spec generation; reject mismatched examples |\n\nRefer to `${CLAUDE_SKILL_DIR}\u002Freferences\u002Ferrors.md` for comprehensive error patterns.\n\n## Examples\n\n**Code-first OpenAPI generation**: Scan Express route decorators and Zod validation schemas to auto-generate a complete OpenAPI 3.1 spec with accurate request\u002Fresponse schemas, examples, and descriptions.\n\n**Consumer-driven contract testing**: Frontend team publishes Pact contracts defining the API interactions they depend on; backend CI verifies every contract on each deployment, preventing breaking changes.\n\n**Design-first workflow**: Author OpenAPI spec in Stoplight Studio, generate server stubs and client SDKs from the spec, then implement business logic in the stubs -- spec stays as the single source of truth.\n\nSee `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fexamples.md` for additional examples.\n\n## Resources\n\n- OpenAPI Specification 3.1: https:\u002F\u002Fspec.openapis.org\u002Foas\u002Fv3.1.0\n- Pact contract testing: https:\u002F\u002Fpact.io\u002F\n- Swagger Editor: https:\u002F\u002Feditor.swagger.io\u002F\n- Dredd API contract testing: https:\u002F\u002Fdredd.org\u002F","# Generating API Contracts\n\n## Overview\n\nGenerate OpenAPI 3.0\u002F3.1 specifications and consumer-driven contract tests from existing API implementations, design documents, or database schemas. Produce machine-readable contracts that serve as the single source of truth for code generation, documentation, testing, and gateway configuration, with Pact integration for consumer-driven contract verification.\n\n## Prerequisites\n\n- API implementation with route definitions and handler logic, or design requirements document\n- OpenAPI authoring tool: Swagger Editor, Stoplight Studio, or IDE with OpenAPI extension\n- Consumer-driven contract framework: Pact (polyglot), Spring Cloud Contract (Java), or Dredd (generic)\n- Schema validation tool: Spectral for OpenAPI linting\n- Version control for contract files with diff-based review process\n\n## Instructions\n\n1. Scan existing route handlers and controller files using Grep and Read to extract all endpoint paths, HTTP methods, request parameter names\u002Ftypes, and response body shapes.\n2. Generate OpenAPI 3.0 specification from the extracted data, including `info` (title, version, description), `servers` (environment URLs), `paths` (operations), and `components` (reusable schemas).\n3. Define request schemas with field-level constraints: `type`, `format`, `required`, `minimum\u002Fmaximum`, `pattern` (regex), `enum`, and `example` values for every property.\n4. Document all response status codes per endpoint with separate schemas: 200\u002F201 for success, 400 for validation errors (with field-level error array), 401\u002F403 for auth failures, and 404\u002F500.\n5. Add security scheme definitions (`bearerAuth`, `apiKey`, `oauth2`) and apply them to appropriate operations using the `security` field.\n6. Create Pact consumer contract tests that capture expected interactions from the API consumer perspective, defining expected request\u002Fresponse pairs per endpoint.\n7. Set up provider verification that replays Pact interactions against the actual API implementation, verifying the provider satisfies all consumer expectations.\n8. Generate contract artifacts: OpenAPI spec file, Postman collection, and consumer contract (Pact JSON), all versioned alongside the API source code.\n\nSee `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fimplementation.md` for the full implementation guide.\n\n## Output\n\n- `${CLAUDE_SKILL_DIR}\u002Fopenapi.yaml` - Complete OpenAPI 3.0\u002F3.1 specification\n- `${CLAUDE_SKILL_DIR}\u002Fcontracts\u002Fpact\u002F` - Consumer-driven contract definitions (Pact JSON)\n- `${CLAUDE_SKILL_DIR}\u002Fcontracts\u002Fpostman\u002F` - Generated Postman collection for API testing\n- `${CLAUDE_SKILL_DIR}\u002Ftests\u002Fcontract\u002Fconsumer\u002F` - Consumer contract test implementations\n- `${CLAUDE_SKILL_DIR}\u002Ftests\u002Fcontract\u002Fprovider\u002F` - Provider verification test suite\n- `${CLAUDE_SKILL_DIR}\u002Fscripts\u002Fgenerate-contract.sh` - Contract generation automation script\n\n## Error Handling\n\n| Error | Cause | Solution |\n|-------|-------|----------|\n| Spec-code divergence | API implementation changed without updating the OpenAPI spec | Add CI check that generates spec from code and diffs against committed spec |\n| Pact verification failure | Provider response does not match consumer expectation | Review consumer contract for correctness; update provider if contract is valid |\n| Missing operation ID | Endpoint has no `operationId`, preventing code generation | Generate deterministic operation IDs from method + path (e.g., `getUsers`, `createUser`) |\n| Circular schema reference | Components reference each other creating infinite recursion | Break cycles with `allOf` composition or introduce intermediate types |\n| Example\u002Fschema mismatch | Example values do not validate against their own schema | Auto-validate all examples during spec generation; reject mismatched examples |\n\nRefer to `${CLAUDE_SKILL_DIR}\u002Freferences\u002Ferrors.md` for comprehensive error patterns.\n\n## Examples\n\n**Code-first OpenAPI generation**: Scan Express route decorators and Zod validation schemas to auto-generate a complete OpenAPI 3.1 spec with accurate request\u002Fresponse schemas, examples, and descriptions.\n\n**Consumer-driven contract testing**: Frontend team publishes Pact contracts defining the API interactions they depend on; backend CI verifies every contract on each deployment, preventing breaking changes.\n\n**Design-first workflow**: Author OpenAPI spec in Stoplight Studio, generate server stubs and client SDKs from the spec, then implement business logic in the stubs -- spec stays as the single source of truth.\n\nSee `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fexamples.md` for additional examples.\n\n## Resources\n\n- OpenAPI Specification 3.1: https:\u002F\u002Fspec.openapis.org\u002Foas\u002Fv3.1.0\n- Pact contract testing: https:\u002F\u002Fpact.io\u002F\n- Swagger Editor: https:\u002F\u002Feditor.swagger.io\u002F\n- Dredd API contract testing: https:\u002F\u002Fdredd.org\u002F",{"name":5,"author":56,"license":14,"version":57,"description":58,"allowed-tools":59,"compatible-with":60},"Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Generate API contracts and OpenAPI specifications from code or design documents.\nUse when documenting API contracts and specifications.\nTrigger with phrases like \"generate API contract\", \"create OpenAPI spec\", or \"document API contract\".\n","Read, Write, Edit, Grep, Glob, Bash(api:contract-*)","claude-code, codex, openclaw","master","3f5d983eb4ef375b749adcd6b07ec03bd82ae8a8","claude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fapi-development\u002Fapi-contract-generator\u002Fskills\u002Fgenerating-api-contracts",0,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills","https:\u002F\u002Fgithub.com\u002Fmicsapp","2026-03-20 11:24:18",{"source":8,"skillName":5,"commands":69,"prompt":79,"zipAvailable":80},[70,73,76],{"tool":71,"command":72},"npx","npx skills add micsapp\u002Fmicstec-skills --skill generating-api-contracts",{"tool":74,"command":75},"bunx","bunx skills add micsapp\u002Fmicstec-skills --skill generating-api-contracts",{"tool":77,"command":78},"pnpm","pnpm dlx skills add micsapp\u002Fmicstec-skills --skill generating-api-contracts","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fapi-development\u002Fapi-contract-generator\u002Fskills\u002Fgenerating-api-contracts\u002FSKILL.md",true,[82,88,92,96],{"path":83,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Ferrors.md","REFERENCE","参考文档",901,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fapi-development\u002Fapi-contract-generator\u002Fskills\u002Fgenerating-api-contracts\u002Freferences\u002Ferrors.md",{"path":89,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":90,"sourceHtmlUrl":91},"references\u002Fexamples.md",5337,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fapi-development\u002Fapi-contract-generator\u002Fskills\u002Fgenerating-api-contracts\u002Freferences\u002Fexamples.md",{"path":93,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":94,"sourceHtmlUrl":95},"references\u002Fimplementation.md",1406,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fapi-development\u002Fapi-contract-generator\u002Fskills\u002Fgenerating-api-contracts\u002Freferences\u002Fimplementation.md",{"path":97,"resourceType":98,"resourceTypeDesc":99,"sizeBytes":100,"sourceHtmlUrl":101},"scripts\u002Fgenerate-contract.sh","SCRIPT","脚本",545,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fapi-development\u002Fapi-contract-generator\u002Fskills\u002Fgenerating-api-contracts\u002Fscripts\u002Fgenerate-contract.sh",[103,131,160,180,200,224],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":111,"publishedAt":51},"01M6HBTJ02FXBFG9NYEHHYAP52","azure-apim-architecture","Analyzes and explains Azure API Management architecture decisions for enterprise API marketplace implementations using VNet Internal mode, Front Door, hybrid authentication, and multi-environment strategies. Use when discussing APIM component selection, network topology, cost optimization, or comparing alternatives like workspaces vs instances, VNet Internal vs External mode, or Front Door vs Application Gateway.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fazure-apim-architecture\u002FSKILL.md",[109,110],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":23,"categoryName":24,"taxonomyType":25,"taxonomyTypeDesc":26},[112,113,114,115,116,117,118,119,120,31,121,122,123,124,125,126,127,128,129,130],"architecture","azure","azure apim architecture","component","authentication","gateway","topology","Optimization","network","team","environment","multi-environment","workspaces","instances","selection","strategies","azure api management","mode","for",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":145,"publishedAt":51},"01M6HBT7J4H082JEEA670B3EQ9","apiops-deployment","Guides deployment of Azure API Management infrastructure using Infrastructure as Code (Bicep\u002FTerraform), CI\u002FCD pipelines (GitHub Actions\u002FAzure DevOps), and APIOps workflows. Use when deploying APIM, creating pipelines, or implementing dev→test→prod promotion strategies.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fapiops-deployment\u002FSKILL.md",[137,138,141,144],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":139,"categoryName":140,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":142,"categoryName":143,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":23,"categoryName":24,"taxonomyType":25,"taxonomyTypeDesc":26},[146,147,148,149,113,150,46,151,152,153,154,155,31,121,127,156,157,128,158,159],"deployment","apiops deployment","workflows","azure devops","infrastructure","infrastructure as code","actions","ci","github actions","github-actions","as","guides","CI\u002FCD","implementing",{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":164,"categories":165,"keywords":167,"publishedAt":51},"01M6HBT2HEA23THNE9E00GYQBE","apim-policy-authoring","Creates production-ready Azure API Management policy XML for authentication (OAuth 2.0, JWT validation, subscription keys), rate limiting, CORS configuration, error handling, and API transformations. Use when implementing API security, access control, or request\u002Fresponse processing logic.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fapim-policy-authoring\u002FSKILL.md",[166],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[168,169,170,171,113,116,31,121,172,34,173,174,175,176,177,128,178,179,159,130],"policy","authoring","apim policy authoring","security","access","ready","api security","Access Control","error","processing","cors configuration","production-ready",{"skillNo":181,"name":182,"nameZh":6,"description":183,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":184,"categories":185,"keywords":188,"publishedAt":51},"01M6HBSY65SB29J9WE9KYD0K6T","api-security-review","Reviews Azure API Management configurations for security vulnerabilities, OWASP API Security Top 10 compliance, VNet Internal mode validation, Private Link verification, and Azure Security Benchmark alignment. Use when performing security audits, pre-deployment validation, or compliance reviews.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fapi-security-review\u002FSKILL.md",[186,187],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":23,"categoryName":24,"taxonomyType":25,"taxonomyTypeDesc":26},[189,171,190,31,174,191,113,146,192,193,194,195,121,196,128,197,198,199,129,130],"review","security review","api security review","benchmark","verification","owasp","owasp-api","alignment","azure security","reviews","top",{"skillNo":201,"name":202,"nameZh":6,"description":203,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":204,"categories":205,"keywords":206,"publishedAt":51},"01M6HBSRW4PDFE6K4F8JYPZQ05","jira-cli","Interact with Jira from the command line to create, list, view, edit, and transition issues, manage sprints and epics, and perform common Jira workflows. Use when the user asks about Jira tasks, tickets, issues, sprints, or needs to manage project work items.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fawesome-copilot-agents\u002Fskills\u002Fjira-cli\u002FSKILL.md",[],[207,208,209,148,210,211,48,212,31,213,214,215,216,217,218,219,220,221,222,223],"cli","jira","jira cli","init","tasks","issues","common","work","command","edit","list","view","project","project work","token","line","sprints",{"skillNo":225,"name":226,"nameZh":6,"description":227,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":228,"categories":229,"keywords":230,"publishedAt":51},"01M6HBSNS3JHMW603G47TWE31H","calculator","Performs arbitrary-precision arithmetic calculations including addition, subtraction, multiplication, division, and exponents. Use when the user asks to calculate, compute, or evaluate math expressions, or when precise decimal arithmetic is needed to avoid floating-point errors.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fawesome-copilot-agents\u002Fskills\u002Fcalculator\u002FSKILL.md",[],[226,231,232,233,234,235,236,34,237,238],"npm","js","calculate","node","math","user","compute","errors"]