[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75QKAHJS6189120M8PE557J":3,"skill-same:01M75QKAHJS6189120M8PE557J":105},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":13,"repositoryHtmlUrl":46,"repositoryHomepageUrl":6,"ownerHtmlUrl":47,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":48,"install":49,"resources":62},"01M75QKAHJS6189120M8PE557J","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.","TehutiRaEl\u002FTHEHIVE","TehutiRaEl","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F267495122?v=4","01M75N1QQQHT359S3XMYK7NPCB","01M75N1QRAW5P8P43HEHWMXCTE",0,"MIT","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fengineering\u002Fskills\u002Fslo-architect\u002FSKILL.md",[],[],"2026-11-12 13:55:43",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":23,"author":33,"context":34,"license":14,"version":35,"description":7,"compatible_tools":36},[24,25,26,27,28,29,30,31,32],"slo","sli","sla","error-budget","burn-rate","sre","reliability","google-sre-workbook","observability","claude-code-skills","fork","2.9.0",[37,38,39,40,41,42],"claude-code","codex-cli","cursor","antigravity","opencode","gemini-cli","main","b4ebd6d8c3b36347a5d435bcb343a5fc1c6f08d1","skills-library\u002Fengineering\u002Fskills\u002Fslo-architect","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE","https:\u002F\u002Fgithub.com\u002FTehutiRaEl","2026-11-15 04:00:21",{"source":8,"skillName":5,"commands":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add TehutiRaEl\u002FTHEHIVE --skill slo-architect",{"tool":55,"command":56},"bunx","bunx skills add TehutiRaEl\u002FTHEHIVE --skill slo-architect",{"tool":58,"command":59},"pnpm","pnpm dlx skills add TehutiRaEl\u002FTHEHIVE --skill slo-architect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fengineering\u002Fskills\u002Fslo-architect\u002FSKILL.md",true,[63,69,73,79,83,87,91,97,101],{"path":64,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":67,"sourceHtmlUrl":68},"assets\u002Ferror_budget_policy.md","ASSET","资产文件",2641,"https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fengineering\u002Fskills\u002Fslo-architect\u002Fassets\u002Ferror_budget_policy.md",{"path":70,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":71,"sourceHtmlUrl":72},"assets\u002Fslo_template.yaml",2293,"https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fengineering\u002Fskills\u002Fslo-architect\u002Fassets\u002Fslo_template.yaml",{"path":74,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Fcomposition.md","REFERENCE","参考文档",5266,"https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fengineering\u002Fskills\u002Fslo-architect\u002Freferences\u002Fcomposition.md",{"path":80,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Ferror_budget.md",4588,"https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fengineering\u002Fskills\u002Fslo-architect\u002Freferences\u002Ferror_budget.md",{"path":84,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Fsli_design.md",5451,"https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fengineering\u002Fskills\u002Fslo-architect\u002Freferences\u002Fsli_design.md",{"path":88,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":89,"sourceHtmlUrl":90},"references\u002Fslo_principles.md",5333,"https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fengineering\u002Fskills\u002Fslo-architect\u002Freferences\u002Fslo_principles.md",{"path":92,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":95,"sourceHtmlUrl":96},"scripts\u002Ferror_budget_calculator.py","SCRIPT","脚本",5609,"https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fengineering\u002Fskills\u002Fslo-architect\u002Fscripts\u002Ferror_budget_calculator.py",{"path":98,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":99,"sourceHtmlUrl":100},"scripts\u002Fslo_designer.py",6680,"https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fengineering\u002Fskills\u002Fslo-architect\u002Fscripts\u002Fslo_designer.py",{"path":102,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":103,"sourceHtmlUrl":104},"scripts\u002Fslo_review.py",5660,"https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fengineering\u002Fskills\u002Fslo-architect\u002Fscripts\u002Fslo_review.py",[106,113,119,126,133,140],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":18},"01M76XP63XDM4PFPX8MMVYN9JX","preamble-gate","Use BEFORE doing any work in this repo — before the first file edit, commit, push, PR, branch operation, workflow dispatch, scheduled trigger or timer, agent\u002Fsubagent spawn, dependency install, or message sent to an outside service. Forces a plain-language preamble to the founder first: WHAT you are about to do, WHY, HOW, why it is NECESSARY, the PROJECTED IMPROVEMENT, and the COST and RISK — then, for consequential work (governance, security, money, CI\u002Ftriggers, rewriting history, multi-agent fan-out), waits for an explicit go-ahead. Read-only investigation (reading files, grep, git log\u002Fdiff, answering questions) is exempt. Applies to every AI that works in this repo, not just Claude. Founder rule, 2026-11-10, written after an unattended automation ran up cost and froze the hive. Not a substitute for wired-or-not (which governs how completion is CLAIMED); this governs what happens BEFORE work starts.","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fpreamble-gate\u002FSKILL.md",[],[],{"skillNo":114,"name":115,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":18},"01M75RAYXC1W361YR9NBXD59AM","visionary-recommender","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills\u002Fvisionary-recommender\u002FSKILL.md",[],[],{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":18},"01M75RAQN9Q450RD57J2S6FSR4","syllabus","Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"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":14,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":18},"01M75RAG1XMCJMF30HFV5S79AK","research","Default entry point for any research request — a hybrid router that classifies the question deterministically and either delegates to a specialist research skill (pulse for trends\u002Fsentiment, grants for NIH funding, litreview for academic literature, syllabus for course reading, patent for prior-art + IP landscape, dossier for entity research) or runs its own plan-decompose-multi-source-search-synthesize-cite fallback workflow when no specialist matches. Always surfaces the routing decision so users can override. Use when the user makes any research request that doesn't obviously match a more-specific specialist skill (e.g., \"research [topic]\", \"look into [topic]\", \"what do we know about [topic]\", \"investigate [topic]\", \"find me information on [topic]\", \"do some research on [topic]\", \"I need to understand [topic]\"). Output is a markdown briefing (default) or .docx document (on request) with full citations and an audit log.","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fresearch\u002Fresearch\u002Fskills\u002Fresearch\u002FSKILL.md",[],[],{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":139,"publishedAt":18},"01M75RA8RK2JVWB8MYGRB65V75","pulse","Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X\u002FTwitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend\u002Fsentiment\u002Fproblems\u002Fopportunities\u002Fcomparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Use when the user requests multi-source recency intelligence on a topic (e.g., 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":146,"publishedAt":18},"01M75RA08RXYRFSTNC6EEEX4ZD","patent","Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search \u002F freedom-to-operate \u002F competitive landscape \u002F acquisition diligence \u002F litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[]]