[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6H4GDCFPXTYHSFX7CJ7B9HT":3,"skill-same:01M6H4GDCFPXTYHSFX7CJ7B9HT":93},{"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":27,"publishedAt":48,"linkOnly":49,"markdownContent":50,"markdownBody":51,"frontMatter":52,"refName":58,"commitSha":59,"skillDirectory":60,"forksCount":61,"repositoryHtmlUrl":62,"repositoryHomepageUrl":6,"ownerHtmlUrl":63,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":64,"install":65,"resources":78},"01M6H4GDCFPXTYHSFX7CJ7B9HT","logging-api-requests",null,"Monitor and log API requests with correlation IDs, performance metrics, and security audit trails.\nUse when auditing API requests and responses.\nTrigger with phrases like \"log API requests\", \"add API logging\", or \"track API calls\".","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-request-logger\u002Fskills\u002Flogging-api-requests\u002FSKILL.md",[17,22],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47],"requests","logging","logging api requests","api","Bash","calls","trails","with","trigger","io","log","use","codex","security audit","ids","correlation","audit","code","monitor","performance","2026-11-10 10:12:30",false,"---\nname: logging-api-requests\ndescription: |\n  Monitor and log API requests with correlation IDs, performance metrics, and security audit trails.\n  Use when auditing API requests and responses.\n  Trigger with phrases like \"log API requests\", \"add API logging\", or \"track API calls\".\n  \nallowed-tools: Read, Write, Edit, Grep, Glob, Bash(api:log-*)\nversion: 1.0.0\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\nlicense: MIT\ncompatible-with: claude-code, codex, openclaw\n---\n# Logging API Requests\n\n## Overview\n\nImplement structured API request logging with correlation IDs, performance timing, security audit trails, and PII redaction. Capture request\u002Fresponse metadata in JSON format suitable for aggregation in ELK Stack, Loki, or CloudWatch Logs, enabling debugging, performance analysis, and compliance auditing across distributed services.\n\n## Prerequisites\n\n- Structured logging library: Pino or Winston (Node.js), structlog (Python), Logback with JSON encoder (Java)\n- Log aggregation system: ELK Stack (Elasticsearch, Logstash, Kibana), Grafana Loki, or CloudWatch Logs\n- Correlation ID propagation mechanism (middleware-injected or from incoming `X-Request-ID` header)\n- PII data classification for the API domain (which fields contain personal data requiring redaction)\n- Log retention and rotation policy defined per compliance requirements\n\n## Instructions\n\n1. Examine existing logging configuration using Grep and Read to identify current log format, output destinations, and any structured logging already in place.\n2. Implement request logging middleware that captures: timestamp (ISO 8601), correlation ID, HTTP method, URL path (without query string PII), status code, response time (ms), request size, response size, and client IP.\n3. Generate a unique correlation ID (`X-Request-ID`) for each request if not provided by the caller, and propagate it to all downstream service calls and log entries within the request scope.\n4. Add PII redaction rules that mask sensitive fields (passwords, tokens, SSNs, email addresses) in logged request\u002Fresponse bodies using configurable field-path patterns.\n5. Implement log levels per context: `info` for successful requests, `warn` for 4xx client errors, `error` for 5xx server errors with stack traces, and `debug` for request\u002Fresponse bodies (development only).\n6. Configure response body logging for error responses only (4xx\u002F5xx), capturing the error payload for debugging while skipping successful response bodies to reduce log volume.\n7. Add security audit logging for sensitive operations: authentication attempts, permission changes, data exports, and admin actions, tagged with `audit: true` for separate indexing.\n8. Set up log rotation and retention policies: 30 days for application logs, 90 days for audit logs, with automatic compression of logs older than 7 days.\n9. Write tests verifying that PII redaction works correctly, correlation IDs propagate through nested calls, and log output matches expected JSON structure.\n\nSee `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fimplementation.md` for the full implementation guide.\n\n## Output\n\n- `${CLAUDE_SKILL_DIR}\u002Fsrc\u002Fmiddleware\u002Frequest-logger.js` - Structured request\u002Fresponse logging middleware\n- `${CLAUDE_SKILL_DIR}\u002Fsrc\u002Fmiddleware\u002Fcorrelation-id.js` - Correlation ID generation and propagation\n- `${CLAUDE_SKILL_DIR}\u002Fsrc\u002Futils\u002Fpii-redactor.js` - Field-level PII redaction with configurable patterns\n- `${CLAUDE_SKILL_DIR}\u002Fsrc\u002Futils\u002Faudit-logger.js` - Security audit event logger for sensitive operations\n- `${CLAUDE_SKILL_DIR}\u002Fsrc\u002Fconfig\u002Flogging.js` - Log level, format, and output destination configuration\n- `${CLAUDE_SKILL_DIR}\u002Ftests\u002Flogging\u002F` - Logging middleware tests including PII redaction verification\n\n## Error Handling\n\n| Error | Cause | Solution |\n|-------|-------|----------|\n| Log volume overwhelming storage | High-traffic endpoint logging full request\u002Fresponse bodies | Log bodies only for errors; sample successful request bodies at configurable rate (1%) |\n| PII leak in logs | New field added to API response containing personal data not covered by redaction rules | Maintain allowlist of loggable fields rather than blocklist; audit log output regularly |\n| Correlation ID missing | Upstream service does not propagate X-Request-ID header | Generate new correlation ID when header is absent; log warning about missing upstream propagation |\n| Log parsing failure | Log message contains unescaped characters breaking JSON structure | Use structured logging library that handles serialization; never concatenate user input into log strings |\n| Audit log gap | Async logging dropped events during high-load period | Use synchronous logging for audit events; implement write-ahead buffer for audit trail completeness |\n\nRefer to `${CLAUDE_SKILL_DIR}\u002Freferences\u002Ferrors.md` for comprehensive error patterns.\n\n## Examples\n\n**Structured JSON log entry**: `{\"timestamp\":\"2026-03-10T14:30:00Z\",\"correlationId\":\"abc-123\",\"method\":\"POST\",\"path\":\"\u002Fapi\u002Fusers\",\"status\":201,\"durationMs\":45,\"userId\":\"usr_456\",\"audit\":false}` -- every field queryable in log aggregation.\n\n**Distributed tracing correlation**: Propagate `X-Request-ID` from API gateway through 3 microservices, enabling a single Kibana query to show the complete request lifecycle across all services.\n\n**Compliance audit trail**: Tag all data modification operations (POST, PUT, DELETE) with `audit: true`, capturing the authenticated user, modified resource ID, and change summary for SOC 2 compliance evidence.\n\nSee `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fexamples.md` for additional examples.\n\n## Resources\n\n- Structured logging best practices (12-Factor App: Logs)\n- ELK Stack documentation: https:\u002F\u002Fwww.elastic.co\u002Fguide\u002F\n- Pino logger: https:\u002F\u002Fgetpino.io\u002F\n- OpenTelemetry for distributed tracing context propagation","# Logging API Requests\n\n## Overview\n\nImplement structured API request logging with correlation IDs, performance timing, security audit trails, and PII redaction. Capture request\u002Fresponse metadata in JSON format suitable for aggregation in ELK Stack, Loki, or CloudWatch Logs, enabling debugging, performance analysis, and compliance auditing across distributed services.\n\n## Prerequisites\n\n- Structured logging library: Pino or Winston (Node.js), structlog (Python), Logback with JSON encoder (Java)\n- Log aggregation system: ELK Stack (Elasticsearch, Logstash, Kibana), Grafana Loki, or CloudWatch Logs\n- Correlation ID propagation mechanism (middleware-injected or from incoming `X-Request-ID` header)\n- PII data classification for the API domain (which fields contain personal data requiring redaction)\n- Log retention and rotation policy defined per compliance requirements\n\n## Instructions\n\n1. Examine existing logging configuration using Grep and Read to identify current log format, output destinations, and any structured logging already in place.\n2. Implement request logging middleware that captures: timestamp (ISO 8601), correlation ID, HTTP method, URL path (without query string PII), status code, response time (ms), request size, response size, and client IP.\n3. Generate a unique correlation ID (`X-Request-ID`) for each request if not provided by the caller, and propagate it to all downstream service calls and log entries within the request scope.\n4. Add PII redaction rules that mask sensitive fields (passwords, tokens, SSNs, email addresses) in logged request\u002Fresponse bodies using configurable field-path patterns.\n5. Implement log levels per context: `info` for successful requests, `warn` for 4xx client errors, `error` for 5xx server errors with stack traces, and `debug` for request\u002Fresponse bodies (development only).\n6. Configure response body logging for error responses only (4xx\u002F5xx), capturing the error payload for debugging while skipping successful response bodies to reduce log volume.\n7. Add security audit logging for sensitive operations: authentication attempts, permission changes, data exports, and admin actions, tagged with `audit: true` for separate indexing.\n8. Set up log rotation and retention policies: 30 days for application logs, 90 days for audit logs, with automatic compression of logs older than 7 days.\n9. Write tests verifying that PII redaction works correctly, correlation IDs propagate through nested calls, and log output matches expected JSON structure.\n\nSee `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fimplementation.md` for the full implementation guide.\n\n## Output\n\n- `${CLAUDE_SKILL_DIR}\u002Fsrc\u002Fmiddleware\u002Frequest-logger.js` - Structured request\u002Fresponse logging middleware\n- `${CLAUDE_SKILL_DIR}\u002Fsrc\u002Fmiddleware\u002Fcorrelation-id.js` - Correlation ID generation and propagation\n- `${CLAUDE_SKILL_DIR}\u002Fsrc\u002Futils\u002Fpii-redactor.js` - Field-level PII redaction with configurable patterns\n- `${CLAUDE_SKILL_DIR}\u002Fsrc\u002Futils\u002Faudit-logger.js` - Security audit event logger for sensitive operations\n- `${CLAUDE_SKILL_DIR}\u002Fsrc\u002Fconfig\u002Flogging.js` - Log level, format, and output destination configuration\n- `${CLAUDE_SKILL_DIR}\u002Ftests\u002Flogging\u002F` - Logging middleware tests including PII redaction verification\n\n## Error Handling\n\n| Error | Cause | Solution |\n|-------|-------|----------|\n| Log volume overwhelming storage | High-traffic endpoint logging full request\u002Fresponse bodies | Log bodies only for errors; sample successful request bodies at configurable rate (1%) |\n| PII leak in logs | New field added to API response containing personal data not covered by redaction rules | Maintain allowlist of loggable fields rather than blocklist; audit log output regularly |\n| Correlation ID missing | Upstream service does not propagate X-Request-ID header | Generate new correlation ID when header is absent; log warning about missing upstream propagation |\n| Log parsing failure | Log message contains unescaped characters breaking JSON structure | Use structured logging library that handles serialization; never concatenate user input into log strings |\n| Audit log gap | Async logging dropped events during high-load period | Use synchronous logging for audit events; implement write-ahead buffer for audit trail completeness |\n\nRefer to `${CLAUDE_SKILL_DIR}\u002Freferences\u002Ferrors.md` for comprehensive error patterns.\n\n## Examples\n\n**Structured JSON log entry**: `{\"timestamp\":\"2026-03-10T14:30:00Z\",\"correlationId\":\"abc-123\",\"method\":\"POST\",\"path\":\"\u002Fapi\u002Fusers\",\"status\":201,\"durationMs\":45,\"userId\":\"usr_456\",\"audit\":false}` -- every field queryable in log aggregation.\n\n**Distributed tracing correlation**: Propagate `X-Request-ID` from API gateway through 3 microservices, enabling a single Kibana query to show the complete request lifecycle across all services.\n\n**Compliance audit trail**: Tag all data modification operations (POST, PUT, DELETE) with `audit: true`, capturing the authenticated user, modified resource ID, and change summary for SOC 2 compliance evidence.\n\nSee `${CLAUDE_SKILL_DIR}\u002Freferences\u002Fexamples.md` for additional examples.\n\n## Resources\n\n- Structured logging best practices (12-Factor App: Logs)\n- ELK Stack documentation: https:\u002F\u002Fwww.elastic.co\u002Fguide\u002F\n- Pino logger: https:\u002F\u002Fgetpino.io\u002F\n- OpenTelemetry for distributed tracing context propagation",{"name":5,"author":53,"license":14,"version":54,"description":55,"allowed-tools":56,"compatible-with":57},"Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Monitor and log API requests with correlation IDs, performance metrics, and security audit trails.\nUse when auditing API requests and responses.\nTrigger with phrases like \"log API requests\", \"add API logging\", or \"track API calls\".\n","Read, Write, Edit, Grep, Glob, Bash(api:log-*)","claude-code, codex, openclaw","master","3f5d983eb4ef375b749adcd6b07ec03bd82ae8a8","claude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fapi-development\u002Fapi-request-logger\u002Fskills\u002Flogging-api-requests",0,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills","https:\u002F\u002Fgithub.com\u002Fmicsapp","2026-03-20 11:24:18",{"source":8,"skillName":5,"commands":66,"prompt":76,"zipAvailable":77},[67,70,73],{"tool":68,"command":69},"npx","npx skills add micsapp\u002Fmicstec-skills --skill logging-api-requests",{"tool":71,"command":72},"bunx","bunx skills add micsapp\u002Fmicstec-skills --skill logging-api-requests",{"tool":74,"command":75},"pnpm","pnpm dlx skills add micsapp\u002Fmicstec-skills --skill logging-api-requests","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fapi-development\u002Fapi-request-logger\u002Fskills\u002Flogging-api-requests\u002FSKILL.md",true,[79,85,89],{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Ferrors.md","REFERENCE","参考文档",901,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fapi-development\u002Fapi-request-logger\u002Fskills\u002Flogging-api-requests\u002Freferences\u002Ferrors.md",{"path":86,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Fexamples.md",4652,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fapi-development\u002Fapi-request-logger\u002Fskills\u002Flogging-api-requests\u002Freferences\u002Fexamples.md",{"path":90,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":91,"sourceHtmlUrl":92},"references\u002Fimplementation.md",1401,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fapi-development\u002Fapi-request-logger\u002Fskills\u002Flogging-api-requests\u002Freferences\u002Fimplementation.md",[94,122,151,171,191,216],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":102,"publishedAt":48},"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",[100,101],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":23,"categoryName":24,"taxonomyType":25,"taxonomyTypeDesc":26},[103,104,105,106,107,108,109,110,111,31,112,113,114,115,116,117,118,119,120,121],"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":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":136,"publishedAt":48},"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",[128,129,132,135],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":130,"categoryName":131,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":133,"categoryName":134,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":23,"categoryName":24,"taxonomyType":25,"taxonomyTypeDesc":26},[137,138,139,140,104,141,45,142,143,144,145,146,31,112,118,147,148,119,149,150],"deployment","apiops deployment","workflows","azure devops","infrastructure","infrastructure as code","actions","ci","github actions","github-actions","as","guides","CI\u002FCD","implementing",{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":158,"publishedAt":48},"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",[157],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[159,160,161,162,104,107,31,112,163,39,164,165,166,167,168,119,169,170,150,121],"policy","authoring","apim policy authoring","security","access","ready","api security","Access Control","error","processing","cors configuration","production-ready",{"skillNo":172,"name":173,"nameZh":6,"description":174,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":175,"categories":176,"keywords":179,"publishedAt":48},"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",[177,178],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":23,"categoryName":24,"taxonomyType":25,"taxonomyTypeDesc":26},[180,162,181,31,165,182,104,137,183,184,185,186,112,187,119,188,189,190,120,121],"review","security review","api security review","benchmark","verification","owasp","owasp-api","alignment","azure security","reviews","top",{"skillNo":192,"name":193,"nameZh":6,"description":194,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":195,"categories":196,"keywords":197,"publishedAt":48},"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",[],[198,199,200,139,201,202,203,204,31,205,206,207,208,209,210,211,212,213,214,215],"cli","jira","jira cli","init","tasks","create","issues","common","work","command","edit","list","view","project","project work","token","line","sprints",{"skillNo":217,"name":218,"nameZh":6,"description":219,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":220,"categories":221,"keywords":222,"publishedAt":48},"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",[],[218,223,224,225,226,227,228,39,229,230],"npm","js","calculate","node","math","user","compute","errors"]