[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72ZMBP2CQJKWJ5Z1R2G2XQQ":3,"skill-same:01M72ZMBP2CQJKWJ5Z1R2G2XQQ":74},{"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},"01M72ZMBP2CQJKWJ5Z1R2G2XQQ","sre-engineer",null,"Defines service level objectives, creates error budget policies, designs incident response procedures, develops capacity models, and produces monitoring configurations and automation scripts for production systems. Use when defining SLIs\u002FSLOs, managing error budgets, building reliable systems at scale, incident management, chaos engineering, toil reduction, or capacity planning.","andrewthomastaylor\u002FSkills","andrewthomastaylor","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F249856925?v=4","01M72Z00NZWQPWA1TVXZPKXXWJ","01M72Z00PJ210Z6DAD1N93P2HG",0,"MIT","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fskills\u002Fsre-engineer\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: sre-engineer\ndescription: Defines service level objectives, creates error budget policies, designs incident response procedures, develops capacity models, and produces monitoring configurations and automation scripts for production systems. Use when defining SLIs\u002FSLOs, managing error budgets, building reliable systems at scale, incident management, chaos engineering, toil reduction, or capacity planning.\nlicense: MIT\nmetadata:\n  author: https:\u002F\u002Fgithub.com\u002FJeffallan\n  version: \"1.1.0\"\n  domain: devops\n  triggers: SRE, site reliability, SLO, SLI, error budget, incident management, chaos engineering, toil reduction, on-call, MTTR\n  role: specialist\n  scope: implementation\n  output-format: code\n  related-skills: devops-engineer, cloud-architect, kubernetes-specialist\n---\n\n# SRE Engineer\n\n## Core Workflow\n\n1. **Assess reliability** - Review architecture, SLOs, incidents, toil levels\n2. **Define SLOs** - Identify meaningful SLIs and set appropriate targets\n3. **Verify alignment** - Confirm SLO targets reflect user expectations before proceeding\n4. **Implement monitoring** - Build golden signal dashboards and alerting\n5. **Automate toil** - Identify repetitive tasks and build automation\n6. **Test resilience** - Design and execute chaos experiments; verify recovery meets RTO\u002FRPO targets before marking the experiment complete; validate recovery behavior end-to-end\n\n## Reference Guide\n\nLoad detailed guidance based on context:\n\n| Topic | Reference | Load When |\n|-------|-----------|-----------|\n| SLO\u002FSLI | `references\u002Fslo-sli-management.md` | Defining SLOs, calculating error budgets |\n| Error Budgets | `references\u002Ferror-budget-policy.md` | Managing budgets, burn rates, policies |\n| Monitoring | `references\u002Fmonitoring-alerting.md` | Golden signals, alert design, dashboards |\n| Automation | `references\u002Fautomation-toil.md` | Toil reduction, automation patterns |\n| Incidents | `references\u002Fincident-chaos.md` | Incident response, chaos engineering |\n\n## Constraints\n\n### MUST DO\n- Define quantitative SLOs (e.g., 99.9% availability)\n- Calculate error budgets from SLO targets\n- Monitor golden signals (latency, traffic, errors, saturation)\n- Write blameless postmortems for all incidents\n- Measure toil and track reduction progress\n- Automate repetitive operational tasks\n- Test failure scenarios with chaos engineering\n- Balance reliability with feature velocity\n\n### MUST NOT DO\n- Set SLOs without user impact justification\n- Alert on symptoms without actionable runbooks\n- Tolerate >50% toil without automation plan\n- Skip postmortems or assign blame\n- Implement manual processes for recurring tasks\n- Deploy without capacity planning\n- Ignore error budget exhaustion\n- Build systems that can't degrade gracefully\n\n## Output Templates\n\nWhen implementing SRE practices, provide:\n1. SLO definitions with SLI measurements and targets\n2. Monitoring\u002Falerting configuration (Prometheus, etc.)\n3. Automation scripts (Python, Go, Terraform)\n4. Runbooks with clear remediation steps\n5. Brief explanation of reliability impact\n\n## Concrete Examples\n\n### SLO Definition & Error Budget Calculation\n\n```\n# 99.9% availability SLO over a 30-day window\n# Allowed downtime: (1 - 0.999) * 30 * 24 * 60 = 43.2 minutes\u002Fmonth\n# Error budget (request-based): 0.001 * total_requests\n\n# Example: 10M requests\u002Fmonth → 10,000 error budget requests\n# If 5,000 errors consumed in week 1 → 50% budget burned in 25% of window\n# → Trigger error budget policy: freeze non-critical releases\n```\n\n### Prometheus SLO Alerting Rule (Multiwindow Burn Rate)\n\n```yaml\ngroups:\n  - name: slo_availability\n    rules:\n      # Fast burn: 2% budget in 1h (14.4x burn rate)\n      - alert: HighErrorBudgetBurn\n        expr: |\n          (\n            sum(rate(http_requests_total{status=~\"5..\"}[1h]))\n            \u002F\n            sum(rate(http_requests_total[1h]))\n          ) > 0.014400\n          and\n          (\n            sum(rate(http_requests_total{status=~\"5..\"}[5m]))\n            \u002F\n            sum(rate(http_requests_total[5m]))\n          ) > 0.014400\n        for: 2m\n        labels:\n          severity: critical\n        annotations:\n          summary: \"High error budget burn rate detected\"\n          runbook: \"https:\u002F\u002Fwiki.internal\u002Frunbooks\u002Fhigh-error-burn\"\n\n      # Slow burn: 5% budget in 6h (1x burn rate sustained)\n      - alert: SlowErrorBudgetBurn\n        expr: |\n          (\n            sum(rate(http_requests_total{status=~\"5..\"}[6h]))\n            \u002F\n            sum(rate(http_requests_total[6h]))\n          ) > 0.001\n        for: 15m\n        labels:\n          severity: warning\n        annotations:\n          summary: \"Sustained error budget consumption\"\n          runbook: \"https:\u002F\u002Fwiki.internal\u002Frunbooks\u002Fslow-error-burn\"\n```\n\n### PromQL Golden Signal Queries\n\n```promql\n# Latency — 99th percentile request duration\nhistogram_quantile(0.99, sum(rate(http_request_duration_seconds_bucket[5m])) by (le, service))\n\n# Traffic — requests per second by service\nsum(rate(http_requests_total[5m])) by (service)\n\n# Errors — error rate ratio\nsum(rate(http_requests_total{status=~\"5..\"}[5m])) by (service)\n  \u002F\nsum(rate(http_requests_total[5m])) by (service)\n\n# Saturation — CPU throttling ratio\nsum(rate(container_cpu_cfs_throttled_seconds_total[5m])) by (pod)\n  \u002F\nsum(rate(container_cpu_cfs_periods_total[5m])) by (pod)\n```\n\n### Toil Automation Script (Python)\n\n```python\n#!\u002Fusr\u002Fbin\u002Fenv python3\n\"\"\"Auto-remediation: restart pods exceeding error threshold.\"\"\"\nimport subprocess, sys, json\n\nERROR_THRESHOLD = 0.05  # 5% error rate triggers restart\n\ndef get_error_rate(service: str) -> float:\n    \"\"\"Query Prometheus for current error rate.\"\"\"\n    import urllib.request\n    query = f'sum(rate(http_requests_total{{status=~\"5..\",service=\"{service}\"}}[5m])) \u002F sum(rate(http_requests_total{{service=\"{service}\"}}[5m]))'\n    url = f\"http:\u002F\u002Fprometheus:9090\u002Fapi\u002Fv1\u002Fquery?query={urllib.request.quote(query)}\"\n    with urllib.request.urlopen(url) as resp:\n        data = json.load(resp)\n    results = data[\"data\"][\"result\"]\n    return float(results[0][\"value\"][1]) if results else 0.0\n\ndef restart_deployment(namespace: str, deployment: str) -> None:\n    subprocess.run(\n        [\"kubectl\", \"rollout\", \"restart\", f\"deployment\u002F{deployment}\", \"-n\", namespace],\n        check=True\n    )\n    print(f\"Restarted {namespace}\u002F{deployment}\")\n\nif __name__ == \"__main__\":\n    service, namespace, deployment = sys.argv[1], sys.argv[2], sys.argv[3]\n    rate = get_error_rate(service)\n    print(f\"Error rate for {service}: {rate:.2%}\")\n    if rate > ERROR_THRESHOLD:\n        restart_deployment(namespace, deployment)\n    else:\n        print(\"Within SLO threshold — no action required\")\n```\n\n[Documentation](https:\u002F\u002Fjeffallan.github.io\u002Fclaude-skills\u002Fskills\u002Fdevops\u002Fsre-engineer\u002F)\n","# SRE Engineer\n\n## Core Workflow\n\n1. **Assess reliability** - Review architecture, SLOs, incidents, toil levels\n2. **Define SLOs** - Identify meaningful SLIs and set appropriate targets\n3. **Verify alignment** - Confirm SLO targets reflect user expectations before proceeding\n4. **Implement monitoring** - Build golden signal dashboards and alerting\n5. **Automate toil** - Identify repetitive tasks and build automation\n6. **Test resilience** - Design and execute chaos experiments; verify recovery meets RTO\u002FRPO targets before marking the experiment complete; validate recovery behavior end-to-end\n\n## Reference Guide\n\nLoad detailed guidance based on context:\n\n| Topic | Reference | Load When |\n|-------|-----------|-----------|\n| SLO\u002FSLI | `references\u002Fslo-sli-management.md` | Defining SLOs, calculating error budgets |\n| Error Budgets | `references\u002Ferror-budget-policy.md` | Managing budgets, burn rates, policies |\n| Monitoring | `references\u002Fmonitoring-alerting.md` | Golden signals, alert design, dashboards |\n| Automation | `references\u002Fautomation-toil.md` | Toil reduction, automation patterns |\n| Incidents | `references\u002Fincident-chaos.md` | Incident response, chaos engineering |\n\n## Constraints\n\n### MUST DO\n- Define quantitative SLOs (e.g., 99.9% availability)\n- Calculate error budgets from SLO targets\n- Monitor golden signals (latency, traffic, errors, saturation)\n- Write blameless postmortems for all incidents\n- Measure toil and track reduction progress\n- Automate repetitive operational tasks\n- Test failure scenarios with chaos engineering\n- Balance reliability with feature velocity\n\n### MUST NOT DO\n- Set SLOs without user impact justification\n- Alert on symptoms without actionable runbooks\n- Tolerate >50% toil without automation plan\n- Skip postmortems or assign blame\n- Implement manual processes for recurring tasks\n- Deploy without capacity planning\n- Ignore error budget exhaustion\n- Build systems that can't degrade gracefully\n\n## Output Templates\n\nWhen implementing SRE practices, provide:\n1. SLO definitions with SLI measurements and targets\n2. Monitoring\u002Falerting configuration (Prometheus, etc.)\n3. Automation scripts (Python, Go, Terraform)\n4. Runbooks with clear remediation steps\n5. Brief explanation of reliability impact\n\n## Concrete Examples\n\n### SLO Definition & Error Budget Calculation\n\n```\n# 99.9% availability SLO over a 30-day window\n# Allowed downtime: (1 - 0.999) * 30 * 24 * 60 = 43.2 minutes\u002Fmonth\n# Error budget (request-based): 0.001 * total_requests\n\n# Example: 10M requests\u002Fmonth → 10,000 error budget requests\n# If 5,000 errors consumed in week 1 → 50% budget burned in 25% of window\n# → Trigger error budget policy: freeze non-critical releases\n```\n\n### Prometheus SLO Alerting Rule (Multiwindow Burn Rate)\n\n```yaml\ngroups:\n  - name: slo_availability\n    rules:\n      # Fast burn: 2% budget in 1h (14.4x burn rate)\n      - alert: HighErrorBudgetBurn\n        expr: |\n          (\n            sum(rate(http_requests_total{status=~\"5..\"}[1h]))\n            \u002F\n            sum(rate(http_requests_total[1h]))\n          ) > 0.014400\n          and\n          (\n            sum(rate(http_requests_total{status=~\"5..\"}[5m]))\n            \u002F\n            sum(rate(http_requests_total[5m]))\n          ) > 0.014400\n        for: 2m\n        labels:\n          severity: critical\n        annotations:\n          summary: \"High error budget burn rate detected\"\n          runbook: \"https:\u002F\u002Fwiki.internal\u002Frunbooks\u002Fhigh-error-burn\"\n\n      # Slow burn: 5% budget in 6h (1x burn rate sustained)\n      - alert: SlowErrorBudgetBurn\n        expr: |\n          (\n            sum(rate(http_requests_total{status=~\"5..\"}[6h]))\n            \u002F\n            sum(rate(http_requests_total[6h]))\n          ) > 0.001\n        for: 15m\n        labels:\n          severity: warning\n        annotations:\n          summary: \"Sustained error budget consumption\"\n          runbook: \"https:\u002F\u002Fwiki.internal\u002Frunbooks\u002Fslow-error-burn\"\n```\n\n### PromQL Golden Signal Queries\n\n```promql\n# Latency — 99th percentile request duration\nhistogram_quantile(0.99, sum(rate(http_request_duration_seconds_bucket[5m])) by (le, service))\n\n# Traffic — requests per second by service\nsum(rate(http_requests_total[5m])) by (service)\n\n# Errors — error rate ratio\nsum(rate(http_requests_total{status=~\"5..\"}[5m])) by (service)\n  \u002F\nsum(rate(http_requests_total[5m])) by (service)\n\n# Saturation — CPU throttling ratio\nsum(rate(container_cpu_cfs_throttled_seconds_total[5m])) by (pod)\n  \u002F\nsum(rate(container_cpu_cfs_periods_total[5m])) by (pod)\n```\n\n### Toil Automation Script (Python)\n\n```python\n#!\u002Fusr\u002Fbin\u002Fenv python3\n\"\"\"Auto-remediation: restart pods exceeding error threshold.\"\"\"\nimport subprocess, sys, json\n\nERROR_THRESHOLD = 0.05  # 5% error rate triggers restart\n\ndef get_error_rate(service: str) -> float:\n    \"\"\"Query Prometheus for current error rate.\"\"\"\n    import urllib.request\n    query = f'sum(rate(http_requests_total{{status=~\"5..\",service=\"{service}\"}}[5m])) \u002F sum(rate(http_requests_total{{service=\"{service}\"}}[5m]))'\n    url = f\"http:\u002F\u002Fprometheus:9090\u002Fapi\u002Fv1\u002Fquery?query={urllib.request.quote(query)}\"\n    with urllib.request.urlopen(url) as resp:\n        data = json.load(resp)\n    results = data[\"data\"][\"result\"]\n    return float(results[0][\"value\"][1]) if results else 0.0\n\ndef restart_deployment(namespace: str, deployment: str) -> None:\n    subprocess.run(\n        [\"kubectl\", \"rollout\", \"restart\", f\"deployment\u002F{deployment}\", \"-n\", namespace],\n        check=True\n    )\n    print(f\"Restarted {namespace}\u002F{deployment}\")\n\nif __name__ == \"__main__\":\n    service, namespace, deployment = sys.argv[1], sys.argv[2], sys.argv[3]\n    rate = get_error_rate(service)\n    print(f\"Error rate for {service}: {rate:.2%}\")\n    if rate > ERROR_THRESHOLD:\n        restart_deployment(namespace, deployment)\n    else:\n        print(\"Within SLO threshold — no action required\")\n```\n\n[Documentation](https:\u002F\u002Fjeffallan.github.io\u002Fclaude-skills\u002Fskills\u002Fdevops\u002Fsre-engineer\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},"specialist","implementation","https:\u002F\u002Fgithub.com\u002FJeffallan","devops","1.1.0","SRE, site reliability, SLO, SLI, error budget, incident management, chaos engineering, toil reduction, on-call, MTTR","code","devops-engineer, cloud-architect, kubernetes-specialist","main","cb7b4065bacb4b06224de86d509ccef568f68b79","claude-skills\u002Fskills\u002Fsre-engineer","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor","2026-05-29 06:53:07",{"source":8,"skillName":5,"commands":39,"prompt":49,"zipAvailable":50},[40,43,46],{"tool":41,"command":42},"npx","npx skills add andrewthomastaylor\u002FSkills --skill sre-engineer",{"tool":44,"command":45},"bunx","bunx skills add andrewthomastaylor\u002FSkills --skill sre-engineer",{"tool":47,"command":48},"pnpm","pnpm dlx skills add andrewthomastaylor\u002FSkills --skill sre-engineer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fskills\u002Fsre-engineer\u002FSKILL.md",true,[52,58,62,66,70],{"path":53,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fautomation-toil.md","REFERENCE","参考文档",14820,"https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fskills\u002Fsre-engineer\u002Freferences\u002Fautomation-toil.md",{"path":59,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Ferror-budget-policy.md",9852,"https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fskills\u002Fsre-engineer\u002Freferences\u002Ferror-budget-policy.md",{"path":63,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Fincident-chaos.md",16791,"https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fskills\u002Fsre-engineer\u002Freferences\u002Fincident-chaos.md",{"path":67,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Fmonitoring-alerting.md",11553,"https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fskills\u002Fsre-engineer\u002Freferences\u002Fmonitoring-alerting.md",{"path":71,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fslo-sli-management.md",6774,"https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fskills\u002Fsre-engineer\u002Freferences\u002Fslo-sli-management.md",[75,84,92,99,106,113],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":79,"licenseFileUrl":80,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":18},"01M732GDQJ0CWHBAW4D7ENMA3N","skill-creator","Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fskill-creator\u002Fskills\u002Fskill-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fskill-creator\u002Fskills\u002Fskill-creator\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":88,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":18},"01M731QVEE2QCT389Z3X1JWFVQ","humanizer-zh","去除文本中的 AI 生成痕迹。适用于编辑或审阅文本，使其听起来更自然、更像人类书写。\n基于维基百科的\"AI 写作特征\"综合指南。检测并修复以下模式：夸大的象征意义、\n宣传性语言、以 -ing 结尾的肤浅分析、模糊的归因、破折号过度使用、三段式法则、\nAI 词汇、否定式排比、过多的连接性短语。","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fhumanizer-zh\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fhumanizer-zh\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":79,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":18},"01M731AMWEC72GFFNFS55F0TTC","returns-reverse-logistics","Codified expertise for returns authorization, receipt and inspection, disposition decisions, refund processing, fraud detection, and warranty claims management. Informed by returns operations managers with 15+ years experience. Includes grading frameworks, disposition economics, fraud pattern recognition, and vendor recovery processes. Use when handling product returns, reverse logistics, refund decisions, return fraud detection, or warranty claims.","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Feverything-claude-code\u002Fskills\u002Freturns-reverse-logistics\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":79,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":18},"01M7319BJFM3CBX39C85QWSMD1","quality-nonconformance","Codified expertise for quality control, non-conformance investigation, root cause analysis, corrective action, and supplier quality management in regulated manufacturing. Informed by quality engineers with 15+ years experience across FDA, IATF 16949, and AS9100 environments. Includes NCR lifecycle management, CAPA systems, SPC interpretation, and audit methodology. Use when investigating non-conformances, performing root cause analysis, managing CAPAs, interpreting SPC data, or handling supplier quality issues.","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Feverything-claude-code\u002Fskills\u002Fquality-nonconformance\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":79,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":18},"01M7318DPHWK6CEVCVT7PHNKDZ","production-scheduling","Codified expertise for production scheduling, job sequencing, line balancing, changeover optimization, and bottleneck resolution in discrete and batch manufacturing. Informed by production schedulers with 15+ years experience. Includes TOC\u002Fdrum-buffer-rope, SMED, OEE analysis, disruption response frameworks, and ERP\u002FMES interaction patterns. Use when scheduling production, resolving bottlenecks, optimizing changeovers, responding to disruptions, or balancing manufacturing lines.","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Feverything-claude-code\u002Fskills\u002Fproduction-scheduling\u002FSKILL.md",[],[],{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":79,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":18},"01M7315ZE0J0AB6KTQAFGCYF5V","logistics-exception-management","Codified expertise for handling freight exceptions, shipment delays, damages, losses, and carrier disputes. Informed by logistics professionals with 15+ years operational experience. Includes escalation protocols, carrier-specific behaviors, claims procedures, and judgment frameworks. Use when handling shipping exceptions, freight claims, delivery issues, or carrier disputes.","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Feverything-claude-code\u002Fskills\u002Flogistics-exception-management\u002FSKILL.md",[],[]]