[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70NVYMWBBXYTX7ZFMCBCZSB":3,"skill-same:01M70NVYMWBBXYTX7ZFMCBCZSB":66},{"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":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":42,"commitSha":43,"skillDirectory":44,"forksCount":45,"repositoryHtmlUrl":46,"repositoryHomepageUrl":47,"ownerHtmlUrl":48,"ownerBlogUrl":49,"ownerDescription":50,"updatedAt":51,"install":52,"resources":65},"01M70NVYMWBBXYTX7ZFMCBCZSB","slo-implementation",null,"Define and implement Service Level Indicators (SLIs) and Service Level Objectives (SLOs) with error budgets and alerting. Use when establishing reliability targets, implementing SRE practices, or measuring service performance.","shengdabai\u002FTony-Claude-Code-Skills","shengdabai","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F116417419?v=4","01M70F6D2WY5PQV5A92BKYJQEW","Tony Sheng","01M70F6D3GAAAYZ5H4CC1G8VXM",3,"MIT","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fwshobson-agents\u002Fplugins\u002Fobservability-monitoring\u002Fskills\u002Fslo-implementation\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36],"slo implementation","implementation","slo","service","targets","indicators","with","implement","use","define","sre practices","alerting","when","implementing","performance","reliability","sre","error","2026-11-10 10:12:30",false,"---\nname: slo-implementation\ndescription: Define and implement Service Level Indicators (SLIs) and Service Level Objectives (SLOs) with error budgets and alerting. Use when establishing reliability targets, implementing SRE practices, or measuring service performance.\n---\n\n# SLO Implementation\n\nFramework for defining and implementing Service Level Indicators (SLIs), Service Level Objectives (SLOs), and error budgets.\n\n## Purpose\n\nImplement measurable reliability targets using SLIs, SLOs, and error budgets to balance reliability with innovation velocity.\n\n## When to Use\n\n- Define service reliability targets\n- Measure user-perceived reliability\n- Implement error budgets\n- Create SLO-based alerts\n- Track reliability goals\n\n## SLI\u002FSLO\u002FSLA Hierarchy\n\n```\nSLA (Service Level Agreement)\n  ↓ Contract with customers\nSLO (Service Level Objective)\n  ↓ Internal reliability target\nSLI (Service Level Indicator)\n  ↓ Actual measurement\n```\n\n## Defining SLIs\n\n### Common SLI Types\n\n#### 1. Availability SLI\n```promql\n# Successful requests \u002F Total requests\nsum(rate(http_requests_total{status!~\"5..\"}[28d]))\n\u002F\nsum(rate(http_requests_total[28d]))\n```\n\n#### 2. Latency SLI\n```promql\n# Requests below latency threshold \u002F Total requests\nsum(rate(http_request_duration_seconds_bucket{le=\"0.5\"}[28d]))\n\u002F\nsum(rate(http_request_duration_seconds_count[28d]))\n```\n\n#### 3. Durability SLI\n```\n# Successful writes \u002F Total writes\nsum(storage_writes_successful_total)\n\u002F\nsum(storage_writes_total)\n```\n\n**Reference:** See `references\u002Fslo-definitions.md`\n\n## Setting SLO Targets\n\n### Availability SLO Examples\n\n| SLO % | Downtime\u002FMonth | Downtime\u002FYear |\n|-------|----------------|---------------|\n| 99%   | 7.2 hours      | 3.65 days     |\n| 99.9% | 43.2 minutes   | 8.76 hours    |\n| 99.95%| 21.6 minutes   | 4.38 hours    |\n| 99.99%| 4.32 minutes   | 52.56 minutes |\n\n### Choose Appropriate SLOs\n\n**Consider:**\n- User expectations\n- Business requirements\n- Current performance\n- Cost of reliability\n- Competitor benchmarks\n\n**Example SLOs:**\n```yaml\nslos:\n  - name: api_availability\n    target: 99.9\n    window: 28d\n    sli: |\n      sum(rate(http_requests_total{status!~\"5..\"}[28d]))\n      \u002F\n      sum(rate(http_requests_total[28d]))\n\n  - name: api_latency_p95\n    target: 99\n    window: 28d\n    sli: |\n      sum(rate(http_request_duration_seconds_bucket{le=\"0.5\"}[28d]))\n      \u002F\n      sum(rate(http_request_duration_seconds_count[28d]))\n```\n\n## Error Budget Calculation\n\n### Error Budget Formula\n\n```\nError Budget = 1 - SLO Target\n```\n\n**Example:**\n- SLO: 99.9% availability\n- Error Budget: 0.1% = 43.2 minutes\u002Fmonth\n- Current Error: 0.05% = 21.6 minutes\u002Fmonth\n- Remaining Budget: 50%\n\n### Error Budget Policy\n\n```yaml\nerror_budget_policy:\n  - remaining_budget: 100%\n    action: Normal development velocity\n  - remaining_budget: 50%\n    action: Consider postponing risky changes\n  - remaining_budget: 10%\n    action: Freeze non-critical changes\n  - remaining_budget: 0%\n    action: Feature freeze, focus on reliability\n```\n\n**Reference:** See `references\u002Ferror-budget.md`\n\n## SLO Implementation\n\n### Prometheus Recording Rules\n\n```yaml\n# SLI Recording Rules\ngroups:\n  - name: sli_rules\n    interval: 30s\n    rules:\n      # Availability SLI\n      - record: sli:http_availability:ratio\n        expr: |\n          sum(rate(http_requests_total{status!~\"5..\"}[28d]))\n          \u002F\n          sum(rate(http_requests_total[28d]))\n\n      # Latency SLI (requests \u003C 500ms)\n      - record: sli:http_latency:ratio\n        expr: |\n          sum(rate(http_request_duration_seconds_bucket{le=\"0.5\"}[28d]))\n          \u002F\n          sum(rate(http_request_duration_seconds_count[28d]))\n\n  - name: slo_rules\n    interval: 5m\n    rules:\n      # SLO compliance (1 = meeting SLO, 0 = violating)\n      - record: slo:http_availability:compliance\n        expr: sli:http_availability:ratio >= bool 0.999\n\n      - record: slo:http_latency:compliance\n        expr: sli:http_latency:ratio >= bool 0.99\n\n      # Error budget remaining (percentage)\n      - record: slo:http_availability:error_budget_remaining\n        expr: |\n          (sli:http_availability:ratio - 0.999) \u002F (1 - 0.999) * 100\n\n      # Error budget burn rate\n      - record: slo:http_availability:burn_rate_5m\n        expr: |\n          (1 - (\n            sum(rate(http_requests_total{status!~\"5..\"}[5m]))\n            \u002F\n            sum(rate(http_requests_total[5m]))\n          )) \u002F (1 - 0.999)\n```\n\n### SLO Alerting Rules\n\n```yaml\ngroups:\n  - name: slo_alerts\n    interval: 1m\n    rules:\n      # Fast burn: 14.4x rate, 1 hour window\n      # Consumes 2% error budget in 1 hour\n      - alert: SLOErrorBudgetBurnFast\n        expr: |\n          slo:http_availability:burn_rate_1h > 14.4\n          and\n          slo:http_availability:burn_rate_5m > 14.4\n        for: 2m\n        labels:\n          severity: critical\n        annotations:\n          summary: \"Fast error budget burn detected\"\n          description: \"Error budget burning at {{ $value }}x rate\"\n\n      # Slow burn: 6x rate, 6 hour window\n      # Consumes 5% error budget in 6 hours\n      - alert: SLOErrorBudgetBurnSlow\n        expr: |\n          slo:http_availability:burn_rate_6h > 6\n          and\n          slo:http_availability:burn_rate_30m > 6\n        for: 15m\n        labels:\n          severity: warning\n        annotations:\n          summary: \"Slow error budget burn detected\"\n          description: \"Error budget burning at {{ $value }}x rate\"\n\n      # Error budget exhausted\n      - alert: SLOErrorBudgetExhausted\n        expr: slo:http_availability:error_budget_remaining \u003C 0\n        for: 5m\n        labels:\n          severity: critical\n        annotations:\n          summary: \"SLO error budget exhausted\"\n          description: \"Error budget remaining: {{ $value }}%\"\n```\n\n## SLO Dashboard\n\n**Grafana Dashboard Structure:**\n\n```\n┌────────────────────────────────────┐\n│ SLO Compliance (Current)           │\n│ ✓ 99.95% (Target: 99.9%)          │\n├────────────────────────────────────┤\n│ Error Budget Remaining: 65%        │\n│ ████████░░ 65%                     │\n├────────────────────────────────────┤\n│ SLI Trend (28 days)                │\n│ [Time series graph]                │\n├────────────────────────────────────┤\n│ Burn Rate Analysis                 │\n│ [Burn rate by time window]         │\n└────────────────────────────────────┘\n```\n\n**Example Queries:**\n\n```promql\n# Current SLO compliance\nsli:http_availability:ratio * 100\n\n# Error budget remaining\nslo:http_availability:error_budget_remaining\n\n# Days until error budget exhausted (at current burn rate)\n(slo:http_availability:error_budget_remaining \u002F 100)\n*\n28\n\u002F\n(1 - sli:http_availability:ratio) * (1 - 0.999)\n```\n\n## Multi-Window Burn Rate Alerts\n\n```yaml\n# Combination of short and long windows reduces false positives\nrules:\n  - alert: SLOBurnRateHigh\n    expr: |\n      (\n        slo:http_availability:burn_rate_1h > 14.4\n        and\n        slo:http_availability:burn_rate_5m > 14.4\n      )\n      or\n      (\n        slo:http_availability:burn_rate_6h > 6\n        and\n        slo:http_availability:burn_rate_30m > 6\n      )\n    labels:\n      severity: critical\n```\n\n## SLO Review Process\n\n### Weekly Review\n- Current SLO compliance\n- Error budget status\n- Trend analysis\n- Incident impact\n\n### Monthly Review\n- SLO achievement\n- Error budget usage\n- Incident postmortems\n- SLO adjustments\n\n### Quarterly Review\n- SLO relevance\n- Target adjustments\n- Process improvements\n- Tooling enhancements\n\n## Best Practices\n\n1. **Start with user-facing services**\n2. **Use multiple SLIs** (availability, latency, etc.)\n3. **Set achievable SLOs** (don't aim for 100%)\n4. **Implement multi-window alerts** to reduce noise\n5. **Track error budget** consistently\n6. **Review SLOs regularly**\n7. **Document SLO decisions**\n8. **Align with business goals**\n9. **Automate SLO reporting**\n10. **Use SLOs for prioritization**\n\n## Reference Files\n\n- `assets\u002Fslo-template.md` - SLO definition template\n- `references\u002Fslo-definitions.md` - SLO definition patterns\n- `references\u002Ferror-budget.md` - Error budget calculations\n\n## Related Skills\n\n- `prometheus-configuration` - For metric collection\n- `grafana-dashboards` - For SLO visualization\n","# SLO Implementation\n\nFramework for defining and implementing Service Level Indicators (SLIs), Service Level Objectives (SLOs), and error budgets.\n\n## Purpose\n\nImplement measurable reliability targets using SLIs, SLOs, and error budgets to balance reliability with innovation velocity.\n\n## When to Use\n\n- Define service reliability targets\n- Measure user-perceived reliability\n- Implement error budgets\n- Create SLO-based alerts\n- Track reliability goals\n\n## SLI\u002FSLO\u002FSLA Hierarchy\n\n```\nSLA (Service Level Agreement)\n  ↓ Contract with customers\nSLO (Service Level Objective)\n  ↓ Internal reliability target\nSLI (Service Level Indicator)\n  ↓ Actual measurement\n```\n\n## Defining SLIs\n\n### Common SLI Types\n\n#### 1. Availability SLI\n```promql\n# Successful requests \u002F Total requests\nsum(rate(http_requests_total{status!~\"5..\"}[28d]))\n\u002F\nsum(rate(http_requests_total[28d]))\n```\n\n#### 2. Latency SLI\n```promql\n# Requests below latency threshold \u002F Total requests\nsum(rate(http_request_duration_seconds_bucket{le=\"0.5\"}[28d]))\n\u002F\nsum(rate(http_request_duration_seconds_count[28d]))\n```\n\n#### 3. Durability SLI\n```\n# Successful writes \u002F Total writes\nsum(storage_writes_successful_total)\n\u002F\nsum(storage_writes_total)\n```\n\n**Reference:** See `references\u002Fslo-definitions.md`\n\n## Setting SLO Targets\n\n### Availability SLO Examples\n\n| SLO % | Downtime\u002FMonth | Downtime\u002FYear |\n|-------|----------------|---------------|\n| 99%   | 7.2 hours      | 3.65 days     |\n| 99.9% | 43.2 minutes   | 8.76 hours    |\n| 99.95%| 21.6 minutes   | 4.38 hours    |\n| 99.99%| 4.32 minutes   | 52.56 minutes |\n\n### Choose Appropriate SLOs\n\n**Consider:**\n- User expectations\n- Business requirements\n- Current performance\n- Cost of reliability\n- Competitor benchmarks\n\n**Example SLOs:**\n```yaml\nslos:\n  - name: api_availability\n    target: 99.9\n    window: 28d\n    sli: |\n      sum(rate(http_requests_total{status!~\"5..\"}[28d]))\n      \u002F\n      sum(rate(http_requests_total[28d]))\n\n  - name: api_latency_p95\n    target: 99\n    window: 28d\n    sli: |\n      sum(rate(http_request_duration_seconds_bucket{le=\"0.5\"}[28d]))\n      \u002F\n      sum(rate(http_request_duration_seconds_count[28d]))\n```\n\n## Error Budget Calculation\n\n### Error Budget Formula\n\n```\nError Budget = 1 - SLO Target\n```\n\n**Example:**\n- SLO: 99.9% availability\n- Error Budget: 0.1% = 43.2 minutes\u002Fmonth\n- Current Error: 0.05% = 21.6 minutes\u002Fmonth\n- Remaining Budget: 50%\n\n### Error Budget Policy\n\n```yaml\nerror_budget_policy:\n  - remaining_budget: 100%\n    action: Normal development velocity\n  - remaining_budget: 50%\n    action: Consider postponing risky changes\n  - remaining_budget: 10%\n    action: Freeze non-critical changes\n  - remaining_budget: 0%\n    action: Feature freeze, focus on reliability\n```\n\n**Reference:** See `references\u002Ferror-budget.md`\n\n## SLO Implementation\n\n### Prometheus Recording Rules\n\n```yaml\n# SLI Recording Rules\ngroups:\n  - name: sli_rules\n    interval: 30s\n    rules:\n      # Availability SLI\n      - record: sli:http_availability:ratio\n        expr: |\n          sum(rate(http_requests_total{status!~\"5..\"}[28d]))\n          \u002F\n          sum(rate(http_requests_total[28d]))\n\n      # Latency SLI (requests \u003C 500ms)\n      - record: sli:http_latency:ratio\n        expr: |\n          sum(rate(http_request_duration_seconds_bucket{le=\"0.5\"}[28d]))\n          \u002F\n          sum(rate(http_request_duration_seconds_count[28d]))\n\n  - name: slo_rules\n    interval: 5m\n    rules:\n      # SLO compliance (1 = meeting SLO, 0 = violating)\n      - record: slo:http_availability:compliance\n        expr: sli:http_availability:ratio >= bool 0.999\n\n      - record: slo:http_latency:compliance\n        expr: sli:http_latency:ratio >= bool 0.99\n\n      # Error budget remaining (percentage)\n      - record: slo:http_availability:error_budget_remaining\n        expr: |\n          (sli:http_availability:ratio - 0.999) \u002F (1 - 0.999) * 100\n\n      # Error budget burn rate\n      - record: slo:http_availability:burn_rate_5m\n        expr: |\n          (1 - (\n            sum(rate(http_requests_total{status!~\"5..\"}[5m]))\n            \u002F\n            sum(rate(http_requests_total[5m]))\n          )) \u002F (1 - 0.999)\n```\n\n### SLO Alerting Rules\n\n```yaml\ngroups:\n  - name: slo_alerts\n    interval: 1m\n    rules:\n      # Fast burn: 14.4x rate, 1 hour window\n      # Consumes 2% error budget in 1 hour\n      - alert: SLOErrorBudgetBurnFast\n        expr: |\n          slo:http_availability:burn_rate_1h > 14.4\n          and\n          slo:http_availability:burn_rate_5m > 14.4\n        for: 2m\n        labels:\n          severity: critical\n        annotations:\n          summary: \"Fast error budget burn detected\"\n          description: \"Error budget burning at {{ $value }}x rate\"\n\n      # Slow burn: 6x rate, 6 hour window\n      # Consumes 5% error budget in 6 hours\n      - alert: SLOErrorBudgetBurnSlow\n        expr: |\n          slo:http_availability:burn_rate_6h > 6\n          and\n          slo:http_availability:burn_rate_30m > 6\n        for: 15m\n        labels:\n          severity: warning\n        annotations:\n          summary: \"Slow error budget burn detected\"\n          description: \"Error budget burning at {{ $value }}x rate\"\n\n      # Error budget exhausted\n      - alert: SLOErrorBudgetExhausted\n        expr: slo:http_availability:error_budget_remaining \u003C 0\n        for: 5m\n        labels:\n          severity: critical\n        annotations:\n          summary: \"SLO error budget exhausted\"\n          description: \"Error budget remaining: {{ $value }}%\"\n```\n\n## SLO Dashboard\n\n**Grafana Dashboard Structure:**\n\n```\n┌────────────────────────────────────┐\n│ SLO Compliance (Current)           │\n│ ✓ 99.95% (Target: 99.9%)          │\n├────────────────────────────────────┤\n│ Error Budget Remaining: 65%        │\n│ ████████░░ 65%                     │\n├────────────────────────────────────┤\n│ SLI Trend (28 days)                │\n│ [Time series graph]                │\n├────────────────────────────────────┤\n│ Burn Rate Analysis                 │\n│ [Burn rate by time window]         │\n└────────────────────────────────────┘\n```\n\n**Example Queries:**\n\n```promql\n# Current SLO compliance\nsli:http_availability:ratio * 100\n\n# Error budget remaining\nslo:http_availability:error_budget_remaining\n\n# Days until error budget exhausted (at current burn rate)\n(slo:http_availability:error_budget_remaining \u002F 100)\n*\n28\n\u002F\n(1 - sli:http_availability:ratio) * (1 - 0.999)\n```\n\n## Multi-Window Burn Rate Alerts\n\n```yaml\n# Combination of short and long windows reduces false positives\nrules:\n  - alert: SLOBurnRateHigh\n    expr: |\n      (\n        slo:http_availability:burn_rate_1h > 14.4\n        and\n        slo:http_availability:burn_rate_5m > 14.4\n      )\n      or\n      (\n        slo:http_availability:burn_rate_6h > 6\n        and\n        slo:http_availability:burn_rate_30m > 6\n      )\n    labels:\n      severity: critical\n```\n\n## SLO Review Process\n\n### Weekly Review\n- Current SLO compliance\n- Error budget status\n- Trend analysis\n- Incident impact\n\n### Monthly Review\n- SLO achievement\n- Error budget usage\n- Incident postmortems\n- SLO adjustments\n\n### Quarterly Review\n- SLO relevance\n- Target adjustments\n- Process improvements\n- Tooling enhancements\n\n## Best Practices\n\n1. **Start with user-facing services**\n2. **Use multiple SLIs** (availability, latency, etc.)\n3. **Set achievable SLOs** (don't aim for 100%)\n4. **Implement multi-window alerts** to reduce noise\n5. **Track error budget** consistently\n6. **Review SLOs regularly**\n7. **Document SLO decisions**\n8. **Align with business goals**\n9. **Automate SLO reporting**\n10. **Use SLOs for prioritization**\n\n## Reference Files\n\n- `assets\u002Fslo-template.md` - SLO definition template\n- `references\u002Fslo-definitions.md` - SLO definition patterns\n- `references\u002Ferror-budget.md` - Error budget calculations\n\n## Related Skills\n\n- `prometheus-configuration` - For metric collection\n- `grafana-dashboards` - For SLO visualization\n",{"name":5,"description":7},"main","7850740bd837adb32f0a109ab2af82482196c6f2","skills\u002Fwshobson-agents\u002Fplugins\u002Fobservability-monitoring\u002Fskills\u002Fslo-implementation",1,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills","https:\u002F\u002Fzturnsgo.com","https:\u002F\u002Fgithub.com\u002Fshengdabai","https:\u002F\u002Fzturnsgo.com\u002F","AI × education creator — producer, not consumer. Taught 6,000+ learners; shipping learning tools & daily essays with Claude Code, practicing @xiaolai's way 🥋","2026-11-01 21:28:23",{"source":8,"skillName":5,"commands":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add shengdabai\u002FTony-Claude-Code-Skills --skill slo-implementation",{"tool":58,"command":59},"bunx","bunx skills add shengdabai\u002FTony-Claude-Code-Skills --skill slo-implementation",{"tool":61,"command":62},"pnpm","pnpm dlx skills add shengdabai\u002FTony-Claude-Code-Skills --skill slo-implementation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fwshobson-agents\u002Fplugins\u002Fobservability-monitoring\u002Fskills\u002Fslo-implementation\u002FSKILL.md",true,[],[67,86,120,145,167,187],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":78,"publishedAt":37},"01M70P17DAD4C1C47NPH6A96EM","xiaolai-methodology","以李笑来(Li Xiaolai)的思考方式、方法论与表达风格,为用户做全方位 1-on-1 教练指导,覆盖创业、赚钱、投资、学习、自学、读书写作、用 AI、以及人生心态与自我管理。当用户提到 \"李笑来\"、\"笑来\"、\"笑来老师\"、\"扮演李笑来\"、\"找笑来聊聊\"、\"笑来怎么看\"、\"xiaolai\"、\"把时间当作朋友\"、\"通往财富自由之路\"、\"定投改变命运\"、\"韭菜的自我修养\"、\"自学是门手艺\"、\"让时间陪你慢慢变富\"、\"七年就是一辈子\"、\"元认知\"、\"活在未来\"、\"复利\u002F长期主义\"、\"践行\"、\"痴迷改进\"、\"个人商业模式\u002F出售时间\"、\"睡后收入\"、\"定投\"、\"财富自由\"、\"操作系统升级\"、\"最少必要知识\"、\"北极星提示词\"、\"用 AI 该怎么学\u002F思考\" 等任一触发词,或当用户带着关于创业\u002F赚钱\u002F投资\u002F学习\u002F职业\u002F重大人生决策的困惑、希望被人用笑来式的「逻辑 + 大白话 + 类比 + 重新定义 + 践行导向」来点醒和指导时,自动进入李笑来教练模式。","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fxiaolai-methodology\u002FSKILL.md",[73],{"categoryNo":74,"categoryName":75,"taxonomyType":76,"taxonomyTypeDesc":77},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",[79,80,81,82,83,84,85],"methodology","xiaolai","xiaolai methodology","朋友","投资","writing","收入",{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":100,"publishedAt":37},"01M70P13NB9YP7ACJR1S861CDS","zread","Produce and consume a wiki-style knowledge base for a code repository via the `zread` CLI and its on-disk output under `.\u002F.zread\u002Fwiki\u002F`. Use this skill whenever the user wants to understand, onboard onto, explore, summarize, map, or get an overview of an unfamiliar codebase; asks for architecture docs, a project wiki, a repo walkthrough, module\u002Fpackage explanations, or \"what does this repo do\"; wants to generate, regenerate, resume, browse, or serve code documentation locally; or mentions zread \u002F zread.ai directly. Also use it proactively before diving into a large unknown repo — if `.\u002F.zread\u002Fwiki\u002Fcurrent` exists, read the generated pages instead of crawling source file-by-file; if it doesn't, consider offering to run `zread generate`. The trigger is the intent (understand a codebase through generated docs), not the literal word \"zread\".","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fzread\u002FSKILL.md",[92,95],{"categoryNo":93,"categoryName":94,"taxonomyType":76,"taxonomyTypeDesc":77},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":96,"categoryName":97,"taxonomyType":98,"taxonomyTypeDesc":99},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[88,101,102,103,104,105,106,107,108,109,110,111,112,113,114,115,116,117,118,119],"knowledge","wiki","explore","walkthrough","project","get","knowledge base","run","generate","intent","cli","map","documentation","project wiki","disk","architecture","code","unknown","generated",{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":130,"publishedAt":37},"01M70P10S4SWMZQ8BJAFBFDRW3","youtube","Launch the YouTube Creator Agent to auto-generate videos.\nUse when: user types \u002Fyoutube, wants to create YouTube videos,\ngenerate video content, or upload to YouTube.\nKeywords: youtube, video, 视频, 创作视频, 发布视频","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube\u002FSKILL.md",[126,127],{"categoryNo":93,"categoryName":94,"taxonomyType":76,"taxonomyTypeDesc":77},{"categoryNo":128,"categoryName":129,"taxonomyType":98,"taxonomyTypeDesc":99},"01JBSEEDCAT000000000000036","内容创作者",[122,131,132,133,134,135,136,137,109,138,139,140,31,27,141,142,143,144],"user","content","视频","creator","generate video","videos","launch","video content","create","upload","auto","types","Video","创作",{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":152,"publishedAt":37},"01M70P0YE95D8BACZCGV8BK90K","youtube-script-sync","Sync, update, or optimize Tony's GetNote knowledge base `Youtube视频逐字稿` by turning each parent recording or first-person idea note into an idempotent child note containing a directly recordable YouTube long-video or Shorts script. Use when the user says “更新\u002F同步\u002F优化 Youtube视频逐字稿知识库”, or says “更新\u002F同步\u002F优化该知识库” while this knowledge base is the active context.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube-script-sync\u002FSKILL.md",[151],{"categoryNo":93,"categoryName":94,"taxonomyType":76,"taxonomyTypeDesc":77},[153,154,122,155,156,143,157,158,159,160,161,162,163,164,107,165,31,27,101,166],"sync","script","youtube script sync","recording","shorts","first","base","person","update","active","child","optimize","idempotent","long",{"skillNo":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":171,"categories":172,"keywords":177,"publishedAt":37},"01M70P0WMV5XT0EEC0N445PW07","writing-skills","How to write SKILL.md files that trigger reliably and teach effectively. Use when creating, improving, or reviewing Claude Code skills.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fxiaolai\u002Fnlpm\u002Fskills\u002Fnlpm\u002Fwriting-skills\u002FSKILL.md",[173,174,175,176],{"categoryNo":74,"categoryName":75,"taxonomyType":76,"taxonomyTypeDesc":77},{"categoryNo":93,"categoryName":94,"taxonomyType":76,"taxonomyTypeDesc":77},{"categoryNo":96,"categoryName":97,"taxonomyType":98,"taxonomyTypeDesc":99},{"categoryNo":128,"categoryName":129,"taxonomyType":98,"taxonomyTypeDesc":99},[178,84,179,180,181,182,117,31,27,183,184,185,186],"writing skills","how","teach","write skill","write","claude code skills","files","how to","trigger",{"skillNo":188,"name":189,"nameZh":6,"description":190,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":191,"categories":192,"keywords":195,"publishedAt":37},"01M70P0SJFR4YVJQBGMHKGSKXT","writing-rules","How to write .claude\u002Frules\u002F files that Claude actually follows. Use when creating, improving, or reviewing project rules.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fxiaolai\u002Fnlpm\u002Fskills\u002Fnlpm\u002Fwriting-rules\u002FSKILL.md",[193,194],{"categoryNo":74,"categoryName":75,"taxonomyType":76,"taxonomyTypeDesc":77},{"categoryNo":128,"categoryName":129,"taxonomyType":98,"taxonomyTypeDesc":99},[196,84,197,105,198,184,31,179,182,27,185],"Rules","writing rules","project rules"]