# Changelog

All notable changes to the Claude Skills Library will be documented in this file.

The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## [2.5.7] - 2026-05-13 — Docs site refresh: nav additions, dual-publish dedup, 301 redirects

### Added

- **5 new C-role docs pages** added to `mkdocs.yml` nav (C-Level Advisory section): General Counsel Advisor, Chief Data Officer Advisor, Chief AI Officer Advisor, Chief Customer Officer Advisor, VP Engineering Advisor.
- **13 new cs-* agent docs pages** added to `mkdocs.yml` nav (Agents section): cs-cfo / cs-cmo / cs-cro / cs-cpo / cs-coo / cs-chro / cs-ciso / cs-chief-of-staff / cs-general-counsel / cs-cdo / cs-caio / cs-cco / cs-vpe.
- **`mkdocs-redirects` plugin** added to `mkdocs.yml` plugins list. Provides client-side redirects (meta-refresh + JS fallback) — Google's SERP indexing treats meta-refresh with delay=0 as 301-equivalent.

### Fixed

- **`scripts/generate-docs.py` dedup bug:** the auto-generator created BOTH `<name>.md` (bundled) AND `<name>-<name>.md` (standalone wrapper) for dual-published skills, producing duplicate-content pages. The dedup now detects the dual-publish pattern (`<domain>/<name>/skills/<same-name>/SKILL.md` paired with `<domain>/skills/<name>/SKILL.md`) and skips the standalone mirror in favor of the bundled (canonical) version.
- **4 pre-existing engineering dual-publish duplicate pages deleted** with 301-equivalent redirects:
  - `skills/engineering/chaos-engineering-chaos-engineering.md` → `skills/engineering/chaos-engineering.md`
  - `skills/engineering/feature-flags-architect-feature-flags-architect.md` → `skills/engineering/feature-flags-architect.md`
  - `skills/engineering/kubernetes-operator-kubernetes-operator.md` → `skills/engineering/kubernetes-operator.md`
  - `skills/engineering/slo-architect-slo-architect.md` → `skills/engineering/slo-architect.md`
  - All 4 old URLs redirect to the canonical page; existing Google SERP indexes preserved.

### Changed

- **`mkdocs.yml` `site_description`** — updated from "246 skills, 20 cs-* agents" (6 versions stale) to current "268 skills, 33 cs-* agents (incl. founder-mode C-suite), 21 /cs:* slash commands."
- **`README.md`** — header counts updated: 246 → 268 skills; 20 → 33 agents; 33 → 54 commands; 359 → 373 Python tools. Subtitle expanded with founder-mode lineup callout.
- **`.github/workflows/static.yml`** — install step updated from `pip install mkdocs-material` to `pip install mkdocs-material mkdocs-redirects` to support the new plugin.

### Verified

- `mkdocs build` succeeds (357 HTML pages generated)
- Redirect HTML correctly emitted with `<meta http-equiv="refresh" content="0; url=...">` + JavaScript fallback that preserves URL anchors
- karpathy `diff_surgeon`: clean on staged diff
- 71 pre-existing skill pages preserved (no SEO equity loss)

### Pre-existing (not addressed in this PR)

13 INFO-level link warnings exist from before this session (broken anchors and relative-link-without-index hints). These are pre-existing in the docs and not introduced or worsened by this PR. Tracked as a separate cleanup if desired.

## [2.5.6] - 2026-05-13 — Cleanup: missing voice specs + broken agent paths

### Fixed

- **3 missing voice specs added to `c-level-advisor/c-level-agents/references/persona-voices.md`:**
  - `cs-ceo-advisor` — The Strategic Translator (tree-of-thought reasoning; refuses to debate tactics until the strategic question is named)
  - `cs-cto-advisor` — The Architecture-First Pragmatist (ReAct reasoning; treats every architecture decision as a 3-year commitment)
  - `cs-general-counsel-advisor` — The Risk-Paranoid Lawyer (Not Your Lawyer) — carry-over from v2.5.1
  - All three agents existed but their voice specs were never added to the persona reference (cs-ceo / cs-cto pre-date the c-level-agents plugin; cs-gc was an oversight in v2.5.1).
- **Broken paths fixed in 2 pre-existing agent files** (`agents/c-level/cs-ceo-advisor.md` and `agents/c-level/cs-cto-advisor.md`):
  - All 57 references to `../../c-level-advisor/ceo-advisor/` and `../../c-level-advisor/cto-advisor/` updated to `../../c-level-advisor/skills/ceo-advisor/` and `../../c-level-advisor/skills/cto-advisor/` respectively (correct path; the bundled skills live under `skills/`)
  - YAML `skills:` field also corrected (was `c-level-advisor/ceo-advisor`, now `c-level-advisor/skills/ceo-advisor`)
- **karpathy-coder/diff_surgeon:** clean on staged diff

### Why

Both gaps were carry-over items noted across multiple PRs in this session (v2.5.1 → v2.5.5) per karpathy principle #3 (surgical scope — no unrelated cleanups inside scoped feature PRs). This dedicated cleanup PR addresses them in one focused change without touching any feature work.

### Changed

- `c-level-advisor/c-level-agents/references/persona-voices.md` — 13 → 13 voice specs cataloged (all cs-* agents in the persona-voices list now match the agents that exist)
- `agents/c-level/cs-ceo-advisor.md` — 32 path corrections
- `agents/c-level/cs-cto-advisor.md` — 25 path corrections

No skill/agent/command count changes; no manifest version bumps (this is a pure-fix PR).

## [2.5.5] - 2026-05-13 — vpe-advisor: throughput-first VP of Engineering

### Added — C-Level Advisory

- **vpe-advisor** skill (`./c-level-advisor/skills/vpe-advisor/`) — opinionated throughput-first VP of Engineering skill. Fifth decision-driven C-role skill in the founder-mode lineup (after GC, CDO, CAIO, CCO). Covers four specific decisions distinct from CTO:
  1. **Are we delivering at the right throughput?** (DORA 4 metrics + bottleneck identification)
  2. **How do we scale the eng hiring funnel?** (7-stage funnel + pipeline gap + weakest-stage fix)
  3. **What's our eng team structure — when to add a tech-lead manager?** (squad/tribe + manager-trigger + span-of-control)
  4. **What's our production discipline?** (on-call, deployment cadence, postmortem culture, SLO discipline — reference-only)
- **Critical distinction enforced:** VPE is NOT a CTO skill. CTO owns *what to build* (architecture, scaling cliffs, build-vs-buy). VPE owns *how to ship it* (delivery operations, hiring execution, team structure, production discipline). At early stage these are often the same person; at scale they're distinct roles.
- **3 stdlib Python tools with deterministic logic:**
  - **`delivery_throughput_analyzer.py`** — Returns DORA 4 metrics (Deployment Frequency, Lead Time for Changes, MTTR, Change Failure Rate) with Elite/High/Medium/Low verdict per metric and overall. Cycle-time bottleneck identification (top wait stage as % of cycle) with typical fixes per bottleneck (review queue, CI flakiness, deploy gates, scheduled releases). Embedded sample (30-day Platform Squad, 28 deploys) → overall High; bottleneck = first_review_to_approval at 45.8% of cycle.
  - **`eng_hiring_funnel_calculator.py`** — Stage-by-stage conversion rates for 7-stage funnel (Applied → Sourcer → Recruiter → Hiring Mgr → Tech → Onsite → Offer → Accept) with healthy/leaky verdict per stage. End-to-end conversion rate, required top-of-funnel volume for hiring target, weakest-stage identification with fixes (sourcing channel diversification, calibration, interview design, comp/close discipline). Embedded sample (Q2 2026, 4-engineer hiring target) → 0.62% end-to-end, gap of 160 candidates, weakest = offer_extended_to_offer_accepted at 60%.
  - **`eng_team_structure_designer.py`** — Recommended structure (informal pods / formal squads / squads+tribes / multi-tribe) based on headcount. Squad sizing assessment (5-9 IC healthy range). Manager-trigger (first EM at 5-7 ICs; EM-overstretched > 10 ICs; EM-underutilized < 4 ICs). Director-trigger (3+ EMs reporting directly to VPE/CTO). Embedded sample (25-engineer team, 22 ICs / 3 EMs / 1 CTO) → 4-squad structure, no EM trigger (3 EMs for 22 ICs = healthy 7.3 per EM), director trigger FIRES (3 EMs report directly to CTO).
- **4 in-depth references each citing 5+ authoritative sources:**
  - `delivery_throughput.md` — Full DORA framework with thresholds + 4 common bottlenecks + what to fix first (lead time → failure rate → frequency → MTTR) + 4 anti-patterns. Cites Accelerate (Forsgren/Humble/Kim), Google State of DevOps annual report, The Phoenix Project, Reinertsen Flow, Newman Microservices, Humble Continuous Delivery, Atlassian/GitHub/GitLab benchmarks.
  - `engineering_hiring_funnel.md` — 7-stage funnel + healthy conversion benchmarks + leakage diagnosis per stage + pipeline volume math + sourcing channel diversification + technical interview design + cost-per-hire. Cites LinkedIn Talent Insights, Atlassian Recruiting Ops, Levels.fyi + Pave, Lou Adler "Hire With Your Head", Adler/Bock "Work Rules!", CMU/Booth interview validity research, SHRM surveys.
  - `eng_team_structure.md` — Conway's Law + headcount-to-structure map + span-of-control benchmarks + EM vs tech lead distinction + manager/director/VPE triggers + squad sizing + chapter discipline. Cites Kniberg "Scaling Agile @ Spotify", Kniberg 2020 retrospective, Will Larson "Elegant Puzzle", Camille Fournier "Manager's Path", Conway 1968, Schwartz "A Seat at the Table", Lencioni "Five Dysfunctions", Stripe/Shopify/GitHub/Netflix engineering blogs.
  - `production_discipline.md` — On-call rotation design (≥ 6 people; burnout signals) + incident response (4-tier severity, IC role, blameless postmortems) + deployment cadence (continuous vs scheduled; progressive delivery) + SLO discipline integration + 5-level maturity model. Cites Google SRE (Beyer/Jones/Petoff/Murphy), SRE Workbook, John Allspaw postmortem writings, PagerDuty Incident Response docs, Charity Majors observability, Nora Jones chaos engineering, Mikey Dickerson reliability hierarchy.
- **cs-vpe-advisor** agent (`./c-level-advisor/c-level-agents/agents/cs-vpe-advisor.md`) — throughput-first operator. Voice: "What's your cycle time, and where does the work spend most of its time waiting?" Trusts DORA metrics over vibe. Refuses to recommend hires without naming the throughput or quality bottleneck they unblock.
- **`/cs:vpe-review`** slash command (`./c-level-advisor/c-level-agents/skills/vpe-review/SKILL.md`) — 6-question forcing interrogation: cycle time + waits, DORA verdict, hiring funnel leakage, team structure health, production discipline maturity, VPE-vs-CTO scope decision.
- **cs-vpe-advisor voice spec** added to `persona-voices.md`.
- **Dual-published from the start:** standalone plugin at `c-level-advisor/vpe-advisor/` with mirrored content (per #624 pattern). `sync_skill_bundles.py` keeps both copies aligned.

### Why This Matters

The single most-asked staffing question at Series B is: "Do we need a VPE separately from the CTO?" This skill makes the decision mechanical:

- If CTO is spending > 50% on management vs strategy, VPE is needed
- If CTO is a co-founder more comfortable with strategy than execution, VPE complements
- At small scale (< 20 eng), one person can do both — but the operating decisions still need to be made

Existing skills don't quite own these decisions: cs-cto-advisor is about architecture; cs-engineering-lead is day-to-day incident coordination; cs-chro-advisor owns hiring SYSTEMS company-wide but not eng-specific funnel execution. VPE fills the gap with deterministic frameworks for delivery operations.

### Built with Karpathy-Coder Discipline (5th Consecutive PR)

Maintained the discipline established in v2.5.2:

- **Principle 1:** assumptions surfaced upfront, including the critical CTO-vs-VPE distinction. Locked direction before code.
- **Principle 2:** rejected generic "engineering operations survey" framing. Each tool/reference covers ONE decision. No overlap with engineering tactical skills (`engineering/slo-architect/`, `engineering/feature-flags-architect/`, etc.).
- **Principle 3:** touched only files in the locked plan. No "while I'm here" cleanup. No edits to other c-level skills.
- **Principle 4:** all 3 Python tools smoke-tested with embedded samples before commit. Verifiable outputs (DORA overall High; hiring gap +160 candidates; 25-eng team → 4 squads, director trigger fired).

### Changed

- **Total skills:** 267 → 268 (+1 vpe-advisor)
- **cs-* agents:** 32 → 33 (+1 cs-vpe-advisor in c-level-agents plugin)
- **/cs:* slash commands:** 20 → 21 (+1 /cs:vpe-review)
- **Python tools:** 370 → 373 (+3 in vpe-advisor/scripts/)
- **References:** 502 → 506 (+4 in vpe-advisor/references/)
- **Marketplace plugins:** 38 → 39 (+1 standalone vpe-advisor entry)
- **c-level-skills** plugin: v2.5.4 → v2.5.5 (description expanded; 32 → 33 skills, 12 → 13 cs-* agents)
- **c-level-agents** plugin: v1.4.0 → v1.5.0 (description expanded with VPE; new agent + command; +`vp-engineering`, `vpe`, `dora`, `delivery-throughput`, `engineering-hiring`, `eng-team-structure`, `production-discipline` keywords)

### Known follow-ups (NOT in this PR per surgical scope)

- `cs-general-counsel-advisor` voice spec still missing from `persona-voices.md` (carried from v2.5.1; multi-PR carry-over)
- Phase 2 final remainder (1 role): CCO-comms (Chief Communications Officer) — naming conflict with CCO (Chief Customer Officer); needs disambiguation before adding

### Disclaimer

DORA benchmarks come from cross-industry research; specific thresholds shift with stage and complexity. Hiring funnel benchmarks vary by role level + geography. This skill provides operating-baseline guidance; pair with cs-cto-advisor (architecture), cs-chro-advisor (hiring systems), and engineering tactical skills for execution.

## [2.5.4] - 2026-05-13 — chief-customer-officer-advisor: retention-obsessed CCO

### Added — C-Level Advisory

- **chief-customer-officer-advisor** skill (`./c-level-advisor/skills/chief-customer-officer-advisor/`) — opinionated, retention-obsessed CCO skill. Fourth decision-driven C-role skill in the founder-mode lineup. Covers four specific decisions (not generic CS survey):
  1. **What's our retention architecture — and is gross retention vs NRR honest?** (decomposition + 7-category churn taxonomy)
  2. **How do we segment customers for differential investment?** (4-tier framework + ICP fit scoring + kill list)
  3. **What's the CS team's coverage model — and when do we go pooled vs named?** (ratio math + manager trigger)
  4. **What CS role do we hire next?** (stage-to-role map; CSM ≠ Support ≠ AM ≠ IM)
- **3 stdlib Python tools with deterministic logic:**
  - **`retention_decomposition_analyzer.py`** — Decomposes ARR retention by cohort into GRR (truth) / NRR (vanity if alone) / Logo Retention separately. Flags leaky-bucket pattern (NRR > 100% AND GRR < 85%). Categorizes churn across 7-category root-cause taxonomy (product_fit / competitor_loss / no_value_realized / pricing / champion_left / company_event / tactical_failure) and computes preventable % (CS-controllable). Embedded sample: 2 cohorts, Q1 GRR 91.7% CONCERNING (NRR too low at 106.7%), Q2 GRR 84.7% CRITICAL (declining trend), top driver = product_fit at 54.5% preventable.
  - **`customer_segmentation_designer.py`** — Assigns 4-tier segment (Strategic / Enterprise / Mid-market / SMB-long-tail) by ARR. Scores ICP fit 0-10 from 7 weighted signals (industry, size, workflow, exec sponsor, advocacy, expansion potential, competitor concentration). Surfaces kill list (support cost > 50% of ARR AND ICP fit < 5) with the 3 paths (non-renewal / downgrade-to-tech-touch / raise-price). Surfaces upgrade candidates (high fit + expansion potential).
  - **`cs_coverage_calculator.py`** — Calculates required CSM headcount per tier with two constraints (ARR ratio AND account count, whichever is binding). Surfaces manager-trigger thresholds (5+ ICs in tier OR 8+ across function). Generates 12-month hiring plan with quarterly sequencing. Includes fully-loaded cost projection.
- **4 in-depth references each citing 5+ authoritative sources:**
  - `retention_decomposition.md` — GRR vs NRR honest math + leaky-bucket pattern + 7-category churn taxonomy + leading-indicator playbook + cohort discipline. Cites Mehta/Steinman/Murphy "Customer Success", Lincoln Murphy, David Skok (forEntrepreneurs), BVP State of the Cloud, ChartMogul/ProfitWell benchmarks, Reichheld "The Loyalty Effect", Tomasz Tunguz.
  - `customer_segmentation_strategy.md` — 4-tier framework + ICP fit weighting (7 signals) + tier transition triggers + kill list criteria + the 3 paths. Cites Lincoln Murphy, Bain "Loyalty Effect", Tunguz, Skok, ChartMogul/ProfitWell, Adamson/Dixon/Toman "Challenger Customer".
  - `cs_coverage_model.md` — Tech-touch / pooled / named / named+exec models + ARR-per-CSM ratios by stage and segment + manager-trigger + CS comp design + ramp curves. Cites Gainsight, TSIA, Mehta/Pickens "Customer Success Economy", ChurnZero, Skok, Lincoln Murphy, Pacific Crest/KeyBanc SaaS survey.
  - `cs_team_org_evolution.md` — 5-stage role map + 6-role definition table (CSM ≠ Support ≠ AM ≠ IM ≠ CS Ops ≠ Customer Marketing) + AM-vs-CSM split decision + 7 anti-patterns. Cites Mehta/Steinman/Murphy, Mehta/Pickens, BVP, TSIA, Gainsight, ChurnZero, Lincoln Murphy.
- **cs-cco-advisor** agent (`./c-level-advisor/c-level-agents/agents/cs-cco-advisor.md`) — retention-obsessed pragmatist. Voice: "What's your gross retention rate, and what's the #1 reason customers leave?" Trusts gross retention over NRR. Refuses to recommend CS hires without naming the customer outcome they unblock.
- **`/cs:cco-review`** slash command (`./c-level-advisor/c-level-agents/skills/cco-review/SKILL.md`) — 6-question forcing interrogation: GRR (not NRR), top churn driver, time-to-value, kill-list candidates, ARR-per-CSM ratio + coverage model, CS comp alignment.
- **cs-cco-advisor voice spec** added to `persona-voices.md`.
- **Dual-published from the start:** standalone plugin at `c-level-advisor/chief-customer-officer-advisor/` with mirrored content (per the same pattern as #624 for GC/CDO/CAIO). `sync_skill_bundles.py` keeps both copies aligned.

### Why This Matters

By 2026, every B2B SaaS founder is being asked a board-level question: "What's your NRR?" The truth is that NRR alone is the vanity metric — it can hide a leaky bucket where 85% gross retention is masked by expansion from the survivors. This skill enforces the discipline of decomposition before reporting, and surfaces three decisions the other C-roles can't quite own:

- **CRO** owns the revenue math (NRR, expansion comp, ramp); **CCO** owns customer *experience* and the 7-category churn root cause analysis. Clean split.
- **CPO** owns product roadmap; **CCO** surfaces product gaps via churn data. CPO decides; CCO feeds.
- **CHRO** owns CS team comp; **CCO** designs the coverage model + ratios. CHRO executes; CCO designs.

The differential-investment framework (kill list + upgrade candidates) is the strategically distinct CCO contribution. Most founders avoid the kill-list conversation; this skill makes it mechanical.

### Built with Karpathy-Coder Discipline (fourth consecutive PR)

Maintained the discipline established in v2.5.2:

- **Principle 1:** assumptions surfaced upfront, including the CRO vs CCO split assumption (revenue math vs customer experience). Locked direction before code.
- **Principle 2:** rejected generic "customer success survey" framing. Each tool/reference covers ONE decision. No overlap with `business-growth/customer-success-management/`.
- **Principle 3:** touched only files in the locked plan. No "while I'm here" cleanup of unrelated files. No edits to other c-level skills.
- **Principle 4:** all 3 Python tools smoke-tested with embedded samples before commit. Verifiable outputs (Q1 GRR 91.7% CONCERNING / Q2 GRR 84.7% CRITICAL; 5 customers tiered with 1 kill + 2 upgrade candidates; 4 → 12 CSMs / $2.25M annual cost at 40% growth).

### Changed

- **Total skills:** 266 → 267 (+1 chief-customer-officer-advisor)
- **cs-* agents:** 31 → 32 (+1 cs-cco-advisor in c-level-agents plugin)
- **/cs:* slash commands:** 19 → 20 (+1 /cs:cco-review)
- **Python tools:** 367 → 370 (+3 in chief-customer-officer-advisor/scripts/)
- **References:** 498 → 502 (+4 in chief-customer-officer-advisor/references/)
- **Marketplace plugins:** 37 → 38 (+1 standalone chief-customer-officer-advisor entry)
- **c-level-skills** plugin: v2.5.3 → v2.5.4 (description expanded; 31 → 32 skills, 11 → 12 cs-* agents)
- **c-level-agents** plugin: v1.3.0 → v1.4.0 (description expanded with CCO; new agent + command; +`chief-customer-officer`, `cco`, `retention-decomposition`, `customer-segmentation`, `cs-coverage` keywords)

### Known follow-ups (NOT in this PR per surgical scope)

- The `cs-general-counsel-advisor` voice spec is still missing from `persona-voices.md` (carried from v2.5.1). Will be addressed in a separate small PR.
- Phase 2 remainder (2 more C-roles: VPE engineering execution, CCO-comms) deferred to v2.5.5+.

### Disclaimer

Retention benchmarks vary significantly by ACV, segment, and industry. This skill provides B2B SaaS-baseline guidance; consumer SaaS, marketplaces, and hardware have materially different retention math.

## [2.5.3] - 2026-05-12 — chief-ai-officer-advisor: AI strategy with citations

### Added — C-Level Advisory

- **chief-ai-officer-advisor** skill (`./c-level-advisor/skills/chief-ai-officer-advisor/`) — opinionated, eval-demanding CAIO skill covering 4 specific decisions. The third decision-driven C-role skill in the founder-mode lineup, after general-counsel-advisor (v2.5.1) and chief-data-officer-advisor (v2.5.2).
- **4 specific decisions covered** (not a generic AI strategy survey):
  1. **Should we use an API, fine-tune, or build our own?** (model build-vs-buy with 3-year TCO)
  2. **Is this AI use case high-risk under regulation, and how do we govern it?** (EU AI Act + NIST AI RMF + US state patchwork)
  3. **When do we switch from API to self-hosted, and at what cost?** (token economics with breakeven analysis)
  4. **What AI role do we hire next?** (stage-to-role map; AI engineer ≠ ML engineer ≠ research scientist)
- **3 stdlib Python tools with deterministic logic**:
  - **`model_buildvsbuy_calculator.py`** — Returns API / FINE_TUNE / BUILD recommendation, 3-year TCO across 6 path variants (API frontier-premium/economy/open-hosted, fine-tune, self-hosted 70B-class, build-from-scratch), and breakeven analysis. Balances economic crossover with practical feasibility (data availability, ML team capacity, compliance constraints). Embedded sample (B2B customer support, 4M queries/mo) → API recommendation despite economic breakeven crossed, due to no fine-tune data + 1-engineer ML team.
  - **`ai_risk_classifier.py`** — Returns EU AI Act tier (PROHIBITED / HIGH / LIMITED / MINIMAL) with Article-level citations, US state triggers (NYC LL 144, CO AI Act, IL HB 53, CA SB 1001, IL BIPA), industry overlays (FDA AI/ML, ECOA, NAIC AI bulletin), required-controls list, and conformity-assessment flag. Embedded sample (AI hiring screening in EU+NY+CO+IL+CA) → HIGH risk, conformity required, 3 US state triggers, 14 controls. 7 EU AI Act articles cited (5, 6, 9-15, 43, 49, 72).
  - **`ai_cost_economics.py`** — Returns monthly costs at 6 paths (3 API tiers + self-hosted at low/mid/high GPU rates), breakeven monthly tokens, sensitivity to GPU pricing. Embedded sample (5M tokens/day, 750M/mo) → API at $1,500/mo beats self-hosted at $13,450/mo by 9x; breakeven at 6.7B tokens/mo for 70B-class on A100s. Reveals key insight that self-hosted floor (24/7 warm GPUs + ops) makes API economics dominate at typical B2B SaaS scale.
- **4 in-depth references each citing 5+ authoritative sources**:
  - `model_buildvsbuy_strategy.md` — 3 paths with failure modes, 6 fine-tuning approaches (few-shot, prompt eng, RAG, LoRA, full FT, RLHF/DPO, continued pre-training) ranked by cost and use case, decision tree, eval-first discipline. Cites Anthropic/OpenAI/Google/Meta model cards, LoRA paper (Hu et al.), RLHF paper (Ouyang et al.), DPO paper (Rafailov et al.), Foundation Models report (Stanford CRFM), Foundation Models and Fair Use (Henderson et al.).
  - `ai_risk_governance.md` — Full EU AI Act tier map (prohibited Article 5, high-risk Article 6 + Annex III, limited-risk Article 50, minimal-risk) with all 8 high-risk domains + 11 obligation Articles. NIST AI RMF 1.0 (4 functions, 7 trustworthy characteristics). US state patchwork (NYC LL 144, CO AI Act, IL HB 53, CA SB 1001, CA AB 2013, CA AB 1008, IL BIPA, WA MHMD, TX biometric). Industry overlays (FDA, CFPB, Fed SR 11-7, NYDFS Reg 23, ECOA, NAIC). 10-item governance program checklist. When-to-hire-AI-counsel criteria.
  - `ai_cost_economics.md` — 2026 API pricing across 4 tiers, GPU rental (A100/H100/H200/B200), throughput estimates, GPU count by model size, cost-per-million-tokens calculations, utilization reality (interactive 20-40%, batch 60-80%), 6 hidden costs of self-hosted, 6 hidden costs of API, migration cost (3-6 months, 2-3 engineers), prompt caching as economics lever. Cites vLLM paper, DistServe (NSDI 2024), HELM benchmark, Artificial Analysis, Llama 3.1 paper.
  - `ai_team_org_evolution.md` — 5-stage role map (pre-seed → late-stage), 9-role definition table distinguishing AI engineer / ML engineer / research scientist / data scientist / AI safety / AI PM / Head of AI / CAIO. AI team vs data team contrast (8 dimensions). 7 specific anti-patterns. Hiring sequencing rule. Cites Huyen "Designing ML Systems" + "AI Engineering", State of AI Report, Karpathy's AI engineer archetype discussions.
- **cs-caio-advisor** agent (`./c-level-advisor/c-level-agents/agents/cs-caio-advisor.md`) — eval-demanding realist orchestrating the skill. Voice: "What does this AI need to be good at, and how would you measure it?" Treats every AI use case as a hiring decision; pushes back on AI hype; demands fallback behavior before scale.
- **`/cs:caio-review`** slash command (`./c-level-advisor/c-level-agents/skills/caio-review/SKILL.md`) — 6-question forcing interrogation: eval discipline, hallucination SLO, regulatory tier, model selection, cost trajectory, role-that-unblocks-this.
- **cs-caio-advisor voice spec** added to `persona-voices.md`.

### Why This Matters

By 2026, every founder is making AI decisions that didn't exist 18 months ago — and gstack, general legal counsel, CTOs, and CISOs each only cover part of the picture. The CAIO concerns that this skill uniquely owns:

1. **Model build-vs-buy is not a single answer.** 80% of B2B SaaS should use frontier APIs; 15% should fine-tune; <1% should pre-train. The decision depends on data availability + team capacity + economics + compliance, not on technology preference.
2. **EU AI Act conformity is consequential and slow.** A high-risk AI use case requires 3-12 months of conformity work + EU database registration + 10 Articles of obligations. Discovering this 2 weeks before EU launch is a category of pain this skill prevents.
3. **API vs self-hosted breakeven is much higher than founders expect.** For 70B-class on rented A100s, breakeven is typically 1-10 billion tokens per month — not the 100M-500M most founders intuit. Self-hosting "to save money" usually wastes engineering capacity.
4. **AI team confusion costs 12 months of productivity.** Hiring a research scientist as first AI hire is the single most common AI hiring mistake, and it's expensive to undo.

### Built with Karpathy-Coder Discipline

Maintained the discipline established in v2.5.2:

- **Principle 1 (Think before coding):** assumptions surfaced upfront before file writes. Locked 4 decisions, 3 tools, 4 references, success criteria. User confirmed direction.
- **Principle 2 (Simplicity first):** rejected "generic AI strategy survey" framing. Each tool covers ONE decision. Each reference answers ONE decision. No overlap with engineering/rag-architect, engineering/agent-designer, engineering/llm-cost-optimizer.
- **Principle 3 (Surgical changes):** touched only files in the locked plan. No "while I'm here" cleanup.
- **Principle 4 (Goal-driven execution):** all 3 tools smoke-tested with embedded samples before commit. Verifiable success criteria met.

### Changed

- **Total skills:** 265 → 266 (+1 chief-ai-officer-advisor)
- **cs-* agents:** 30 → 31 (+1 cs-caio-advisor in c-level-agents plugin)
- **/cs:* slash commands:** 18 → 19 (+1 /cs:caio-review)
- **Python tools:** 364 → 367 (+3 in chief-ai-officer-advisor/scripts/)
- **References:** 494 → 498 (+4 in chief-ai-officer-advisor/references/)
- **c-level-skills** plugin: v2.5.2 → v2.5.3 (description expanded; 30 → 31 skills, 10 → 11 cs-* agents)
- **c-level-agents** plugin: v1.2.0 → v1.3.0 (description expanded with CAIO; new agent + command; +`chief-ai-officer`, `caio`, `ai-strategy`, `model-buildvsbuy`, `eu-ai-act`, `ai-cost-economics` keywords)

### Known follow-ups (NOT included this PR per surgical scope)

- The `cs-general-counsel-advisor` voice spec is still missing from `persona-voices.md` (carried from v2.5.1). Will be addressed in a separate small PR.
- Phase 2 remainder (3 more C-roles: CCO customer, VPE engineering execution, CCO comms) deferred to v2.5.4+.

### Disclaimer

The `chief-ai-officer-advisor` skill surfaces strategic AI decisions but is **not legal advice** for AI regulation, **not a replacement for outside AI counsel** for EU AI Act conformity assessments, and **not a tactical AI/ML engineering skill**. For tactical AI engineering, see `engineering/rag-architect/`, `engineering/agent-designer/`, `engineering/prompt-governance/`, `engineering/self-eval/`, `engineering/llm-cost-optimizer/`.

## [2.5.2] - 2026-05-12 — chief-data-officer-advisor: data strategy without surveys

### Added — C-Level Advisory

- **chief-data-officer-advisor** skill (`./c-level-advisor/skills/chief-data-officer-advisor/`) — opinionated, decision-driven CDO skill. Refuses to be a generic data-governance survey; instead answers four specific decisions:
  1. **Can we train our model on this data?** (AI training data rights matrix)
  2. **Warehouse, lakehouse, or mesh — and what do we build vs buy?** (data product strategy)
  3. **What is our customer data worth?** (B2B customer-data-as-asset valuation + M&A multiplier)
  4. **What data role do we hire next?** (data team org evolution)
- **3 stdlib Python tools with deterministic logic** (not pattern-match prose):
  - **`ai_training_data_audit.py`** — Audits data sources on 3 dimensions (origin × data class × use case). Returns GO/MITIGATE/NO-GO per source with risk, remediation, and GDPR Art. 6 + EU AI Act + US state citations. Embedded sample tests 7 sources spanning all 3 verdicts. Implements 6+ rule branches (scraped always NO-GO, regulated requires framework-specific consent, PII for fine-tuning requires explicit opt-in, etc.).
  - **`data_product_strategy_picker.py`** — Picks warehouse/lakehouse/mesh from a company profile (stage, consumers, data volume, ML models, culture). Returns architecture + 6-layer build-vs-buy decisions (storage, ELT, modeling, BI, feature store, ML platform) + 12-month sequencing roadmap. Deterministic: same profile → same recommendation. Embedded sample (Series A B2B SaaS, 8 consumers, 4.5TB, 1 ML model) → LAKEHOUSE recommendation.
  - **`data_asset_valuator.py`** — Computes strategic value 0-10 from 4 components (exclusivity, freshness, cohort breadth, history depth), derives moat strength (NONE/WEAK/MEDIUM/STRONG), applies M&A multiplier (1.0x–1.7x ARR depending on moat) with penalties for MSA carve-out rate and failed anonymization audit. Ranks 3 productization paths (benchmark report / embedding endpoint / direct license) by risk + viability. Embedded sample (B2B sales engagement corpus, 380 customers, 47 carve-outs) → 8.2/10 STRONG moat, 1.33-1.61x multiplier, recommends benchmark report as starting path.
- **4 references answering one decision each** (not topic surveys):
  - `ai_training_data_rights.md` — Decision: can we train on this source? Three-dimension matrix + GDPR Art. 6 lawful basis decision tree + EU AI Act high-risk triggers + US state patchwork (CCPA/CPRA, NYC LL 144, IL BIPA, WA MHMD).
  - `data_product_strategy.md` — Decision: which architecture and what do we build? Stage-driven kill criteria per architecture + 6-layer build-vs-buy decision tree + sequencing pattern + anti-patterns.
  - `customer_data_as_asset.md` — Decision: what's our data worth and can we productize it? 5-component valuation framework + M&A multiplier with carve-out impact + 3 productization paths with prerequisites + 10-item M&A diligence prep checklist + quarterly contractual constraint audit pattern.
  - `data_team_org_evolution.md` — Decision: what role next, when to centralize vs embed? 5-stage map (seed → late-stage) with specific role definitions + centralize-vs-embed-vs-federated triggers + 6 anti-patterns ("hiring data scientist as first data hire" etc.).
- **cs-cdo-advisor** agent (`./c-level-advisor/c-level-agents/agents/cs-cdo-advisor.md`) — decision-driven realist orchestrating the skill. Voice: "What decision does this data drive?" Refuses to recommend tooling before naming the consumer. Treats AI training data as both contractual liability and strategic asset.
- **`/cs:cdo-review`** slash command (`./c-level-advisor/c-level-agents/skills/cdo-review/SKILL.md`) — 6-question forcing interrogation pattern matching the /cs:cfo-review / /cs:gc-review etc. shape.
- **cs-cdo-advisor voice spec** added to `persona-voices.md`.

### Why This Matters

By 2026 every B2B SaaS founder is asking three questions the existing C-level skills can't fully answer:
1. **"Can we train our model on customer data?"** — overlaps cs-ciso (security), cs-general-counsel (contracts), and engineering (tactics), but none of them owns the strategic data picture.
2. **"What's the right data architecture — and when?"** — engineering's database-designer and observability-designer cover tactics, but the warehouse-vs-lakehouse-vs-mesh decision is stage-driven, not technology-driven.
3. **"What's our data actually worth in M&A?"** — this comes up at every Series B+ and has no home in existing skills.

This skill fills that gap with **deterministic decision logic** (not survey prose), explicit kill criteria, and a hard rule against duplicating engineering data skills.

### Built with Karpathy-Coder Discipline

This PR was the first in this repo built under explicit karpathy-coder guidance:
- **Principle 1 (Think before coding):** assumptions surfaced upfront, verifiable success criteria locked before any file was written.
- **Principle 2 (Simplicity first):** rejected "generic governance survey" framing; each tool/reference covers ONE decision; refused to add scope ("data product strategy picker" doesn't try to also do data quality, RAG, or schema design).
- **Principle 3 (Surgical changes):** touched only the files in the locked plan. Caught one scope-creep attempt (adding cs-general-counsel-advisor voice spec while editing persona-voices.md) and reverted it — that gap belongs in a separate PR.
- **Principle 4 (Goal-driven execution):** all 3 Python tools smoke-tested with embedded samples before commit (audit: 7 sources → 2 NO-GO / 2 MITIGATE / 3 GO; strategy picker: Series A → LAKEHOUSE; valuator: 8.2/10 STRONG moat).

### Changed

- **Total skills:** 264 → 265 (+1 chief-data-officer-advisor)
- **cs-* agents:** 29 → 30 (+1 cs-cdo-advisor in c-level-agents plugin)
- **/cs:* slash commands:** 17 → 18 (+1 /cs:cdo-review)
- **Python tools:** 361 → 364 (+3 in chief-data-officer-advisor/scripts/)
- **References:** 490 → 494 (+4 in chief-data-officer-advisor/references/)
- **c-level-skills** plugin: v2.5.1 → v2.5.2 (description expanded; 29 → 30 skills, 9 → 10 cs-* agents)
- **c-level-agents** plugin: v1.1.0 → v1.2.0 (description expanded with CDO; new agent; +`chief-data-officer`, `cdo`, `ai-training-data`, `data-product-strategy`, `data-as-asset` keywords)

### Known follow-ups (NOT included this PR per surgical scope)

- The `cs-general-counsel-advisor` voice spec is missing from `persona-voices.md` (introduced in v2.5.1 but not added to the voice reference). Will be addressed in a separate small PR alongside other voice cleanup.
- Phase 2 remainder (4 more C-roles: CAIO AI, CCO customer, VPE engineering execution, CCO comms) deferred to v2.5.3+.

### Disclaimer

The `chief-data-officer-advisor` skill surfaces strategic decisions but is **not legal advice** for AI training, **not a replacement for outside counsel** for productization/licensing decisions, and **not a tactical data engineering skill**. For tactical data engineering, see the engineering/ domain (`database-designer`, `observability-designer`, `data-quality-auditor`, `sql-database-assistant`, `rag-architect`, `llm-cost-optimizer`).

## [2.5.1] - 2026-05-12 — general-counsel-advisor: the gstack-can't-touch lane

### Added — C-Level Advisory

- **general-counsel-advisor** skill (`./c-level-advisor/skills/general-counsel-advisor/`) — full standalone C-role skill backing the `/cs:gc-review` command (which previously had no underlying skill). 2 stdlib Python tools, 3 reference docs.
  - **`contract_risk_scanner.py`** — Scans contract text for 12 founder-killer clause patterns: auto-renewal with long notice (>30 day), customer-indemnity-carved-out-from-cap, one-sided indemnity, vague IP ownership, aggressive non-compete (>1 year), one-sided choice-of-law/venue, one-sided force majeure, missing DPA when personal data flows, MFN pricing, one-sided audit rights, broad non-solicit, perpetual license-back. Outputs ranked findings (CRITICAL/HIGH/MEDIUM) with excerpt, why-it-matters, and suggested redline. Stdlib-only, JSON or text output. Embedded sample MSA detects 7 risks across all 3 severity levels.
  - **`term_sheet_analyzer.py`** — Scores a term sheet 0-100 across 12 dimensions: liquidation preference (1x non-participating vs participating vs multi-preference), anti-dilution (broad-based weighted average vs narrow vs full ratchet), option pool (pre-money vs post-money + size), board composition (founder vs investor vs independent seats), vesting + acceleration (single vs double trigger), pro-rata, drag-along (founder consent / price floor), protective provisions (NVCA standard vs aggressive), information rights, dividends (none / non-cumulative / cumulative), valuation/dilution sanity, holistic posture. Outputs FOUNDER_FRIENDLY / NEGOTIATE / HOSTILE grade plus per-clause flags. Stdlib-only, JSON-input + JSON-or-text output.
  - **`references/contracts_playbook.md`** — 7 standard startup contracts (MSA, customer SaaS, NDA, DPA, employment, contractor, equity), top redlines per type, quick triage heuristics.
  - **`references/ip_and_regulatory.md`** — Full IP strategy (patents, copyright, trademark, trade secrets, invention assignment, OSS license compliance for permissive/weak-copyleft/strong-copyleft including AGPL) plus regulatory trigger matrix (HIPAA, PCI DSS, BSA/AML, FDA 510(k), MDR, GDPR, CCPA, COPPA, securities, ITAR, EU AI Act, telehealth, insurance) with SOC 2 → ISO 27001 → ISO 42001 sequencing and when-to-hire-a-GC criteria.
  - **`references/term_sheet_decoder.md`** — Full term sheet glossary, founder-friendly defaults cheat sheet, the three clauses that matter most (liquidation preference, option pool pre/post-money, anti-dilution), and negotiation strategy.
- **cs-general-counsel-advisor** agent (`./c-level-advisor/c-level-agents/agents/cs-general-counsel-advisor.md`) — risk-paranoid persona orchestrating the skill via `/cs:gc-review`. Distinct voice: "Before we sign, three things need to be settled in writing." Hard rule: never gives definitive legal advice; always escalates to qualified outside counsel.
- **`/cs:gc-review`** updated to invoke the new tools and reference the skill (the command previously pointed at a planned skill with a CHANGELOG note).

### Why This Matters

YC Garry Tan's `gstack` has zero coverage for General Counsel — its "executives" are all software-shipping personas (CEO = scope-cutter, Eng Mgr = test matrix). But legal exposure is where startups most often discover a problem after it's expensive to fix: a missed DPA exposes the company to GDPR fines, vague IP clauses kill acquisition deals years later, full-ratchet anti-dilution silently transfers 5-15% of founder equity at the next down round. This is the first plugin in the founder-mode lineup to outclass gstack on a domain it doesn't even attempt.

### Changed

- **Total skills:** 263 → 264 (+1 general-counsel-advisor)
- **cs-* agents:** 28 → 29 (+1 cs-general-counsel-advisor in c-level-agents plugin)
- **Python tools:** 359 → 361 (+2 in general-counsel-advisor/scripts/)
- **References:** 487 → 490 (+3 in general-counsel-advisor/references/)
- **c-level-skills** plugin: v2.5.0 → v2.5.1 (description expanded; 28 → 29 skills, 8 → 9 cs-* agents)
- **c-level-agents** plugin: v1.0.0 → v1.1.0 (description expanded with General Counsel; new agent added; +`contract-review`, `term-sheet`, `ip-strategy` keywords)

### Disclaimer

The `general-counsel-advisor` skill and `cs-general-counsel-advisor` agent are **not legal advice**. Every output surfaces questions to bring to qualified counsel; both Python tools and all 3 references repeatedly remind users to engage licensed attorneys for binding decisions. The skill is positioned as a triage layer — useful for catching the obvious traps before $500/hour counsel time, never as a substitute.

## [2.5.0] - 2026-05-12 — c-level-agents: Founder-Mode Executive Team

### Added — C-Level Advisory

- **c-level-agents** plugin (`./c-level-advisor/c-level-agents/`) — surfaces the existing 28 c-level skills through a founder-mode interface of cs-* persona agents and `/cs:*` slash commands. New marketplace entry registered separately (category: leadership).
- **8 new cs-* persona agents** with distinct cognitive voices, completing agent coverage for every C-role:
  - `cs-cfo-advisor` (numerate skeptic) wraps cfo-advisor
  - `cs-cmo-advisor` (narrative-first) wraps cmo-advisor
  - `cs-cro-advisor` (pipeline-paranoid) wraps cro-advisor
  - `cs-cpo-advisor` (JTBD-driven) wraps cpo-advisor
  - `cs-coo-advisor` (execution OS) wraps coo-advisor
  - `cs-chro-advisor` (people-systems) wraps chro-advisor
  - `cs-ciso-advisor` (risk-paranoid) wraps ciso-advisor
  - `cs-chief-of-staff` (router & synthesist) wraps chief-of-staff
- **17 /cs:* slash commands** delivered as sub-skills under `c-level-agents/skills/`:
  - **Forcing-question office hours (8):** `/cs:office-hours` (YC-style 6-question intake), `/cs:cfo-review`, `/cs:cmo-review`, `/cs:cpo-review`, `/cs:cro-review`, `/cs:cto-review`, `/cs:ciso-review`, `/cs:gc-review` (General Counsel — a lane gstack has zero of)
  - **Strategic sprint pipeline (5):** `/cs:brief` → `/cs:boardroom` (6-phase deliberation with Phase 2 isolation + devil's advocate pass) → `/cs:decide` (two-layer memory log with preserved dissent) → `/cs:execute` (90-day plan with weekly milestones + DRIs) → `/cs:post-mortem` (scored against pre-committed criteria and revisited dissent)
  - **Meta + safety (4):** `/cs:founder-mode` (auto-router — the killer command), `/cs:onboard` (12-question founder interview → `~/.claude/company-context.md`), `/cs:cross-eval` (multi-model consensus with graceful degradation to Claude-only adversarial mode when Codex/Gemini absent), `/cs:freeze` (cooldown lock on irreversible decisions with `/cs:unfreeze` audit trail)
- **References:** `c-level-agents/references/persona-voices.md` (voice specs per role — moderate aggression: bookend opening + closing, neutral analysis body) and `c-level-agents/references/llm-wiki-bridge.md` (Markdown-only persistent memory via `llm-wiki` — the answer to gstack's gbrain Postgres+pgvector dependency).
- **c-level-skills marketplace entry** description expanded and version bumped to v2.5.0 to reflect the bundled plugin layer.

### Why This Matters

Garry Tan's `gstack` (~66K stars) demonstrated the power of slash-command-first, forcing-question agent gearing — but its "executives" are all software-shipping personas (CEO = scope-cutter, Eng Mgr = test matrix). This release brings the same pattern to **real business decisions**: CFO with unit economics, CMO with positioning, General Counsel with contract risk, CISO with threat modeling, and a 6-phase boardroom that surpasses gstack's sequential review chain with Phase 2 isolation + adversarial pass. Combined with this repo's pre-existing compliance (ra-qm-team), finance, marketing, business-growth, and product domains, this is the business-domain answer to founder-mode — broader role coverage, real frameworks, Markdown-only memory, and explicit voice differentiation.

### Changed

- **Total skills:** 246 → 263 (+17 from c-level-agents sub-skills)
- **cs-* agents:** 20 → 28 (+8 new c-level personas inside the plugin)
- **Slash commands:** 33 → 50 (+17 /cs:* commands as sub-skills)
- **Marketplace plugins:** 33 → 34 (+1 c-level-agents entry)
- **c-level-skills** plugin: v2.2.3 → v2.5.0

## [2.4.5] - 2026-05-11 — Reliability Portfolio + Count-Truth Reconciliation

### Added — Engineering POWERFUL

- **slo-architect** — End-to-end SLO/SLI/error-budget discipline per Google SRE Workbook. Generates structured SLO definitions and refuses to render if required fields (owner, error-budget policy, SLI numerator/denominator) are missing (`slo_designer.py`). Computes error budget and the canonical multi-window burn-rate alert thresholds — fast (1h/5m, page), slow (6h/30m, page), ticket (3d/6h) — with PromQL-shaped output ready to paste (`error_budget_calculator.py`). Reviews existing SLO docs for the 7 common bugs: target too high (≥99.99%), target too low (≤99%), window too short (<7d), window too long (>90d), no SLI definition, no error budget policy, CPU-as-SLI (`slo_review.py`). 4 references on SLO principles, SLI design (5 types), error budget math, and composition with the rest of the portfolio. Asset templates for SLO YAML and error budget policy. New `/slo-design` slash command. Karpathy complexity 95/100. Composes explicitly with feature-flags-architect (rollout abort uses SLO burn-rate), chaos-engineering (blast-radius bounded by SLO error budget), kubernetes-operator (Capability Level 4 requires SLOs).
- **ship-gate** — Pre-production audit skill from external contributor @rx4u (originally PR #527, re-applied to post-restructure dev layout). Scans codebases across 8 categories — security, database, deployment, code quality, AI/LLM, dependencies, frontend, observability — with 89 automated and manual checks. Intercepts deploy-intent phrases ("push to production", "ship it", "go live") and blocks until critical issues resolve. Stack-agnostic (Node/Next/React/Vue/Svelte/Astro/Express/Python/Django/Flask/etc.). Stdlib-only Python scanner (`ship_gate_scanner.py`, ~1230 LOC) with JSON output, ANSI color, interactive manual prompts, and exit codes (0=CLEAR, 1=CRITICAL, 2=HIGH).
- **feature-flags-architect** — End-to-end feature-flag discipline. Detects stale flags as debt (`flag_debt_scanner.py`), generates phased rollout plans across ring/linear/log/cohort strategies (`rollout_planner.py`), and audits every flag for documented kill switch (`kill_switch_audit.py`). 4 references on flag taxonomy, provider comparison (LaunchDarkly / GrowthBook / Statsig / Unleash / Flipt / DIY), rollout strategies, and lifecycle. Ships standalone plugin AND in the engineering-advanced-skills bundle. New `/flag-cleanup` slash command.
- **kubernetes-operator** — End-to-end Kubernetes Operator discipline. Validates CRDs against operator-pattern best practices (`crd_validator.py`), lints Go reconcile functions for anti-patterns like `time.Sleep`, spec mutation, missing requeue, finalizer imbalance (`reconcile_lint.py`), and scores operators against OperatorHub Capability Levels 1-5 (`operator_capability_audit.py`). 4 references on operator pattern, CRD design, reconcile loop patterns, and framework comparison (controller-runtime / kubebuilder / operator-sdk / metacontroller / KOPF). Asset templates for production CRD YAML and Go controller skeleton (both pass linters). New `/operator-audit` slash command. NOT a generic k8s skill — specifically the Operator pattern. Self-tested: linters caught 4 real bugs in their own asset templates during build.
- **chaos-engineering** — End-to-end chaos engineering discipline. Generates structured experiment plans with hypothesis + steady-state + blast-radius + abort-criteria (`experiment_designer.py`), computes blast radius with GREEN/YELLOW/RED risk score against monthly error budget (`blast_radius_calculator.py`), and produces blameless postmortems with blame-language detection (`experiment_postmortem.py`). 4 references on the 4 founding principles + 5th abort-criteria principle, hypothesis/steady-state/abort design, the 7-attack taxonomy (latency / error / resource / network-partition / dependency / time / infrastructure), and tooling landscape (Chaos Toolkit / Chaos Mesh / Litmus / Gremlin / AWS FIS / DIY). Templates for plans and postmortems. New `/chaos-experiment` slash command. Composes explicitly with feature-flags-architect (kill switches as abort triggers) and kubernetes-operator (operators are common chaos targets). Karpathy complexity 95/100 — best score in the new portfolio.

### Added — Repo infrastructure

- **scripts/sync_skill_bundles.py** — mirror standalone plugin payloads into their domain-bundled location; `--check` exits 1 on drift, `--sync` rewrites the mirror. Locks in the dual-publish invariant for every new skill.
- **scripts/check_plugin_json.py** — strict ClawHub schema validator (exactly 8 fields, semver, `author{name,url}`, `skills` as string or array — bare `"./"` rejected per Claude Code v2.1.107+). Verified against all 31 existing plugin.json files.

### Changed

- **Total skills:** 235 (v2.3.0 claim) → 246 (file-system truth via `find . -name SKILL.md` minus 4 distribution duplicates). +5 new skills this cycle (slo-architect, ship-gate, feature-flags-architect, kubernetes-operator, chaos-engineering); +6 discovered during #608/#609 reconciliation.
- **Python tools:** 314 → 359 (`find . -path '*/scripts/*.py' | wc -l`)
- **References:** 435 → 485 (`find . -path '*/references/*.md' | wc -l`)
- **Agents:** 28 → 27 (file-system truth: 20 `cs-*` + 7 personas. Previous "30" miscounted README/TEMPLATE as agents)
- **Slash commands:** 27 → 33 (`find commands -name '*.md' | wc -l`)
- **Marketplace plugins:** 30 → 33 (registered in `.claude-plugin/marketplace.json`)
- **engineering-advanced-skills** plugin: v2.3.3 → v2.4.2
- **marketplace.json**: `feature-flags-architect`, `kubernetes-operator`, and `chaos-engineering` registered as standalone plugins

### Fixed

- `tests/test_skill_integrity.py::TestScriptDirectories::test_scripts_dirs_have_python_files` — was rejecting valid skills shipping `.mjs`/`.js`/`.ts`/`.sh` scripts (e.g., `full-page-screenshot`). Now accepts any executable script extension while keeping the "scripts/ dir is non-empty" intent.
- **#608, #609 — Count claims aligned to ground-truth.** Every metric in `CLAUDE.md`, `README.md`, `docs/`, `mkdocs.yml`, and `.claude-plugin/marketplace.json` now reproduces from a deterministic `find` or `python3 -c "import json"` command. Stale claims of "188 skills", "30 agents", "3 personas", "235 skills" (current-state) were replaced with file-system truth. Per-domain marketplace breakdown also reconciled: engineering-advanced 40→67 unique, engineering-core 32→51, marketing 44→45, c-level 28→34, product 13→17, finance 3→4. Domains ra-qm-team (14), project-management (9), business-growth (5) unchanged.
- **skill-security-auditor** — self-skip false positives via `noqa` directive (the auditor was flagging its own scanner code).

## [2.2.0] - 2026-03-31

### Added — Security Skills Suite & Self-Eval

**6 New Security Skills (engineering-team):**
- **adversarial-reviewer** — Adversarial code review with 3 hostile personas (Saboteur, New Hire, Security Auditor) to break self-review monoculture
- **ai-security** — ATLAS-mapped prompt injection detection, model inversion & data poisoning risk scoring (`ai_threat_scanner.py`)
- **cloud-security** — IAM privilege escalation paths, S3 public access checks, security group detection across AWS/Azure/GCP (`cloud_posture_check.py`)
- **incident-response** — SEV1-SEV4 triage, 14-type incident taxonomy, NIST SP 800-61 forensics (`incident_triage.py`)
- **red-team** — MITRE ATT&CK kill-chain planning, effort scoring, choke point identification (`engagement_planner.py`)
- **threat-detection** — Hypothesis-driven threat hunting, IOC sweep generation, z-score anomaly detection (`threat_signal_analyzer.py`)

**1 New Engineering Skill (engineering/):**
- **self-eval** — Honest AI work quality evaluation with two-axis scoring (substance + execution), score inflation detection, devil's advocate reasoning, and session persistence

**1 New Engineering Skill (engineering-team/):**
- **snowflake-development** — Snowflake data warehouse development, SQL optimization, and data pipeline patterns

### Changed
- **Total skills:** 205 → 223 across 9 domains
- **Python tools:** 268 → 298 CLI scripts (all stdlib-only, verified)
- **Reference guides:** 384 → 416
- **Agents:** 16 → 23
- **Commands:** 19 → 22
- **Engineering Core:** 30 → 36 skills
- **Engineering POWERFUL:** 35 → 36 skills
- **MkDocs docs site:** 269 generated pages, 301 HTML pages
- All domain plugin.json files updated to v2.2.0
- Marketplace description updated with new skill counts
- Codex CLI and Gemini CLI indexes re-synced

### Documentation
- Root CLAUDE.md, README.md, docs/index.md, docs/getting-started.md updated with new counts
- engineering-team/CLAUDE.md updated with security skills section
- mkdocs.yml site_description updated
- New skill docs pages auto-generated for all 8 new skills

### Backward Compatibility
- All existing SKILL.md files, scripts, and references unchanged
- No skill removals or renames
- Plugin source paths unchanged — existing installations will not break
- All new skills are additive only

---

## [2.1.2] - 2026-03-10

### Changed — Product Team Quality & Cross-Domain Integration

**Landing Page Generator — TSX + Brand Voice Integration:**
- Landing page scaffolder now defaults to **Next.js/React TSX output** with Tailwind CSS (HTML preserved via `--format html`)
- 4 Tailwind design styles: `dark-saas`, `clean-minimal`, `bold-startup`, `enterprise` with complete class mappings
- 7 section generators: nav, hero, features, testimonials, pricing, CTA, footer
- Brand voice integration: generation workflow now includes brand voice analysis (step 2) using `marketing-skill/content-production/scripts/brand_voice_analyzer.py` to map voice profile to design style + copy framework
- Added Related Skills cross-references to SKILL.md

**Documentation Updates:**
- `product-team/CLAUDE.md` — Added Workflow 4 (Brand-Aligned Landing Page), updated scaffolder section with TSX docs, added Cross-Domain Integration section
- `product-team/README.md` — Fixed ghost script references (removed 7 scripts that never existed), corrected skill/tool/agent/command counts
- `product-team/.codex/instructions.md` — Added brand voice cross-domain workflow and TSX default note

### Fixed
- **competitive-teardown/SKILL.md** — Fixed 6 broken file references (`DATA_COLLECTION.md` → `references/data-collection-guide.md`, `TEMPLATES.md` → `references/analysis-templates.md`)
- **saas-scaffolder/scripts/project_bootstrapper.py** — Fixed f-string backslash syntax incompatible with Python <3.12
- **237 Python scripts verified** — All pass `--help` without errors (previous session fixed 25 scripts across all domains)

### Added
- `landing-page-generator/SKILL.md` — Brand voice analysis as prerequisite step in generation workflow
- Codex and Gemini skill indexes re-synced with updated SKILL.md content

### Backward Compatibility
- `--format html` still works for landing page scaffolder (TSX is new default)
- All existing script CLIs and arguments unchanged
- No skill removals or renames
- Plugin source paths unchanged — existing installations will not break

---

## [2.1.1] - 2026-03-07

### Changed — Tessl Quality Optimization (#287)
18 skills optimized from 66-83% to 85-100% via `tessl skill review --optimize`:

| Skill | Before | After |
|-------|--------|-------|
| `project-management/confluence-expert` | 66% | 94% |
| `project-management/jira-expert` | 77% | 97% |
| `product-team/product-strategist` | 76% | 85%+ |
| `marketing-skill/campaign-analytics` | 70% | 85%+ |
| `business-growth/customer-success-manager` | 70% | 85%+ |
| `business-growth/revenue-operations` | 70% | 85%+ |
| `finance/financial-analyst` | 70% | 85%+ |
| `engineering-team/senior-secops` | 75% | 94% |
| `marketing-skill/prompt-engineer-toolkit` | 79% | 90% |
| `ra-qm-team/quality-manager-qms-iso13485` | 76% | 85%+ |
| `engineering-team/senior-security` | 80% | 93% |
| `engineering-team/playwright-pro` | 82% | 100% |
| `engineering-team/senior-backend` | 83% | 100% |
| `engineering-team/senior-qa` | 83% | 100% |
| `engineering-team/senior-ml-engineer` | 82% | 99% |
| `engineering-team/ms365-tenant-manager` | 83% | 100% |
| `engineering-team/aws-solution-architect` | 83% | 94% |
| `c-level-advisor/cto-advisor` | 82% | 99% |
| `marketing-skill/marketing-demand-acquisition` | 72% | 99% |

### Fixed
- Created missing `finance/financial-analyst/references/industry-adaptations.md` (reference was declared but file didn't exist)
- Removed dead `project-management/packaged-skills/` folder (zip files redundant)

### Added
- `SKILL_PIPELINE.md` — Mandatory 9-phase production pipeline for all skill work

### Verified
- Claude Code compliance: 18/18 pass (after fix)
- All YAML frontmatter valid
- All file references resolve
- All SKILL.md files under 500 lines

## [Unreleased]

### Added
- **skill-security-auditor** (POWERFUL tier) — Security audit and vulnerability scanner for AI agent skills. Scans for malicious code, prompt injection, data exfiltration, supply chain risks, and privilege escalation. Zero dependencies, PASS/WARN/FAIL verdicts.
- `engineering/git-worktree-manager` enhancements:
  - Added `scripts/worktree_manager.py` (worktree creation, port allocation, env sync, optional dependency install)
  - Added `scripts/worktree_cleanup.py` (stale/dirty/merged analysis with safe cleanup options)
  - Added extracted references and new skill README
- `engineering/mcp-server-builder` enhancements:
  - Added `scripts/openapi_to_mcp.py` (OpenAPI -> MCP manifest + scaffold generation)
  - Added `scripts/mcp_validator.py` (tool definition validation and strict checks)
  - Extracted templates/guides into references and added skill README
- `engineering/changelog-generator` enhancements:
  - Added `scripts/generate_changelog.py` (conventional commit parsing + Keep a Changelog rendering)
  - Added `scripts/commit_linter.py` (strict conventional commit validation)
  - Extracted CI/format/monorepo docs into references and added skill README
- `engineering/ci-cd-pipeline-builder` enhancements:
  - Added `scripts/stack_detector.py` (stack and tooling detection)
  - Added `scripts/pipeline_generator.py` (GitHub Actions / GitLab CI YAML generation)
  - Extracted platform templates into references and added skill README
- `marketing-skill/prompt-engineer-toolkit` enhancements:
  - Added `scripts/prompt_tester.py` (A/B prompt evaluation with per-case scoring)
  - Added `scripts/prompt_versioner.py` (prompt history, diff, changelog management)
  - Extracted prompt libraries/guides into references and added skill README

### Changed
- Refactored the five enhanced skills to slim, workflow-first `SKILL.md` documents aligned to Anthropic best practices.
- Updated `engineering/.claude-plugin/plugin.json` metadata:
  - Description now reflects 25 advanced engineering skills
  - Version bumped from `1.0.0` to `1.1.0`
- Updated root `README.md` with a dedicated \"Recently Enhanced Skills\" section.

### Planned
- Complete Anthropic best practices refactoring (5/42 skills remaining)
- Production Python tools for remaining RA/QM skills
- Marketing expansion: SEO Optimizer, Social Media Manager skills

---

## [2.0.0] - 2026-02-16

### ⚡ POWERFUL Tier — 25 New Skills

A new tier of advanced, deeply-engineered skills with comprehensive tooling:

- **incident-commander** — Incident response playbook with severity classifier, timeline reconstructor, and PIR generator
- **tech-debt-tracker** — Codebase debt scanner with AST parsing, debt prioritizer, and trend dashboard
- **api-design-reviewer** — REST API linter, breaking change detector, and API design scorecard
- **interview-system-designer** — Interview loop designer, question bank generator, and hiring calibrator
- **migration-architect** — Migration planner, compatibility checker, and rollback generator
- **observability-designer** — SLO designer, alert optimizer, and dashboard generator
- **dependency-auditor** — Multi-language dependency scanner, license compliance checker, and upgrade planner
- **release-manager** — Automated changelog generator, semantic version bumper, and release readiness checker
- **database-designer** — Schema analyzer with ERD generation, index optimizer, and migration generator
- **rag-architect** — RAG pipeline builder, chunking optimizer, and retrieval evaluator
- **agent-designer** — Multi-agent architect, tool schema generator, and agent performance evaluator
- **skill-tester** — Meta-skill validator, script tester, and quality scorer
- **agent-workflow-designer** — Multi-agent orchestration system designer with sequential, parallel, router, orchestrator, and evaluator patterns
- **api-test-suite-builder** — API route scanner and test suite generator across frameworks (Next.js, Express, FastAPI, Django REST)
- **changelog-generator** — Conventional commit parser, semantic version bumper, and structured changelog generator
- **ci-cd-pipeline-builder** — Stack-aware CI/CD pipeline generator for GitHub Actions, GitLab CI, and more
- **codebase-onboarding** — Codebase analyzer and onboarding documentation generator for new team members
- **database-schema-designer** — Database schema design and modeling tool with migration support
- **env-secrets-manager** — Environment and secrets management across dev/staging/prod lifecycle
- **git-worktree-manager** — Systematic Git worktree management for parallel development workflows
- **mcp-server-builder** — MCP (Model Context Protocol) server scaffolder and implementation guide
- **monorepo-navigator** — Monorepo management for Turborepo, Nx, pnpm workspaces, and Lerna
- **performance-profiler** — Systematic performance profiling for Node.js, Python, and Go applications
- **pr-review-expert** — Structured code review for GitHub PRs and GitLab MRs with systematic analysis
- **runbook-generator** — Production-grade operational runbook generator with stack detection

### 🆕 New Domains & Skills

- **business-growth** domain (3 skills):
  - `customer-success-manager` — Onboarding, retention, expansion, health scoring (2 Python tools)
  - `sales-engineer` — Technical sales, solution design, RFP responses (2 Python tools)
  - `revenue-operations` — Pipeline analytics, forecasting, process optimization (2 Python tools)
- **finance** domain (1 skill):
  - `financial-analyst` — DCF valuation, budgeting, forecasting, financial modeling (3 Python tools)
- **marketing** addition:
  - `campaign-analytics` — Multi-touch attribution, funnel conversion, campaign ROI (3 Python tools)

### 🔄 Anthropic Best Practices Refactoring (37/42 Skills)

Major rewrite of existing skills following Anthropic's agent skills specification. Each refactored skill received:
- Professional metadata (license, version, category, domain, keywords)
- Trigger phrases for better Claude activation
- Table of contents with proper section navigation
- Numbered workflows with validation checkpoints
- Progressive Disclosure Architecture (PDA)
- Concise SKILL.md (<200 lines target) with layered reference files

**Engineering skills refactored (14):**
- `senior-architect`, `senior-frontend`, `senior-backend`, `senior-fullstack`
- `senior-qa`, `senior-secops`, `senior-security`, `code-reviewer`
- `senior-data-engineer`, `senior-computer-vision`, `senior-ml-engineer`
- `senior-prompt-engineer`, `tdd-guide`, `tech-stack-evaluator`

**Product & PM skills refactored (5):**
- `product-manager-toolkit`, `product-strategist`, `agile-product-owner`
- `ux-researcher-designer`, `ui-design-system`

**RA/QM skills refactored (12):**
- `regulatory-affairs-head`, `quality-manager-qmr`, `quality-manager-qms-iso13485`
- `capa-officer`, `quality-documentation-manager`, `risk-management-specialist`
- `information-security-manager-iso27001`, `mdr-745-specialist`, `fda-consultant-specialist`
- `qms-audit-expert`, `isms-audit-expert`, `gdpr-dsgvo-expert`

**Marketing skills refactored (4):**
- `marketing-demand-acquisition`, `marketing-strategy-pmm`
- `content-creator`, `app-store-optimization`

**Other refactored (2):**
- `aws-solution-architect`, `ms365-tenant-manager`

### 🔧 Elevated Skills
- `scrum-master` and `senior-pm` elevated to POWERFUL tier — PR #190

### 🤖 Platform Support
- **OpenAI Codex support** — Full compatibility without restructuring — PR #43, #45, #47
- **Claude Code native marketplace** — `marketplace.json` and plugin support — PR #182, #185
- **Codex skills sync** — Automated symlink workflow for Codex integration

### 📊 Stats
- **86 total skills** across 9 domains (up from 42 across 6)
- **92+ Python automation tools** (up from 20+)
- **26 POWERFUL-tier skills** in `engineering/` domain (including skill-security-auditor)
- **37/42 original skills refactored** to Anthropic best practices

### Fixed
- CI workflows (`smart-sync.yml`, `pr-issue-auto-close.yml`) — PR #193
- Installation documentation (Issue #189) — PR #193
- Plugin JSON with correct counts and missing domains — PR #186
- PM skills extracted from zips into standard directories — PR #184, #185
- Marketing skill count corrected (6 total) — PR #182
- Codex skills sync workflow fixes — PR #178, #179, #180
- `social-media-analyzer` restructured with proper organization — PR #147, #151

---

## [1.1.0] - 2025-10-21 - Anthropic Best Practices Refactoring (Phase 1)

### Changed — Marketing & C-Level Skills

**Enhanced with Anthropic Agent Skills Specification:**

**Marketing Skills (3 skills):**
- Added professional metadata (license, version, category, domain)
- Added keywords sections for better discovery
- Enhanced descriptions with explicit triggers
- Added python-tools and tech-stack documentation

**C-Level Skills (2 skills):**
- Added professional metadata with frameworks
- Added keywords sections (20+ keywords per skill)
- Enhanced descriptions for better Claude activation
- Added technical and strategic terminology

### Added
- `documentation/implementation/SKILLS_REFACTORING_PLAN.md` — Complete 4-phase refactoring roadmap
- `documentation/PYTHON_TOOLS_AUDIT.md` — Comprehensive tools quality assessment

**Refactoring Progress:** 5/42 skills complete (12%)

---

## [1.0.2] - 2025-10-21

### Added
- `LICENSE` file — Official MIT License
- `CONTRIBUTING.md` — Contribution guidelines and standards
- `CODE_OF_CONDUCT.md` — Community standards (Contributor Covenant 2.0)
- `SECURITY.md` — Security policy and vulnerability reporting
- `CHANGELOG.md` — Version history tracking

### Documentation
- Complete GitHub repository setup for open source
- Professional community health files
- Clear contribution process
- Security vulnerability handling

---

## [1.0.1] - 2025-10-21

### Added
- GitHub Star History chart to README.md
- Professional repository presentation

### Changed
- README.md table of contents anchor links fixed
- Project management folder reorganized (packaged-skills/ structure)

---

## [1.0.0] - 2025-10-21

### Added — Complete Initial Release

**42 Production-Ready Skills across 6 Domains:**

#### Marketing Skills (3)
- `content-creator` — Brand voice analyzer, SEO optimizer, content frameworks
- `marketing-demand-acquisition` — Demand gen, paid media, CAC calculator
- `marketing-strategy-pmm` — Positioning, GTM, competitive intelligence

#### C-Level Advisory (2)
- `ceo-advisor` — Strategy analyzer, financial scenario modeling, board governance
- `cto-advisor` — Tech debt analyzer, team scaling calculator, engineering metrics

#### Product Team (5)
- `product-manager-toolkit` — RICE prioritizer, interview analyzer, PRD templates
- `agile-product-owner` — User story generator, sprint planning
- `product-strategist` — OKR cascade generator, strategic planning
- `ux-researcher-designer` — Persona generator, user research
- `ui-design-system` — Design token generator, component architecture

#### Project Management (6)
- `senior-pm` — Portfolio management, stakeholder alignment
- `scrum-master` — Sprint ceremonies, agile coaching
- `jira-expert` — JQL mastery, configuration, dashboards
- `confluence-expert` — Knowledge management, documentation
- `atlassian-admin` — System administration, security
- `atlassian-templates` — Template design, 15+ ready templates

#### Engineering — Core (9)
- `senior-architect` — Architecture diagrams, dependency analysis, ADRs
- `senior-frontend` — React components, bundle optimization
- `senior-backend` — API scaffolder, database migrations, load testing
- `senior-fullstack` — Project scaffolder, code quality analyzer
- `senior-qa` — Test suite generator, coverage analyzer, E2E tests
- `senior-devops` — CI/CD pipelines, Terraform, deployment automation
- `senior-secops` — Security scanner, vulnerability assessment, compliance
- `code-reviewer` — PR analyzer, code quality checker
- `senior-security` — Threat modeling, security audits, pentesting

#### Engineering — AI/ML/Data (5)
- `senior-data-scientist` — Experiment designer, feature engineering, statistical analysis
- `senior-data-engineer` — Pipeline orchestrator, data quality validator, ETL
- `senior-ml-engineer` — Model deployment, MLOps setup, RAG system builder
- `senior-prompt-engineer` — Prompt optimizer, RAG evaluator, agent orchestrator
- `senior-computer-vision` — Vision model trainer, inference optimizer, video processor

#### Regulatory Affairs & Quality Management (12)
- `regulatory-affairs-head` — Regulatory pathway analyzer, submission tracking
- `quality-manager-qmr` — QMS effectiveness monitor, compliance dashboards
- `quality-manager-qms-iso13485` — QMS compliance checker, design control tracker
- `capa-officer` — CAPA tracker, root cause analyzer, trend analysis
- `quality-documentation-manager` — Document version control, technical file builder
- `risk-management-specialist` — Risk register manager, FMEA calculator
- `information-security-manager-iso27001` — ISMS compliance, security risk assessment
- `mdr-745-specialist` — MDR compliance checker, UDI generator
- `fda-consultant-specialist` — FDA submission packager, QSR compliance
- `qms-audit-expert` — Audit planner, finding tracker
- `isms-audit-expert` — ISMS audit planner, security controls assessor
- `gdpr-dsgvo-expert` — GDPR compliance checker, DPIA generator

### Documentation
- Comprehensive README.md with all 42 skills
- Domain-specific README files (6 domains)
- CLAUDE.md development guide
- Installation and usage guides
- Real-world scenario walkthroughs

### Automation
- 20+ verified production-ready Python CLI tools
- 90+ comprehensive reference guides
- Atlassian MCP Server integration

---

## Version History Summary

| Version | Date | Skills | Domains | Key Changes |
|---------|------|--------|---------|-------------|
| 2.1.2 | 2026-03-10 | 170 | 9 | Landing page TSX output, brand voice integration, 25 script fixes |
| 2.1.1 | 2026-03-07 | 170 | 9 | 18 skills optimized via Tessl, YAML frontmatter, agents + commands |
| 2.0.0 | 2026-02-16 | 86 | 9 | 26 POWERFUL-tier skills, 37 refactored, Codex support, 3 new domains |
| 1.1.0 | 2025-10-21 | 42 | 6 | Anthropic best practices refactoring (5 skills) |
| 1.0.2 | 2025-10-21 | 42 | 6 | GitHub repository pages (LICENSE, CONTRIBUTING, etc.) |
| 1.0.1 | 2025-10-21 | 42 | 6 | Star History, link fixes |
| 1.0.0 | 2025-10-21 | 42 | 6 | Initial release — 42 skills, 6 domains |

---

## Semantic Versioning

- **Major (x.0.0):** Breaking changes, major new domains, significant architecture shifts
- **Minor (1.x.0):** New skills, significant enhancements
- **Patch (1.0.x):** Bug fixes, documentation updates, minor improvements

---

[Unreleased]: https://github.com/alirezarezvani/claude-skills/compare/v2.1.2...HEAD
[2.1.2]: https://github.com/alirezarezvani/claude-skills/compare/v2.1.1...v2.1.2
[2.1.1]: https://github.com/alirezarezvani/claude-skills/compare/v2.0.0...v2.1.1
[2.0.0]: https://github.com/alirezarezvani/claude-skills/compare/v1.0.2...v2.0.0
[1.1.0]: https://github.com/alirezarezvani/claude-skills/compare/v1.0.1...v1.1.0
[1.0.2]: https://github.com/alirezarezvani/claude-skills/compare/v1.0.1...v1.0.2
[1.0.1]: https://github.com/alirezarezvani/claude-skills/compare/v1.0.0...v1.0.1
[1.0.0]: https://github.com/alirezarezvani/claude-skills/releases/tag/v1.0.0
