[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DP48ZR9BQF4MGKDY3F99FA":3,"skill-same:01M7DP48ZR9BQF4MGKDY3F99FA":107},{"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":44,"commitSha":45,"skillDirectory":46,"forksCount":14,"repositoryHtmlUrl":47,"repositoryHomepageUrl":6,"ownerHtmlUrl":48,"ownerBlogUrl":6,"ownerDescription":49,"updatedAt":50,"install":51,"resources":64},"01M7DP48ZR9BQF4MGKDY3F99FA","slo-architect",null,"Use when defining, reviewing, or operating SLOs\u002FSLIs\u002Ferror budgets. Triggers on \"define an SLO\", \"what should our SLO be\", \"error budget\", \"burn rate\", \"SLI\", \"service level objective\", \"Google SRE workbook\", \"multi-window burn-rate alert\", or any reliability-target question. Ships SLO designer, error-budget calculator with multi-window burn-rate thresholds, and SLO reviewer that catches the common bugs (target too aggressive, window too short, conflicting SLOs, no SLI definition). 4 references on SLO principles + SLI design + error budget math + composition with feature-flags-architect\u002Fchaos-engineering\u002Fkubernetes-operator. NOT a generic observability skill — specifically the SLO discipline.","Prudhviraj101\u002FX_Agent","Prudhviraj101","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F141725940?v=4","01M7DN1Y3RW3QD7692M89MPS3D","MALLA PRUDHVI RAJ S S N MURTHY","01M7DN1Y4A763ESFP16P13EE19",0,"MIT","https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Falirezarezvani\u002Fengineering__slo-architect\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: slo-architect\ndescription: Use when defining, reviewing, or operating SLOs\u002FSLIs\u002Ferror budgets. Triggers on \"define an SLO\", \"what should our SLO be\", \"error budget\", \"burn rate\", \"SLI\", \"service level objective\", \"Google SRE workbook\", \"multi-window burn-rate alert\", or any reliability-target question. Ships SLO designer, error-budget calculator with multi-window burn-rate thresholds, and SLO reviewer that catches the common bugs (target too aggressive, window too short, conflicting SLOs, no SLI definition). 4 references on SLO principles + SLI design + error budget math + composition with feature-flags-architect\u002Fchaos-engineering\u002Fkubernetes-operator. NOT a generic observability skill — specifically the SLO discipline.\ncontext: fork\nversion: 2.9.0\nauthor: claude-code-skills\nlicense: MIT\ntags: [slo, sli, sla, error-budget, burn-rate, sre, reliability, google-sre-workbook, observability]\ncompatible_tools: [claude-code, codex-cli, cursor, antigravity, opencode, gemini-cli]\n---\n\n# SLO Architect\n\nDefine SLOs that mean something. Most \"SLOs\" in the wild are arbitrary numbers no one believes — 99.9% on every endpoint, no SLI definition, no error budget, no policy for what happens when budget burns. This skill enforces the discipline from Google's SRE Workbook: pick the right SLI, set a target users actually care about, calculate the error budget, wire multi-window burn-rate alerts, and have a written policy for when budget runs out.\n\n## When to use\n\n- Defining a new SLO for a service or feature\n- Reviewing existing SLOs for common bugs\n- Picking the right SLI (event-based vs time-window based vs request-based)\n- Computing error budgets and burn-rate alert thresholds\n- Tying SLOs to existing controls — feature flags abort, chaos blast radius, operator capability levels\n\n## When NOT to use\n\n- General observability strategy (metrics + logs + traces) → use `observability-designer`\n- Customer-facing SLAs with legal teeth → that's contract drafting, not engineering\n- Performance load testing (capacity, not reliability) → use `performance-profiler`\n- Active incident response → use `incident-response`\n\n## Core principle: an SLO is a promise about user experience\n\n```\nSLI  ⟶  measurable signal of user-perceived health (e.g., HTTP 2xx rate)\nSLO  ⟶  target for the SLI over a window (e.g., 99.9% over 30 days)\nSLA  ⟶  customer-facing commitment with consequences (separate concern)\nEB   ⟶  error budget: 100% − SLO target = how much \"bad\" you can spend\nBR   ⟶  burn rate: how fast you're consuming the error budget\n```\n\nThe four cardinal mistakes:\n\n1. **Target too high** (99.99%+ on services that can't support it) — every minor blip violates SLO; alerts become noise.\n2. **Wrong SLI** (CPU usage as proxy for user experience) — system can be \"green\" while users suffer.\n3. **No error budget policy** — burning budget means nothing if there's no agreed action.\n4. **Single-window burn-rate alert** — either too noisy (page on a 5-min spike) or too slow (notice budget exhausted after the fact).\n\nThe 3 tools below catch each of these.\n\n## Quick start\n\n```bash\nSKILL=engineering\u002Fslo-architect\u002Fskills\u002Fslo-architect\n\n# 1. Design an SLO\npython \"$SKILL\u002Fscripts\u002Fslo_designer.py\" \\\n  --service checkout-svc \\\n  --sli-type request-success-rate \\\n  --target 99.9 \\\n  --window-days 30\n\n# 2. Compute error budget + multi-window burn-rate alerts\npython \"$SKILL\u002Fscripts\u002Ferror_budget_calculator.py\" \\\n  --target 99.9 --window-days 30\n\n# 3. Review existing SLO definitions for common bugs\npython \"$SKILL\u002Fscripts\u002Fslo_review.py\" --slo-doc docs\u002Fslos\u002F\n```\n\n## The 3 Python tools\n\nAll stdlib-only.\n\n### `slo_designer.py`\n\nGenerates a structured SLO definition with required fields. Refuses to render if any required field is missing (`exit 1`).\n\n```bash\npython scripts\u002Fslo_designer.py \\\n  --service checkout-svc \\\n  --sli-type request-success-rate \\\n  --target 99.9 \\\n  --window-days 30 \\\n  --owner team-checkout\n```\n\n**SLI types supported:**\n- `request-success-rate` — `(total_requests - bad_requests) \u002F total_requests`\n- `request-latency` — `count(requests \u003C threshold) \u002F total_requests`\n- `availability-time` — `(window - downtime) \u002F window`\n- `data-freshness` — `count(data_age \u003C threshold) \u002F total_data_points`\n- `correctness` — `count(correct_outputs) \u002F total_outputs`\n\nOutput is markdown by default with all required fields filled or marked `\u003Cmust define>`. JSON output (`--format json`) is consumed by `slo_review.py`.\n\n### `error_budget_calculator.py`\n\nGiven target availability + window, computes:\n- Allowed downtime in the window\n- Multi-window burn-rate thresholds per Google SRE Workbook (Chapter 5):\n  - **Fast burn** — page if 2% of monthly budget consumed in 1 hour\n  - **Slow burn** — page if 10% consumed in 6 hours, ticket if 10% in 3 days\n- Recommended alerting rules (PromQL-shaped output)\n\n```bash\npython scripts\u002Ferror_budget_calculator.py --target 99.9 --window-days 30\npython scripts\u002Ferror_budget_calculator.py --target 99.95 --window-days 7 --format json\n```\n\n### `slo_review.py`\n\nAudits a directory of SLO definitions (markdown or JSON) for the common bugs.\n\n```bash\npython scripts\u002Fslo_review.py --slo-doc docs\u002Fslos\u002F\n```\n\n**Checks:**\n- `target_too_high`: target ≥ 99.99% (sustainable only with massive engineering investment)\n- `target_too_low`: target ≤ 99.0% (probably wrong SLI; users will notice)\n- `window_too_short`: window \u003C 7 days (statistical noise dominates)\n- `window_too_long`: window > 90 days (slow feedback)\n- `no_sli_definition`: SLI section missing or vague (\"everything OK\")\n- `no_error_budget_policy`: no documented action when budget burns\n- `cpu_as_sli`: CPU\u002Fmemory used as user-experience proxy (wrong signal)\n\n## SLI selection cheatsheet\n\n| User experience | SLI type | What you measure |\n|---|---|---|\n| \"Did the request succeed?\" | request-success-rate | `2xx \u002F total` |\n| \"Was the response fast?\" | request-latency | `count(p99 \u003C threshold) \u002F total` |\n| \"Was the service up?\" | availability-time | `(window - downtime) \u002F window` |\n| \"Is the data current?\" | data-freshness | `count(data_age \u003C threshold) \u002F total` |\n| \"Was the answer correct?\" | correctness | `count(correct) \u002F total` |\n\nSee `references\u002Fsli_design.md` for examples and anti-patterns.\n\n## Error budget math (the basics)\n\nFor 99.9% SLO over 30 days:\n- Allowed unavailability: `0.1% × 30 × 24 × 60 = 43.2 minutes`\n- 1-hour fast-burn threshold (2% of monthly budget burned): `2% × 43.2 \u002F 60 ≈ 1.44 ratio multiplier`\n- 6-hour slow-burn threshold (10% in 6h): `10% × 43.2 \u002F 360 ≈ 0.6 ratio multiplier`\n\n`error_budget_calculator.py` does this math for you and emits ready-to-paste alert rules.\n\n## Composition with the rest of the portfolio\n\nThis skill explicitly composes with three others:\n\n| Skill | Composition |\n|---|---|\n| `feature-flags-architect` | Rollout abort criteria reference SLO burn-rate thresholds |\n| `chaos-engineering` | Blast-radius calculator already takes monthly error budget as input — define it here |\n| `kubernetes-operator` | Operator capability L4 (Deep Insights) requires SLOs + Prometheus rules |\n\nThe `error_budget_calculator.py` output is in the same shape `engineering\u002Fskills\u002Fchaos-engineering\u002Fscripts\u002Fblast_radius_calculator.py` expects on stdin.\n\n## Workflows\n\n### Workflow 1: Define a new SLO\n\n```\n1. Pick the user journey to protect (e.g., \"checkout completion\").\n2. Choose SLI type (request-success-rate, latency, availability, freshness, correctness).\n3. Define the SLI precisely: numerator\u002Fdenominator with concrete labels.\n4. Pick a target by measuring 30 days of historical SLI value:\n     target = floor(p50 of last 30 days × 100) \u002F 100\n   This avoids targets the system has never sustained.\n5. Pick a window (28 days = 4 calendar weeks, recommended).\n6. Run slo_designer.py to render the SLO definition.\n7. Run error_budget_calculator.py to get burn-rate alerts.\n8. Write the error budget policy (what happens when budget burns).\n9. Run slo_review.py — must pass before the SLO is \"live\".\n```\n\n### Workflow 2: Quarterly SLO review\n\n```\n1. For every active SLO, run slo_review.py — fix any FAIL findings.\n2. Look at last quarter's data:\n   - Was the SLO too easy (never burned budget)? Tighten target.\n   - Was it too hard (frequently burned)? Loosen target OR fix the system.\n   - Did burn-rate alerts fire usefully (not too noisy, not too late)? Adjust thresholds.\n3. Audit error budget policies — were they actually followed when budget burned?\n4. Commit revised SLOs; archive old versions with date stamps.\n```\n\n### Workflow 3: SLO-driven rollback\n\n```\n1. New deploy starts burning error budget faster than baseline.\n2. Burn-rate alert fires (from error_budget_calculator.py thresholds).\n3. Auto-rollback via feature flag (kill switch from feature-flags-architect).\n4. Postmortem feeds into next SLO revision.\n```\n\n## References\n\n- `references\u002Fslo_principles.md` — SLI vs SLO vs SLA, Google SRE Workbook canon\n- `references\u002Fsli_design.md` — picking the right SLI; 5 types with examples\n- `references\u002Ferror_budget.md` — error budget math, burn-rate alerts, budget policy\n- `references\u002Fcomposition.md` — how SLOs feed feature flags, chaos, operators\n\n## Slash command\n\n`\u002Fslo-design` — interactive SLO design wizard that runs all 3 tools.\n\n## Asset templates\n\n- `assets\u002Fslo_template.yaml` — fillable SLO YAML\n- `assets\u002Ferror_budget_policy.md` — fillable policy template\n\n## Anti-patterns\n\n- **99.99% on every endpoint** — copy-paste SLOs that nobody verified the system can sustain\n- **CPU usage as SLI** — system metrics aren't user experience\n- **Single-window burn-rate alert** — too noisy if 5-min, too slow if 30-day\n- **No error budget policy** — burning budget means nothing without an action\n- **SLOs without owners** — no one is responsible; they bit-rot\n- **SLOs reviewed once a year** — system characteristics change faster than that\n- **SLAs in the SLO doc** — different audience, different stakes; keep them separate\n- **SLO target = SLA target** — SLO must be tighter (you should beat your contract before customers notice)\n\n## Verifiable success\n\nA team using this skill should achieve:\n\n- 100% of SLOs pass `slo_review.py` with 0 FAIL findings\n- Every SLO has a documented owner, error budget, burn-rate alerts, and policy\n- Burn-rate alerts fire ≤2 times\u002Fmonth per SLO that's hit (signal, not noise)\n- Mean time to detect SLO violation: \u003C30 min (multi-window burn-rate alerts working)\n- Quarterly SLO review happens every quarter (not annually)\n","# SLO Architect\n\nDefine SLOs that mean something. Most \"SLOs\" in the wild are arbitrary numbers no one believes — 99.9% on every endpoint, no SLI definition, no error budget, no policy for what happens when budget burns. This skill enforces the discipline from Google's SRE Workbook: pick the right SLI, set a target users actually care about, calculate the error budget, wire multi-window burn-rate alerts, and have a written policy for when budget runs out.\n\n## When to use\n\n- Defining a new SLO for a service or feature\n- Reviewing existing SLOs for common bugs\n- Picking the right SLI (event-based vs time-window based vs request-based)\n- Computing error budgets and burn-rate alert thresholds\n- Tying SLOs to existing controls — feature flags abort, chaos blast radius, operator capability levels\n\n## When NOT to use\n\n- General observability strategy (metrics + logs + traces) → use `observability-designer`\n- Customer-facing SLAs with legal teeth → that's contract drafting, not engineering\n- Performance load testing (capacity, not reliability) → use `performance-profiler`\n- Active incident response → use `incident-response`\n\n## Core principle: an SLO is a promise about user experience\n\n```\nSLI  ⟶  measurable signal of user-perceived health (e.g., HTTP 2xx rate)\nSLO  ⟶  target for the SLI over a window (e.g., 99.9% over 30 days)\nSLA  ⟶  customer-facing commitment with consequences (separate concern)\nEB   ⟶  error budget: 100% − SLO target = how much \"bad\" you can spend\nBR   ⟶  burn rate: how fast you're consuming the error budget\n```\n\nThe four cardinal mistakes:\n\n1. **Target too high** (99.99%+ on services that can't support it) — every minor blip violates SLO; alerts become noise.\n2. **Wrong SLI** (CPU usage as proxy for user experience) — system can be \"green\" while users suffer.\n3. **No error budget policy** — burning budget means nothing if there's no agreed action.\n4. **Single-window burn-rate alert** — either too noisy (page on a 5-min spike) or too slow (notice budget exhausted after the fact).\n\nThe 3 tools below catch each of these.\n\n## Quick start\n\n```bash\nSKILL=engineering\u002Fslo-architect\u002Fskills\u002Fslo-architect\n\n# 1. Design an SLO\npython \"$SKILL\u002Fscripts\u002Fslo_designer.py\" \\\n  --service checkout-svc \\\n  --sli-type request-success-rate \\\n  --target 99.9 \\\n  --window-days 30\n\n# 2. Compute error budget + multi-window burn-rate alerts\npython \"$SKILL\u002Fscripts\u002Ferror_budget_calculator.py\" \\\n  --target 99.9 --window-days 30\n\n# 3. Review existing SLO definitions for common bugs\npython \"$SKILL\u002Fscripts\u002Fslo_review.py\" --slo-doc docs\u002Fslos\u002F\n```\n\n## The 3 Python tools\n\nAll stdlib-only.\n\n### `slo_designer.py`\n\nGenerates a structured SLO definition with required fields. Refuses to render if any required field is missing (`exit 1`).\n\n```bash\npython scripts\u002Fslo_designer.py \\\n  --service checkout-svc \\\n  --sli-type request-success-rate \\\n  --target 99.9 \\\n  --window-days 30 \\\n  --owner team-checkout\n```\n\n**SLI types supported:**\n- `request-success-rate` — `(total_requests - bad_requests) \u002F total_requests`\n- `request-latency` — `count(requests \u003C threshold) \u002F total_requests`\n- `availability-time` — `(window - downtime) \u002F window`\n- `data-freshness` — `count(data_age \u003C threshold) \u002F total_data_points`\n- `correctness` — `count(correct_outputs) \u002F total_outputs`\n\nOutput is markdown by default with all required fields filled or marked `\u003Cmust define>`. JSON output (`--format json`) is consumed by `slo_review.py`.\n\n### `error_budget_calculator.py`\n\nGiven target availability + window, computes:\n- Allowed downtime in the window\n- Multi-window burn-rate thresholds per Google SRE Workbook (Chapter 5):\n  - **Fast burn** — page if 2% of monthly budget consumed in 1 hour\n  - **Slow burn** — page if 10% consumed in 6 hours, ticket if 10% in 3 days\n- Recommended alerting rules (PromQL-shaped output)\n\n```bash\npython scripts\u002Ferror_budget_calculator.py --target 99.9 --window-days 30\npython scripts\u002Ferror_budget_calculator.py --target 99.95 --window-days 7 --format json\n```\n\n### `slo_review.py`\n\nAudits a directory of SLO definitions (markdown or JSON) for the common bugs.\n\n```bash\npython scripts\u002Fslo_review.py --slo-doc docs\u002Fslos\u002F\n```\n\n**Checks:**\n- `target_too_high`: target ≥ 99.99% (sustainable only with massive engineering investment)\n- `target_too_low`: target ≤ 99.0% (probably wrong SLI; users will notice)\n- `window_too_short`: window \u003C 7 days (statistical noise dominates)\n- `window_too_long`: window > 90 days (slow feedback)\n- `no_sli_definition`: SLI section missing or vague (\"everything OK\")\n- `no_error_budget_policy`: no documented action when budget burns\n- `cpu_as_sli`: CPU\u002Fmemory used as user-experience proxy (wrong signal)\n\n## SLI selection cheatsheet\n\n| User experience | SLI type | What you measure |\n|---|---|---|\n| \"Did the request succeed?\" | request-success-rate | `2xx \u002F total` |\n| \"Was the response fast?\" | request-latency | `count(p99 \u003C threshold) \u002F total` |\n| \"Was the service up?\" | availability-time | `(window - downtime) \u002F window` |\n| \"Is the data current?\" | data-freshness | `count(data_age \u003C threshold) \u002F total` |\n| \"Was the answer correct?\" | correctness | `count(correct) \u002F total` |\n\nSee `references\u002Fsli_design.md` for examples and anti-patterns.\n\n## Error budget math (the basics)\n\nFor 99.9% SLO over 30 days:\n- Allowed unavailability: `0.1% × 30 × 24 × 60 = 43.2 minutes`\n- 1-hour fast-burn threshold (2% of monthly budget burned): `2% × 43.2 \u002F 60 ≈ 1.44 ratio multiplier`\n- 6-hour slow-burn threshold (10% in 6h): `10% × 43.2 \u002F 360 ≈ 0.6 ratio multiplier`\n\n`error_budget_calculator.py` does this math for you and emits ready-to-paste alert rules.\n\n## Composition with the rest of the portfolio\n\nThis skill explicitly composes with three others:\n\n| Skill | Composition |\n|---|---|\n| `feature-flags-architect` | Rollout abort criteria reference SLO burn-rate thresholds |\n| `chaos-engineering` | Blast-radius calculator already takes monthly error budget as input — define it here |\n| `kubernetes-operator` | Operator capability L4 (Deep Insights) requires SLOs + Prometheus rules |\n\nThe `error_budget_calculator.py` output is in the same shape `engineering\u002Fskills\u002Fchaos-engineering\u002Fscripts\u002Fblast_radius_calculator.py` expects on stdin.\n\n## Workflows\n\n### Workflow 1: Define a new SLO\n\n```\n1. Pick the user journey to protect (e.g., \"checkout completion\").\n2. Choose SLI type (request-success-rate, latency, availability, freshness, correctness).\n3. Define the SLI precisely: numerator\u002Fdenominator with concrete labels.\n4. Pick a target by measuring 30 days of historical SLI value:\n     target = floor(p50 of last 30 days × 100) \u002F 100\n   This avoids targets the system has never sustained.\n5. Pick a window (28 days = 4 calendar weeks, recommended).\n6. Run slo_designer.py to render the SLO definition.\n7. Run error_budget_calculator.py to get burn-rate alerts.\n8. Write the error budget policy (what happens when budget burns).\n9. Run slo_review.py — must pass before the SLO is \"live\".\n```\n\n### Workflow 2: Quarterly SLO review\n\n```\n1. For every active SLO, run slo_review.py — fix any FAIL findings.\n2. Look at last quarter's data:\n   - Was the SLO too easy (never burned budget)? Tighten target.\n   - Was it too hard (frequently burned)? Loosen target OR fix the system.\n   - Did burn-rate alerts fire usefully (not too noisy, not too late)? Adjust thresholds.\n3. Audit error budget policies — were they actually followed when budget burned?\n4. Commit revised SLOs; archive old versions with date stamps.\n```\n\n### Workflow 3: SLO-driven rollback\n\n```\n1. New deploy starts burning error budget faster than baseline.\n2. Burn-rate alert fires (from error_budget_calculator.py thresholds).\n3. Auto-rollback via feature flag (kill switch from feature-flags-architect).\n4. Postmortem feeds into next SLO revision.\n```\n\n## References\n\n- `references\u002Fslo_principles.md` — SLI vs SLO vs SLA, Google SRE Workbook canon\n- `references\u002Fsli_design.md` — picking the right SLI; 5 types with examples\n- `references\u002Ferror_budget.md` — error budget math, burn-rate alerts, budget policy\n- `references\u002Fcomposition.md` — how SLOs feed feature flags, chaos, operators\n\n## Slash command\n\n`\u002Fslo-design` — interactive SLO design wizard that runs all 3 tools.\n\n## Asset templates\n\n- `assets\u002Fslo_template.yaml` — fillable SLO YAML\n- `assets\u002Ferror_budget_policy.md` — fillable policy template\n\n## Anti-patterns\n\n- **99.99% on every endpoint** — copy-paste SLOs that nobody verified the system can sustain\n- **CPU usage as SLI** — system metrics aren't user experience\n- **Single-window burn-rate alert** — too noisy if 5-min, too slow if 30-day\n- **No error budget policy** — burning budget means nothing without an action\n- **SLOs without owners** — no one is responsible; they bit-rot\n- **SLOs reviewed once a year** — system characteristics change faster than that\n- **SLAs in the SLO doc** — different audience, different stakes; keep them separate\n- **SLO target = SLA target** — SLO must be tighter (you should beat your contract before customers notice)\n\n## Verifiable success\n\nA team using this skill should achieve:\n\n- 100% of SLOs pass `slo_review.py` with 0 FAIL findings\n- Every SLO has a documented owner, error budget, burn-rate alerts, and policy\n- Burn-rate alerts fire ≤2 times\u002Fmonth per SLO that's hit (signal, not noise)\n- Mean time to detect SLO violation: \u003C30 min (multi-window burn-rate alerts working)\n- Quarterly SLO review happens every quarter (not annually)\n",{"name":5,"tags":24,"author":34,"context":35,"license":15,"version":36,"description":7,"compatible_tools":37},[25,26,27,28,29,30,31,32,33],"slo","sli","sla","error-budget","burn-rate","sre","reliability","google-sre-workbook","observability","claude-code-skills","fork","2.9.0",[38,39,40,41,42,43],"claude-code","codex-cli","cursor","antigravity","opencode","gemini-cli","main","229636be8dd3adf33e35a2aa95b85dc022251d6b",".agents\u002Fskills\u002Falirezarezvani\u002Fengineering__slo-architect","https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent","https:\u002F\u002Fgithub.com\u002FPrudhviraj101","B.Tech CSE (AI\u002FML) Student | Building practical software with AI 🚀 | AI\u002FML Developer | Building AI agents, intelligent automation & real-world software ","2026-10-02 21:19:59",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add Prudhviraj101\u002FX_Agent --skill slo-architect",{"tool":57,"command":58},"bunx","bunx skills add Prudhviraj101\u002FX_Agent --skill slo-architect",{"tool":60,"command":61},"pnpm","pnpm dlx skills add Prudhviraj101\u002FX_Agent --skill slo-architect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Falirezarezvani\u002Fengineering__slo-architect\u002FSKILL.md",true,[65,71,75,81,85,89,93,99,103],{"path":66,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":69,"sourceHtmlUrl":70},"assets\u002Ferror_budget_policy.md","ASSET","资产文件",2641,"https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Falirezarezvani\u002Fengineering__slo-architect\u002Fassets\u002Ferror_budget_policy.md",{"path":72,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":73,"sourceHtmlUrl":74},"assets\u002Fslo_template.yaml",2293,"https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Falirezarezvani\u002Fengineering__slo-architect\u002Fassets\u002Fslo_template.yaml",{"path":76,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Fcomposition.md","REFERENCE","参考文档",5266,"https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Falirezarezvani\u002Fengineering__slo-architect\u002Freferences\u002Fcomposition.md",{"path":82,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Ferror_budget.md",4588,"https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Falirezarezvani\u002Fengineering__slo-architect\u002Freferences\u002Ferror_budget.md",{"path":86,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Fsli_design.md",5451,"https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Falirezarezvani\u002Fengineering__slo-architect\u002Freferences\u002Fsli_design.md",{"path":90,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":91,"sourceHtmlUrl":92},"references\u002Fslo_principles.md",5333,"https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Falirezarezvani\u002Fengineering__slo-architect\u002Freferences\u002Fslo_principles.md",{"path":94,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":97,"sourceHtmlUrl":98},"scripts\u002Ferror_budget_calculator.py","SCRIPT","脚本",5609,"https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Falirezarezvani\u002Fengineering__slo-architect\u002Fscripts\u002Ferror_budget_calculator.py",{"path":100,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":101,"sourceHtmlUrl":102},"scripts\u002Fslo_designer.py",6680,"https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Falirezarezvani\u002Fengineering__slo-architect\u002Fscripts\u002Fslo_designer.py",{"path":104,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":105,"sourceHtmlUrl":106},"scripts\u002Fslo_review.py",5660,"https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Falirezarezvani\u002Fengineering__slo-architect\u002Fscripts\u002Fslo_review.py",[108,117,125,133,140,148],{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":112,"licenseFileUrl":113,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":19},"01M7DQMKNKM6F5G21PPJNW3HR5","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\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":112,"licenseFileUrl":121,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":19},"01M7DQMF21V9VHCTVS8H5JFNJM","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\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fweb-artifacts-builder\u002FSKILL.md",[],[],{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":112,"licenseFileUrl":129,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":19},"01M7DQM8HREQ0DN1HV12K0W3VT","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\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftheme-factory\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftheme-factory\u002FSKILL.md",[],[],{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":139,"publishedAt":19},"01M7DQM5J7B71CQ8EVHBXCCCN2","systematic-planning","Formulate crisp, executable multi-phase implementation plans for non-trivial features, refactors, and architectural migrations. Use before writing code on any task with multiple files, uncertain requirements, or breaking changes.","https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsystematic-planning\u002FSKILL.md",[],[],{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":112,"licenseFileUrl":144,"sourceHtmlUrl":145,"categories":146,"keywords":147,"publishedAt":19},"01M7DQKG6WREWGRRCKHCJS96Y1","slack-gif-creator","Knowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like \"make me a GIF of X doing Y for Slack.\"","https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fslack-gif-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fslack-gif-creator\u002FSKILL.md",[],[],{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":112,"licenseFileUrl":152,"sourceHtmlUrl":153,"categories":154,"keywords":155,"publishedAt":19},"01M7DQJY7AN1XCX6G3ACA5K4JH","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.","https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fskill-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fskill-creator\u002FSKILL.md",[],[]]