[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CDVT5QG2SP07E710APQH4E":3,"skill-same:01M7CDVT5QG2SP07E710APQH4E":50},{"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":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":32,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M7CDVT5QG2SP07E710APQH4E","slo-implementation",null,"Framework for defining and implementing Service Level Indicators (SLIs), Service Level Objectives (SLOs), and error budgets.","YYC-Cube\u002FYYC3-Knowledge-Base","YYC-Cube","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F235006543?v=4","01M79J2PH4SWD2X0825X6PN748","yyc3","01M79J2PHVK3F6ZBYT8K2SCZCW",1,"MIT","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-awesome-skills\u002Fskills\u002Fslo-implementation\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: slo-implementation\ndescription: \"Framework for defining and implementing Service Level Indicators (SLIs), Service Level Objectives (SLOs), and error budgets.\"\nrisk: unknown\nsource: community\ndate_added: \"2026-02-27\"\n---\n\n# SLO Implementation\n\nFramework for defining and implementing Service Level Indicators (SLIs), Service Level Objectives (SLOs), and error budgets.\n\n## Do not use this skill when\n\n- The task is unrelated to slo implementation\n- You need a different domain or tool outside this scope\n\n## Instructions\n\n- Clarify goals, constraints, and required inputs.\n- Apply relevant best practices and validate outcomes.\n- Provide actionable steps and verification.\n- If detailed examples are required, open `resources\u002Fimplementation-playbook.md`.\n\n## Purpose\n\nImplement measurable reliability targets using SLIs, SLOs, and error budgets to balance reliability with innovation velocity.\n\n## Use this skill when\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\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n","# SLO Implementation\n\nFramework for defining and implementing Service Level Indicators (SLIs), Service Level Objectives (SLOs), and error budgets.\n\n## Do not use this skill when\n\n- The task is unrelated to slo implementation\n- You need a different domain or tool outside this scope\n\n## Instructions\n\n- Clarify goals, constraints, and required inputs.\n- Apply relevant best practices and validate outcomes.\n- Provide actionable steps and verification.\n- If detailed examples are required, open `resources\u002Fimplementation-playbook.md`.\n\n## Purpose\n\nImplement measurable reliability targets using SLIs, SLOs, and error budgets to balance reliability with innovation velocity.\n\n## Use this skill when\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\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n",{"name":5,"risk":24,"source":25,"date_added":26,"description":7},"unknown","community","2026-02-27","main","87afe6ce96220accf50a345dea46784c8c9f210e","YYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-awesome-skills\u002Fskills\u002Fslo-implementation",0,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base","https:\u002F\u002Fkb.yyc3.top\u002F","https:\u002F\u002Fgithub.com\u002FYYC-Cube","万象归元于云枢 | 深栈智启新纪元","2026-11-10 10:37:32",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill slo-implementation",{"tool":42,"command":43},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill slo-implementation",{"tool":45,"command":46},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill slo-implementation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-awesome-skills\u002Fskills\u002Fslo-implementation\u002FSKILL.md",true,[],[51,58,65,72,79,86],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M7CTDWHERCXPQCP0K03A86AS","vercel-sandbox","Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include \"Vercel Sandbox browser\", \"microVM Chrome\", \"agent-browser in sandbox\", \"browser automation on Vercel\", or any task requiring Chrome in a Vercel Sandbox.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fvercel-sandbox\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7CTD8D2BNJY54S65M47HEJA","slack","Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include \"check my Slack\", \"what channels have unreads\", \"send a message to\", \"search Slack for\", \"extract from Slack\", \"find who said\", or any task requiring programmatic Slack interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fslack\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7CTCSSB8ZP3Q58C3YZDZK1W","electron","Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include \"automate Slack app\", \"control VS Code\", \"interact with Discord app\", \"test this Electron app\", \"connect to desktop app\", or any task requiring automation of a native Electron application.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Felectron\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7CTCBJY76688V4DCZGWFHGQ","dogfood","Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to \"dogfood\", \"QA\", \"exploratory test\", \"find issues\", \"bug hunt\", \"test this app\u002Fsite\u002Fplatform\", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fdogfood\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7CTC4H0FFGVEAQR9PA4GA1A","agent-browser","Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to \"open a website\", \"fill out a form\", \"click a button\", \"take a screenshot\", \"scrape data from a page\", \"test this web app\", \"login to a site\", \"automate browser actions\", or any task requiring programmatic web interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fagent-browser\u002FSKILL.md",[],[],{"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":92,"publishedAt":19},"01M7CTBKVFYBG78FDSABSDJTTQ","shadcn","Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn\u002Fui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for \"shadcn init\", \"create an app with --preset\", \"switch to --preset\", and for building a design system or applying a DESIGN.md or brand spec to shadcn\u002Fui.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-UI-界面组件\u002FYYC3-UI-界面组件-ui\u002Fskills\u002Fshadcn\u002FSKILL.md",[],[]]