[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6HREGKM9ZYSKFAR3CEWCAJT":3,"skill-same:01M6HREGKM9ZYSKFAR3CEWCAJT":62},{"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":36,"linkOnly":37,"markdownContent":38,"markdownBody":39,"frontMatter":40,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":6,"ownerHtmlUrl":46,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":47,"install":48,"resources":61},"01M6HREGKM9ZYSKFAR3CEWCAJT","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.","welflau\u002Fai-dev-system","welflau","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F7010385?v=4","01M6HPTDGF18RFY07M229P8CTM","01M6HPTDMRMZCJPYBFEA9XVVYT",3,"MIT","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fexternal_plugins\u002Fobservability-monitoring\u002Fskills\u002Fslo-implementation\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35],"slo","implementation","slo implementation","when","performance","sre practices","implementing","with","targets","error","service","define","reliability","sre","use","indicators","alerting","implement","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","18d0e63d1313ca87098f614aa7c1e2dcf6de79c7","backend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fexternal_plugins\u002Fobservability-monitoring\u002Fskills\u002Fslo-implementation",1,"https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system","https:\u002F\u002Fgithub.com\u002Fwelflau","2026-11-12 14:55:20",{"source":8,"skillName":5,"commands":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add welflau\u002Fai-dev-system --skill slo-implementation",{"tool":54,"command":55},"bunx","bunx skills add welflau\u002Fai-dev-system --skill slo-implementation",{"tool":57,"command":58},"pnpm","pnpm dlx skills add welflau\u002Fai-dev-system --skill slo-implementation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fexternal_plugins\u002Fobservability-monitoring\u002Fskills\u002Fslo-implementation\u002FSKILL.md",true,[],[63,97,126,152,181,206],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":67,"licenseFileUrl":68,"sourceHtmlUrl":69,"categories":70,"keywords":79,"publishedAt":96},"01M6HS9Z4B0YA8CJCS2Y2F04Y3","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fexternal_plugins\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fexternal_plugins\u002Fwebapp-testing\u002FSKILL.md",[71,76],{"categoryNo":72,"categoryName":73,"taxonomyType":74,"taxonomyTypeDesc":75},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":77,"categoryName":78,"taxonomyType":74,"taxonomyTypeDesc":75},"01JBSEEDCAT000000000000009","前端开发",[80,81,82,83,84,85,86,87,88,89,90,91,92,93,94,25,95],"testing","webapp testing","webapp","frontend","screenshots","playwright","web","debugging","toolkit","browser","ui","logs","applications","behavior","local","for","2026-11-11 15:11:14",{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":67,"licenseFileUrl":101,"sourceHtmlUrl":102,"categories":103,"keywords":107,"publishedAt":96},"01M6HRAGMG7JF0HXYHMA5QHS8A","internal-comms","A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fexternal_plugins\u002Finternal-comms\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fexternal_plugins\u002Finternal-comms\u002FSKILL.md",[104],{"categoryNo":105,"categoryName":106,"taxonomyType":74,"taxonomyTypeDesc":75},"01JBSEEDCAT000000000000005","邮件与沟通",[108,109,110,111,112,113,32,114,115,116,117,118,119,120,121,122,123,124,125],"internal comms","comms","status","help","SET","write","reports","me","incident","leadership","project","resources","communications","internal communications","formats","sort","my","updates",{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":67,"licenseFileUrl":130,"sourceHtmlUrl":131,"categories":132,"keywords":134,"publishedAt":36},"01M6HSTDP4M3JFXEBK91VFB4PA","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fplugins\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fplugins\u002Fweb-artifacts-builder\u002FSKILL.md",[133],{"categoryNo":77,"categoryName":78,"taxonomyType":74,"taxonomyTypeDesc":75},[135,86,136,137,138,83,139,140,141,142,143,144,145,146,32,147,148,149,150,95,151],"web artifacts builder","artifacts","artifacts builder","builder","css","components","react","routing","state management","state","file","Tailwind","single-file","simple","ui components","multi","single",{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":67,"licenseFileUrl":156,"sourceHtmlUrl":157,"categories":158,"keywords":168,"publishedAt":36},"01M6HSDXH0JSP8R3QTNY9XZ8HN","frontend-design","Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML\u002FCSS layouts, or when styling\u002Fbeautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fplugins\u002Ffrontend-design\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fplugins\u002Ffrontend-design\u002FSKILL.md",[159,160,163],{"categoryNo":77,"categoryName":78,"taxonomyType":74,"taxonomyTypeDesc":75},{"categoryNo":161,"categoryName":162,"taxonomyType":74,"taxonomyTypeDesc":75},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":164,"categoryName":165,"taxonomyType":166,"taxonomyTypeDesc":167},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[83,169,170,139,86,140,141,171,172,173,136,174,92,175,32,176,177,178,179,25,180,21],"design","frontend design","react components","create","code","examples","landing","ui design","pages","aesthetics","web ui","generic",{"skillNo":182,"name":183,"nameZh":6,"description":184,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":67,"licenseFileUrl":185,"sourceHtmlUrl":186,"categories":187,"keywords":189,"publishedAt":36},"01M6HSA77QYVP7A72HREGTDN2C","algorithmic-art","Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fplugins\u002Falgorithmic-art\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fplugins\u002Falgorithmic-art\u002FSKILL.md",[188],{"categoryNo":161,"categoryName":162,"taxonomyType":74,"taxonomyTypeDesc":75},[190,191,192,172,173,193,194,195,196,32,197,198,199,200,25,201,202,203,204,205,21],"algorithmic art","Art","algorithmic","flow","js","work","interactive","generative art","exploration","systems","users","Existing","request","generative","copyright","fields",{"skillNo":207,"name":208,"nameZh":6,"description":209,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":67,"licenseFileUrl":210,"sourceHtmlUrl":211,"categories":212,"keywords":214,"publishedAt":36},"01M6HS9HE0X390Y6RQKTY1YNGJ","theme-factory","Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors\u002Ffonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fexternal_plugins\u002Ftheme-factory\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fexternal_plugins\u002Ftheme-factory\u002FSKILL.md",[213],{"categoryNo":161,"categoryName":162,"taxonomyType":74,"taxonomyTypeDesc":75},[215,216,217,218,88,219,136,112,220,221,175,222,223,177,224,25,225,226,227,95,228,229],"theme factory","factory","theme","docs","generate","fly","slides","styling","artifact","themes","you","fonts","can","apply","new"]