[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77RVS29RAT4BZQRC33MMY25":3,"skill-same:01M77RVS29RAT4BZQRC33MMY25":55},{"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":28,"commitSha":29,"skillDirectory":30,"forksCount":14,"repositoryHtmlUrl":31,"repositoryHomepageUrl":32,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M77RVS29RAT4BZQRC33MMY25","error-handling",null,"Define consistent error handling, exception management, recovery strategies, and user-friendly error reporting across all systems.","panksooungman-dot\u002FAI-Web-Master","panksooungman-dot","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F263377190?v=4","01M77RQKZAR08JG1JSWP1MVXPV","cnbiz","01M77RQM00YBBJX4F6Y04HT8RN",0,"MIT","https:\u002F\u002Fgithub.com\u002Fpanksooungman-dot\u002FAI-Web-Master\u002Fblob\u002Fmain\u002Fskills\u002Fshared\u002Ferror-handling\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: error-handling\ndescription: Define consistent error handling, exception management, recovery strategies, and user-friendly error reporting across all systems.\nversion: 1.0.0\nauthor: AI Business OS\nlicense: MIT\ncategory: shared\npriority: required\n---\n\n# Error Handling\n\n## Purpose\n\nThis skill establishes standards for handling errors consistently across applications, APIs, services, and infrastructure.\n\nThe objective is to improve system reliability, simplify troubleshooting, and provide meaningful feedback without exposing sensitive information.\n\n---\n\n# When to Use\n\nExecute when:\n\n- Designing application logic\n- Building APIs\n- Handling exceptions\n- Implementing background jobs\n- Processing external integrations\n- Reviewing production reliability\n\n---\n\n# Objectives\n\nEnsure error handling is:\n\n- Consistent\n- Predictable\n- Secure\n- Recoverable\n- Observable\n\n---\n\n# Inputs\n\nExpected inputs:\n\n- Business Requirements\n- System Architecture\n- API Specifications\n- Security Requirements\n- Logging Standards\n- Monitoring Requirements\n\n---\n\n# Error Categories\n\nClassify errors into:\n\n- Validation Errors\n- Business Rule Errors\n- Authentication Errors\n- Authorization Errors\n- Resource Not Found\n- Conflict Errors\n- External Service Errors\n- Infrastructure Errors\n- Internal Server Errors\n\nAssign standardized error codes where applicable.\n\n---\n\n# Exception Management\n\nImplement:\n\n- Centralized Exception Handling\n- Domain-specific Exceptions\n- Graceful Failure\n- Retry Logic\n- Fallback Strategies\n- Timeout Handling\n\nAvoid unhandled exceptions.\n\n---\n\n# Error Responses\n\nEnsure responses include:\n\n- Error Code\n- Human-readable Message\n- Technical Details (when appropriate)\n- Correlation ID\n- Timestamp\n\nNever expose stack traces or sensitive internal details to end users.\n\n---\n\n# Recovery Strategy\n\nSupport:\n\n- Retry with Backoff\n- Circuit Breaker\n- Fallback Responses\n- Transaction Rollback\n- Compensation Logic\n\nRecover automatically whenever safe and appropriate.\n\n---\n\n# Logging\n\nRecord:\n\n- Error Type\n- Severity\n- Correlation ID\n- Context\n- Root Cause\n- Stack Trace (internal only)\n\nIntegrate with centralized logging.\n\n---\n\n# Validation Checklist\n\nBefore completion verify:\n\n- Error categories defined\n- Exceptions handled centrally\n- Responses standardized\n- Recovery strategy documented\n- Logging integrated\n- Sensitive data protected\n\n---\n\n# Failure Conditions\n\nStop and request clarification if:\n\n- Error strategy is undefined\n- Recovery approach is missing\n- Logging requirements are unclear\n- Sensitive information may be exposed\n- Monitoring is unavailable\n\n---\n\n# Outputs\n\nGenerate:\n\n- Error Handling Guide\n- Exception Strategy\n- Error Response Standard\n- Recovery Checklist\n\n---\n\n# Rules\n\n- Fail safely and predictably.\n- Never expose sensitive implementation details.\n- Use consistent error codes.\n- Log errors with sufficient context.\n- Design for graceful degradation.\n\n---\n\n# Success Criteria\n\nThis skill succeeds when:\n\n- errors are handled consistently\n- failures are observable\n- users receive meaningful feedback\n- systems recover whenever possible\n- troubleshooting is efficient\n\n---\n\n# Related Skills\n\n- logging\n- monitoring\n- validation\n- security\n- api-design\n\n---\n\n# Version History\n\n| Version | Date | Description |\n|---------|------|-------------|\n| 1.0.0 | 2026-07-10 | Initial release |","# Error Handling\n\n## Purpose\n\nThis skill establishes standards for handling errors consistently across applications, APIs, services, and infrastructure.\n\nThe objective is to improve system reliability, simplify troubleshooting, and provide meaningful feedback without exposing sensitive information.\n\n---\n\n# When to Use\n\nExecute when:\n\n- Designing application logic\n- Building APIs\n- Handling exceptions\n- Implementing background jobs\n- Processing external integrations\n- Reviewing production reliability\n\n---\n\n# Objectives\n\nEnsure error handling is:\n\n- Consistent\n- Predictable\n- Secure\n- Recoverable\n- Observable\n\n---\n\n# Inputs\n\nExpected inputs:\n\n- Business Requirements\n- System Architecture\n- API Specifications\n- Security Requirements\n- Logging Standards\n- Monitoring Requirements\n\n---\n\n# Error Categories\n\nClassify errors into:\n\n- Validation Errors\n- Business Rule Errors\n- Authentication Errors\n- Authorization Errors\n- Resource Not Found\n- Conflict Errors\n- External Service Errors\n- Infrastructure Errors\n- Internal Server Errors\n\nAssign standardized error codes where applicable.\n\n---\n\n# Exception Management\n\nImplement:\n\n- Centralized Exception Handling\n- Domain-specific Exceptions\n- Graceful Failure\n- Retry Logic\n- Fallback Strategies\n- Timeout Handling\n\nAvoid unhandled exceptions.\n\n---\n\n# Error Responses\n\nEnsure responses include:\n\n- Error Code\n- Human-readable Message\n- Technical Details (when appropriate)\n- Correlation ID\n- Timestamp\n\nNever expose stack traces or sensitive internal details to end users.\n\n---\n\n# Recovery Strategy\n\nSupport:\n\n- Retry with Backoff\n- Circuit Breaker\n- Fallback Responses\n- Transaction Rollback\n- Compensation Logic\n\nRecover automatically whenever safe and appropriate.\n\n---\n\n# Logging\n\nRecord:\n\n- Error Type\n- Severity\n- Correlation ID\n- Context\n- Root Cause\n- Stack Trace (internal only)\n\nIntegrate with centralized logging.\n\n---\n\n# Validation Checklist\n\nBefore completion verify:\n\n- Error categories defined\n- Exceptions handled centrally\n- Responses standardized\n- Recovery strategy documented\n- Logging integrated\n- Sensitive data protected\n\n---\n\n# Failure Conditions\n\nStop and request clarification if:\n\n- Error strategy is undefined\n- Recovery approach is missing\n- Logging requirements are unclear\n- Sensitive information may be exposed\n- Monitoring is unavailable\n\n---\n\n# Outputs\n\nGenerate:\n\n- Error Handling Guide\n- Exception Strategy\n- Error Response Standard\n- Recovery Checklist\n\n---\n\n# Rules\n\n- Fail safely and predictably.\n- Never expose sensitive implementation details.\n- Use consistent error codes.\n- Log errors with sufficient context.\n- Design for graceful degradation.\n\n---\n\n# Success Criteria\n\nThis skill succeeds when:\n\n- errors are handled consistently\n- failures are observable\n- users receive meaningful feedback\n- systems recover whenever possible\n- troubleshooting is efficient\n\n---\n\n# Related Skills\n\n- logging\n- monitoring\n- validation\n- security\n- api-design\n\n---\n\n# Version History\n\n| Version | Date | Description |\n|---------|------|-------------|\n| 1.0.0 | 2026-07-10 | Initial release |",{"name":5,"author":24,"license":15,"version":25,"category":26,"priority":27,"description":7},"AI Business OS","1.0.0","shared","required","main","8ba4c8c0d58db28bdcfccd02e7d75b7a3cf70dc9","skills\u002Fshared\u002Ferror-handling","https:\u002F\u002Fgithub.com\u002Fpanksooungman-dot\u002FAI-Web-Master","https:\u002F\u002Fai-web-master-cnbiz-web.vercel.app","https:\u002F\u002Fgithub.com\u002Fpanksooungman-dot","2026-11-14 20:43:00",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add panksooungman-dot\u002FAI-Web-Master --skill error-handling",{"tool":41,"command":42},"bunx","bunx skills add panksooungman-dot\u002FAI-Web-Master --skill error-handling",{"tool":44,"command":45},"pnpm","pnpm dlx skills add panksooungman-dot\u002FAI-Web-Master --skill error-handling","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fpanksooungman-dot\u002FAI-Web-Master\u002Fblob\u002Fmain\u002Fskills\u002Fshared\u002Ferror-handling\u002FSKILL.md",true,[49],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"README.md","REFERENCE","参考文档",168,"https:\u002F\u002Fgithub.com\u002Fpanksooungman-dot\u002FAI-Web-Master\u002Fblob\u002Fmain\u002Fskills\u002Fshared\u002Ferror-handling\u002FREADME.md",[56,63,70,77,84,91],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M77S2FHFC73NY664GYHNHGE8","rollback","Plan, validate, and execute safe rollback procedures to restore a stable system state when deployments introduce critical issues.","https:\u002F\u002Fgithub.com\u002Fpanksooungman-dot\u002FAI-Web-Master\u002Fblob\u002Fmain\u002Fskills\u002Fworkflows\u002Frelease\u002Frollback\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M77S2C5NW59NY9F939ECFVN0","release-note","Create clear, concise, and stakeholder-friendly release notes that communicate new features, improvements, fixes, breaking changes, and operational guidance for each release.","https:\u002F\u002Fgithub.com\u002Fpanksooungman-dot\u002FAI-Web-Master\u002Fblob\u002Fmain\u002Fskills\u002Fworkflows\u002Frelease\u002Frelease-note\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M77S28YMHR597AZF39CR0CNG","monitoring","Continuously observe application health, performance, reliability, and business metrics after deployment to detect issues early and support operational excellence.","https:\u002F\u002Fgithub.com\u002Fpanksooungman-dot\u002FAI-Web-Master\u002Fblob\u002Fmain\u002Fskills\u002Fworkflows\u002Frelease\u002Fmonitoring\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M77S26FGE7P6W5MDSBQ1WTPV","maintenance","Maintain, improve, and support production systems after release through continuous monitoring, issue resolution, updates, and operational excellence.","https:\u002F\u002Fgithub.com\u002Fpanksooungman-dot\u002FAI-Web-Master\u002Fblob\u002Fmain\u002Fskills\u002Fworkflows\u002Frelease\u002Fmaintenance\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M77S24CZGKFZEXXS3N0B067G","deployment","Plan, validate, and execute application deployments safely and consistently across environments while minimizing downtime and deployment risk.","https:\u002F\u002Fgithub.com\u002Fpanksooungman-dot\u002FAI-Web-Master\u002Fblob\u002Fmain\u002Fskills\u002Fworkflows\u002Frelease\u002Fdeployment\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M77S21AG798PAEH5HEVYBYF7","changelog","Maintain a structured, accurate, and versioned changelog that records all notable changes made to the project across releases.","https:\u002F\u002Fgithub.com\u002Fpanksooungman-dot\u002FAI-Web-Master\u002Fblob\u002Fmain\u002Fskills\u002Fworkflows\u002Frelease\u002Fchangelog\u002FSKILL.md",[],[]]