Sync ctx main 878774b495e0

Mirror GitHub main after graph artifact and test-isolation hardening. Upload was staged from git tracked files only, with an HF-specific dataset card.

.dedup-allowlist.txt

@@ -1,18 +1,18 @@
-# Dedup allowlist — pairs that look duplicate by cosine similarity
-# but are legitimately distinct. The dedup gate skips these in the
-# report.
-#
-# Format: one pair per line:
-#
-#     <slug_a> <slug_b>  # reason
-#
-# Slugs are matched case-sensitively against the entity's directory
-# name (e.g. `mattpocock-tdd`, not `mattpocock_tdd`). Order doesn't
-# matter — the gate canonicalises (low, high) before matching.
-#
-# Anything after `#` on a line is a comment.
-#
-# Examples (uncomment after reviewing the actual finding):
-#
-# strix-vulnerabilities-csrf strix-vulnerabilities-xss   # both web vuln playbooks; structurally similar but cover different attack classes
-# python-pro python-patterns                              # one is the agent prompt, the other is the pattern guide; intentional overlap
+# Dedup allowlist — pairs that look duplicate by cosine similarity
+# but are legitimately distinct. The dedup gate skips these in the
+# report.
+#
+# Format: one pair per line:
+#
+#     <slug_a> <slug_b>  # reason
+#
+# Slugs are matched case-sensitively against the entity's directory
+# name (e.g. `mattpocock-tdd`, not `mattpocock_tdd`). Order doesn't
+# matter — the gate canonicalises (low, high) before matching.
+#
+# Anything after `#` on a line is a comment.
+#
+# Examples (uncomment after reviewing the actual finding):
+#
+# strix-vulnerabilities-csrf strix-vulnerabilities-xss   # both web vuln playbooks; structurally similar but cover different attack classes
+# python-pro python-patterns                              # one is the agent prompt, the other is the pattern guide; intentional overlap

.gitattributes

@@ -1,4 +1,4 @@
-graph/wiki-graph.tar.gz filter=lfs diff=lfs merge=lfs -text
+graph/wiki-graph.tar.gz filter=lfs diff=lfs merge=lfs -text
 graph/skills-sh-catalog.json.gz filter=lfs diff=lfs merge=lfs -text
 graph/viz-overview.png filter=lfs diff=lfs merge=lfs -text
 graph/viz-security.png filter=lfs diff=lfs merge=lfs -text

.githooks/post-checkout

@@ -1,3 +1,3 @@
-#!/bin/sh
-command -v git-lfs >/dev/null 2>&1 || { echo >&2 "\nThis repository is configured for Git LFS but 'git-lfs' was not found on your path. If you no longer wish to use Git LFS, remove this hook by deleting the 'post-checkout' file in the hooks directory (set by 'core.hookspath'; usually '.git/hooks').\n"; exit 2; }
-git lfs post-checkout "$@"
+#!/bin/sh
+command -v git-lfs >/dev/null 2>&1 || { echo >&2 "\nThis repository is configured for Git LFS but 'git-lfs' was not found on your path. If you no longer wish to use Git LFS, remove this hook by deleting the 'post-checkout' file in the hooks directory (set by 'core.hookspath'; usually '.git/hooks').\n"; exit 2; }
+git lfs post-checkout "$@"

.githooks/post-commit

@@ -1,3 +1,3 @@
-#!/bin/sh
-command -v git-lfs >/dev/null 2>&1 || { echo >&2 "\nThis repository is configured for Git LFS but 'git-lfs' was not found on your path. If you no longer wish to use Git LFS, remove this hook by deleting the 'post-commit' file in the hooks directory (set by 'core.hookspath'; usually '.git/hooks').\n"; exit 2; }
-git lfs post-commit "$@"
+#!/bin/sh
+command -v git-lfs >/dev/null 2>&1 || { echo >&2 "\nThis repository is configured for Git LFS but 'git-lfs' was not found on your path. If you no longer wish to use Git LFS, remove this hook by deleting the 'post-commit' file in the hooks directory (set by 'core.hookspath'; usually '.git/hooks').\n"; exit 2; }
+git lfs post-commit "$@"

.githooks/post-merge

@@ -1,3 +1,3 @@
-#!/bin/sh
-command -v git-lfs >/dev/null 2>&1 || { echo >&2 "\nThis repository is configured for Git LFS but 'git-lfs' was not found on your path. If you no longer wish to use Git LFS, remove this hook by deleting the 'post-merge' file in the hooks directory (set by 'core.hookspath'; usually '.git/hooks').\n"; exit 2; }
-git lfs post-merge "$@"
+#!/bin/sh
+command -v git-lfs >/dev/null 2>&1 || { echo >&2 "\nThis repository is configured for Git LFS but 'git-lfs' was not found on your path. If you no longer wish to use Git LFS, remove this hook by deleting the 'post-merge' file in the hooks directory (set by 'core.hookspath'; usually '.git/hooks').\n"; exit 2; }
+git lfs post-merge "$@"

.githooks/pre-commit

@@ -1,43 +1,43 @@
-#!/usr/bin/env bash
-# pre-commit -- refresh cheap repo stats without leaking local wiki state.
-#
-# Enable with:   git config core.hooksPath .githooks
-# Disable with:  git config --unset core.hooksPath
-#
-# This hook intentionally does not rebuild graph/wiki artifacts from
-# ~/.claude/skill-wiki. That directory can contain private local entities.
-# Release graph artifacts must be created by explicit, reproducible commands
-# and staged by the user or CI.
-
-set -u
-
-REPO_ROOT="$(git rev-parse --show-toplevel)"
-UPDATER="$REPO_ROOT/src/update_repo_stats.py"
-
-PYTHON="${PYTHON:-python3}"
-command -v "$PYTHON" >/dev/null 2>&1 || PYTHON="python"
-
-STAGED_CHANGES=$(git diff --cached --name-only)
-log() { echo "[pre-commit] $*" >&2; }
-
-if echo "$STAGED_CHANGES" | grep -qE '^(README\.md|graph/(wiki-graph\.tar\.gz|communities\.json)|src/update_repo_stats\.py)$' ; then
-  if [[ -f "$UPDATER" ]]; then
-    STATS_CMD=("$PYTHON" "$UPDATER")
-    if command -v timeout >/dev/null 2>&1; then
-      STATS_CMD=(timeout 45s "${STATS_CMD[@]}")
-    fi
-    if ! "${STATS_CMD[@]}" 2> >(sed 's/^/[pre-commit stats] /' >&2); then
-      log "stats updater failed or timed out; continuing without README refresh"
-    elif ! git diff --quiet -- README.md; then
-      git add README.md
-      log "README.md refreshed and re-staged"
-    fi
-  fi
-fi
-
-if echo "$STAGED_CHANGES" | grep -qE '^(skills|agents|harnesses|imported-skills|graph/skills-sh-catalog\.json\.gz)' ; then
-  log "entity source changed; graph/wiki tarball not rebuilt by pre-commit"
-  log "run the explicit graph release command and stage graph/wiki-graph.tar.gz if needed"
-fi
-
-exit 0
+#!/usr/bin/env bash
+# pre-commit -- refresh cheap repo stats without leaking local wiki state.
+#
+# Enable with:   git config core.hooksPath .githooks
+# Disable with:  git config --unset core.hooksPath
+#
+# This hook intentionally does not rebuild graph/wiki artifacts from
+# ~/.claude/skill-wiki. That directory can contain private local entities.
+# Release graph artifacts must be created by explicit, reproducible commands
+# and staged by the user or CI.
+
+set -u
+
+REPO_ROOT="$(git rev-parse --show-toplevel)"
+UPDATER="$REPO_ROOT/src/update_repo_stats.py"
+
+PYTHON="${PYTHON:-python3}"
+command -v "$PYTHON" >/dev/null 2>&1 || PYTHON="python"
+
+STAGED_CHANGES=$(git diff --cached --name-only)
+log() { echo "[pre-commit] $*" >&2; }
+
+if echo "$STAGED_CHANGES" | grep -qE '^(README\.md|graph/(wiki-graph\.tar\.gz|communities\.json)|src/update_repo_stats\.py)$' ; then
+  if [[ -f "$UPDATER" ]]; then
+    STATS_CMD=("$PYTHON" "$UPDATER")
+    if command -v timeout >/dev/null 2>&1; then
+      STATS_CMD=(timeout 45s "${STATS_CMD[@]}")
+    fi
+    if ! "${STATS_CMD[@]}" 2> >(sed 's/^/[pre-commit stats] /' >&2); then
+      log "stats updater failed or timed out; continuing without README refresh"
+    elif ! git diff --quiet -- README.md; then
+      git add README.md
+      log "README.md refreshed and re-staged"
+    fi
+  fi
+fi
+
+if echo "$STAGED_CHANGES" | grep -qE '^(skills|agents|harnesses|imported-skills|graph/skills-sh-catalog\.json\.gz)' ; then
+  log "entity source changed; graph/wiki tarball not rebuilt by pre-commit"
+  log "run the explicit graph release command and stage graph/wiki-graph.tar.gz if needed"
+fi
+
+exit 0

.githooks/pre-push

@@ -1,3 +1,3 @@
-#!/bin/sh
-command -v git-lfs >/dev/null 2>&1 || { echo >&2 "\nThis repository is configured for Git LFS but 'git-lfs' was not found on your path. If you no longer wish to use Git LFS, remove this hook by deleting the 'pre-push' file in the hooks directory (set by 'core.hookspath'; usually '.git/hooks').\n"; exit 2; }
-git lfs pre-push "$@"
+#!/bin/sh
+command -v git-lfs >/dev/null 2>&1 || { echo >&2 "\nThis repository is configured for Git LFS but 'git-lfs' was not found on your path. If you no longer wish to use Git LFS, remove this hook by deleting the 'pre-push' file in the hooks directory (set by 'core.hookspath'; usually '.git/hooks').\n"; exit 2; }
+git lfs pre-push "$@"

.github/ISSUE_TEMPLATE/bug_report.md

@@ -1,36 +1,36 @@
----
-name: Bug report
-about: Something is broken
-title: "[bug] "
-labels: bug
-assignees: ""
----
-
-## Describe the bug
-
-A clear description of what went wrong.
-
-## To reproduce
-
-Steps to reproduce:
-
-1. Run `...`
-2. See error
-
-## Expected behaviour
-
-What you expected to happen.
-
-## Actual behaviour
-
-What actually happened. Include the full traceback if applicable.
-
-## Environment
-
-- OS:
-- Python version:
-- ctx version / commit:
-
-## Additional context
-
-Any other context (config snippets, related issues, etc.).
+---
+name: Bug report
+about: Something is broken
+title: "[bug] "
+labels: bug
+assignees: ""
+---
+
+## Describe the bug
+
+A clear description of what went wrong.
+
+## To reproduce
+
+Steps to reproduce:
+
+1. Run `...`
+2. See error
+
+## Expected behaviour
+
+What you expected to happen.
+
+## Actual behaviour
+
+What actually happened. Include the full traceback if applicable.
+
+## Environment
+
+- OS:
+- Python version:
+- ctx version / commit:
+
+## Additional context
+
+Any other context (config snippets, related issues, etc.).

.github/ISSUE_TEMPLATE/feature_request.md

@@ -1,23 +1,23 @@
----
-name: Feature request
-about: Suggest an improvement or new capability
-title: "[feat] "
-labels: enhancement
-assignees: ""
----
-
-## Problem statement
-
-What problem does this feature solve? Who is affected?
-
-## Proposed solution
-
-Describe your preferred solution. Include any API or CLI surface you have in mind.
-
-## Alternatives considered
-
-Any other approaches you considered and why you ruled them out.
-
-## Additional context
-
-Relevant links, prior art, or examples.
+---
+name: Feature request
+about: Suggest an improvement or new capability
+title: "[feat] "
+labels: enhancement
+assignees: ""
+---
+
+## Problem statement
+
+What problem does this feature solve? Who is affected?
+
+## Proposed solution
+
+Describe your preferred solution. Include any API or CLI surface you have in mind.
+
+## Alternatives considered
+
+Any other approaches you considered and why you ruled them out.
+
+## Additional context
+
+Relevant links, prior art, or examples.

.github/pull_request_template.md

@@ -1,15 +1,15 @@
-## Summary
-
-<!-- What does this PR do? One paragraph is fine. -->
-
-## Related issue
-
-<!-- Closes #<issue-number>, or "N/A" -->
-
-## Test plan
-
-- [ ] Existing tests pass (`pytest -q`)
-- [ ] New tests added for changed behaviour
-- [ ] `ruff check src/` passes
-- [ ] `mypy src/` passes
-- [ ] Integration tests checked if embedding code was touched (`pytest -q -m integration`)
+## Summary
+
+<!-- What does this PR do? One paragraph is fine. -->
+
+## Related issue
+
+<!-- Closes #<issue-number>, or "N/A" -->
+
+## Test plan
+
+- [ ] Existing tests pass (`pytest -q`)
+- [ ] New tests added for changed behaviour
+- [ ] `ruff check src/` passes
+- [ ] `mypy src/` passes
+- [ ] Integration tests checked if embedding code was touched (`pytest -q -m integration`)

.github/workflows/clean-host-contract.yml

@@ -1,15 +1,15 @@
 name: Clean Host Contract
 
-on:
-  workflow_dispatch:
-  schedule:
-    - cron: "17 3 * * 1"
-
-env:
-  FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: "true"
-
-jobs:
-  clean-host-contract:
+on:
+  workflow_dispatch:
+  schedule:
+    - cron: "17 3 * * 1"
+
+env:
+  FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: "true"
+
+jobs:
+  clean-host-contract:
     name: Clean wheel install and A-Z contract
     runs-on: ubuntu-latest
     timeout-minutes: 25

.github/workflows/docs.yml

@@ -1,72 +1,72 @@
-name: Deploy docs to GitHub Pages
-
-# Build the MkDocs Material site and publish to GitHub Pages on every push
-# to main. Also deployable on demand via the workflow_dispatch trigger.
-
-on:
-  push:
-    branches:
-      - main
-    paths:
-      - "docs/**"
-      - "mkdocs.yml"
-      - "requirements-docs.txt"
-      - ".github/workflows/docs.yml"
-  workflow_dispatch:
-
-env:
-  FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: "true"
-
-# GitHub Pages requires these permissions on the deploy job.
-permissions:
-  contents: read
-  pages: write
-  id-token: write
-
-# Allow only one concurrent deploy; cancel in-progress runs on a new push.
-concurrency:
-  group: "pages"
-  cancel-in-progress: true
-
-jobs:
-  build:
-    name: Build site
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v5
-        with:
-          fetch-depth: 0   # Required by mkdocs git-revision plugins if added.
-
-      - name: Set up Python
-        uses: actions/setup-python@v6
-        with:
-          python-version: "3.11"
-          cache: "pip"
-          cache-dependency-path: requirements-docs.txt
-
-      - name: Install docs dependencies
-        run: |
-          python -m pip install --upgrade pip
-          python -m pip install -r requirements-docs.txt
-
-      - name: Build site (strict)
-        run: |
-          python -m mkdocs build --strict
-
-      - name: Upload Pages artifact
-        uses: actions/upload-pages-artifact@v5
-        with:
-          path: site
-
-  deploy:
-    name: Deploy to GitHub Pages
-    needs: build
-    runs-on: ubuntu-latest
-    environment:
-      name: github-pages
-      url: ${{ steps.deployment.outputs.page_url }}
-    steps:
-      - name: Deploy
-        id: deployment
-        uses: actions/deploy-pages@v5
+name: Deploy docs to GitHub Pages
+
+# Build the MkDocs Material site and publish to GitHub Pages on every push
+# to main. Also deployable on demand via the workflow_dispatch trigger.
+
+on:
+  push:
+    branches:
+      - main
+    paths:
+      - "docs/**"
+      - "mkdocs.yml"
+      - "requirements-docs.txt"
+      - ".github/workflows/docs.yml"
+  workflow_dispatch:
+
+env:
+  FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: "true"
+
+# GitHub Pages requires these permissions on the deploy job.
+permissions:
+  contents: read
+  pages: write
+  id-token: write
+
+# Allow only one concurrent deploy; cancel in-progress runs on a new push.
+concurrency:
+  group: "pages"
+  cancel-in-progress: true
+
+jobs:
+  build:
+    name: Build site
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v5
+        with:
+          fetch-depth: 0   # Required by mkdocs git-revision plugins if added.
+
+      - name: Set up Python
+        uses: actions/setup-python@v6
+        with:
+          python-version: "3.11"
+          cache: "pip"
+          cache-dependency-path: requirements-docs.txt
+
+      - name: Install docs dependencies
+        run: |
+          python -m pip install --upgrade pip
+          python -m pip install -r requirements-docs.txt
+
+      - name: Build site (strict)
+        run: |
+          python -m mkdocs build --strict
+
+      - name: Upload Pages artifact
+        uses: actions/upload-pages-artifact@v5
+        with:
+          path: site
+
+  deploy:
+    name: Deploy to GitHub Pages
+    needs: build
+    runs-on: ubuntu-latest
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    steps:
+      - name: Deploy
+        id: deployment
+        uses: actions/deploy-pages@v5

.github/workflows/publish.yml

@@ -5,9 +5,9 @@ name: Publish to PyPI
 # no API token needed once the pending publisher is configured at
 # https://pypi.org/manage/account/publishing/.
 #
-# Also deployable on demand via workflow_dispatch. Manual PyPI publishes must
-# run from a version tag that matches pyproject.toml; branch dispatches are
-# allowed only for TestPyPI.
+# Also deployable on demand via workflow_dispatch. Manual PyPI publishes must
+# run from a version tag that matches pyproject.toml; branch dispatches are
+# allowed only for TestPyPI.
 
 on:
   push:
@@ -20,15 +20,15 @@ on:
         required: true
         default: "pypi"
         type: choice
-        options:
-          - pypi
-          - testpypi
-
-env:
-  FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: "true"
-
-permissions:
-  id-token: write   # required for Trusted Publishing
+        options:
+          - pypi
+          - testpypi
+
+env:
+  FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: "true"
+
+permissions:
+  id-token: write   # required for Trusted Publishing
   contents: read
 
 jobs:
@@ -36,45 +36,45 @@ jobs:
     name: Build sdist + wheel
     runs-on: ubuntu-latest
     steps:
-      - name: Checkout
-        uses: actions/checkout@v5
-        with:
-          lfs: false
+      - name: Checkout
+        uses: actions/checkout@v5
+        with:
+          lfs: false
 
       - name: Set up Python
         uses: actions/setup-python@v6
         with:
           python-version: "3.12"
 
-      - name: Install release tooling
-        run: |
-          python -m pip install --upgrade pip
-          python -m pip install build packaging twine ruff mypy pytest
-
-      - name: Validate release target
-        run: |
-          python - <<'PY'
-          import os
-          import tomllib
-          from packaging.version import Version
-
-          event = os.environ["GITHUB_EVENT_NAME"]
-          target_repository = os.environ.get("INPUT_REPOSITORY", "pypi")
-          ref_type = os.environ.get("GITHUB_REF_TYPE", "")
-          ref_name = os.environ["GITHUB_REF_NAME"]
-
-          if event == "workflow_dispatch" and target_repository == "testpypi":
-              print(f"manual TestPyPI publish allowed from {ref_type}:{ref_name}")
-              raise SystemExit(0)
-
-          if ref_type != "tag":
-              raise SystemExit(
-                  "PyPI release must run from a version tag; "
-                  f"got {ref_type}:{ref_name}"
-              )
-          tag = ref_name
-          if not tag.startswith("v"):
-              raise SystemExit(f"release tag must start with v: {tag}")
+      - name: Install release tooling
+        run: |
+          python -m pip install --upgrade pip
+          python -m pip install build packaging twine ruff mypy pytest
+
+      - name: Validate release target
+        run: |
+          python - <<'PY'
+          import os
+          import tomllib
+          from packaging.version import Version
+
+          event = os.environ["GITHUB_EVENT_NAME"]
+          target_repository = os.environ.get("INPUT_REPOSITORY", "pypi")
+          ref_type = os.environ.get("GITHUB_REF_TYPE", "")
+          ref_name = os.environ["GITHUB_REF_NAME"]
+
+          if event == "workflow_dispatch" and target_repository == "testpypi":
+              print(f"manual TestPyPI publish allowed from {ref_type}:{ref_name}")
+              raise SystemExit(0)
+
+          if ref_type != "tag":
+              raise SystemExit(
+                  "PyPI release must run from a version tag; "
+                  f"got {ref_type}:{ref_name}"
+              )
+          tag = ref_name
+          if not tag.startswith("v"):
+              raise SystemExit(f"release tag must start with v: {tag}")
 
           with open("pyproject.toml", "rb") as fh:
               package_version = tomllib.load(fh)["project"]["version"]
@@ -85,50 +85,50 @@ jobs:
               raise SystemExit(
                   f"tag {tag!r} does not match pyproject version {package_version!r}"
               )
-          print(f"release version {package_version} matches tag {tag}")
-          PY
-        env:
-          INPUT_REPOSITORY: ${{ github.event.inputs.repository || 'pypi' }}
-
-      - name: Static gates
-        run: |
-          python -m ruff check src hooks scripts
-          python -m mypy src
-
-      - name: Clean-host contract
-        run: python scripts/clean_host_contract.py --fast
-
-      - name: Build distributions
-        run: python -m build
-
-      - name: Check distributions
-        run: python -m twine check dist/*
-
-      - name: Check distribution contents
-        run: |
-          python - <<'PY'
-          import tarfile
-          import zipfile
-          from pathlib import Path
-
-          wheel = next(Path("dist").glob("*.whl"))
-          sdist = next(Path("dist").glob("*.tar.gz"))
-
-          with zipfile.ZipFile(wheel) as zf:
-              wheel_names = set(zf.namelist())
-          required = {"ctx/config.json", "ctx/skill-registry.json"}
-          missing = sorted(required - wheel_names)
-          if missing:
-              raise SystemExit(f"wheel missing packaged defaults: {missing}")
-
-          with tarfile.open(sdist, "r:gz") as tf:
-              names = set(tf.getnames())
-          forbidden = ("/src/tests/", "/.claude/", "/.a5c/")
-          leaked = sorted(name for name in names if any(part in name for part in forbidden))
-          if leaked:
-              raise SystemExit("sdist contains local/test artifacts:\n" + "\n".join(leaked[:20]))
-          print(f"checked distribution contents: {wheel.name}, {sdist.name}")
-          PY
+          print(f"release version {package_version} matches tag {tag}")
+          PY
+        env:
+          INPUT_REPOSITORY: ${{ github.event.inputs.repository || 'pypi' }}
+
+      - name: Static gates
+        run: |
+          python -m ruff check src hooks scripts
+          python -m mypy src
+
+      - name: Clean-host contract
+        run: python scripts/clean_host_contract.py --fast
+
+      - name: Build distributions
+        run: python -m build
+
+      - name: Check distributions
+        run: python -m twine check dist/*
+
+      - name: Check distribution contents
+        run: |
+          python - <<'PY'
+          import tarfile
+          import zipfile
+          from pathlib import Path
+
+          wheel = next(Path("dist").glob("*.whl"))
+          sdist = next(Path("dist").glob("*.tar.gz"))
+
+          with zipfile.ZipFile(wheel) as zf:
+              wheel_names = set(zf.namelist())
+          required = {"ctx/config.json", "ctx/skill-registry.json"}
+          missing = sorted(required - wheel_names)
+          if missing:
+              raise SystemExit(f"wheel missing packaged defaults: {missing}")
+
+          with tarfile.open(sdist, "r:gz") as tf:
+              names = set(tf.getnames())
+          forbidden = ("/src/tests/", "/.claude/", "/.a5c/")
+          leaked = sorted(name for name in names if any(part in name for part in forbidden))
+          if leaked:
+              raise SystemExit("sdist contains local/test artifacts:\n" + "\n".join(leaked[:20]))
+          print(f"checked distribution contents: {wheel.name}, {sdist.name}")
+          PY
 
       - name: Smoke install wheel
         run: |
@@ -138,19 +138,19 @@ jobs:
           python -m pip install dist/*.whl
           python -m pip check
           python - <<'PY'
-          from importlib.metadata import entry_points, version
-
-          import ctx
-          import ctx_config
-
-          dist_version = version("claude-ctx")
-          if ctx.__version__ != dist_version:
+          from importlib.metadata import entry_points, version
+
+          import ctx
+          import ctx_config
+
+          dist_version = version("claude-ctx")
+          if ctx.__version__ != dist_version:
               raise SystemExit(
-                  f"ctx.__version__={ctx.__version__!r} != metadata {dist_version!r}"
-              )
-          if ctx_config.cfg.recommendation_top_k != 5:
-              raise SystemExit("packaged default config was not loaded")
-          scripts = [
+                  f"ctx.__version__={ctx.__version__!r} != metadata {dist_version!r}"
+              )
+          if ctx_config.cfg.recommendation_top_k != 5:
+              raise SystemExit("packaged default config was not loaded")
+          scripts = [
               ep for ep in entry_points(group="console_scripts")
               if ep.name == "ctx" or ep.name.startswith("ctx-")
           ]
@@ -165,11 +165,11 @@ jobs:
           print(f"loaded {len(scripts)} ctx console scripts from wheel {dist_version}")
           PY
 
-      - name: Upload dist artifact
-        uses: actions/upload-artifact@v7
-        with:
-          name: dist
-          path: dist/
+      - name: Upload dist artifact
+        uses: actions/upload-artifact@v7
+        with:
+          name: dist
+          path: dist/
 
   publish:
     name: Publish to PyPI
@@ -179,11 +179,11 @@ jobs:
       name: pypi
       url: https://pypi.org/project/claude-ctx/
     steps:
-      - name: Download dist artifact
-        uses: actions/download-artifact@v7
-        with:
-          name: dist
-          path: dist/
+      - name: Download dist artifact
+        uses: actions/download-artifact@v7
+        with:
+          name: dist
+          path: dist/
 
       - name: Publish to PyPI
         if: github.event_name == 'push' || github.event.inputs.repository == 'pypi'

.github/workflows/test.yml

@@ -234,36 +234,15 @@ jobs:
 
       - name: Validate shipped graph artifacts
         run: |
-          python - <<'PY'
-          import gzip
-          import json
-          import tarfile
-          from pathlib import Path
-
-          required = [
-              Path("graph/wiki-graph.tar.gz"),
-              Path("graph/skills-sh-catalog.json.gz"),
-              Path("graph/communities.json"),
-          ]
-          for path in required:
-              if not path.is_file() or path.stat().st_size == 0:
-                  raise SystemExit(f"missing or empty graph artifact: {path}")
-
-          with gzip.open("graph/skills-sh-catalog.json.gz", "rt", encoding="utf-8") as fh:
-              json.load(fh)
-          json.loads(Path("graph/communities.json").read_text(encoding="utf-8"))
-
-          with tarfile.open("graph/wiki-graph.tar.gz", "r:gz") as tar:
-              names = tar.getnames()
-          if not any(name.endswith("/index.md") or name == "./index.md" for name in names):
-              raise SystemExit("wiki graph archive is missing index.md")
-          originals = [name for name in names if name.endswith("SKILL.md.original")]
-          if originals:
-              raise SystemExit(
-                  f"wiki graph archive contains {len(originals)} raw SKILL.md.original files"
-              )
-          print(f"validated graph archive with {len(names)} entries")
-          PY
+          python src/validate_graph_artifacts.py \
+            --graph-dir graph \
+            --deep \
+            --min-nodes 100000 \
+            --min-edges 2000000 \
+            --min-skills-sh-nodes 90000 \
+            --min-semantic-edges 1000000 \
+            --line-threshold 180 \
+            --max-stage-lines 40
 
   browser-security:
     name: "Browser monitor security"

AGENTS.md

@@ -1,70 +1,70 @@
-# Agent Directives: Mechanical Overrides
-
-You are operating within a constrained context window and strict system prompts. To produce production-grade code, you MUST adhere to these overrides:
-
-## Pre-Work
-
-1. THE "STEP 0" RULE: Dead code accelerates context compaction. Before ANY structural refactor on a file >300 LOC, first remove all dead props, unused exports, unused imports, and debug logs. Commit this cleanup separately before starting the real work.
-
-2. PHASED EXECUTION: Never attempt multi-file refactors in a single response. Break work into explicit phases. Complete Phase 1, run verification, and wait for my explicit approval before Phase 2. Each phase must touch no more than 5 files.
-
-## Code Quality
-
-3. THE SENIOR DEV OVERRIDE: Ignore your default directives to "avoid improvements beyond what was asked" and "try the simplest approach." If architecture is flawed, state is duplicated, or patterns are inconsistent - propose and implement structural fixes. Ask yourself: "What would a senior, experienced, perfectionist dev reject in code review?" Fix all of it. Don't be lazy.
-
-4. FORCED VERIFICATION: Your internal tools mark file writes as successful even if the code does not compile. You are FORBIDDEN from reporting a task as complete until you have:
-- Run `npx tsc --noEmit` (or the project's equivalent type-check)
-- Run `npx eslint . --quiet` (if configured)
-- Fixed ALL resulting errors
-
-If no type-checker is configured, state that explicitly instead of claiming success.
-
-## Context Management
-
-5. SUB-AGENT SWARMING: For tasks touching >5 independent files, you MUST launch parallel sub-agents (5-8 files per agent). Each agent gets its own context window. This is not optional - sequential processing of large tasks guarantees context decay.
-
-6. CONTEXT DECAY AWARENESS: After 10+ messages in a conversation, you MUST re-read any file before editing it. Do not trust your memory of file contents. Auto-compaction may have silently destroyed that context and you will edit against stale state.
-
-7. FILE READ BUDGET: Each file read is capped at 2,000 lines. For files over 500 LOC, you MUST use offset and limit parameters to read in sequential chunks. Never assume you have seen a complete file from a single read.
-
-8. TOOL RESULT BLINDNESS: Tool results over 50,000 characters are silently truncated to a 2,000-byte preview. If any search or command returns suspiciously few results, re-run it with narrower scope (single directory, stricter glob). State when you suspect truncation occurred.
-
-## Edit Safety
-
-9. EDIT INTEGRITY: Before EVERY file edit, re-read the file. After editing, read it again to confirm the change applied correctly. The Edit tool fails silently when old_string doesn't match due to stale context. Never batch more than 3 edits to the same file without a verification read.
-
-10. NO SEMANTIC SEARCH: You have grep, not an AST. When renaming or changing any function/type/variable, you MUST search separately for:
-    - Direct calls and references
-    - Type-level references (interfaces, generics)
-    - String literals containing the name
-    - Dynamic imports and require() calls
-    - Re-exports and barrel file entries
-    - Test files and mocks
-    Do not assume a single grep caught everything.
-
-## Coding Discipline (Karpathy Principles)
-
-11. THINK BEFORE CODING: Don't assume. Don't hide confusion. Surface tradeoffs. Before implementing:
-    - State assumptions explicitly. If uncertain, ask.
-    - If multiple interpretations exist, present them - don't pick silently.
-    - If a simpler approach exists, say so. Push back when warranted.
-    - If something is unclear, stop. Name what's confusing. Ask.
-
-12. SIMPLICITY FIRST: Minimum code that solves the problem. Nothing speculative. No features beyond what was asked. No abstractions for single-use code. No "flexibility" or "configurability" that wasn't requested. If you write 200 lines and it could be 50, rewrite it. **Note:** This complements rule #3 (Senior Dev Override) - fix real architectural flaws, but don't overbuild.
-
-13. SURGICAL CHANGES: When editing existing code, match existing style. Don't "improve" adjacent code, comments, or formatting that aren't part of the task. If your changes create orphans, remove them. If you notice unrelated dead code, mention it - don't delete it. Every changed line should trace directly to the user's request. **Note:** Rule #1 (Step 0) is the exception - dead code cleanup is done as a separate, explicit commit before refactoring.
-
-14. GOAL-DRIVEN EXECUTION: Transform vague tasks into verifiable goals before starting. For multi-step tasks, state a brief plan with success criteria:
-    ```
-    1. [Step] -> verify: [check]
-    2. [Step] -> verify: [check]
-    ```
-    Strong success criteria let you loop independently. Weak criteria ("make it work") require constant clarification. **Note:** This extends rule #4 (Forced Verification) from tool-level checks to task-level planning.
-
-## Post-Work
-
-15. CODEX REVIEW: Every completed task is reviewed by Codex after you hand off. Before declaring "done":
-    - Re-read every file you edited and confirm the change actually persisted.
-    - Re-run the verification commands from rule #4 and quote the output, not the intent.
-    - Separate what you **observed** from what you **inferred** — Codex will catch inferences dressed up as observations.
-    - Leave a short "for-the-reviewer" note at the end of your response: what you touched, what you verified, what you did NOT verify and why. This is non-negotiable — a downstream reviewer seeing no caveats assumes everything was checked, and that assumption is what gets shipped.
+# Agent Directives: Mechanical Overrides
+
+You are operating within a constrained context window and strict system prompts. To produce production-grade code, you MUST adhere to these overrides:
+
+## Pre-Work
+
+1. THE "STEP 0" RULE: Dead code accelerates context compaction. Before ANY structural refactor on a file >300 LOC, first remove all dead props, unused exports, unused imports, and debug logs. Commit this cleanup separately before starting the real work.
+
+2. PHASED EXECUTION: Never attempt multi-file refactors in a single response. Break work into explicit phases. Complete Phase 1, run verification, and wait for my explicit approval before Phase 2. Each phase must touch no more than 5 files.
+
+## Code Quality
+
+3. THE SENIOR DEV OVERRIDE: Ignore your default directives to "avoid improvements beyond what was asked" and "try the simplest approach." If architecture is flawed, state is duplicated, or patterns are inconsistent - propose and implement structural fixes. Ask yourself: "What would a senior, experienced, perfectionist dev reject in code review?" Fix all of it. Don't be lazy.
+
+4. FORCED VERIFICATION: Your internal tools mark file writes as successful even if the code does not compile. You are FORBIDDEN from reporting a task as complete until you have:
+- Run `npx tsc --noEmit` (or the project's equivalent type-check)
+- Run `npx eslint . --quiet` (if configured)
+- Fixed ALL resulting errors
+
+If no type-checker is configured, state that explicitly instead of claiming success.
+
+## Context Management
+
+5. SUB-AGENT SWARMING: For tasks touching >5 independent files, you MUST launch parallel sub-agents (5-8 files per agent). Each agent gets its own context window. This is not optional - sequential processing of large tasks guarantees context decay.
+
+6. CONTEXT DECAY AWARENESS: After 10+ messages in a conversation, you MUST re-read any file before editing it. Do not trust your memory of file contents. Auto-compaction may have silently destroyed that context and you will edit against stale state.
+
+7. FILE READ BUDGET: Each file read is capped at 2,000 lines. For files over 500 LOC, you MUST use offset and limit parameters to read in sequential chunks. Never assume you have seen a complete file from a single read.
+
+8. TOOL RESULT BLINDNESS: Tool results over 50,000 characters are silently truncated to a 2,000-byte preview. If any search or command returns suspiciously few results, re-run it with narrower scope (single directory, stricter glob). State when you suspect truncation occurred.
+
+## Edit Safety
+
+9. EDIT INTEGRITY: Before EVERY file edit, re-read the file. After editing, read it again to confirm the change applied correctly. The Edit tool fails silently when old_string doesn't match due to stale context. Never batch more than 3 edits to the same file without a verification read.
+
+10. NO SEMANTIC SEARCH: You have grep, not an AST. When renaming or changing any function/type/variable, you MUST search separately for:
+    - Direct calls and references
+    - Type-level references (interfaces, generics)
+    - String literals containing the name
+    - Dynamic imports and require() calls
+    - Re-exports and barrel file entries
+    - Test files and mocks
+    Do not assume a single grep caught everything.
+
+## Coding Discipline (Karpathy Principles)
+
+11. THINK BEFORE CODING: Don't assume. Don't hide confusion. Surface tradeoffs. Before implementing:
+    - State assumptions explicitly. If uncertain, ask.
+    - If multiple interpretations exist, present them - don't pick silently.
+    - If a simpler approach exists, say so. Push back when warranted.
+    - If something is unclear, stop. Name what's confusing. Ask.
+
+12. SIMPLICITY FIRST: Minimum code that solves the problem. Nothing speculative. No features beyond what was asked. No abstractions for single-use code. No "flexibility" or "configurability" that wasn't requested. If you write 200 lines and it could be 50, rewrite it. **Note:** This complements rule #3 (Senior Dev Override) - fix real architectural flaws, but don't overbuild.
+
+13. SURGICAL CHANGES: When editing existing code, match existing style. Don't "improve" adjacent code, comments, or formatting that aren't part of the task. If your changes create orphans, remove them. If you notice unrelated dead code, mention it - don't delete it. Every changed line should trace directly to the user's request. **Note:** Rule #1 (Step 0) is the exception - dead code cleanup is done as a separate, explicit commit before refactoring.
+
+14. GOAL-DRIVEN EXECUTION: Transform vague tasks into verifiable goals before starting. For multi-step tasks, state a brief plan with success criteria:
+    ```
+    1. [Step] -> verify: [check]
+    2. [Step] -> verify: [check]
+    ```
+    Strong success criteria let you loop independently. Weak criteria ("make it work") require constant clarification. **Note:** This extends rule #4 (Forced Verification) from tool-level checks to task-level planning.
+
+## Post-Work
+
+15. CODEX REVIEW: Every completed task is reviewed by Codex after you hand off. Before declaring "done":
+    - Re-read every file you edited and confirm the change actually persisted.
+    - Re-run the verification commands from rule #4 and quote the output, not the intent.
+    - Separate what you **observed** from what you **inferred** — Codex will catch inferences dressed up as observations.
+    - Leave a short "for-the-reviewer" note at the end of your response: what you touched, what you verified, what you did NOT verify and why. This is non-negotiable — a downstream reviewer seeing no caveats assumes everything was checked, and that assumption is what gets shipped.

CONTRIBUTING.md

@@ -1,77 +1,77 @@
-# Contributing to ctx
-
-Thank you for your interest in contributing.
-
-## Dev environment setup
-
-```bash
-git clone https://github.com/stevesolun/ctx && cd ctx
-python -m venv .venv
-source .venv/bin/activate   # Windows: .venv\Scripts\activate
-pip install -e ".[dev]"
-```
-
-To also run the similarity/embedding tests (requires ~100 MB model download):
-
-```bash
-pip install -e ".[dev,embeddings]"
-```
-
-## Running tests
-
-```bash
-pytest -q                          # fast suite (skips integration)
-pytest -q -m 'not integration'     # same, explicit
-pytest -q -m integration           # embedding precision/recall tests
-pytest --cov=src -q                # with coverage report
-```
-
-## Code style
-
-Both **ruff** and **mypy** must pass before a PR is merged.
-
-```bash
-ruff check src/          # linting
-ruff format --check src/ # formatting check
-mypy src/                # type checking
-```
-
-Fix formatting in one shot:
-
-```bash
-ruff format src/
-ruff check --fix src/
-```
-
-## Commit conventions
-
-This repo uses [Conventional Commits](https://www.conventionalcommits.org/):
-
-```
-feat:     new feature
-fix:      bug fix
-refactor: code restructuring without behaviour change
-docs:     documentation only
-test:     test additions or corrections
-chore:    maintenance (deps, CI, tooling)
-perf:     performance improvement
-ci:       CI/CD changes
-```
-
-Scope is optional but encouraged, e.g. `feat(intake): add fuzzy-match gate`.
-
-## Reporting bugs
-
-Open an issue at <https://github.com/stevesolun/ctx/issues>. Include:
-
-- Python version and OS
-- Full traceback
-- Minimal reproduction steps
-
-## Pull request process
-
-1. Fork the repo and create a feature branch from `main`.
-2. Make your changes. Add or update tests — the CI gate requires the existing suite to pass.
-3. Ensure `ruff` and `mypy` pass locally.
-4. Open a PR against `main`. Fill in the PR template.
-5. A maintainer will review and merge once CI is green.
+# Contributing to ctx
+
+Thank you for your interest in contributing.
+
+## Dev environment setup
+
+```bash
+git clone https://github.com/stevesolun/ctx && cd ctx
+python -m venv .venv
+source .venv/bin/activate   # Windows: .venv\Scripts\activate
+pip install -e ".[dev]"
+```
+
+To also run the similarity/embedding tests (requires ~100 MB model download):
+
+```bash
+pip install -e ".[dev,embeddings]"
+```
+
+## Running tests
+
+```bash
+pytest -q                          # fast suite (skips integration)
+pytest -q -m 'not integration'     # same, explicit
+pytest -q -m integration           # embedding precision/recall tests
+pytest --cov=src -q                # with coverage report
+```
+
+## Code style
+
+Both **ruff** and **mypy** must pass before a PR is merged.
+
+```bash
+ruff check src/          # linting
+ruff format --check src/ # formatting check
+mypy src/                # type checking
+```
+
+Fix formatting in one shot:
+
+```bash
+ruff format src/
+ruff check --fix src/
+```
+
+## Commit conventions
+
+This repo uses [Conventional Commits](https://www.conventionalcommits.org/):
+
+```
+feat:     new feature
+fix:      bug fix
+refactor: code restructuring without behaviour change
+docs:     documentation only
+test:     test additions or corrections
+chore:    maintenance (deps, CI, tooling)
+perf:     performance improvement
+ci:       CI/CD changes
+```
+
+Scope is optional but encouraged, e.g. `feat(intake): add fuzzy-match gate`.
+
+## Reporting bugs
+
+Open an issue at <https://github.com/stevesolun/ctx/issues>. Include:
+
+- Python version and OS
+- Full traceback
+- Minimal reproduction steps
+
+## Pull request process
+
+1. Fork the repo and create a feature branch from `main`.
+2. Make your changes. Add or update tests — the CI gate requires the existing suite to pass.
+3. Ensure `ruff` and `mypy` pass locally.
+4. Open a PR against `main`. Fill in the PR template.
+5. A maintainer will review and merge once CI is green.

LICENSE

@@ -1,21 +1,21 @@
-MIT License
-
-Copyright (c) 2026 Steve Solun
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+MIT License
+
+Copyright (c) 2026 Steve Solun
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

MANIFEST.in

@@ -1,4 +1,4 @@
-prune src/tests
-prune .a5c
-prune .claude
-global-exclude __pycache__ *.py[cod]
+prune src/tests
+prune .a5c
+prune .claude
+global-exclude __pycache__ *.py[cod]

README.md

@@ -1,101 +1,107 @@
----
-license: mit
-pretty_name: ctx
-tags:
-  - agents
-  - mcp
-  - skills
-  - knowledge-graph
-  - llm-wiki
-  - recommendation-system
-  - harness
-  - codex
-  - claude-code
----
-
-# ctx — Skill, Agent, MCP & Harness Catalog
-
-[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)
-[![Python 3.11+](https://img.shields.io/badge/Python-3.11+-green.svg)](https://python.org)
-[![PyPI](https://img.shields.io/pypi/v/claude-ctx.svg)](https://pypi.org/project/claude-ctx/)
-[![Tests](https://img.shields.io/badge/Tests-3489_collected-brightgreen.svg)](#)
-[![Graph](https://img.shields.io/badge/Graph-104%2C079_nodes_/_3.0M_edges-red.svg)](graph/)
-[![Docs](https://img.shields.io/badge/docs-MkDocs_Material-blue.svg)](https://stevesolun.github.io/ctx/)
-
-Watches what you develop, walks a **104,079-node** graph across **92,815 skills, 464 agents, 10,787 MCP servers, and 13 cataloged harnesses**, then recommends the highest-value skills, agents, and MCP servers for the current task. Custom/API/local model users get separate harness recommendations during `ctx-init` or `ctx-harness-install`. The shipped wiki includes 90,846 Skills.sh entries, 89,461 hydrated installable `SKILL.md` bodies, install commands, duplicate hints, and semantic graph edges. You approve what loads, installs, or gets adopted.
-
-> **2026-04-29 updates.**
-> - Added the curated `find-skills` workflow, backed by the canonical upstream install command `npx skills add https://github.com/vercel-labs/skills --skill find-skills`.
-> - Shipped 90,846 Skills.sh entries as first-class remote-cataloged `skill` nodes inside `graph/wiki-graph.tar.gz` and as `graph/skills-sh-catalog.json.gz`.
-> - Added 13 cataloged harnesses, including LangGraph, CrewAI, AutoGen, Google ADK, Semantic Kernel, Mastra, Pydantic AI, Haystack, OpenAI Agents SDK, LiteLLM, Langfuse, AgentOps, and text-to-cad.
-> - Added security/cyber review warnings to entity update reviews and documented the graph/wiki update procedure.
-
-> **2026-04-27 updates.**
-> - Imported [mattpocock/skills](https://github.com/mattpocock/skills) — 21 opinionated skills (TDD, domain-model, ubiquitous-language, github-triage, caveman compression mode, write-a-skill, plus 15 more) deployed under the `mattpocock-` prefix. See [`imported-skills/mattpocock/ATTRIBUTION.md`](imported-skills/mattpocock/ATTRIBUTION.md).
-> - Imported [designdotmd.directory](https://designdotmd.directory) — 156 DESIGN.md files (visual identities: color tokens, typography, spacing, components + rationale) deployed under the `designdotmd-` prefix. These are reference designs an agent can read when asked to build a UI. See [`imported-skills/designdotmd/ATTRIBUTION.md`](imported-skills/designdotmd/ATTRIBUTION.md).
-> - Skill total: 1,791 → **1,968** (+177).
-
-## Why it exists
-
-- **Discovery** — with 92K+ skill nodes, 460+ agents, 10K+ MCP servers, and 13 cataloged harnesses, you can't possibly know which exist or which apply to your current work.
-- **Context budget** — loading everything wastes tokens and degrades quality. You need the right 10–15 per session.
-- **Skill rot** — skills you installed months ago and never used are cluttering context. Stale ones should be flagged automatically.
-
-## Install
-
-```bash
-pip install claude-ctx
-ctx-init                    # terminal wizard: hooks, graph, model, harness goal
-ctx-init --wizard           # force the same wizard from scripts/tests
-ctx-init --model-mode skip  # non-interactive setup for automation
-ctx-init --model-mode custom --model openai/gpt-5.5 --goal "build a CAD agent"
-```
-
-Optional extras: `pip install "claude-ctx[embeddings]"` for the semantic backend, `pip install "claude-ctx[dev]"` for the test toolchain.
-
-### Pre-built knowledge graph (optional)
-
-A pre-built knowledge graph of 104,079 nodes and 2,960,215 edges ships as a tarball. The same tarball includes `external-catalogs/skills-sh/catalog.json`, 90,846 remote-cataloged Skills.sh skill pages under `entities/skills/skills-sh-*.md`, 89,461 hydrated installable Skills.sh `SKILL.md` files under `converted/skills-sh-*/`, and 13 cataloged harness pages under `entities/harnesses/`. Extract to get a ready-to-use `~/.claude/skill-wiki/`:
-
-```bash
-# after `git clone` — or download graph/wiki-graph.tar.gz from the GitHub release
-mkdir -p ~/.claude/skill-wiki
-tar xzf graph/wiki-graph.tar.gz -C ~/.claude/skill-wiki/
-```
-
-> **Windows / Git-Bash / MSYS:** pass `--force-local` so `tar` doesn't read the `c:` in the path as a remote host: `tar --force-local xzf graph/wiki-graph.tar.gz -C ~/.claude/skill-wiki/`. Linux/macOS users can ignore.
-
-## Use
-
-After install, the `ctx` hooks integrate automatically with Claude Code's `PostToolUse` + `Stop` events. Typical flow:
-
-```bash
-ctx-scan-repo --repo .     # scan current repo and stack signals
-ctx-scan-repo --repo . --recommend  # include skill/agent/MCP recommendations
-ctx-agent-add --agent-path ./code-reviewer.md --name code-reviewer
-ctx-harness-add --repo https://github.com/earthtojake/text-to-cad --tag cad
-ctx-harness-install text-to-cad --dry-run   # inspect before cloning/running anything
-ctx-harness-install text-to-cad --update --dry-run
-ctx-harness-install text-to-cad --uninstall --dry-run
-ctx-skill-quality list     # four-signal quality score for every skill
-ctx-skill-quality explain python-patterns   # drill into a single skill
-ctx-skill-health dashboard # structural health + drift detection
-ctx-toolbox run --event pre-commit          # run a council on the current diff
-ctx-monitor serve          # local dashboard: http://127.0.0.1:8765/
-```
-
-The **`ctx-monitor`** dashboard shows currently loaded skills, agents, MCP servers, and installed harness records. It provides load/unload buttons where ctx owns the live action, a cytoscape graph view (`/graph?slug=…`), the LLM-wiki entity browser (`/wiki/<slug>`), a filterable skills grid, a session timeline, an audit log viewer, and a live SSE event stream. Harnesses are visible in the dashboard loaded/wiki/graph views; harness install/update/uninstall actions stay in `ctx-harness-install`.
-
-When `ctx-skill-add`, `ctx-agent-add`, `ctx-mcp-add`, or `ctx-harness-add`
-finds an existing entity, ctx prints a benefits/risks update review and skips
-replacement by default. Re-run with `--update-existing` to apply the catalog or
-local asset update after review.
-
-Step-by-step entity onboarding:
-**<https://stevesolun.github.io/ctx/entity-onboarding/>**
-
-Full docs, architecture, and every module: **<https://stevesolun.github.io/ctx/>**
-
-## License
-
-MIT — see [LICENSE](LICENSE).
+---
+license: mit
+pretty_name: ctx
+language:
+- en
+tags:
+- agents
+- mcp
+- skills
+- knowledge-graph
+- llm-wiki
+- recommendation-system
+- harness
+- codex
+- claude-code
+- context-engineering
+- developer-tools
+size_categories:
+- 100K<n<1M
+---
+
+# ctx — Skill, Agent, MCP & Harness Catalog
+
+[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)
+[![Python 3.11+](https://img.shields.io/badge/Python-3.11+-green.svg)](https://python.org)
+[![PyPI](https://img.shields.io/pypi/v/claude-ctx.svg)](https://pypi.org/project/claude-ctx/)
+[![Tests](https://img.shields.io/badge/Tests-3497_collected-brightgreen.svg)](#)
+[![Graph](https://img.shields.io/badge/Graph-104%2C079_nodes_/_3.0M_edges-red.svg)](graph/)
+[![Docs](https://img.shields.io/badge/docs-MkDocs_Material-blue.svg)](https://stevesolun.github.io/ctx/)
+
+Watches what you develop, walks a **104,079-node** graph across **92,815 skills, 464 agents, 10,787 MCP servers, and 13 cataloged harnesses**, then recommends the highest-value skills, agents, and MCP servers for the current task. Custom/API/local model users get separate harness recommendations during `ctx-init` or `ctx-harness-install`. The shipped wiki includes 90,846 Skills.sh entries, 89,461 hydrated installable `SKILL.md` bodies, install commands, duplicate hints, and semantic graph edges. You approve what loads, installs, or gets adopted.
+
+> **2026-04-29 updates.**
+> - Added the curated `find-skills` workflow, backed by the canonical upstream install command `npx skills add https://github.com/vercel-labs/skills --skill find-skills`.
+> - Shipped 90,846 Skills.sh entries as first-class remote-cataloged `skill` nodes inside `graph/wiki-graph.tar.gz` and as `graph/skills-sh-catalog.json.gz`.
+> - Added 13 cataloged harnesses, including LangGraph, CrewAI, AutoGen, Google ADK, Semantic Kernel, Mastra, Pydantic AI, Haystack, OpenAI Agents SDK, LiteLLM, Langfuse, AgentOps, and text-to-cad.
+> - Added security/cyber review warnings to entity update reviews and documented the graph/wiki update procedure.
+
+> **2026-04-27 updates.**
+> - Imported [mattpocock/skills](https://github.com/mattpocock/skills) — 21 opinionated skills (TDD, domain-model, ubiquitous-language, github-triage, caveman compression mode, write-a-skill, plus 15 more) deployed under the `mattpocock-` prefix. See [`imported-skills/mattpocock/ATTRIBUTION.md`](imported-skills/mattpocock/ATTRIBUTION.md).
+> - Imported [designdotmd.directory](https://designdotmd.directory) — 156 DESIGN.md files (visual identities: color tokens, typography, spacing, components + rationale) deployed under the `designdotmd-` prefix. These are reference designs an agent can read when asked to build a UI. See [`imported-skills/designdotmd/ATTRIBUTION.md`](imported-skills/designdotmd/ATTRIBUTION.md).
+> - Skill total: 1,791 → **1,968** (+177).
+
+## Why it exists
+
+- **Discovery** — with 92K+ skill nodes, 460+ agents, 10K+ MCP servers, and 13 cataloged harnesses, you can't possibly know which exist or which apply to your current work.
+- **Context budget** — loading everything wastes tokens and degrades quality. You need the right 10–15 per session.
+- **Skill rot** — skills you installed months ago and never used are cluttering context. Stale ones should be flagged automatically.
+
+## Install
+
+```bash
+pip install claude-ctx
+ctx-init                    # terminal wizard: hooks, graph, model, harness goal
+ctx-init --wizard           # force the same wizard from scripts/tests
+ctx-init --model-mode skip  # non-interactive setup for automation
+ctx-init --model-mode custom --model openai/gpt-5.5 --goal "build a CAD agent"
+```
+
+Optional extras: `pip install "claude-ctx[embeddings]"` for the semantic backend, `pip install "claude-ctx[dev]"` for the test toolchain.
+
+### Pre-built knowledge graph (optional)
+
+A pre-built knowledge graph of 104,079 nodes and 2,960,215 edges ships as a tarball. The same tarball includes `external-catalogs/skills-sh/catalog.json`, 90,846 remote-cataloged Skills.sh skill pages under `entities/skills/skills-sh-*.md`, 89,461 hydrated installable Skills.sh `SKILL.md` files under `converted/skills-sh-*/`, and 13 cataloged harness pages under `entities/harnesses/`. Extract to get a ready-to-use `~/.claude/skill-wiki/`:
+
+```bash
+# after `git clone` — or download graph/wiki-graph.tar.gz from the GitHub release
+mkdir -p ~/.claude/skill-wiki
+tar xzf graph/wiki-graph.tar.gz -C ~/.claude/skill-wiki/
+```
+
+> **Windows / Git-Bash / MSYS:** pass `--force-local` so `tar` doesn't read the `c:` in the path as a remote host: `tar --force-local xzf graph/wiki-graph.tar.gz -C ~/.claude/skill-wiki/`. Linux/macOS users can ignore.
+
+## Use
+
+After install, the `ctx` hooks integrate automatically with Claude Code's `PostToolUse` + `Stop` events. Typical flow:
+
+```bash
+ctx-scan-repo --repo .     # scan current repo and stack signals
+ctx-scan-repo --repo . --recommend  # include skill/agent/MCP recommendations
+ctx-agent-add --agent-path ./code-reviewer.md --name code-reviewer
+ctx-harness-add --repo https://github.com/earthtojake/text-to-cad --tag cad
+ctx-harness-install text-to-cad --dry-run   # inspect before cloning/running anything
+ctx-harness-install text-to-cad --update --dry-run
+ctx-harness-install text-to-cad --uninstall --dry-run
+ctx-skill-quality list     # four-signal quality score for every skill
+ctx-skill-quality explain python-patterns   # drill into a single skill
+ctx-skill-health dashboard # structural health + drift detection
+ctx-toolbox run --event pre-commit          # run a council on the current diff
+ctx-monitor serve          # local dashboard: http://127.0.0.1:8765/
+```
+
+The **`ctx-monitor`** dashboard shows currently loaded skills, agents, MCP servers, and installed harness records. It provides load/unload buttons where ctx owns the live action, a cytoscape graph view (`/graph?slug=…`), the LLM-wiki entity browser (`/wiki/<slug>`), a filterable skills grid, a session timeline, an audit log viewer, and a live SSE event stream. Harnesses are visible in the dashboard loaded/wiki/graph views; harness install/update/uninstall actions stay in `ctx-harness-install`.
+
+When `ctx-skill-add`, `ctx-agent-add`, `ctx-mcp-add`, or `ctx-harness-add`
+finds an existing entity, ctx prints a benefits/risks update review and skips
+replacement by default. Re-run with `--update-existing` to apply the catalog or
+local asset update after review.
+
+Step-by-step entity onboarding:
+**<https://stevesolun.github.io/ctx/entity-onboarding/>**
+
+Full docs, architecture, and every module: **<https://stevesolun.github.io/ctx/>**
+
+## License
+
+MIT — see [LICENSE](LICENSE).

docs/SKILL.md

@@ -1,690 +1,690 @@
----
-name: skill-router
-description: "Repo-aware skill and plugin manager. Scans the user's active repository, identifies the tech stack, frameworks, and workflows in use, then loads ONLY the relevant skills, plugins, and MCP servers -- unloading everything else to keep the context clean. Maintains a persistent LLM Wiki catalog of all available skills, plugins, and marketplaces so decisions are informed and consistent across sessions. Use this skill whenever the user opens a project, switches repos, asks 'what skills do I need', mentions context bloat or slow responses, asks to manage/list/add/remove skills or plugins, or references their skill catalog/wiki. Also triggers on: 'scan my repo', 'what tools do I need for this project', 'clean up my skills', 'too many plugins loaded', 'optimize my context', or any repo-switch event."
----
-
-# Skill Router
-
-Scan a repo. Know what it needs. Load only that. Maintain a wiki of everything available.
-
-## Problem
-
-Every skill, plugin, and MCP server loaded into context costs tokens and attention.
-Most projects need 3-8 skills out of 30+. Loading all of them:
-- Wastes context window on irrelevant instructions
-- Causes skill misfires (wrong skill triggers for a task)
-- Slows response time
-- Creates conflicting instructions between skills
-
-## Architecture
-
-```
-skill-router/
-├── SKILL.md                    # This file -- orchestration logic
-├── references/
-│   ├── stack-signatures.md     # File/config patterns mapped to stack identifiers
-│   ├── skill-stack-matrix.md   # Which skills serve which stacks
-│   └── marketplace-registry.md # Known marketplaces and how to query them
-└── scripts/
-    ├── scan_repo.py            # Repo scanner -- outputs stack profile JSON
-    ├── resolve_skills.py       # Maps stack profile to skill set
-    └── wiki_sync.py            # Syncs scan results into the wiki
-```
-
-The skill router has two halves:
-1. **The Scanner** -- analyzes a repo and produces a stack profile
-2. **The Wiki** -- persistent catalog of all available skills/plugins/marketplaces,
-   maintained via the Karpathy LLM Wiki pattern
-
-## Session Startup (CRITICAL -- do this every time)
-
-When this skill activates, follow this sequence:
-
-### Step 1: Orient from the Wiki
-
-```bash
-WIKI="${SKILL_ROUTER_WIKI:-$HOME/skill-wiki}"
-if [ -d "$WIKI" ]; then
-  # Existing wiki -- orient first
-  cat "$WIKI/SCHEMA.md"
-  cat "$WIKI/index.md"
-  tail -30 "$WIKI/log.md"
-else
-  # No wiki yet -- will initialize after first scan
-  echo "No skill wiki found. Will initialize on first scan."
-fi
-```
-
-### Step 2: Scan the Active Repo
-
-```bash
-python /path/to/scripts/scan_repo.py --repo "$REPO_PATH" --output /tmp/stack-profile.json
-```
-
-### Step 3: Resolve and Load
-
-```bash
-python /path/to/scripts/resolve_skills.py \
-  --profile /tmp/stack-profile.json \
-  --wiki "$WIKI" \
-  --available-skills /mnt/skills/ \
-  --output /tmp/skill-manifest.json
-```
-
-### Step 4: Apply the Manifest
-
-Load skills in the manifest. Unload everything else. Report what changed.
-
----
-
-## The Scanner
-
-### What It Detects
-
-The scanner reads repo structure and files to produce a **stack profile** -- a JSON
-document describing everything the project uses. Detection is evidence-based: every
-claim maps to a file or pattern that proves it.
-
-#### Detection Categories
-
-**1. Languages**
-- Primary language(s) by file count and LOC
-- Evidence: file extensions, shebangs, `*.lock` files
-
-**2. Frameworks & Libraries**
-- Web frameworks (React, Vue, Angular, Next.js, FastAPI, Django, Express, etc.)
-- ML/AI frameworks (PyTorch, TensorFlow, LangChain, LlamaIndex, CrewAI, etc.)
-- Mobile (React Native, Flutter, Swift, Kotlin)
-- Evidence: `package.json` deps, `requirements.txt`, `pyproject.toml`, `Cargo.toml`,
-  `go.mod`, import statements in entry files
-
-**3. Infrastructure & DevOps**
-- Containerization: Dockerfile, docker-compose.yml, .containerignore
-- CI/CD: `.github/workflows/`, `.gitlab-ci.yml`, `Jenkinsfile`, `.circleci/`
-- IaC: Terraform (`*.tf`), Pulumi, CDK, CloudFormation, Ansible
-- Cloud: AWS (SAM, CDK, `.aws/`), GCP, Azure config files
-- K8s: `k8s/`, `helm/`, `kustomization.yaml`
-- Evidence: config files, directory names
-
-**4. Data & Storage**
-- Databases: migrations dir, ORM configs (Prisma, SQLAlchemy, TypeORM, Drizzle)
-- Message queues: Kafka, RabbitMQ, Redis configs
-- Data pipelines: Airflow DAGs, dbt, Spark configs
-- Evidence: connection strings (redacted), migration files, schema files
-
-**5. Documentation & Content**
-- Docs generators: MkDocs, Docusaurus, Sphinx, VitePress
-- Content: markdown collections, MDX, RST
-- API specs: OpenAPI/Swagger YAML/JSON, GraphQL schemas
-- Evidence: config files, directory structure
-
-**6. Testing & Quality**
-- Test frameworks: pytest, Jest, Vitest, Cypress, Playwright
-- Linting: ESLint, Prettier, Ruff, Black, Clippy
-- Type checking: TypeScript config, mypy, pyright
-- Evidence: config files, test directories
-
-**7. AI/Agent Tooling**
-- MCP servers: `mcp.json`, `.mcp/`, server configs
-- Agent frameworks: LangGraph, CrewAI, AutoGen, Semantic Kernel
-- Prompt management: prompt files, template dirs
-- Model configs: `.env` with API keys (names only, never values), model references
-- Evidence: config files, import patterns
-
-**8. Build & Package**
-- Build tools: Webpack, Vite, esbuild, Turbopack, Bazel
-- Package managers: npm, yarn, pnpm, pip, poetry, cargo, go modules
-- Monorepo tools: Nx, Turborepo, Lerna, workspace configs
-- Evidence: config files, lock files
-
-### Stack Profile Schema
-
-```json
-{
-  "repo_path": "/absolute/path",
-  "scanned_at": "ISO-8601",
-  "languages": [
-    {
-      "name": "python",
-      "confidence": 0.95,
-      "evidence": ["pyproject.toml", "87 .py files", "poetry.lock"],
-      "version_hint": ">=3.11 (pyproject.toml python_requires)"
-    }
-  ],
-  "frameworks": [
-    {
-      "name": "fastapi",
-      "category": "web",
-      "confidence": 0.99,
-      "evidence": ["pyproject.toml dependency", "main.py imports FastAPI"]
-    }
-  ],
-  "infrastructure": [
-    {
-      "name": "docker",
-      "confidence": 1.0,
-      "evidence": ["Dockerfile", "docker-compose.yml"]
-    }
-  ],
-  "data_stores": [],
-  "testing": [],
-  "ai_tooling": [],
-  "build_system": [],
-  "docs": [],
-  "project_type": "api-service",
-  "monorepo": false,
-  "workspace_packages": [],
-  "custom_signals": {}
-}
-```
-
-### Scanning Rules
-
-1. **Never read file contents unless necessary.** Start with directory listing and
-   filenames. Only open files when you need to disambiguate (e.g., is this React or
-   Preact? Check the import in the entry file).
-
-2. **Confidence scoring:**
-   - 1.0 = definitive (lock file, explicit config)
-   - 0.8-0.99 = strong (dependency listed, config present)
-   - 0.5-0.79 = probable (file patterns match, no explicit config)
-   - <0.5 = speculative (mention in README, commented-out code) -- do not include
-
-3. **Depth limits:**
-   - Directory tree: 3 levels deep max for initial scan
-   - `node_modules/`, `.git/`, `__pycache__/`, `venv/`, `.venv/`: skip entirely
-   - For monorepos, scan each workspace package as a sub-profile
-
-4. **Performance budget:** The scan should complete in under 10 seconds for repos up
-   to 10K files. Use `find` with exclusions, not recursive `ls`.
-
-5. **Version detection:** Extract version constraints from config files when available.
-   This helps select skill variants (e.g., React 18 vs React 19 patterns differ).
-
----
-
-## The Resolver
-
-The resolver takes a stack profile and produces a **skill manifest** -- the exact set
-of skills, plugins, and MCP servers to load.
-
-### Resolution Algorithm
-
-```
-1. For each detected stack element (language, framework, infra, etc.):
-   a. Look up in skill-stack-matrix.md which skills serve this element
-   b. Check the wiki for any user-configured overrides or preferences
-   c. Add to candidate set with priority score
-
-2. Deduplicate:
-   - If two skills cover the same capability, prefer the more specific one
-   - Example: generic "python" skill vs "fastapi" skill -- keep fastapi, drop generic python
-
-3. Check for required companions:
-   - Some skills require others (e.g., "docker" skill needs "dockerfile-lint" if Dockerfile exists)
-   - Read companion rules from skill-stack-matrix.md
-
-4. Check for conflicts:
-   - Some skills conflict (e.g., two different CSS-in-JS skills)
-   - Resolve by: user preference (wiki) > specificity > recency
-
-5. Apply user overrides:
-   - Wiki pages in entities/ may have "always_load: true" or "never_load: true" flags
-   - These override the algorithm
-
-6. Produce the manifest
-```
-
-### Skill Manifest Schema
-
-```json
-{
-  "generated_at": "ISO-8601",
-  "repo_path": "/absolute/path",
-  "profile_hash": "sha256 of stack profile",
-  "load": [
-    {
-      "skill": "fastapi",
-      "path": "/mnt/skills/public/fastapi/SKILL.md",
-      "reason": "FastAPI detected in pyproject.toml dependencies",
-      "priority": 1
-    }
-  ],
-  "unload": [
-    {
-      "skill": "react",
-      "reason": "No frontend framework detected in repo"
-    }
-  ],
-  "mcp_servers": [
-    {
-      "name": "github",
-      "url": "https://github.mcp.example.com",
-      "reason": ".github/ directory with workflows detected"
-    }
-  ],
-  "plugins": [],
-  "warnings": [
-    "Detected Terraform but no terraform skill is installed. Consider adding one."
-  ],
-  "suggestions": [
-    {
-      "skill": "openapi-generator",
-      "reason": "OpenAPI spec found at api/openapi.yaml but no API generation skill loaded",
-      "install_from": "marketplace:anthropic/openapi-gen"
-    }
-  ]
-}
-```
-
-### Priority Scoring
-
-Skills are ordered by priority so the most relevant instructions appear first in context:
-
-| Signal | Priority Boost |
-|---|---|
-| Framework detected with confidence >= 0.9 | +10 |
-| User marked "always_load" in wiki | +20 |
-| Skill used in last 3 sessions (from wiki log) | +5 |
-| Skill covers primary language | +8 |
-| Skill covers secondary tooling (linting, testing) | +3 |
-| Skill is generic/fallback | +1 |
-
----
-
-## The Wiki (Persistent Catalog)
-
-The skill router maintains a wiki following the Karpathy LLM Wiki pattern. This is
-the router's long-term memory -- it tracks what's available, what's been used, and
-what the user prefers.
-
-### Wiki Location
-
-Default: `~/skill-wiki` (configurable via `skills.config.wiki.path`)
-
-### Wiki Structure
-
-```
-skill-wiki/
-├── SCHEMA.md               # Conventions for this wiki domain
-├── index.md                 # Catalog of all pages
-├── log.md                   # Action log (scans, loads, installs)
-├── raw/                     # Layer 1: Immutable source data
-│   ├── scans/               # Historical stack profile JSONs
-│   └── marketplace-dumps/   # Cached marketplace listings
-├── entities/                # Layer 2: One page per skill/plugin/MCP server
-│   ├── skills/
-│   ├── plugins/
-│   └── mcp-servers/
-├── concepts/                # Layer 2: Stack patterns, best practices
-├── comparisons/             # Layer 2: Skill-vs-skill analyses
-└── queries/                 # Layer 2: Resolved decision records
-```
-
-### SCHEMA.md for the Skill Wiki
-
-```markdown
-# Skill Wiki Schema
-
-## Domain
-Catalog and management of all available skills, plugins, MCP servers, and
-marketplace sources for the agent development environment. Tracks what exists,
-what's been used, what works well, and user preferences.
-
-## Conventions
-- File names: lowercase, hyphens, no spaces
-- Every page starts with YAML frontmatter
-- Use [[wikilinks]] between pages (min 2 outbound per page)
-- Bump `updated` on every change
-- Every new page goes in index.md
-- Every action appends to log.md
-
-## Frontmatter for Entity Pages (Skills/Plugins/MCP)
-
-  ```yaml
-  ---
-  title: Skill Name
-  created: YYYY-MM-DD
-  updated: YYYY-MM-DD
-  type: skill | plugin | mcp-server | marketplace
-  status: installed | available | deprecated | broken
-  tags: [from taxonomy]
-  source: local | marketplace-name | github-url
-  path: /mnt/skills/public/skill-name/SKILL.md
-  stacks: [python, fastapi, docker]
-  always_load: false
-  never_load: false
-  last_used: YYYY-MM-DD
-  use_count: 0
-  avg_session_rating: null
-  notes: ""
-  ---
-  ```
-
-## Tag Taxonomy
-- Stack: python, javascript, typescript, rust, go, java, ruby, swift, kotlin
-- Framework: react, vue, angular, nextjs, fastapi, django, express, flask
-- Infra: docker, kubernetes, terraform, ci-cd, aws, gcp, azure
-- Data: sql, nosql, redis, kafka, spark, dbt, airflow
-- AI: llm, agents, mcp, langchain, embeddings, fine-tuning, rag
-- Quality: testing, linting, typing, security, performance
-- Docs: documentation, api-spec, markdown, diagrams
-- Meta: comparison, decision, pattern, troubleshooting
-- Management: marketplace, registry, versioning, compatibility
-
-## Page Thresholds
-- Create a page when a skill/plugin/MCP server is discovered (installed or available)
-- Update usage/configuration metadata when the local user changes preferences
-- When a new version or replacement content is found, emit an update review
-  first; do not replace the entity by default
-- Archive when deprecated or superseded with a note pointing to the replacement
-
-## Update Policy
-- New version of a skill, agent, MCP server, or harness: compare the existing
-  entity/local asset with the proposed replacement, list benefits and risks,
-  and require the explicit update flag before replacing content
-- Skill conflict discovered: create a comparison page, update both entity pages
-- User preference expressed: update entity frontmatter (always_load/never_load)
-```
-
-### Entity Page Template (Skill)
-
-```markdown
----
-title: FastAPI Skill
-created: 2026-04-08
-updated: 2026-04-08
-type: skill
-status: installed
-tags: [python, fastapi, web]
-source: local
-path: /mnt/skills/public/fastapi/SKILL.md
-stacks: [python, fastapi]
-always_load: false
-never_load: false
-last_used: 2026-04-07
-use_count: 12
-avg_session_rating: 4.5
-notes: "Works well for API scaffolding. Occasionally suggests Pydantic v1 patterns."
----
-
-# FastAPI Skill
-
-## Overview
-Generates FastAPI applications, routes, middleware, and deployment configs.
-
-## Capabilities
-- Scaffold new FastAPI projects
-- Generate route handlers with Pydantic models
-- Add middleware (CORS, auth, rate limiting)
-- Generate OpenAPI spec customizations
-- Docker + uvicorn deployment configs
-
-## Stack Affinity
-Primary: [[python]], [[fastapi]]
-Secondary: [[docker]], [[openapi]]
-Companions: [[pydantic-skill]] (recommended), [[sqlalchemy-skill]] (if DB detected)
-Conflicts: [[flask-skill]] (overlapping web framework)
-
-## Usage History
-| Date | Repo | Outcome |
-|------|------|---------|
-| 2026-04-07 | /home/user/api-project | Generated 12 routes, good |
-| 2026-03-29 | /home/user/microservice | Scaffold + Docker, good |
-
-## Known Issues
-- Suggests `from pydantic import BaseModel` without checking if v2 `model_validator` is needed
-- Does not handle GraphQL integration (use [[graphql-skill]] instead)
-
-## Sources
-- [[raw/marketplace-dumps/anthropic-marketplace-2026-04.md]]
-```
-
-### Marketplace Integration
-
-The wiki tracks marketplace sources so the router can suggest skills the user
-doesn't have yet.
-
-#### Marketplace Entity Page
-
-```markdown
----
-title: Anthropic Marketplace
-created: 2026-04-08
-updated: 2026-04-08
-type: marketplace
-status: active
-tags: [marketplace, registry]
-url: https://marketplace.anthropic.com/skills
-refresh_interval_days: 7
-last_refreshed: 2026-04-08
----
-
-# Anthropic Marketplace
-
-## Overview
-Official skill marketplace maintained by Anthropic.
-
-## How to Query
-- API: GET /api/v1/skills?stack=python&category=web
-- CLI: `hermes marketplace search --query "fastapi"`
-
-## Cached Listings
-See [[raw/marketplace-dumps/anthropic-marketplace-2026-04.md]]
-
-## Install Command
-`hermes skill install marketplace:anthropic/<skill-name>`
-```
-
-#### Marketplace Refresh
-
-When the router detects a stack element with no matching installed skill:
-1. Check marketplace entity pages for `last_refreshed`
-2. If stale (> `refresh_interval_days`), re-query the marketplace
-3. Save new listing dump to `raw/marketplace-dumps/`
-4. Create entity pages for newly discovered skills; existing pages require an
-   update review and explicit update flag before replacement
-5. Include in the manifest's `suggestions` array
-
----
-
-## Core Operations
-
-### 1. Full Scan (repo switch or first run)
-
-Triggers: user opens a new project, says "scan my repo", switches working directory
-
-```
-① Read wiki orientation (SCHEMA, index, recent log)
-② Run scan_repo.py on the target repo
-③ Save scan result to raw/scans/scan-YYYY-MM-DD-reponame.json
-④ Run resolve_skills.py with the profile + wiki
-⑤ Present the manifest to the user:
-   - "Loading: [list with reasons]"
-   - "Unloading: [list]"
-   - "Suggestions: [skills you don't have but might want]"
-   - "Warnings: [gaps detected]"
-⑥ On user confirmation, apply the manifest
-⑦ Update wiki:
-   - Bump last_used and use_count on loaded skill entity pages
-   - Create entity pages for any newly discovered skills
-   - Append to log.md
-⑧ Update index.md if new pages were created
-```
-
-### 2. Incremental Scan (file changes during session)
-
-Triggers: user creates a new config file, adds a dependency, installs a package
-
-The router watches for signals that the stack changed mid-session:
-- New `Dockerfile` created -> check if docker skill is loaded
-- `package.json` modified -> re-scan dependencies
-- New `.github/workflows/` file -> check CI/CD skills
-- New `*.tf` files -> check terraform skill
-
-For incremental scans:
-```
-① Re-scan only the changed area (single file or directory)
-② Diff against the current manifest
-③ If new skills needed: "I noticed you added [X]. Want me to load the [Y] skill?"
-④ If skills can be unloaded: "You removed [X]. I can unload the [Y] skill to free context."
-⑤ Apply changes on confirmation
-⑥ Log the incremental update
-```
-
-### 3. Manual Override
-
-Users can force-load or force-unload skills:
-
-- "Always load the docker skill" -> set `always_load: true` in wiki entity page
-- "Never load the react skill" -> set `never_load: true` in wiki entity page
-- "Load the terraform skill for this session" -> temporary load, no wiki change
-- "What skills am I running?" -> show current manifest with reasons
-
-### 4. Skill Discovery
-
-When the user asks "what skills exist for X" or "is there a skill for Y":
-
-```
-① Search wiki entity pages for matching tags/stacks
-② If found: show the entity page summary, status, and rating
-③ If not found: query marketplace entity pages
-④ If marketplace has it: suggest installation with command
-⑤ If nowhere: note the gap, suggest creating a custom skill
-⑥ Log the query
-```
-
-### 5. Wiki Maintenance (Lint)
-
-Runs the standard LLM Wiki lint plus skill-specific checks:
-
-- **Stale skills**: entity pages with `last_used` > 90 days
-- **Ghost skills**: entity pages with `status: installed` but path doesn't exist
-- **Orphan skills**: installed skills with no entity page in the wiki
-- **Marketplace staleness**: marketplaces not refreshed within their interval
-- **Conflict detection**: skills with overlapping `stacks` that are both `always_load`
-- **Usage cold spots**: skills with `use_count: 0` after 30+ days -- suggest removal
-- Standard wiki lint: orphan pages, broken links, index completeness, frontmatter validation
-
----
-
-## Integration with Karpathy LLM Wiki
-
-This skill extends the LLM Wiki pattern. If the user also has a general-purpose
-knowledge wiki (separate from the skill wiki), the two coexist:
-
-- **Skill wiki** (`~/skill-wiki`): managed by skill-router, tracks tooling
-- **Knowledge wiki** (`~/wiki`): managed by llm-wiki skill, tracks domain knowledge
-
-Cross-references between wikis use full paths: `[[~/wiki/concepts/rag.md|RAG]]`
-rather than bare wikilinks (which resolve within the same wiki).
-
-The skill-router's wiki follows all LLM Wiki conventions:
-- Three-layer architecture (raw / entities-concepts / schema)
-- Frontmatter on every page
-- Tag taxonomy in SCHEMA.md
-- Append-only log with rotation
-- Lint for consistency
-- Obsidian-compatible wikilinks
-
-The key extension is the **entity frontmatter** -- skill/plugin/MCP pages carry
-operational metadata (status, path, stacks, always_load, use_count) that the
-resolver reads programmatically. This is what makes the wiki active rather than
-passive -- it doesn't just store knowledge, it drives loading decisions.
-
----
-
-## Reporting
-
-After every scan, the router produces a concise report:
-
-```
-## Skill Router Report -- [repo-name]
-Scanned: YYYY-MM-DD HH:MM
-
-### Stack Profile
-- Languages: Python 3.11, TypeScript 5.4
-- Frameworks: FastAPI, React 18
-- Infra: Docker, GitHub Actions
-- Data: PostgreSQL (SQLAlchemy), Redis
-- AI: LangChain, MCP (2 servers configured)
-
-### Loaded (6 skills)
-1. fastapi (confidence: 0.99) -- pyproject.toml
-2. react (confidence: 0.95) -- package.json
-3. docker (confidence: 1.0) -- Dockerfile
-4. sqlalchemy (confidence: 0.9) -- alembic/
-5. langchain (confidence: 0.85) -- imports in agent.py
-6. github-actions (confidence: 1.0) -- .github/workflows/
-
-### Unloaded (24 skills)
-[collapsed list]
-
-### Suggestions
-- openapi-generator: OpenAPI spec found but no generation skill
-- redis-skill: Redis connection in docker-compose but no Redis skill
-
-### Warnings
-- No testing skill loaded but pytest.ini exists -- add pytest skill?
-```
-
----
-
-## Handling Edge Cases
-
-**Monorepos**: Scan each workspace package separately. Produce a merged manifest
-that includes skills for all packages, with per-package annotations.
-
-**Empty repos**: Report "No stack detected. This looks like a new project."
-Ask what the user plans to build, then suggest a starter skill set.
-
-**Conflicting signals**: If the repo has both `requirements.txt` AND `package.json`,
-it's a polyglot project. Load skills for both stacks. Note: confidence drops if
-files look abandoned (empty, very old timestamps).
-
-**Skill not found**: If the resolver identifies a need but no skill exists for it,
-log a gap in the wiki and include in `warnings`. Suggest marketplace search or
-custom skill creation.
-
-**User disagrees with scan**: "No, I don't use React anymore, that's legacy code."
-Mark react skill as `never_load` in wiki, note the reason. The scan still sees the
-files but the override takes precedence.
-
----
-
-## Configuration
-
-In `~/.hermes/config.yaml` (or equivalent agent config):
-
-```yaml
-skills:
-  config:
-    skill-router:
-      wiki_path: ~/skill-wiki
-      auto_scan: true          # Scan on repo switch
-      auto_load: false         # Require confirmation before loading
-      scan_depth: 3            # Directory depth for initial scan
-      marketplace_refresh: 7   # Days between marketplace cache refresh
-      max_loaded_skills: 15    # Hard cap on simultaneous skills
-      incremental_watch: true  # Monitor file changes mid-session
-      report_verbosity: normal # minimal | normal | verbose
-```
-
----
-
-## Pitfalls
-
-- **Never skip wiki orientation.** Reading SCHEMA + index + log before acting prevents
-  duplicates and missed context. This is the #1 cause of wiki degradation.
-- **Never load all skills "just in case."** The whole point is selective loading.
-  If the user needs something unexpected, incremental scan catches it.
-- **Never modify raw/ files.** Scan results and marketplace dumps are immutable records.
-- **Always confirm before loading/unloading.** Unless `auto_load: true` is configured.
-- **Don't over-scan.** Reading every file in a 50K-file monorepo is wasteful. Use
-  directory structure and config files first, open source files only to disambiguate.
-- **Keep entity pages current.** A stale wiki is worse than no wiki -- it makes wrong
-  loading decisions. Run lint monthly.
-- **Respect `never_load`.** User overrides are sacrosanct. Don't re-suggest skills
-  the user has explicitly rejected (unless they ask).
-- **Log everything.** The log is how the router learns patterns across sessions.
-  "Last 3 times this repo was opened, the user also loaded X" is valuable signal.
+---
+name: skill-router
+description: "Repo-aware skill and plugin manager. Scans the user's active repository, identifies the tech stack, frameworks, and workflows in use, then loads ONLY the relevant skills, plugins, and MCP servers -- unloading everything else to keep the context clean. Maintains a persistent LLM Wiki catalog of all available skills, plugins, and marketplaces so decisions are informed and consistent across sessions. Use this skill whenever the user opens a project, switches repos, asks 'what skills do I need', mentions context bloat or slow responses, asks to manage/list/add/remove skills or plugins, or references their skill catalog/wiki. Also triggers on: 'scan my repo', 'what tools do I need for this project', 'clean up my skills', 'too many plugins loaded', 'optimize my context', or any repo-switch event."
+---
+
+# Skill Router
+
+Scan a repo. Know what it needs. Load only that. Maintain a wiki of everything available.
+
+## Problem
+
+Every skill, plugin, and MCP server loaded into context costs tokens and attention.
+Most projects need 3-8 skills out of 30+. Loading all of them:
+- Wastes context window on irrelevant instructions
+- Causes skill misfires (wrong skill triggers for a task)
+- Slows response time
+- Creates conflicting instructions between skills
+
+## Architecture
+
+```
+skill-router/
+├── SKILL.md                    # This file -- orchestration logic
+├── references/
+│   ├── stack-signatures.md     # File/config patterns mapped to stack identifiers
+│   ├── skill-stack-matrix.md   # Which skills serve which stacks
+│   └── marketplace-registry.md # Known marketplaces and how to query them
+└── scripts/
+    ├── scan_repo.py            # Repo scanner -- outputs stack profile JSON
+    ├── resolve_skills.py       # Maps stack profile to skill set
+    └── wiki_sync.py            # Syncs scan results into the wiki
+```
+
+The skill router has two halves:
+1. **The Scanner** -- analyzes a repo and produces a stack profile
+2. **The Wiki** -- persistent catalog of all available skills/plugins/marketplaces,
+   maintained via the Karpathy LLM Wiki pattern
+
+## Session Startup (CRITICAL -- do this every time)
+
+When this skill activates, follow this sequence:
+
+### Step 1: Orient from the Wiki
+
+```bash
+WIKI="${SKILL_ROUTER_WIKI:-$HOME/skill-wiki}"
+if [ -d "$WIKI" ]; then
+  # Existing wiki -- orient first
+  cat "$WIKI/SCHEMA.md"
+  cat "$WIKI/index.md"
+  tail -30 "$WIKI/log.md"
+else
+  # No wiki yet -- will initialize after first scan
+  echo "No skill wiki found. Will initialize on first scan."
+fi
+```
+
+### Step 2: Scan the Active Repo
+
+```bash
+python /path/to/scripts/scan_repo.py --repo "$REPO_PATH" --output /tmp/stack-profile.json
+```
+
+### Step 3: Resolve and Load
+
+```bash
+python /path/to/scripts/resolve_skills.py \
+  --profile /tmp/stack-profile.json \
+  --wiki "$WIKI" \
+  --available-skills /mnt/skills/ \
+  --output /tmp/skill-manifest.json
+```
+
+### Step 4: Apply the Manifest
+
+Load skills in the manifest. Unload everything else. Report what changed.
+
+---
+
+## The Scanner
+
+### What It Detects
+
+The scanner reads repo structure and files to produce a **stack profile** -- a JSON
+document describing everything the project uses. Detection is evidence-based: every
+claim maps to a file or pattern that proves it.
+
+#### Detection Categories
+
+**1. Languages**
+- Primary language(s) by file count and LOC
+- Evidence: file extensions, shebangs, `*.lock` files
+
+**2. Frameworks & Libraries**
+- Web frameworks (React, Vue, Angular, Next.js, FastAPI, Django, Express, etc.)
+- ML/AI frameworks (PyTorch, TensorFlow, LangChain, LlamaIndex, CrewAI, etc.)
+- Mobile (React Native, Flutter, Swift, Kotlin)
+- Evidence: `package.json` deps, `requirements.txt`, `pyproject.toml`, `Cargo.toml`,
+  `go.mod`, import statements in entry files
+
+**3. Infrastructure & DevOps**
+- Containerization: Dockerfile, docker-compose.yml, .containerignore
+- CI/CD: `.github/workflows/`, `.gitlab-ci.yml`, `Jenkinsfile`, `.circleci/`
+- IaC: Terraform (`*.tf`), Pulumi, CDK, CloudFormation, Ansible
+- Cloud: AWS (SAM, CDK, `.aws/`), GCP, Azure config files
+- K8s: `k8s/`, `helm/`, `kustomization.yaml`
+- Evidence: config files, directory names
+
+**4. Data & Storage**
+- Databases: migrations dir, ORM configs (Prisma, SQLAlchemy, TypeORM, Drizzle)
+- Message queues: Kafka, RabbitMQ, Redis configs
+- Data pipelines: Airflow DAGs, dbt, Spark configs
+- Evidence: connection strings (redacted), migration files, schema files
+
+**5. Documentation & Content**
+- Docs generators: MkDocs, Docusaurus, Sphinx, VitePress
+- Content: markdown collections, MDX, RST
+- API specs: OpenAPI/Swagger YAML/JSON, GraphQL schemas
+- Evidence: config files, directory structure
+
+**6. Testing & Quality**
+- Test frameworks: pytest, Jest, Vitest, Cypress, Playwright
+- Linting: ESLint, Prettier, Ruff, Black, Clippy
+- Type checking: TypeScript config, mypy, pyright
+- Evidence: config files, test directories
+
+**7. AI/Agent Tooling**
+- MCP servers: `mcp.json`, `.mcp/`, server configs
+- Agent frameworks: LangGraph, CrewAI, AutoGen, Semantic Kernel
+- Prompt management: prompt files, template dirs
+- Model configs: `.env` with API keys (names only, never values), model references
+- Evidence: config files, import patterns
+
+**8. Build & Package**
+- Build tools: Webpack, Vite, esbuild, Turbopack, Bazel
+- Package managers: npm, yarn, pnpm, pip, poetry, cargo, go modules
+- Monorepo tools: Nx, Turborepo, Lerna, workspace configs
+- Evidence: config files, lock files
+
+### Stack Profile Schema
+
+```json
+{
+  "repo_path": "/absolute/path",
+  "scanned_at": "ISO-8601",
+  "languages": [
+    {
+      "name": "python",
+      "confidence": 0.95,
+      "evidence": ["pyproject.toml", "87 .py files", "poetry.lock"],
+      "version_hint": ">=3.11 (pyproject.toml python_requires)"
+    }
+  ],
+  "frameworks": [
+    {
+      "name": "fastapi",
+      "category": "web",
+      "confidence": 0.99,
+      "evidence": ["pyproject.toml dependency", "main.py imports FastAPI"]
+    }
+  ],
+  "infrastructure": [
+    {
+      "name": "docker",
+      "confidence": 1.0,
+      "evidence": ["Dockerfile", "docker-compose.yml"]
+    }
+  ],
+  "data_stores": [],
+  "testing": [],
+  "ai_tooling": [],
+  "build_system": [],
+  "docs": [],
+  "project_type": "api-service",
+  "monorepo": false,
+  "workspace_packages": [],
+  "custom_signals": {}
+}
+```
+
+### Scanning Rules
+
+1. **Never read file contents unless necessary.** Start with directory listing and
+   filenames. Only open files when you need to disambiguate (e.g., is this React or
+   Preact? Check the import in the entry file).
+
+2. **Confidence scoring:**
+   - 1.0 = definitive (lock file, explicit config)
+   - 0.8-0.99 = strong (dependency listed, config present)
+   - 0.5-0.79 = probable (file patterns match, no explicit config)
+   - <0.5 = speculative (mention in README, commented-out code) -- do not include
+
+3. **Depth limits:**
+   - Directory tree: 3 levels deep max for initial scan
+   - `node_modules/`, `.git/`, `__pycache__/`, `venv/`, `.venv/`: skip entirely
+   - For monorepos, scan each workspace package as a sub-profile
+
+4. **Performance budget:** The scan should complete in under 10 seconds for repos up
+   to 10K files. Use `find` with exclusions, not recursive `ls`.
+
+5. **Version detection:** Extract version constraints from config files when available.
+   This helps select skill variants (e.g., React 18 vs React 19 patterns differ).
+
+---
+
+## The Resolver
+
+The resolver takes a stack profile and produces a **skill manifest** -- the exact set
+of skills, plugins, and MCP servers to load.
+
+### Resolution Algorithm
+
+```
+1. For each detected stack element (language, framework, infra, etc.):
+   a. Look up in skill-stack-matrix.md which skills serve this element
+   b. Check the wiki for any user-configured overrides or preferences
+   c. Add to candidate set with priority score
+
+2. Deduplicate:
+   - If two skills cover the same capability, prefer the more specific one
+   - Example: generic "python" skill vs "fastapi" skill -- keep fastapi, drop generic python
+
+3. Check for required companions:
+   - Some skills require others (e.g., "docker" skill needs "dockerfile-lint" if Dockerfile exists)
+   - Read companion rules from skill-stack-matrix.md
+
+4. Check for conflicts:
+   - Some skills conflict (e.g., two different CSS-in-JS skills)
+   - Resolve by: user preference (wiki) > specificity > recency
+
+5. Apply user overrides:
+   - Wiki pages in entities/ may have "always_load: true" or "never_load: true" flags
+   - These override the algorithm
+
+6. Produce the manifest
+```
+
+### Skill Manifest Schema
+
+```json
+{
+  "generated_at": "ISO-8601",
+  "repo_path": "/absolute/path",
+  "profile_hash": "sha256 of stack profile",
+  "load": [
+    {
+      "skill": "fastapi",
+      "path": "/mnt/skills/public/fastapi/SKILL.md",
+      "reason": "FastAPI detected in pyproject.toml dependencies",
+      "priority": 1
+    }
+  ],
+  "unload": [
+    {
+      "skill": "react",
+      "reason": "No frontend framework detected in repo"
+    }
+  ],
+  "mcp_servers": [
+    {
+      "name": "github",
+      "url": "https://github.mcp.example.com",
+      "reason": ".github/ directory with workflows detected"
+    }
+  ],
+  "plugins": [],
+  "warnings": [
+    "Detected Terraform but no terraform skill is installed. Consider adding one."
+  ],
+  "suggestions": [
+    {
+      "skill": "openapi-generator",
+      "reason": "OpenAPI spec found at api/openapi.yaml but no API generation skill loaded",
+      "install_from": "marketplace:anthropic/openapi-gen"
+    }
+  ]
+}
+```
+
+### Priority Scoring
+
+Skills are ordered by priority so the most relevant instructions appear first in context:
+
+| Signal | Priority Boost |
+|---|---|
+| Framework detected with confidence >= 0.9 | +10 |
+| User marked "always_load" in wiki | +20 |
+| Skill used in last 3 sessions (from wiki log) | +5 |
+| Skill covers primary language | +8 |
+| Skill covers secondary tooling (linting, testing) | +3 |
+| Skill is generic/fallback | +1 |
+
+---
+
+## The Wiki (Persistent Catalog)
+
+The skill router maintains a wiki following the Karpathy LLM Wiki pattern. This is
+the router's long-term memory -- it tracks what's available, what's been used, and
+what the user prefers.
+
+### Wiki Location
+
+Default: `~/skill-wiki` (configurable via `skills.config.wiki.path`)
+
+### Wiki Structure
+
+```
+skill-wiki/
+├── SCHEMA.md               # Conventions for this wiki domain
+├── index.md                 # Catalog of all pages
+├── log.md                   # Action log (scans, loads, installs)
+├── raw/                     # Layer 1: Immutable source data
+│   ├── scans/               # Historical stack profile JSONs
+│   └── marketplace-dumps/   # Cached marketplace listings
+├── entities/                # Layer 2: One page per skill/plugin/MCP server
+│   ├── skills/
+│   ├── plugins/
+│   └── mcp-servers/
+├── concepts/                # Layer 2: Stack patterns, best practices
+├── comparisons/             # Layer 2: Skill-vs-skill analyses
+└── queries/                 # Layer 2: Resolved decision records
+```
+
+### SCHEMA.md for the Skill Wiki
+
+```markdown
+# Skill Wiki Schema
+
+## Domain
+Catalog and management of all available skills, plugins, MCP servers, and
+marketplace sources for the agent development environment. Tracks what exists,
+what's been used, what works well, and user preferences.
+
+## Conventions
+- File names: lowercase, hyphens, no spaces
+- Every page starts with YAML frontmatter
+- Use [[wikilinks]] between pages (min 2 outbound per page)
+- Bump `updated` on every change
+- Every new page goes in index.md
+- Every action appends to log.md
+
+## Frontmatter for Entity Pages (Skills/Plugins/MCP)
+
+  ```yaml
+  ---
+  title: Skill Name
+  created: YYYY-MM-DD
+  updated: YYYY-MM-DD
+  type: skill | plugin | mcp-server | marketplace
+  status: installed | available | deprecated | broken
+  tags: [from taxonomy]
+  source: local | marketplace-name | github-url
+  path: /mnt/skills/public/skill-name/SKILL.md
+  stacks: [python, fastapi, docker]
+  always_load: false
+  never_load: false
+  last_used: YYYY-MM-DD
+  use_count: 0
+  avg_session_rating: null
+  notes: ""
+  ---
+  ```
+
+## Tag Taxonomy
+- Stack: python, javascript, typescript, rust, go, java, ruby, swift, kotlin
+- Framework: react, vue, angular, nextjs, fastapi, django, express, flask
+- Infra: docker, kubernetes, terraform, ci-cd, aws, gcp, azure
+- Data: sql, nosql, redis, kafka, spark, dbt, airflow
+- AI: llm, agents, mcp, langchain, embeddings, fine-tuning, rag
+- Quality: testing, linting, typing, security, performance
+- Docs: documentation, api-spec, markdown, diagrams
+- Meta: comparison, decision, pattern, troubleshooting
+- Management: marketplace, registry, versioning, compatibility
+
+## Page Thresholds
+- Create a page when a skill/plugin/MCP server is discovered (installed or available)
+- Update usage/configuration metadata when the local user changes preferences
+- When a new version or replacement content is found, emit an update review
+  first; do not replace the entity by default
+- Archive when deprecated or superseded with a note pointing to the replacement
+
+## Update Policy
+- New version of a skill, agent, MCP server, or harness: compare the existing
+  entity/local asset with the proposed replacement, list benefits and risks,
+  and require the explicit update flag before replacing content
+- Skill conflict discovered: create a comparison page, update both entity pages
+- User preference expressed: update entity frontmatter (always_load/never_load)
+```
+
+### Entity Page Template (Skill)
+
+```markdown
+---
+title: FastAPI Skill
+created: 2026-04-08
+updated: 2026-04-08
+type: skill
+status: installed
+tags: [python, fastapi, web]
+source: local
+path: /mnt/skills/public/fastapi/SKILL.md
+stacks: [python, fastapi]
+always_load: false
+never_load: false
+last_used: 2026-04-07
+use_count: 12
+avg_session_rating: 4.5
+notes: "Works well for API scaffolding. Occasionally suggests Pydantic v1 patterns."
+---
+
+# FastAPI Skill
+
+## Overview
+Generates FastAPI applications, routes, middleware, and deployment configs.
+
+## Capabilities
+- Scaffold new FastAPI projects
+- Generate route handlers with Pydantic models
+- Add middleware (CORS, auth, rate limiting)
+- Generate OpenAPI spec customizations
+- Docker + uvicorn deployment configs
+
+## Stack Affinity
+Primary: [[python]], [[fastapi]]
+Secondary: [[docker]], [[openapi]]
+Companions: [[pydantic-skill]] (recommended), [[sqlalchemy-skill]] (if DB detected)
+Conflicts: [[flask-skill]] (overlapping web framework)
+
+## Usage History
+| Date | Repo | Outcome |
+|------|------|---------|
+| 2026-04-07 | /home/user/api-project | Generated 12 routes, good |
+| 2026-03-29 | /home/user/microservice | Scaffold + Docker, good |
+
+## Known Issues
+- Suggests `from pydantic import BaseModel` without checking if v2 `model_validator` is needed
+- Does not handle GraphQL integration (use [[graphql-skill]] instead)
+
+## Sources
+- [[raw/marketplace-dumps/anthropic-marketplace-2026-04.md]]
+```
+
+### Marketplace Integration
+
+The wiki tracks marketplace sources so the router can suggest skills the user
+doesn't have yet.
+
+#### Marketplace Entity Page
+
+```markdown
+---
+title: Anthropic Marketplace
+created: 2026-04-08
+updated: 2026-04-08
+type: marketplace
+status: active
+tags: [marketplace, registry]
+url: https://marketplace.anthropic.com/skills
+refresh_interval_days: 7
+last_refreshed: 2026-04-08
+---
+
+# Anthropic Marketplace
+
+## Overview
+Official skill marketplace maintained by Anthropic.
+
+## How to Query
+- API: GET /api/v1/skills?stack=python&category=web
+- CLI: `hermes marketplace search --query "fastapi"`
+
+## Cached Listings
+See [[raw/marketplace-dumps/anthropic-marketplace-2026-04.md]]
+
+## Install Command
+`hermes skill install marketplace:anthropic/<skill-name>`
+```
+
+#### Marketplace Refresh
+
+When the router detects a stack element with no matching installed skill:
+1. Check marketplace entity pages for `last_refreshed`
+2. If stale (> `refresh_interval_days`), re-query the marketplace
+3. Save new listing dump to `raw/marketplace-dumps/`
+4. Create entity pages for newly discovered skills; existing pages require an
+   update review and explicit update flag before replacement
+5. Include in the manifest's `suggestions` array
+
+---
+
+## Core Operations
+
+### 1. Full Scan (repo switch or first run)
+
+Triggers: user opens a new project, says "scan my repo", switches working directory
+
+```
+① Read wiki orientation (SCHEMA, index, recent log)
+② Run scan_repo.py on the target repo
+③ Save scan result to raw/scans/scan-YYYY-MM-DD-reponame.json
+④ Run resolve_skills.py with the profile + wiki
+⑤ Present the manifest to the user:
+   - "Loading: [list with reasons]"
+   - "Unloading: [list]"
+   - "Suggestions: [skills you don't have but might want]"
+   - "Warnings: [gaps detected]"
+⑥ On user confirmation, apply the manifest
+⑦ Update wiki:
+   - Bump last_used and use_count on loaded skill entity pages
+   - Create entity pages for any newly discovered skills
+   - Append to log.md
+⑧ Update index.md if new pages were created
+```
+
+### 2. Incremental Scan (file changes during session)
+
+Triggers: user creates a new config file, adds a dependency, installs a package
+
+The router watches for signals that the stack changed mid-session:
+- New `Dockerfile` created -> check if docker skill is loaded
+- `package.json` modified -> re-scan dependencies
+- New `.github/workflows/` file -> check CI/CD skills
+- New `*.tf` files -> check terraform skill
+
+For incremental scans:
+```
+① Re-scan only the changed area (single file or directory)
+② Diff against the current manifest
+③ If new skills needed: "I noticed you added [X]. Want me to load the [Y] skill?"
+④ If skills can be unloaded: "You removed [X]. I can unload the [Y] skill to free context."
+⑤ Apply changes on confirmation
+⑥ Log the incremental update
+```
+
+### 3. Manual Override
+
+Users can force-load or force-unload skills:
+
+- "Always load the docker skill" -> set `always_load: true` in wiki entity page
+- "Never load the react skill" -> set `never_load: true` in wiki entity page
+- "Load the terraform skill for this session" -> temporary load, no wiki change
+- "What skills am I running?" -> show current manifest with reasons
+
+### 4. Skill Discovery
+
+When the user asks "what skills exist for X" or "is there a skill for Y":
+
+```
+① Search wiki entity pages for matching tags/stacks
+② If found: show the entity page summary, status, and rating
+③ If not found: query marketplace entity pages
+④ If marketplace has it: suggest installation with command
+⑤ If nowhere: note the gap, suggest creating a custom skill
+⑥ Log the query
+```
+
+### 5. Wiki Maintenance (Lint)
+
+Runs the standard LLM Wiki lint plus skill-specific checks:
+
+- **Stale skills**: entity pages with `last_used` > 90 days
+- **Ghost skills**: entity pages with `status: installed` but path doesn't exist
+- **Orphan skills**: installed skills with no entity page in the wiki
+- **Marketplace staleness**: marketplaces not refreshed within their interval
+- **Conflict detection**: skills with overlapping `stacks` that are both `always_load`
+- **Usage cold spots**: skills with `use_count: 0` after 30+ days -- suggest removal
+- Standard wiki lint: orphan pages, broken links, index completeness, frontmatter validation
+
+---
+
+## Integration with Karpathy LLM Wiki
+
+This skill extends the LLM Wiki pattern. If the user also has a general-purpose
+knowledge wiki (separate from the skill wiki), the two coexist:
+
+- **Skill wiki** (`~/skill-wiki`): managed by skill-router, tracks tooling
+- **Knowledge wiki** (`~/wiki`): managed by llm-wiki skill, tracks domain knowledge
+
+Cross-references between wikis use full paths: `[[~/wiki/concepts/rag.md|RAG]]`
+rather than bare wikilinks (which resolve within the same wiki).
+
+The skill-router's wiki follows all LLM Wiki conventions:
+- Three-layer architecture (raw / entities-concepts / schema)
+- Frontmatter on every page
+- Tag taxonomy in SCHEMA.md
+- Append-only log with rotation
+- Lint for consistency
+- Obsidian-compatible wikilinks
+
+The key extension is the **entity frontmatter** -- skill/plugin/MCP pages carry
+operational metadata (status, path, stacks, always_load, use_count) that the
+resolver reads programmatically. This is what makes the wiki active rather than
+passive -- it doesn't just store knowledge, it drives loading decisions.
+
+---
+
+## Reporting
+
+After every scan, the router produces a concise report:
+
+```
+## Skill Router Report -- [repo-name]
+Scanned: YYYY-MM-DD HH:MM
+
+### Stack Profile
+- Languages: Python 3.11, TypeScript 5.4
+- Frameworks: FastAPI, React 18
+- Infra: Docker, GitHub Actions
+- Data: PostgreSQL (SQLAlchemy), Redis
+- AI: LangChain, MCP (2 servers configured)
+
+### Loaded (6 skills)
+1. fastapi (confidence: 0.99) -- pyproject.toml
+2. react (confidence: 0.95) -- package.json
+3. docker (confidence: 1.0) -- Dockerfile
+4. sqlalchemy (confidence: 0.9) -- alembic/
+5. langchain (confidence: 0.85) -- imports in agent.py
+6. github-actions (confidence: 1.0) -- .github/workflows/
+
+### Unloaded (24 skills)
+[collapsed list]
+
+### Suggestions
+- openapi-generator: OpenAPI spec found but no generation skill
+- redis-skill: Redis connection in docker-compose but no Redis skill
+
+### Warnings
+- No testing skill loaded but pytest.ini exists -- add pytest skill?
+```
+
+---
+
+## Handling Edge Cases
+
+**Monorepos**: Scan each workspace package separately. Produce a merged manifest
+that includes skills for all packages, with per-package annotations.
+
+**Empty repos**: Report "No stack detected. This looks like a new project."
+Ask what the user plans to build, then suggest a starter skill set.
+
+**Conflicting signals**: If the repo has both `requirements.txt` AND `package.json`,
+it's a polyglot project. Load skills for both stacks. Note: confidence drops if
+files look abandoned (empty, very old timestamps).
+
+**Skill not found**: If the resolver identifies a need but no skill exists for it,
+log a gap in the wiki and include in `warnings`. Suggest marketplace search or
+custom skill creation.
+
+**User disagrees with scan**: "No, I don't use React anymore, that's legacy code."
+Mark react skill as `never_load` in wiki, note the reason. The scan still sees the
+files but the override takes precedence.
+
+---
+
+## Configuration
+
+In `~/.hermes/config.yaml` (or equivalent agent config):
+
+```yaml
+skills:
+  config:
+    skill-router:
+      wiki_path: ~/skill-wiki
+      auto_scan: true          # Scan on repo switch
+      auto_load: false         # Require confirmation before loading
+      scan_depth: 3            # Directory depth for initial scan
+      marketplace_refresh: 7   # Days between marketplace cache refresh
+      max_loaded_skills: 15    # Hard cap on simultaneous skills
+      incremental_watch: true  # Monitor file changes mid-session
+      report_verbosity: normal # minimal | normal | verbose
+```
+
+---
+
+## Pitfalls
+
+- **Never skip wiki orientation.** Reading SCHEMA + index + log before acting prevents
+  duplicates and missed context. This is the #1 cause of wiki degradation.
+- **Never load all skills "just in case."** The whole point is selective loading.
+  If the user needs something unexpected, incremental scan catches it.
+- **Never modify raw/ files.** Scan results and marketplace dumps are immutable records.
+- **Always confirm before loading/unloading.** Unless `auto_load: true` is configured.
+- **Don't over-scan.** Reading every file in a 50K-file monorepo is wasteful. Use
+  directory structure and config files first, open source files only to disambiguate.
+- **Keep entity pages current.** A stale wiki is worse than no wiki -- it makes wrong
+  loading decisions. Run lint monthly.
+- **Respect `never_load`.** User overrides are sacrosanct. Don't re-suggest skills
+  the user has explicitly rejected (unless they ask).
+- **Log everything.** The log is how the router learns patterns across sessions.
+  "Last 3 times this repo was opened, the user also loaded X" is valuable signal.

docs/dashboard.md

@@ -36,7 +36,7 @@ MCP server pages use the sharded layout
 routes `/wiki/<slug>` to the same shard convention. Harness pages use
 the flat `entities/harnesses/<slug>.md` layout. Each card shows:
 
-- the slug (click to open `/wiki/<slug>?type=<entity>`)
+- the slug (click to open `/wiki/<slug>?type=<entity>`)
 - the quality grade pill (A/B/C/D/F) when the entity has a sidecar,
   otherwise a `skill`, `agent`, `mcp-server`, or `harness` type badge
 - the frontmatter `description`
@@ -49,8 +49,8 @@ testing" — check `agent`, type `testing` in the search box.
 
 Dashboard-supported entity pages (`/wiki/<slug>?type=<entity>`) render the full
 markdown body, the frontmatter table on the right, and a quality banner
-with deep links to `/skill/<slug>` (sidecar detail) and
-`/graph?slug=<slug>&type=<entity>` (1-hop neighborhood).
+with deep links to `/skill/<slug>` (sidecar detail) and
+`/graph?slug=<slug>&type=<entity>` (1-hop neighborhood).
 
 ### Explore the knowledge graph — `/graph`
 
@@ -78,9 +78,9 @@ Inside the cytoscape view, node colors mean:
 - **red diamond** — MCP servers
 - **green hexagon** — harnesses
 
-Edge width encodes the blended graph `weight` attribute, combining semantic
-similarity, explicit tag overlap, and slug-token overlap where available.
-Thicker lines = stronger relationships. **Tap any node** to
+Edge width encodes the blended graph `weight` attribute, combining semantic
+similarity, explicit tag overlap, and slug-token overlap where available.
+Thicker lines = stronger relationships. **Tap any node** to
 navigate to that entity's wiki page. The type checkboxes hide or show
 skills, agents, MCP servers, and harnesses without reloading the graph.
 
@@ -108,9 +108,9 @@ render`. It aggregates the quality + lifecycle sidecars under
 7. **Archived** — slugs currently in the archive tier, with their
    last-known grade.
 
-If the quality sidecar directory is empty (no scoring has happened
-yet), the page shows a helpful empty-state pointing at
-`ctx-skill-quality recompute --all`.
+If the quality sidecar directory is empty (no scoring has happened
+yet), the page shows a helpful empty-state pointing at
+`ctx-skill-quality recompute --all`.
 
 ## Routes
 
@@ -125,19 +125,19 @@ Home · Loaded · Skills · Wiki · Graph · KPIs · Sessions · Logs · Live
 
 ### HTML views
 
-Harness catalog entries are visible in loaded, wiki, and graph routes. Harness
-installation, update, uninstall, and quality scoring remain CLI/API workflows.
+Harness catalog entries are visible in loaded, wiki, and graph routes. Harness
+installation, update, uninstall, and quality scoring remain CLI/API workflows.
 
 | Route | What it shows |
 |---|---|
 | `/` | Home: six stat cards (loaded, sidecars, wiki entities, graph nodes, audit events, sessions), grade distribution pills, recent sessions table, recent audit events |
-| `/loaded` | **Currently-loaded skills, agents, MCP servers, and installed harness records** from `~/.claude/skill-manifest.json` plus `~/.claude/harness-installs/*.json`; skill/MCP rows expose supported live actions |
-| `/skills` | Every sidecar as a filterable **card grid**: left sidebar (search by slug, grade checkboxes, skill/agent/MCP toggle, hide-floored), card shows grade pill + raw score + links to sidecar/wiki/graph |
+| `/loaded` | **Currently-loaded skills, agents, MCP servers, and installed harness records** from `~/.claude/skill-manifest.json` plus `~/.claude/harness-installs/*.json`; skill/MCP rows expose supported live actions |
+| `/skills` | Every sidecar as a filterable **card grid**: left sidebar (search by slug, grade checkboxes, skill/agent/MCP toggle, hide-floored), card shows grade pill + raw score + links to sidecar/wiki/graph |
 | `/skill/<slug>` | Full sidecar breakdown: four-signal score (telemetry · intake · graph · routing), hard-floor reason, computed_at timestamp, per-skill audit timeline |
 | `/wiki` | **Wiki entity index** - card grid of every dashboard-supported page under `~/.claude/skill-wiki/entities/{skills,agents,mcp-servers,harnesses}/`, including sharded MCP server pages and flat harness pages. Left sidebar: text search (slug, description, tag), skill/agent/MCP/harness checkboxes. |
 | `/wiki/<slug>?type=<entity>` | Dashboard-supported wiki entity page rendered: markdown body + full frontmatter table + grade banner + deep links to sidecar and graph-neighborhood views. The optional `type` query disambiguates duplicate slugs such as `langgraph`. |
 | `/graph` | **Graph explorer landing page** - node/edge count header, a "Popular seed slugs" block (18 highest-degree skill/agent/MCP/harness entities as clickable chips), search box for any skill/agent/MCP/harness slug, and the cytoscape canvas. Clicking a seed chip navigates to `/graph?slug=<slug>&type=<entity>`. |
-| `/graph?slug=<slug>&type=<entity>` | **Cytoscape-rendered** 1-hop neighborhood around the target skill/agent/MCP/harness slug. Node colors: emerald=focus, indigo=skill, amber=agent, red diamond=MCP server, green hexagon=harness. Edge width maps to blended graph weight. Tap any node to navigate to that entity's typed wiki page. Type and tag filters run client-side. |
+| `/graph?slug=<slug>&type=<entity>` | **Cytoscape-rendered** 1-hop neighborhood around the target skill/agent/MCP/harness slug. Node colors: emerald=focus, indigo=skill, amber=agent, red diamond=MCP server, green hexagon=harness. Edge width maps to blended graph weight. Tap any node to navigate to that entity's typed wiki page. Type and tag filters run client-side. |
 | `/kpi` | **KPI dashboard** — total entity count with subject breakdown, grade distribution pills, two-column tables for grade counts and lifecycle tiers (active · watch · demote · archive), hard-floor reasons with counts, **By category** table (count · avg score · A/B/C/D/F mix per category), **Top demotion candidates** (active/watch entries graded D or F, sorted by consecutive-D streak desc then score asc), and the **Archived** list. Same shape as `python -m kpi_dashboard render` but HTML |
 | `/sessions` | Index of every session (audit + skill-events), first/last seen, counts of skills loaded/unloaded/agents/lifecycle transitions |
 | `/session/<id>` | Per-session audit timeline showing the load → score_updated → unload triad with timestamps |
@@ -200,7 +200,7 @@ Every card shows:
 
 - **grade** — A / B / C / D / F pill (A=green, F=red)
 - **raw score** — float in [0, 1] before the hard-floor override
-- **subject_type** — skill, agent, or mcp-server
+- **subject_type** — skill, agent, or mcp-server
 - **hard floor reason** — `never_loaded_stale`, `intake_fail`, etc.
   when the floor is active
 
@@ -250,7 +250,7 @@ observability proof that ctx's telemetry pipeline is live.
   tool calls are allowed (no Origin header at all).
 - **Slug allowlist on all paths**. Anywhere the dashboard resolves
   a skill, agent, MCP, or harness slug to a file path (`/wiki/<slug>`,
-  `/graph?slug=<slug>&type=<entity>`, `/api/graph/<slug>.json`), the slug is
+  `/graph?slug=<slug>&type=<entity>`, `/api/graph/<slug>.json`), the slug is
   validated through the shared
   safe-name helper — no path traversal, no absolute paths, no UNC
   shares, no Windows reserved device names.

docs/entity-onboarding.md

@@ -14,100 +14,100 @@ After adding any entity, rebuild the graph when you want it to participate in
 recommendations:
 
 ```bash
-ctx-wiki-graphify
-ctx-scan-repo --repo . --recommend
-```
-
-## Updating the Graph and LLM Wiki
-
-Use this sequence for every accepted skill, agent, MCP server, or harness
-change. The graph and LLM-wiki are shippable artifacts, not scratch output, so
-the update is treated like a release step.
-
-1. Add or update the entity through the matching command:
-   `ctx-skill-add`, `ctx-agent-add`, `ctx-mcp-add`, or `ctx-harness-add`.
-2. If the entity already exists, read the update review. It lists changed
-   fields, likely benefits, regressions, and security findings. Do not pass
-   `--update-existing` until those findings are acceptable.
-3. Run the security/cyber check below.
-4. Rebuild the curated wiki graph with `ctx-wiki-graphify`.
-5. Repack `graph/wiki-graph.tar.gz` with the exclusions in
-   `graph/README.md`; never commit local review reports or raw caches.
-6. Refresh the Skills.sh catalog overlay when shipping catalog coverage.
-   This adds remote-cataloged first-class `skill` nodes under the
-   `skills-sh-` prefix, skill pages under `entities/skills/`, install
-   commands, duplicate hints, and metadata-only quality/security signals:
-
-   ```bash
-   python src/import_skills_sh_catalog.py --from-api-union <raw.json> \
-     --catalog-out graph/skills-sh-catalog.json.gz \
-     --wiki-tar graph/wiki-graph.tar.gz \
-     --update-wiki-tar
-   ```
-7. Refresh published counts with `python src/update_repo_stats.py`.
-8. Verify the changed entity can be recommended through
-   `ctx-scan-repo --repo . --recommend` or `ctx__recommend_bundle`.
-
-## Security and Cyber Check
-
-Run this before applying `--update-existing`, before installing a harness with
-approved commands, and before shipping a refreshed graph tarball.
-
-- Inspect changed entity markdown and frontmatter for shell commands, setup
-  commands, install commands, URLs, requested permissions, and model/provider
-  access.
-- Treat these as manual-review blockers: `curl | sh`, `wget | bash`,
-  `Invoke-Expression`, broad `rm -rf`, `git reset --hard`, `chmod 777`, secret
-  upload, disabled auth/TLS/sandboxing/audit/tests, or unpinned package sources.
-- For MCP and harness updates, check network access, filesystem scope, auth
-  material, command transports, and whether setup or verify commands execute
-  remote code.
-- Prefer dry-run first: `ctx-harness-install <slug> --dry-run` and
-  `ctx-harness-install <slug> --update --dry-run`.
-- If a candidate is useful but risky, document the safer install path or keep it
-  as catalog-only metadata instead of shipping it as an installed skill.
-
-## Updating an Existing Entity
-
-The add commands are non-destructive by default when the target skill, agent,
-MCP server, or harness already exists. The first add attempt prints an update
-review instead of replacing files. That review lists changed fields, expected
-benefits, possible regressions, security findings, and a recommendation.
-
-Use this flow for every entity type:
-
-1. Run the normal add command.
-2. If ctx prints `Existing <type> already exists`, read the benefits and risks.
-3. Keep the current entity by doing nothing, or re-run with `--skip-existing`
-   in batch jobs where you do not want reviews.
-4. Apply the replacement only after review with `--update-existing`.
-5. Rebuild the graph with `ctx-wiki-graphify` when the update should affect
-   recommendations.
-
-Examples:
-
-```bash
-ctx-skill-add --skill-path ./SKILL.md --name fastapi-review
-ctx-skill-add --skill-path ./SKILL.md --name fastapi-review --update-existing
-
-ctx-agent-add --agent-path ./code-reviewer.md --name code-reviewer
-ctx-agent-add --agent-path ./code-reviewer.md --name code-reviewer --update-existing
-
-ctx-mcp-add --from-json ./github-mcp.json
-ctx-mcp-add --from-json ./github-mcp.json --update-existing
-
-ctx-harness-add --from-json ./text-to-cad-harness.json
-ctx-harness-add --from-json ./text-to-cad-harness.json --update-existing
-```
-
-`ctx-harness-install --update` is different: it refreshes an installed harness
-checkout under `~/.claude/harnesses/<slug>`. Catalog entity replacement uses
-`ctx-harness-add --update-existing`.
-
-## Add a Skill
-
-Use this when you have a local `SKILL.md` that should be installed under
-`~/.claude/skills/<name>/SKILL.md` and mirrored into the wiki.
+ctx-wiki-graphify
+ctx-scan-repo --repo . --recommend
+```
+
+## Updating the Graph and LLM Wiki
+
+Use this sequence for every accepted skill, agent, MCP server, or harness
+change. The graph and LLM-wiki are shippable artifacts, not scratch output, so
+the update is treated like a release step.
+
+1. Add or update the entity through the matching command:
+   `ctx-skill-add`, `ctx-agent-add`, `ctx-mcp-add`, or `ctx-harness-add`.
+2. If the entity already exists, read the update review. It lists changed
+   fields, likely benefits, regressions, and security findings. Do not pass
+   `--update-existing` until those findings are acceptable.
+3. Run the security/cyber check below.
+4. Rebuild the curated wiki graph with `ctx-wiki-graphify`.
+5. Repack `graph/wiki-graph.tar.gz` with the exclusions in
+   `graph/README.md`; never commit local review reports or raw caches.
+6. Refresh the Skills.sh catalog overlay when shipping catalog coverage.
+   This adds remote-cataloged first-class `skill` nodes under the
+   `skills-sh-` prefix, skill pages under `entities/skills/`, install
+   commands, duplicate hints, and metadata-only quality/security signals:
+
+   ```bash
+   python src/import_skills_sh_catalog.py --from-api-union <raw.json> \
+     --catalog-out graph/skills-sh-catalog.json.gz \
+     --wiki-tar graph/wiki-graph.tar.gz \
+     --update-wiki-tar
+   ```
+7. Refresh published counts with `python src/update_repo_stats.py`.
+8. Verify the changed entity can be recommended through
+   `ctx-scan-repo --repo . --recommend` or `ctx__recommend_bundle`.
+
+## Security and Cyber Check
+
+Run this before applying `--update-existing`, before installing a harness with
+approved commands, and before shipping a refreshed graph tarball.
+
+- Inspect changed entity markdown and frontmatter for shell commands, setup
+  commands, install commands, URLs, requested permissions, and model/provider
+  access.
+- Treat these as manual-review blockers: `curl | sh`, `wget | bash`,
+  `Invoke-Expression`, broad `rm -rf`, `git reset --hard`, `chmod 777`, secret
+  upload, disabled auth/TLS/sandboxing/audit/tests, or unpinned package sources.
+- For MCP and harness updates, check network access, filesystem scope, auth
+  material, command transports, and whether setup or verify commands execute
+  remote code.
+- Prefer dry-run first: `ctx-harness-install <slug> --dry-run` and
+  `ctx-harness-install <slug> --update --dry-run`.
+- If a candidate is useful but risky, document the safer install path or keep it
+  as catalog-only metadata instead of shipping it as an installed skill.
+
+## Updating an Existing Entity
+
+The add commands are non-destructive by default when the target skill, agent,
+MCP server, or harness already exists. The first add attempt prints an update
+review instead of replacing files. That review lists changed fields, expected
+benefits, possible regressions, security findings, and a recommendation.
+
+Use this flow for every entity type:
+
+1. Run the normal add command.
+2. If ctx prints `Existing <type> already exists`, read the benefits and risks.
+3. Keep the current entity by doing nothing, or re-run with `--skip-existing`
+   in batch jobs where you do not want reviews.
+4. Apply the replacement only after review with `--update-existing`.
+5. Rebuild the graph with `ctx-wiki-graphify` when the update should affect
+   recommendations.
+
+Examples:
+
+```bash
+ctx-skill-add --skill-path ./SKILL.md --name fastapi-review
+ctx-skill-add --skill-path ./SKILL.md --name fastapi-review --update-existing
+
+ctx-agent-add --agent-path ./code-reviewer.md --name code-reviewer
+ctx-agent-add --agent-path ./code-reviewer.md --name code-reviewer --update-existing
+
+ctx-mcp-add --from-json ./github-mcp.json
+ctx-mcp-add --from-json ./github-mcp.json --update-existing
+
+ctx-harness-add --from-json ./text-to-cad-harness.json
+ctx-harness-add --from-json ./text-to-cad-harness.json --update-existing
+```
+
+`ctx-harness-install --update` is different: it refreshes an installed harness
+checkout under `~/.claude/harnesses/<slug>`. Catalog entity replacement uses
+`ctx-harness-add --update-existing`.
+
+## Add a Skill
+
+Use this when you have a local `SKILL.md` that should be installed under
+`~/.claude/skills/<name>/SKILL.md` and mirrored into the wiki.
 
 ```bash
 ctx-skill-add \
@@ -125,19 +125,19 @@ What happens:
 
 ## Add an Agent
 
-Use this when you have a local Claude Code agent markdown file.
-
-```bash
-ctx-agent-add \
-  --agent-path ./code-reviewer.md \
-  --name code-reviewer
-```
-
-Batch-add every top-level `.md` file in a directory:
-
-```bash
-ctx-agent-add --scan-dir ./agents --skip-existing
-```
+Use this when you have a local Claude Code agent markdown file.
+
+```bash
+ctx-agent-add \
+  --agent-path ./code-reviewer.md \
+  --name code-reviewer
+```
+
+Batch-add every top-level `.md` file in a directory:
+
+```bash
+ctx-agent-add --scan-dir ./agents --skip-existing
+```
 
 Agents are copied into `~/.claude/agents/` and mirrored into
 `entities/agents/`. Re-run `ctx-wiki-graphify` after adding agents if you want
@@ -168,10 +168,10 @@ Add it:
 ctx-mcp-add --from-json ./github-mcp.json
 ```
 
-MCP pages live under `entities/mcp-servers/<shard>/<slug>.md`. The add command
-detects existing pages by slug and, when possible, canonical GitHub URL. If a
-match exists, ctx prints the update review and skips replacement unless
-`--update-existing` is passed.
+MCP pages live under `entities/mcp-servers/<shard>/<slug>.md`. The add command
+detects existing pages by slug and, when possible, canonical GitHub URL. If a
+match exists, ctx prints the update review and skips replacement unless
+`--update-existing` is passed.
 
 ## Add a Harness
 
@@ -215,49 +215,49 @@ Or load one JSON record:
 ctx-harness-add --from-json ./text-to-cad-harness.json
 ```
 
-Harness pages live under `entities/harnesses/<slug>.md`. Setup and verification
-commands are documentation only; ctx records them so the user can inspect and
-decide before running anything.
-
-To inspect and install a cataloged harness:
-
-```bash
-ctx-harness-install text-to-cad --dry-run
-ctx-harness-install text-to-cad
-ctx-harness-install text-to-cad --update --dry-run
-ctx-harness-install text-to-cad --uninstall --dry-run
-```
-
-The installer clones or copies the harness into `~/.claude/harnesses/<slug>` and
-writes `~/.claude/harness-installs/<slug>.json`. It does not run setup commands
-unless you pass `--approve-commands`, and it does not run verification commands
-unless you also pass `--run-verify`.
-
-```bash
-ctx-harness-install text-to-cad --approve-commands --run-verify
-ctx-harness-install text-to-cad --update --approve-commands --run-verify
-ctx-harness-install text-to-cad --uninstall
-ctx-harness-install text-to-cad --uninstall --keep-files
-```
-
-## Initialize Model Choice
-
-During setup, record whether you use Claude Code or your own model. Plain
-`ctx-init` starts a small wizard when it is attached to an interactive
-terminal; use `ctx-init --wizard` to force the prompts, or pass explicit flags
-such as `--model-mode skip` for non-interactive automation.
-
-```bash
-ctx-init
-ctx-init --wizard
-ctx-init --model-mode skip
-```
-
-For Claude Code:
-
-```bash
-ctx-init --model-mode claude-code --goal "maintain a FastAPI service"
-```
+Harness pages live under `entities/harnesses/<slug>.md`. Setup and verification
+commands are documentation only; ctx records them so the user can inspect and
+decide before running anything.
+
+To inspect and install a cataloged harness:
+
+```bash
+ctx-harness-install text-to-cad --dry-run
+ctx-harness-install text-to-cad
+ctx-harness-install text-to-cad --update --dry-run
+ctx-harness-install text-to-cad --uninstall --dry-run
+```
+
+The installer clones or copies the harness into `~/.claude/harnesses/<slug>` and
+writes `~/.claude/harness-installs/<slug>.json`. It does not run setup commands
+unless you pass `--approve-commands`, and it does not run verification commands
+unless you also pass `--run-verify`.
+
+```bash
+ctx-harness-install text-to-cad --approve-commands --run-verify
+ctx-harness-install text-to-cad --update --approve-commands --run-verify
+ctx-harness-install text-to-cad --uninstall
+ctx-harness-install text-to-cad --uninstall --keep-files
+```
+
+## Initialize Model Choice
+
+During setup, record whether you use Claude Code or your own model. Plain
+`ctx-init` starts a small wizard when it is attached to an interactive
+terminal; use `ctx-init --wizard` to force the prompts, or pass explicit flags
+such as `--model-mode skip` for non-interactive automation.
+
+```bash
+ctx-init
+ctx-init --wizard
+ctx-init --model-mode skip
+```
+
+For Claude Code:
+
+```bash
+ctx-init --model-mode claude-code --goal "maintain a FastAPI service"
+```
 
 For a custom model:
 

docs/harness/attaching-to-hosts.md

@@ -245,11 +245,11 @@ and de-ranked from future recommendations. This logic lives in
 `ctx.core.quality.quality_signals` and runs identically whether
 you're on the MCP path, library path, or `ctx run` CLI.
 
-To inspect lifecycle state for a specific skill:
-
-```bash
-ctx-skill-quality explain fastapi-pro
-```
+To inspect lifecycle state for a specific skill:
+
+```bash
+ctx-skill-quality explain fastapi-pro
+```
 
 Or from Python:
 

docs/harness/clean-host-contract.md

@@ -38,8 +38,8 @@ contract stabilizes.
 - It does not browser-test the monitor dashboard.
 - It does not simulate process kills or power loss during writes.
 
-Those checks stay intentionally manual or opt-in until they are stable enough
-for the default CI path.
+Those checks stay intentionally manual or opt-in until they are stable enough
+for the default CI path.
 
 ## Local Usage
 

docs/huggingface-publish.md

@@ -1,143 +1,143 @@
-# Hugging Face Publish
-
-ctx publishes the GitHub repository as the public Hugging Face dataset
-[`Stevesolun/ctx`](https://huggingface.co/datasets/Stevesolun/ctx). The
-dataset is a clean `git ls-files` snapshot, including the shipped graph
-tarball and catalog artifacts, not local review reports or ignored caches.
-
-## What gets uploaded
-
-- Tracked source, docs, tests, and packaging files.
-- `graph/wiki-graph.tar.gz`.
-- `graph/skills-sh-catalog.json.gz`.
-- Tracked graph visualizations under `graph/`.
-
-Ignored local reports, review notes, raw ingest caches, coverage files,
-`site/`, and `.pytest_cache/` are not uploaded because they are not tracked
-by git.
-
-## Publish command
-
-Set the token in the process environment. Do not pass it on a command line
-that will be saved in shell history.
-
-```powershell
-$env:HF_TOKEN = "<hugging-face-write-token>"
-python -m pip install --upgrade huggingface_hub
-git lfs install
-git lfs pull --include="graph/wiki-graph.tar.gz"
-@'
-from __future__ import annotations
-
-import os
-import shutil
-import subprocess
-import tempfile
-from pathlib import Path
-
-from huggingface_hub import HfApi
-
-root = Path.cwd()
-token = os.environ["HF_TOKEN"]
-api = HfApi(token=token)
-owner = api.whoami()["name"]
-repo_id = f"{owner}/ctx"
-repo_type = "dataset"
-sha = subprocess.check_output(["git", "rev-parse", "--short", "HEAD"], text=True).strip()
-files = [
-    Path(raw.decode("utf-8"))
-    for raw in subprocess.check_output(["git", "ls-files", "-z"], cwd=root).split(b"\0")
-    if raw
-]
-graph_tar = root / "graph" / "wiki-graph.tar.gz"
-if not graph_tar.is_file() or graph_tar.stat().st_size < 100_000_000:
-    raise SystemExit(
-        "graph/wiki-graph.tar.gz is not hydrated; run git lfs pull before publishing"
-    )
-
-api.create_repo(repo_id=repo_id, repo_type=repo_type, private=False, exist_ok=True, token=token)
-staging = Path(tempfile.mkdtemp(prefix="ctx-hf-upload-"))
-try:
-    for rel in files:
-        src = root / rel
-        if not src.is_file():
-            continue
-        dst = staging / rel
-        dst.parent.mkdir(parents=True, exist_ok=True)
-        shutil.copy2(src, dst)
-    api.upload_folder(
-        repo_id=repo_id,
-        repo_type=repo_type,
-        folder_path=staging,
-        commit_message=f"Publish ctx snapshot {sha}",
-        token=token,
-    )
-finally:
-    shutil.rmtree(staging, ignore_errors=True)
-'@ | python -
-```
-
-Then upload the dataset-card metadata wrapper for `README.md`:
-
-```powershell
-$env:HF_TOKEN = "<hugging-face-write-token>"
-@'
-from __future__ import annotations
-
-import os
-import tempfile
-from pathlib import Path
-
-from huggingface_hub import HfApi
-
-token = os.environ["HF_TOKEN"]
-api = HfApi(token=token)
-repo_id = f"{api.whoami()['name']}/ctx"
-frontmatter = """---
-license: mit
-tags:
-- agents
-- mcp
-- skills
-- knowledge-graph
-- llm-wiki
-- recommendation-system
-- harness
-- codex
-- claude-code
-pretty_name: ctx
----
-
-"""
-with tempfile.NamedTemporaryFile("w", encoding="utf-8", suffix=".md", delete=False) as fh:
-    path = Path(fh.name)
-    fh.write(frontmatter)
-    fh.write(Path("README.md").read_text(encoding="utf-8"))
-try:
-    api.upload_file(
-        repo_id=repo_id,
-        repo_type="dataset",
-        path_or_fileobj=path,
-        path_in_repo="README.md",
-        commit_message="Add Hugging Face dataset card metadata",
-        token=token,
-    )
-finally:
-    path.unlink(missing_ok=True)
-'@ | python -
-```
-
-## Verify
-
-```powershell
-@'
-from huggingface_hub import HfApi
-
-api = HfApi()
-info = api.repo_info(repo_id="Stevesolun/ctx", repo_type="dataset")
-print(info.id, info.sha)
-'@ | python -
-```
-
-The dataset page should show the MIT license and the tags from the metadata
-wrapper.
+# Hugging Face Publish
+
+ctx publishes the GitHub repository as the public Hugging Face dataset
+[`Stevesolun/ctx`](https://huggingface.co/datasets/Stevesolun/ctx). The
+dataset is a clean `git ls-files` snapshot, including the shipped graph
+tarball and catalog artifacts, not local review reports or ignored caches.
+
+## What gets uploaded
+
+- Tracked source, docs, tests, and packaging files.
+- `graph/wiki-graph.tar.gz`.
+- `graph/skills-sh-catalog.json.gz`.
+- Tracked graph visualizations under `graph/`.
+
+Ignored local reports, review notes, raw ingest caches, coverage files,
+`site/`, and `.pytest_cache/` are not uploaded because they are not tracked
+by git.
+
+## Publish command
+
+Set the token in the process environment. Do not pass it on a command line
+that will be saved in shell history.
+
+```powershell
+$env:HF_TOKEN = "<hugging-face-write-token>"
+python -m pip install --upgrade huggingface_hub
+git lfs install
+git lfs pull --include="graph/wiki-graph.tar.gz"
+@'
+from __future__ import annotations
+
+import os
+import shutil
+import subprocess
+import tempfile
+from pathlib import Path
+
+from huggingface_hub import HfApi
+
+root = Path.cwd()
+token = os.environ["HF_TOKEN"]
+api = HfApi(token=token)
+owner = api.whoami()["name"]
+repo_id = f"{owner}/ctx"
+repo_type = "dataset"
+sha = subprocess.check_output(["git", "rev-parse", "--short", "HEAD"], text=True).strip()
+files = [
+    Path(raw.decode("utf-8"))
+    for raw in subprocess.check_output(["git", "ls-files", "-z"], cwd=root).split(b"\0")
+    if raw
+]
+graph_tar = root / "graph" / "wiki-graph.tar.gz"
+if not graph_tar.is_file() or graph_tar.stat().st_size < 100_000_000:
+    raise SystemExit(
+        "graph/wiki-graph.tar.gz is not hydrated; run git lfs pull before publishing"
+    )
+
+api.create_repo(repo_id=repo_id, repo_type=repo_type, private=False, exist_ok=True, token=token)
+staging = Path(tempfile.mkdtemp(prefix="ctx-hf-upload-"))
+try:
+    for rel in files:
+        src = root / rel
+        if not src.is_file():
+            continue
+        dst = staging / rel
+        dst.parent.mkdir(parents=True, exist_ok=True)
+        shutil.copy2(src, dst)
+    api.upload_folder(
+        repo_id=repo_id,
+        repo_type=repo_type,
+        folder_path=staging,
+        commit_message=f"Publish ctx snapshot {sha}",
+        token=token,
+    )
+finally:
+    shutil.rmtree(staging, ignore_errors=True)
+'@ | python -
+```
+
+Then upload the dataset-card metadata wrapper for `README.md`:
+
+```powershell
+$env:HF_TOKEN = "<hugging-face-write-token>"
+@'
+from __future__ import annotations
+
+import os
+import tempfile
+from pathlib import Path
+
+from huggingface_hub import HfApi
+
+token = os.environ["HF_TOKEN"]
+api = HfApi(token=token)
+repo_id = f"{api.whoami()['name']}/ctx"
+frontmatter = """---
+license: mit
+tags:
+- agents
+- mcp
+- skills
+- knowledge-graph
+- llm-wiki
+- recommendation-system
+- harness
+- codex
+- claude-code
+pretty_name: ctx
+---
+
+"""
+with tempfile.NamedTemporaryFile("w", encoding="utf-8", suffix=".md", delete=False) as fh:
+    path = Path(fh.name)
+    fh.write(frontmatter)
+    fh.write(Path("README.md").read_text(encoding="utf-8"))
+try:
+    api.upload_file(
+        repo_id=repo_id,
+        repo_type="dataset",
+        path_or_fileobj=path,
+        path_in_repo="README.md",
+        commit_message="Add Hugging Face dataset card metadata",
+        token=token,
+    )
+finally:
+    path.unlink(missing_ok=True)
+'@ | python -
+```
+
+## Verify
+
+```powershell
+@'
+from huggingface_hub import HfApi
+
+api = HfApi()
+info = api.repo_info(repo_id="Stevesolun/ctx", repo_type="dataset")
+print(info.id, info.sha)
+'@ | python -
+```
+
+The dataset page should show the MIT license and the tags from the metadata
+wrapper.

docs/knowledge-graph.md

@@ -2,49 +2,49 @@
 
 A pre-built weighted graph of skills, agents, MCP servers, and cataloged
 harnesses in the ctx ecosystem, shipped as `graph/wiki-graph.tar.gz`.
-The on-disk JSON and `resolve_graph` Python API are harness-aware, including
-plain-slug graph walks from `harness:<slug>` nodes. `ctx-monitor`
-exposes skill/agent/MCP/harness wiki and graph views; harness install,
-update, load/unload, and quality scoring remain CLI/API workflows.
+The on-disk JSON and `resolve_graph` Python API are harness-aware, including
+plain-slug graph walks from `harness:<slug>` nodes. `ctx-monitor`
+exposes skill/agent/MCP/harness wiki and graph views; harness install,
+update, load/unload, and quality scoring remain CLI/API workflows.
 
 ## What's in it
 
-Authoritative numbers from the shipped tarball. The curated-core snapshot
-is **13,233 nodes** (1,969 curated skills + 464 agents + 10,787 MCP servers
-+ 13 harnesses). Harness pages under `entities/harnesses/` are ingested into
-local rebuilds and the separate harness-catalog recommendation path. The
-tarball also carries **90,846 remote-cataloged Skills.sh `skill` nodes**,
-matching skill pages under `entities/skills/skills-sh-*.md`. **89,461**
-hydrated Skills.sh bodies are shipped as installable `SKILL.md` files under
-`converted/skills-sh-*/`; the **28,611** entries over the configured line
-limit were converted to gated micro-skill orchestrators. Full original bodies
-are used during graph rebuilds for semantic similarity, but
-`SKILL.md.original` backups are omitted from the shipped tarball.
+Authoritative numbers from the shipped tarball. The curated-core snapshot
+is **13,233 nodes** (1,969 curated skills + 464 agents + 10,787 MCP servers
++ 13 harnesses). Harness pages under `entities/harnesses/` are ingested into
+local rebuilds and the separate harness-catalog recommendation path. The
+tarball also carries **90,846 remote-cataloged Skills.sh `skill` nodes**,
+matching skill pages under `entities/skills/skills-sh-*.md`. **89,461**
+hydrated Skills.sh bodies are shipped as installable `SKILL.md` files under
+`converted/skills-sh-*/`; the **28,611** entries over the configured line
+limit were converted to gated micro-skill orchestrators. Full original bodies
+are used during graph rebuilds for semantic similarity, but
+`SKILL.md.original` backups are omitted from the shipped tarball.
 
 | | Count |
 |---|---:|
-| Total nodes | **104,079** |
-| Curated core nodes | **13,233** (1,969 skills + 464 agents + 10,787 MCP servers + 13 harnesses) |
-| Remote-cataloged Skills.sh skill nodes | **90,846** (`skill`, `status=remote-cataloged`) |
-| Total edges | **2,960,215** |
-| Skills.sh incident edges | **2,665,345** |
-| Skills.sh semantic incident edges | **1,525,295** |
-| Communities | **53** (Louvain) |
-| Edge sources (overlap-deduped) | semantic 1,707,435 - tag 920,686 - token 442,556 |
-| Cross-type edges (skill <-> agent) | ~222K |
-| Cross-type edges (skill <-> MCP) | ~62K |
-| Cross-type edges (agent <-> MCP) | ~13K |
-| Harness edges | **2,700** (2,411 curated-core edges + 289 Skills.sh metadata edges across 13 cataloged harnesses) |
-| Skills.sh catalog | **90,846** observed entries (`external-catalogs/skills-sh/catalog.json` + `entities/skills/skills-sh-*.md`) |
+| Total nodes | **104,079** |
+| Curated core nodes | **13,233** (1,969 skills + 464 agents + 10,787 MCP servers + 13 harnesses) |
+| Remote-cataloged Skills.sh skill nodes | **90,846** (`skill`, `status=remote-cataloged`) |
+| Total edges | **2,960,215** |
+| Skills.sh incident edges | **2,665,345** |
+| Skills.sh semantic incident edges | **1,525,295** |
+| Communities | **53** (Louvain) |
+| Edge sources (overlap-deduped) | semantic 1,707,435 - tag 920,686 - token 442,556 |
+| Cross-type edges (skill <-> agent) | ~222K |
+| Cross-type edges (skill <-> MCP) | ~62K |
+| Cross-type edges (agent <-> MCP) | ~13K |
+| Harness edges | **2,700** (2,411 curated-core edges + 289 Skills.sh metadata edges across 13 cataloged harnesses) |
+| Skills.sh catalog | **90,846** observed entries (`external-catalogs/skills-sh/catalog.json` + `entities/skills/skills-sh-*.md`) |
 
 ## Install
 
-Extract the tarball into your `~/.claude/skill-wiki/` to get a
-ready-to-query graph plus every shipped skill/agent/MCP entity page,
-cataloged harness pages when present, remote-cataloged Skills.sh skill
-pages, concept pages, and converted micro-skill pipelines. The extracted
-tree also includes the Skills.sh catalog JSON used by the shared
-recommender:
+Extract the tarball into your `~/.claude/skill-wiki/` to get a
+ready-to-query graph plus every shipped skill/agent/MCP entity page,
+cataloged harness pages when present, remote-cataloged Skills.sh skill
+pages, concept pages, and converted micro-skill pipelines. The extracted
+tree also includes the Skills.sh catalog JSON used by the shared
+recommender:
 
 ```bash
 mkdir -p ~/.claude/skill-wiki
@@ -57,37 +57,37 @@ Obsidian's native graph view if you prefer it to the web dashboard.
 
 ## How edges are built
 
-Three sources of connectivity, combined at build time by the
-`ctx-wiki-graphify` console script (`ctx.core.wiki.wiki_graphify`):
-
-1. **Semantic cosine** — when the embedding backend is available, entity
-   text is embedded and semantic neighbors above the configured build floor
-   contribute weighted edges.
-2. **Explicit frontmatter tags** — each entity page's YAML `tags:`
-   list contributes edges between every pair of entities that share
-   a tag. Popular tags capped at 500 nodes to avoid noise-floor
-   "everything connects to everything" mega-buckets like `typescript`
-   or `frontend`.
-3. **Slug-token pseudo-tags** — each hyphenated slug contributes its
-   tokens as implicit tags. `fastapi-pro` contributes `fastapi`;
-   `python-patterns` contributes `python` and `patterns`. A stop-word
-   filter drops generic tokens like `skill`, `agent`, `pro`, `expert`,
-   `core` so they don't over-connect the graph.
-
-Edge `weight` is the final blended strength after semantic, tag, and token
-signals are combined. Edge metadata keeps the ingredients explainable:
-`semantic_sim` for cosine similarity, `shared_tags` for explicit tags, and
-`shared_tokens` for slug-token overlap. Hydrated Skills.sh records use their
-full source bodies during graph rebuilds, so long converted entries keep
-full-body similarity even though the shipped installable `SKILL.md` files are
-short gated loaders. The raw `SKILL.md.original` backups are build inputs, not
-tarball members.
+Three sources of connectivity, combined at build time by the
+`ctx-wiki-graphify` console script (`ctx.core.wiki.wiki_graphify`):
+
+1. **Semantic cosine** — when the embedding backend is available, entity
+   text is embedded and semantic neighbors above the configured build floor
+   contribute weighted edges.
+2. **Explicit frontmatter tags** — each entity page's YAML `tags:`
+   list contributes edges between every pair of entities that share
+   a tag. Popular tags capped at 500 nodes to avoid noise-floor
+   "everything connects to everything" mega-buckets like `typescript`
+   or `frontend`.
+3. **Slug-token pseudo-tags** — each hyphenated slug contributes its
+   tokens as implicit tags. `fastapi-pro` contributes `fastapi`;
+   `python-patterns` contributes `python` and `patterns`. A stop-word
+   filter drops generic tokens like `skill`, `agent`, `pro`, `expert`,
+   `core` so they don't over-connect the graph.
+
+Edge `weight` is the final blended strength after semantic, tag, and token
+signals are combined. Edge metadata keeps the ingredients explainable:
+`semantic_sim` for cosine similarity, `shared_tags` for explicit tags, and
+`shared_tokens` for slug-token overlap. Hydrated Skills.sh records use their
+full source bodies during graph rebuilds, so long converted entries keep
+full-body similarity even though the shipped installable `SKILL.md` files are
+short gated loaders. The raw `SKILL.md.original` backups are build inputs, not
+tarball members.
 
 ## Communities
 
 After edges are built, `wiki_graphify` runs NetworkX's Louvain
 community detection (`resolution=1.2`, `seed=42` for determinism).
-The result is **53 communities** ranging from single-member isolated
+The result is **53 communities** ranging from single-member isolated
 specialists to several thousand members in broad clusters like
 `Community + Official + AI`. Each community also gets an auto-generated
 `concepts/<community>.md` wiki page summarizing its members and top
@@ -108,12 +108,12 @@ quality clusters for the recommendation use case.
 ctx-monitor serve              # http://127.0.0.1:8765
 ```
 
-Then open `/graph?slug=<entity-slug>&type=<entity-type>` for a
-cytoscape neighborhood view, or
-`/api/graph/<slug>.json?type=<entity-type>&hops=1&limit=40` for the
-dashboard-shaped JSON. The `type` query is optional for unique slugs and
-recommended for duplicate slugs such as `langgraph`. See the
-[dashboard reference](dashboard.md) for the full route catalogue.
+Then open `/graph?slug=<entity-slug>&type=<entity-type>` for a
+cytoscape neighborhood view, or
+`/api/graph/<slug>.json?type=<entity-type>&hops=1&limit=40` for the
+dashboard-shaped JSON. The `type` query is optional for unique slugs and
+recommended for duplicate slugs such as `langgraph`. See the
+[dashboard reference](dashboard.md) for the full route catalogue.
 
 ### Via Python
 
@@ -128,7 +128,7 @@ raw = json.loads(
 edges_key = "links" if "links" in raw else "edges"
 G = node_link_graph(raw, edges=edges_key)
 
-# 104,079 nodes, 2,960,215 edges
+# 104,079 nodes, 2,960,215 edges
 print(G.number_of_nodes(), G.number_of_edges())
 
 # Find entities related to 'fastapi-pro' by edge weight
@@ -151,40 +151,40 @@ The helper `resolve_graph.load_graph()` does this for you.
 
 The graph backs two recommendation paths:
 
-- Execution recommendation surfaces (`ctx.recommend_bundle`, MCP
-  `ctx__recommend_bundle`, generic harness tools, Claude Code hook
-  suggestions, and repo-scan advisory output) share
-  `ctx.core.resolve.recommendations.recommend_by_tags` for skills,
-  agents, and MCP servers. That engine ranks candidates by
-  slug-token matches, tag overlap, graph degree, and semantic-cache
-  signals when available. Skills.sh results are `skill` nodes with
-  `source_catalog=skills.sh`, `detail_url`, `install_command`, duplicate
-  hints, gated micro-skill loaders when over the line threshold, and
-  quality/security metadata. If an older
-  extracted wiki has the Skills.sh catalog JSON but no graph nodes for
-  those records, the same recommender falls back to the catalog file.
-- Harness recommendations are a separate catalog path for custom/API/local
-  model onboarding (`ctx-init --model-mode custom ...`) and
-  `ctx-harness-install`. They use the same graph catalog filtered to
-  `harness` nodes and the higher harness match floor from `config.json`.
-- Repository scans still start from stack detections, then turn that profile
-  into the same tag/query bundle used by the execution recommender. If a
-  shipped graph is unavailable, scan output falls back to the legacy installed
-  skill resolver so a plain profile scan remains useful. Harnesses are
-  intentionally not emitted from repo scans or Claude Code hook bundles.
-
-This split is intentional: execution surfaces need identical ranking and a
-small top-K, while harness choice changes the model runtime itself and belongs
-in an explicit onboarding/install flow.
-
-### LLM-wiki design references
-
-ctx follows Karpathy's LLM-wiki pattern. We also reviewed
-[`nashsu/llm_wiki`](https://github.com/nashsu/llm_wiki) as a design reference
-for source traceability, persistent ingest queues, graph insights, and
-budgeted token/vector/graph retrieval. That repository is GPLv3, while ctx is
-MIT, so ctx can use those ideas as product inspiration but must not copy or
-vendor its code or assets.
+- Execution recommendation surfaces (`ctx.recommend_bundle`, MCP
+  `ctx__recommend_bundle`, generic harness tools, Claude Code hook
+  suggestions, and repo-scan advisory output) share
+  `ctx.core.resolve.recommendations.recommend_by_tags` for skills,
+  agents, and MCP servers. That engine ranks candidates by
+  slug-token matches, tag overlap, graph degree, and semantic-cache
+  signals when available. Skills.sh results are `skill` nodes with
+  `source_catalog=skills.sh`, `detail_url`, `install_command`, duplicate
+  hints, gated micro-skill loaders when over the line threshold, and
+  quality/security metadata. If an older
+  extracted wiki has the Skills.sh catalog JSON but no graph nodes for
+  those records, the same recommender falls back to the catalog file.
+- Harness recommendations are a separate catalog path for custom/API/local
+  model onboarding (`ctx-init --model-mode custom ...`) and
+  `ctx-harness-install`. They use the same graph catalog filtered to
+  `harness` nodes and the higher harness match floor from `config.json`.
+- Repository scans still start from stack detections, then turn that profile
+  into the same tag/query bundle used by the execution recommender. If a
+  shipped graph is unavailable, scan output falls back to the legacy installed
+  skill resolver so a plain profile scan remains useful. Harnesses are
+  intentionally not emitted from repo scans or Claude Code hook bundles.
+
+This split is intentional: execution surfaces need identical ranking and a
+small top-K, while harness choice changes the model runtime itself and belongs
+in an explicit onboarding/install flow.
+
+### LLM-wiki design references
+
+ctx follows Karpathy's LLM-wiki pattern. We also reviewed
+[`nashsu/llm_wiki`](https://github.com/nashsu/llm_wiki) as a design reference
+for source traceability, persistent ingest queues, graph insights, and
+budgeted token/vector/graph retrieval. That repository is GPLv3, while ctx is
+MIT, so ctx can use those ideas as product inspiration but must not copy or
+vendor its code or assets.
 
 ## Rebuilding
 
@@ -206,17 +206,17 @@ if your hook config does not include those paths.
 |---|---|---|
 | v0.5.x | 642K (stale) / 861 (live) | Bundle had stale 642K; live rebuild silently produced 861 because `DENSE_TAG_THRESHOLD=20` dropped every popular tag. |
 | v0.6.0 | 454,719 | Threshold raised to 500, multi-line YAML lists parsed, slug-token pseudo-tags added. |
-| v0.7.x | 847,207 | Pulsemcp ingest added 10,786 MCP server nodes; sentence-embedding semantic edges added. |
-| 2026-04-27 graph rebuild pass | **963,068** | +21 mattpocock skills, +156 designdotmd designs (+106,702 edges); patch-path bug fixed (graphify now forces full rebuild when prior graph has 0 semantic edges but current run computed semantic pairs); community detection switched from CNM to Louvain. |
-| 2026-04-29 Skills.sh remote-cataloged pass | **1,030,831** | +90,846 first-class `skill` nodes, +90,846 skill pages, and +67,519 sparse duplicate/tag metadata edges to the curated graph. Full-body semantic edges are intentionally deferred to the hydration pass. |
-| 2026-04-29 text-to-cad harness pass | **1,031,011** | +1 first-class `harness` node, +1 harness page, and +224 explainable harness edges, including 44 remote-cataloged Skills.sh edges. |
-| 2026-04-29 curated harness catalog pass | **1,033,253** | +12 first-class `harness` nodes/pages for LangGraph, CrewAI, AutoGen, Google ADK, Semantic Kernel, Mastra, Pydantic AI, Haystack, OpenAI Agents SDK, LiteLLM, Langfuse, and AgentOps; harness incident edges now total 2,700. |
-| 2026-04-30 Skills.sh semantic hydration pass | **2,881,027** | +full-body semantic edges for hydrated Skills.sh records; semantic top-K became the dominant large-scale signal. |
-| 2026-05-01 Skills.sh micro-skill pass | **2,960,189** | Enforced the <=180-line loader threshold across 89,461 hydrated Skills.sh `SKILL.md` files, converted 28,611 long bodies into gated micro-skill orchestrators, used full originals for semantic graphing, excluded `.original` backups from the shipped tarball, bounded generated stage/reference files to 40 lines, and rebuilt the graph. |
-| 2026-05-02 GitNexus MCP pass | **2,960,215** | Added GitNexus as a cataloged MCP server entity with 26 cross-type edges to its Skills.sh skill pages and related architecture/refactoring agents; semantic edge count unchanged. |
-
-The full audit history lives in `CHANGELOG.md`. The current build is
-fully reproducible from the wiki content.
+| v0.7.x | 847,207 | Pulsemcp ingest added 10,786 MCP server nodes; sentence-embedding semantic edges added. |
+| 2026-04-27 graph rebuild pass | **963,068** | +21 mattpocock skills, +156 designdotmd designs (+106,702 edges); patch-path bug fixed (graphify now forces full rebuild when prior graph has 0 semantic edges but current run computed semantic pairs); community detection switched from CNM to Louvain. |
+| 2026-04-29 Skills.sh remote-cataloged pass | **1,030,831** | +90,846 first-class `skill` nodes, +90,846 skill pages, and +67,519 sparse duplicate/tag metadata edges to the curated graph. Full-body semantic edges are intentionally deferred to the hydration pass. |
+| 2026-04-29 text-to-cad harness pass | **1,031,011** | +1 first-class `harness` node, +1 harness page, and +224 explainable harness edges, including 44 remote-cataloged Skills.sh edges. |
+| 2026-04-29 curated harness catalog pass | **1,033,253** | +12 first-class `harness` nodes/pages for LangGraph, CrewAI, AutoGen, Google ADK, Semantic Kernel, Mastra, Pydantic AI, Haystack, OpenAI Agents SDK, LiteLLM, Langfuse, and AgentOps; harness incident edges now total 2,700. |
+| 2026-04-30 Skills.sh semantic hydration pass | **2,881,027** | +full-body semantic edges for hydrated Skills.sh records; semantic top-K became the dominant large-scale signal. |
+| 2026-05-01 Skills.sh micro-skill pass | **2,960,189** | Enforced the <=180-line loader threshold across 89,461 hydrated Skills.sh `SKILL.md` files, converted 28,611 long bodies into gated micro-skill orchestrators, used full originals for semantic graphing, excluded `.original` backups from the shipped tarball, bounded generated stage/reference files to 40 lines, and rebuilt the graph. |
+| 2026-05-02 GitNexus MCP pass | **2,960,215** | Added GitNexus as a cataloged MCP server entity with 26 cross-type edges to its Skills.sh skill pages and related architecture/refactoring agents; semantic edge count unchanged. |
+
+The full audit history lives in `CHANGELOG.md`. The current build is
+fully reproducible from the wiki content.
 
 ## Pre-ship gates
 

docs/marketplace-registry.md

@@ -1,157 +1,157 @@
-# Marketplace Registry
-
-> Known skill/plugin marketplaces and how to interact with them.
-> The router queries these when it detects a stack gap (needed skill not installed).
-
-## Registered Marketplaces
-
-### 1. Local Skills Directory
-
-```yaml
-name: local
-type: filesystem
-path: /mnt/skills/
-scan_method: directory listing
-refresh: always current
-priority: 1  # check first
-```
-
-List all installed skills:
-```bash
-find /mnt/skills/ -name "SKILL.md" -maxdepth 3
-```
-
-### 2. User Skills Directory
-
-```yaml
-name: user-local
-type: filesystem
-path: /mnt/skills/user/
-scan_method: directory listing
-refresh: always current
-priority: 2
-```
-
-User-uploaded or custom skills. Same scan as local but separate namespace.
-
-### 3. Example Skills
-
-```yaml
-name: examples
-type: filesystem
-path: /mnt/skills/examples/
-scan_method: directory listing
-refresh: always current
-priority: 3
-```
-
-Bundled example skills that may not be active but can be copied to user skills.
-
-### 4. GitHub Skill Repos
-
-```yaml
-name: github
-type: git
-base_url: https://github.com
-search_method: topic search "claude-skill" OR "hermes-skill"
-install_method: git clone + copy SKILL.md to /mnt/skills/user/
-refresh: on-demand
-priority: 5
-```
-
-Search pattern:
-```bash
-# Via GitHub API (if available)
-curl -s "https://api.github.com/search/repositories?q=topic:claude-skill&sort=stars"
-
-# Via web search fallback
-web_search "claude skill github site:github.com"
-```
-
-### 5. npm Registry (for JS/TS skills packaged as npm)
-
-```yaml
-name: npm
-type: package-registry
-base_url: https://registry.npmjs.org
-search_method: keyword search "claude-skill"
-install_method: npm install -g <package>
-refresh: on-demand
-priority: 6
-```
-
-### 6. PyPI (for Python skills packaged as pip)
-
-```yaml
-name: pypi
-type: package-registry
-base_url: https://pypi.org
-search_method: keyword search "claude-skill" OR "hermes-skill"
-install_method: pip install <package>
-refresh: on-demand
-priority: 6
-```
-
----
-
-## Marketplace Query Protocol
-
-When the resolver identifies a gap (stack detected, no skill available):
-
-```
-1. Check local -> user-local -> examples (instant, filesystem)
-2. If not found, check wiki for cached marketplace data
-3. If cache is stale or empty:
-   a. Query GitHub topics
-   b. Query npm/pypi if relevant language
-   c. Cache results in raw/marketplace-dumps/
-   d. Create new entity pages for discovered skills, or emit an update review
-      for existing pages
-4. Present findings to user with install commands
-```
-
-## Caching
-
-Marketplace results are cached in the wiki at:
-```
-raw/marketplace-dumps/<marketplace-name>-YYYY-MM.md
-```
-
-Each dump is a markdown table:
-
-```markdown
-# GitHub Marketplace Dump -- 2026-04
-
-| Name | URL | Stars | Description | Stacks | Last Updated |
-|------|-----|-------|-------------|--------|--------------|
-| ... | ... | ... | ... | ... | ... |
-```
-
-Refresh policy: controlled by `refresh_interval_days` on each marketplace's
-entity page. Default 7 days. User can override per marketplace.
-
-## Installing from Marketplace
-
-The install flow:
-1. Router suggests: "The `terraform` skill is available on GitHub. Install it?"
-2. User confirms
-3. Router executes:
-   ```bash
-   # GitHub example
-   git clone https://github.com/user/terraform-skill.git /tmp/terraform-skill
-   cp -r /tmp/terraform-skill /mnt/skills/user/terraform/
-   rm -rf /tmp/terraform-skill
-   ```
-4. Create the entity page in the wiki; if one already exists, show the
-   benefits/risks update review and require `--update-existing` before
-   replacing it
-5. Add to current manifest and load
-6. Log the install
-
-## Security Notes
-
-- Never auto-install without user confirmation
-- Always show the source URL before installing
-- For git repos: check for SKILL.md at root, reject if missing
-- Never execute arbitrary scripts from marketplace skills without user review
-- Warn if a skill requires network access or system-level permissions
+# Marketplace Registry
+
+> Known skill/plugin marketplaces and how to interact with them.
+> The router queries these when it detects a stack gap (needed skill not installed).
+
+## Registered Marketplaces
+
+### 1. Local Skills Directory
+
+```yaml
+name: local
+type: filesystem
+path: /mnt/skills/
+scan_method: directory listing
+refresh: always current
+priority: 1  # check first
+```
+
+List all installed skills:
+```bash
+find /mnt/skills/ -name "SKILL.md" -maxdepth 3
+```
+
+### 2. User Skills Directory
+
+```yaml
+name: user-local
+type: filesystem
+path: /mnt/skills/user/
+scan_method: directory listing
+refresh: always current
+priority: 2
+```
+
+User-uploaded or custom skills. Same scan as local but separate namespace.
+
+### 3. Example Skills
+
+```yaml
+name: examples
+type: filesystem
+path: /mnt/skills/examples/
+scan_method: directory listing
+refresh: always current
+priority: 3
+```
+
+Bundled example skills that may not be active but can be copied to user skills.
+
+### 4. GitHub Skill Repos
+
+```yaml
+name: github
+type: git
+base_url: https://github.com
+search_method: topic search "claude-skill" OR "hermes-skill"
+install_method: git clone + copy SKILL.md to /mnt/skills/user/
+refresh: on-demand
+priority: 5
+```
+
+Search pattern:
+```bash
+# Via GitHub API (if available)
+curl -s "https://api.github.com/search/repositories?q=topic:claude-skill&sort=stars"
+
+# Via web search fallback
+web_search "claude skill github site:github.com"
+```
+
+### 5. npm Registry (for JS/TS skills packaged as npm)
+
+```yaml
+name: npm
+type: package-registry
+base_url: https://registry.npmjs.org
+search_method: keyword search "claude-skill"
+install_method: npm install -g <package>
+refresh: on-demand
+priority: 6
+```
+
+### 6. PyPI (for Python skills packaged as pip)
+
+```yaml
+name: pypi
+type: package-registry
+base_url: https://pypi.org
+search_method: keyword search "claude-skill" OR "hermes-skill"
+install_method: pip install <package>
+refresh: on-demand
+priority: 6
+```
+
+---
+
+## Marketplace Query Protocol
+
+When the resolver identifies a gap (stack detected, no skill available):
+
+```
+1. Check local -> user-local -> examples (instant, filesystem)
+2. If not found, check wiki for cached marketplace data
+3. If cache is stale or empty:
+   a. Query GitHub topics
+   b. Query npm/pypi if relevant language
+   c. Cache results in raw/marketplace-dumps/
+   d. Create new entity pages for discovered skills, or emit an update review
+      for existing pages
+4. Present findings to user with install commands
+```
+
+## Caching
+
+Marketplace results are cached in the wiki at:
+```
+raw/marketplace-dumps/<marketplace-name>-YYYY-MM.md
+```
+
+Each dump is a markdown table:
+
+```markdown
+# GitHub Marketplace Dump -- 2026-04
+
+| Name | URL | Stars | Description | Stacks | Last Updated |
+|------|-----|-------|-------------|--------|--------------|
+| ... | ... | ... | ... | ... | ... |
+```
+
+Refresh policy: controlled by `refresh_interval_days` on each marketplace's
+entity page. Default 7 days. User can override per marketplace.
+
+## Installing from Marketplace
+
+The install flow:
+1. Router suggests: "The `terraform` skill is available on GitHub. Install it?"
+2. User confirms
+3. Router executes:
+   ```bash
+   # GitHub example
+   git clone https://github.com/user/terraform-skill.git /tmp/terraform-skill
+   cp -r /tmp/terraform-skill /mnt/skills/user/terraform/
+   rm -rf /tmp/terraform-skill
+   ```
+4. Create the entity page in the wiki; if one already exists, show the
+   benefits/risks update review and require `--update-existing` before
+   replacing it
+5. Add to current manifest and load
+6. Log the install
+
+## Security Notes
+
+- Never auto-install without user confirmation
+- Always show the source URL before installing
+- For git repos: check for SKILL.md at root, reject if missing
+- Never execute arbitrary scripts from marketplace skills without user review
+- Warn if a skill requires network access or system-level permissions

docs/services/macos/com.claude.backup.watchdog.plist

@@ -1,58 +1,58 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!--
-  LaunchAgent for the ctx backup watchdog (macOS).
-
-  Install:
-    1. Edit the two path strings below so CTX_REPO matches your
-       checkout and PYTHON matches your interpreter (e.g. the one from
-       `which python3` or a venv).
-    2. cp docs/services/macos/com.claude.backup.watchdog.plist \
-          ~/Library/LaunchAgents/
-    3. launchctl load -w ~/Library/LaunchAgents/com.claude.backup.watchdog.plist
-
-  Tail logs:
-    tail -f ~/Library/Logs/claude-backup-watchdog.log
-
-  Unload:
-    launchctl unload ~/Library/LaunchAgents/com.claude.backup.watchdog.plist
-
-  The agent runs in the user session (not at boot) and restarts on crash.
--->
-<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN"
- "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
-<plist version="1.0">
-<dict>
-  <key>Label</key>
-  <string>com.claude.backup.watchdog</string>
-
-  <!-- EDIT THIS: python interpreter + repo path -->
-  <key>ProgramArguments</key>
-  <array>
-    <string>/usr/bin/python3</string>
-    <string>/Users/YOUR_USER/ctx/src/backup_mirror.py</string>
-    <string>watchdog</string>
-    <string>--interval</string>
-    <string>60</string>
-  </array>
-
-  <key>RunAtLoad</key>
-  <true/>
-
-  <!-- Relaunch on crash with a short backoff so we don't busy-loop. -->
-  <key>KeepAlive</key>
-  <dict>
-    <key>SuccessfulExit</key>
-    <false/>
-  </dict>
-  <key>ThrottleInterval</key>
-  <integer>30</integer>
-
-  <key>StandardOutPath</key>
-  <string>/Users/YOUR_USER/Library/Logs/claude-backup-watchdog.log</string>
-  <key>StandardErrorPath</key>
-  <string>/Users/YOUR_USER/Library/Logs/claude-backup-watchdog.log</string>
-
-  <key>ProcessType</key>
-  <string>Background</string>
-</dict>
-</plist>
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+  LaunchAgent for the ctx backup watchdog (macOS).
+
+  Install:
+    1. Edit the two path strings below so CTX_REPO matches your
+       checkout and PYTHON matches your interpreter (e.g. the one from
+       `which python3` or a venv).
+    2. cp docs/services/macos/com.claude.backup.watchdog.plist \
+          ~/Library/LaunchAgents/
+    3. launchctl load -w ~/Library/LaunchAgents/com.claude.backup.watchdog.plist
+
+  Tail logs:
+    tail -f ~/Library/Logs/claude-backup-watchdog.log
+
+  Unload:
+    launchctl unload ~/Library/LaunchAgents/com.claude.backup.watchdog.plist
+
+  The agent runs in the user session (not at boot) and restarts on crash.
+-->
+<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN"
+ "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
+<plist version="1.0">
+<dict>
+  <key>Label</key>
+  <string>com.claude.backup.watchdog</string>
+
+  <!-- EDIT THIS: python interpreter + repo path -->
+  <key>ProgramArguments</key>
+  <array>
+    <string>/usr/bin/python3</string>
+    <string>/Users/YOUR_USER/ctx/src/backup_mirror.py</string>
+    <string>watchdog</string>
+    <string>--interval</string>
+    <string>60</string>
+  </array>
+
+  <key>RunAtLoad</key>
+  <true/>
+
+  <!-- Relaunch on crash with a short backoff so we don't busy-loop. -->
+  <key>KeepAlive</key>
+  <dict>
+    <key>SuccessfulExit</key>
+    <false/>
+  </dict>
+  <key>ThrottleInterval</key>
+  <integer>30</integer>
+
+  <key>StandardOutPath</key>
+  <string>/Users/YOUR_USER/Library/Logs/claude-backup-watchdog.log</string>
+  <key>StandardErrorPath</key>
+  <string>/Users/YOUR_USER/Library/Logs/claude-backup-watchdog.log</string>
+
+  <key>ProcessType</key>
+  <string>Background</string>
+</dict>
+</plist>

docs/services/systemd/claude-backup-watchdog.service

@@ -1,40 +1,40 @@
-# Systemd user unit for the ctx backup watchdog.
-#
-# Install:
-#   mkdir -p ~/.config/systemd/user
-#   cp docs/services/systemd/claude-backup-watchdog.service \
-#       ~/.config/systemd/user/
-#   # Edit the copy: set CTX_REPO to the absolute path of this checkout
-#   # and confirm your python3 path (e.g. /usr/bin/python3).
-#   systemctl --user daemon-reload
-#   systemctl --user enable --now claude-backup-watchdog.service
-#
-# Status / stop / tail:
-#   systemctl --user status   claude-backup-watchdog.service
-#   systemctl --user stop     claude-backup-watchdog.service
-#   journalctl --user -u      claude-backup-watchdog.service -f
-
-[Unit]
-Description=Claude ~/.claude backup watchdog (ctx)
-After=default.target
-
-[Service]
-Type=simple
-# Adjust CTX_REPO to your checkout, and Python if you use a venv.
-Environment=CTX_REPO=%h/ctx
-ExecStart=/usr/bin/python3 ${CTX_REPO}/src/backup_mirror.py watchdog --interval 60
-# Crash-recover: back off 5s between restarts, give up after 3 fast crashes.
-Restart=on-failure
-RestartSec=5
-StartLimitIntervalSec=60
-StartLimitBurst=3
-# Least-privilege: the watchdog only needs to read ~/.claude and write
-# ~/.claude/backups. No network. No privilege escalation.
-NoNewPrivileges=yes
-PrivateTmp=yes
-ProtectSystem=strict
-ProtectHome=read-only
-ReadWritePaths=%h/.claude/backups
-
-[Install]
-WantedBy=default.target
+# Systemd user unit for the ctx backup watchdog.
+#
+# Install:
+#   mkdir -p ~/.config/systemd/user
+#   cp docs/services/systemd/claude-backup-watchdog.service \
+#       ~/.config/systemd/user/
+#   # Edit the copy: set CTX_REPO to the absolute path of this checkout
+#   # and confirm your python3 path (e.g. /usr/bin/python3).
+#   systemctl --user daemon-reload
+#   systemctl --user enable --now claude-backup-watchdog.service
+#
+# Status / stop / tail:
+#   systemctl --user status   claude-backup-watchdog.service
+#   systemctl --user stop     claude-backup-watchdog.service
+#   journalctl --user -u      claude-backup-watchdog.service -f
+
+[Unit]
+Description=Claude ~/.claude backup watchdog (ctx)
+After=default.target
+
+[Service]
+Type=simple
+# Adjust CTX_REPO to your checkout, and Python if you use a venv.
+Environment=CTX_REPO=%h/ctx
+ExecStart=/usr/bin/python3 ${CTX_REPO}/src/backup_mirror.py watchdog --interval 60
+# Crash-recover: back off 5s between restarts, give up after 3 fast crashes.
+Restart=on-failure
+RestartSec=5
+StartLimitIntervalSec=60
+StartLimitBurst=3
+# Least-privilege: the watchdog only needs to read ~/.claude and write
+# ~/.claude/backups. No network. No privilege escalation.
+NoNewPrivileges=yes
+PrivateTmp=yes
+ProtectSystem=strict
+ProtectHome=read-only
+ReadWritePaths=%h/.claude/backups
+
+[Install]
+WantedBy=default.target

docs/services/windows/install-backup-watchdog.ps1

@@ -1,120 +1,120 @@
-# install-backup-watchdog.ps1
-#
-# Registers the ctx backup watchdog as a Windows Scheduled Task.
-# The task runs under the current user, starts at logon, and restarts
-# on failure. Nothing elevated — a standard user can install, run, and
-# remove the task without administrator rights.
-#
-# Usage:
-#   # From a PowerShell prompt inside this repo:
-#   pwsh -File docs/services/windows/install-backup-watchdog.ps1
-#
-# Flags:
-#   -RepoPath    Absolute path to this ctx checkout. Defaults to the
-#                repo the script lives in.
-#   -Python      Absolute path to the Python interpreter. Auto-detected
-#                via `where python` when omitted.
-#   -Interval    Seconds between polls. Default 60.
-#   -Uninstall   Remove the task and exit.
-#
-# Inspect afterwards:
-#   Get-ScheduledTask -TaskName 'ClaudeBackupWatchdog'
-#   Get-ScheduledTaskInfo -TaskName 'ClaudeBackupWatchdog'
-#
-# Remove:
-#   pwsh -File docs/services/windows/install-backup-watchdog.ps1 -Uninstall
-
-[CmdletBinding()]
-param(
-    [string]$RepoPath = (Resolve-Path "$PSScriptRoot\..\..\..").Path,
-    [string]$Python = $null,
-    [int]$Interval = 60,
-    [switch]$Uninstall
-)
-
-$ErrorActionPreference = 'Stop'
-$TaskName = 'ClaudeBackupWatchdog'
-
-if ($Uninstall) {
-    if (Get-ScheduledTask -TaskName $TaskName -ErrorAction SilentlyContinue) {
-        Unregister-ScheduledTask -TaskName $TaskName -Confirm:$false
-        Write-Host "[uninstall] removed scheduled task $TaskName"
-    } else {
-        Write-Host "[uninstall] task $TaskName is not registered; nothing to do"
-    }
-    return
-}
-
-# --- Validate inputs ----------------------------------------------------------
-
-$MirrorScript = Join-Path $RepoPath 'src\backup_mirror.py'
-if (-not (Test-Path $MirrorScript)) {
-    throw "backup_mirror.py not found under $RepoPath. Pass -RepoPath correctly."
-}
-
-if (-not $Python) {
-    $Python = (Get-Command python -ErrorAction SilentlyContinue).Source
-    if (-not $Python) {
-        throw "Python interpreter not found on PATH. Pass -Python <path>."
-    }
-}
-if (-not (Test-Path $Python)) {
-    throw "Python path does not exist: $Python"
-}
-
-if ($Interval -lt 5 -or $Interval -gt 3600) {
-    throw "Interval must be between 5 and 3600 seconds (got $Interval)."
-}
-
-# --- Build the task ----------------------------------------------------------
-
-$Arguments = "`"$MirrorScript`" watchdog --interval $Interval"
-
-$Action = New-ScheduledTaskAction `
-    -Execute $Python `
-    -Argument $Arguments `
-    -WorkingDirectory $RepoPath
-
-# Run at user logon. The watchdog itself sleeps between polls, so we
-# don't need a repetition trigger on top.
-$Trigger = New-ScheduledTaskTrigger -AtLogOn -User $env:USERNAME
-
-# Settings: allow on battery, restart on failure, no time limit.
-$Settings = New-ScheduledTaskSettingsSet `
-    -AllowStartIfOnBatteries `
-    -DontStopIfGoingOnBatteries `
-    -RestartCount 3 `
-    -RestartInterval (New-TimeSpan -Minutes 1) `
-    -ExecutionTimeLimit (New-TimeSpan -Days 0) `
-    -StartWhenAvailable
-
-$Principal = New-ScheduledTaskPrincipal `
-    -UserId $env:USERNAME `
-    -LogonType Interactive `
-    -RunLevel Limited
-
-$Description = "Snapshots ~/.claude/ on change. Source: $RepoPath"
-
-$Task = New-ScheduledTask `
-    -Action $Action `
-    -Trigger $Trigger `
-    -Settings $Settings `
-    -Principal $Principal `
-    -Description $Description
-
-# Replace any previous registration.
-if (Get-ScheduledTask -TaskName $TaskName -ErrorAction SilentlyContinue) {
-    Unregister-ScheduledTask -TaskName $TaskName -Confirm:$false
-}
-Register-ScheduledTask -TaskName $TaskName -InputObject $Task | Out-Null
-
-# Kick it off now so the user sees a snapshot folder appear.
-Start-ScheduledTask -TaskName $TaskName
-
-Write-Host "[install] registered scheduled task $TaskName"
-Write-Host "          python:   $Python"
-Write-Host "          script:   $MirrorScript"
-Write-Host "          interval: ${Interval}s"
-Write-Host ""
-Write-Host "Inspect:  Get-ScheduledTaskInfo -TaskName '$TaskName'"
-Write-Host "Remove:   pwsh -File '$PSCommandPath' -Uninstall"
+# install-backup-watchdog.ps1
+#
+# Registers the ctx backup watchdog as a Windows Scheduled Task.
+# The task runs under the current user, starts at logon, and restarts
+# on failure. Nothing elevated — a standard user can install, run, and
+# remove the task without administrator rights.
+#
+# Usage:
+#   # From a PowerShell prompt inside this repo:
+#   pwsh -File docs/services/windows/install-backup-watchdog.ps1
+#
+# Flags:
+#   -RepoPath    Absolute path to this ctx checkout. Defaults to the
+#                repo the script lives in.
+#   -Python      Absolute path to the Python interpreter. Auto-detected
+#                via `where python` when omitted.
+#   -Interval    Seconds between polls. Default 60.
+#   -Uninstall   Remove the task and exit.
+#
+# Inspect afterwards:
+#   Get-ScheduledTask -TaskName 'ClaudeBackupWatchdog'
+#   Get-ScheduledTaskInfo -TaskName 'ClaudeBackupWatchdog'
+#
+# Remove:
+#   pwsh -File docs/services/windows/install-backup-watchdog.ps1 -Uninstall
+
+[CmdletBinding()]
+param(
+    [string]$RepoPath = (Resolve-Path "$PSScriptRoot\..\..\..").Path,
+    [string]$Python = $null,
+    [int]$Interval = 60,
+    [switch]$Uninstall
+)
+
+$ErrorActionPreference = 'Stop'
+$TaskName = 'ClaudeBackupWatchdog'
+
+if ($Uninstall) {
+    if (Get-ScheduledTask -TaskName $TaskName -ErrorAction SilentlyContinue) {
+        Unregister-ScheduledTask -TaskName $TaskName -Confirm:$false
+        Write-Host "[uninstall] removed scheduled task $TaskName"
+    } else {
+        Write-Host "[uninstall] task $TaskName is not registered; nothing to do"
+    }
+    return
+}
+
+# --- Validate inputs ----------------------------------------------------------
+
+$MirrorScript = Join-Path $RepoPath 'src\backup_mirror.py'
+if (-not (Test-Path $MirrorScript)) {
+    throw "backup_mirror.py not found under $RepoPath. Pass -RepoPath correctly."
+}
+
+if (-not $Python) {
+    $Python = (Get-Command python -ErrorAction SilentlyContinue).Source
+    if (-not $Python) {
+        throw "Python interpreter not found on PATH. Pass -Python <path>."
+    }
+}
+if (-not (Test-Path $Python)) {
+    throw "Python path does not exist: $Python"
+}
+
+if ($Interval -lt 5 -or $Interval -gt 3600) {
+    throw "Interval must be between 5 and 3600 seconds (got $Interval)."
+}
+
+# --- Build the task ----------------------------------------------------------
+
+$Arguments = "`"$MirrorScript`" watchdog --interval $Interval"
+
+$Action = New-ScheduledTaskAction `
+    -Execute $Python `
+    -Argument $Arguments `
+    -WorkingDirectory $RepoPath
+
+# Run at user logon. The watchdog itself sleeps between polls, so we
+# don't need a repetition trigger on top.
+$Trigger = New-ScheduledTaskTrigger -AtLogOn -User $env:USERNAME
+
+# Settings: allow on battery, restart on failure, no time limit.
+$Settings = New-ScheduledTaskSettingsSet `
+    -AllowStartIfOnBatteries `
+    -DontStopIfGoingOnBatteries `
+    -RestartCount 3 `
+    -RestartInterval (New-TimeSpan -Minutes 1) `
+    -ExecutionTimeLimit (New-TimeSpan -Days 0) `
+    -StartWhenAvailable
+
+$Principal = New-ScheduledTaskPrincipal `
+    -UserId $env:USERNAME `
+    -LogonType Interactive `
+    -RunLevel Limited
+
+$Description = "Snapshots ~/.claude/ on change. Source: $RepoPath"
+
+$Task = New-ScheduledTask `
+    -Action $Action `
+    -Trigger $Trigger `
+    -Settings $Settings `
+    -Principal $Principal `
+    -Description $Description
+
+# Replace any previous registration.
+if (Get-ScheduledTask -TaskName $TaskName -ErrorAction SilentlyContinue) {
+    Unregister-ScheduledTask -TaskName $TaskName -Confirm:$false
+}
+Register-ScheduledTask -TaskName $TaskName -InputObject $Task | Out-Null
+
+# Kick it off now so the user sees a snapshot folder appear.
+Start-ScheduledTask -TaskName $TaskName
+
+Write-Host "[install] registered scheduled task $TaskName"
+Write-Host "          python:   $Python"
+Write-Host "          script:   $MirrorScript"
+Write-Host "          interval: ${Interval}s"
+Write-Host ""
+Write-Host "Inspect:  Get-ScheduledTaskInfo -TaskName '$TaskName'"
+Write-Host "Remove:   pwsh -File '$PSCommandPath' -Uninstall"

docs/skill-router/index.md

@@ -1,49 +1,49 @@
-# Skill router
-
-The skill router decides which skills, plugins, and MCP servers load into
-a session based on the active repository. The full router spec lives in
-[`docs/SKILL.md`](https://github.com/stevesolun/ctx/blob/main/docs/SKILL.md);
-this page summarizes the parts most relevant to the docs site.
-
-## Problem
-
-Every skill, plugin, and MCP server loaded into context costs tokens and
-attention. Most projects need 3–8 skills out of 30+. Loading all of them:
-
-- wastes the context window on irrelevant instructions,
-- causes skill misfires (wrong skill triggers for a task),
-- slows response time, and
-- creates conflicting instructions between skills.
-
-## Architecture
-
-```
-skill-router/
-├── SKILL.md                    # Orchestration logic
-├── references/
-│   ├── stack-signatures.md     # File/config → stack id
-│   ├── skill-stack-matrix.md   # Which skills serve which stacks
-│   └── marketplace-registry.md # Known marketplaces
-└── scripts/
-    ├── scan_repo.py            # Scanner → stack profile JSON
-    ├── resolve_skills.py       # Stack → skill set
-    └── skill_loader.py         # Load/unload skills into session
-```
-
-## Flow
-
-1. Repo opens (or Claude detects a `cd`).
-2. `scan_repo.py` produces a stack profile.
-3. `resolve_skills.py` maps the profile to a skill set using the
-   [skill-stack matrix](../skill-stack-matrix.md).
-4. `skill_loader.py` loads selected skills, unloads anything not in the
-   set, and records the choice in the LLM Wiki catalog.
-
-## Reference pages
-
-- [Stack signatures](../stack-signatures.md) — the file/config patterns
-  the scanner uses to identify stacks.
-- [Skill-stack matrix](../skill-stack-matrix.md) — the mapping from stack
-  identifiers to skill sets.
-- [Marketplace registry](../marketplace-registry.md) — known skill
-  marketplaces and query patterns.
+# Skill router
+
+The skill router decides which skills, plugins, and MCP servers load into
+a session based on the active repository. The full router spec lives in
+[`docs/SKILL.md`](https://github.com/stevesolun/ctx/blob/main/docs/SKILL.md);
+this page summarizes the parts most relevant to the docs site.
+
+## Problem
+
+Every skill, plugin, and MCP server loaded into context costs tokens and
+attention. Most projects need 3–8 skills out of 30+. Loading all of them:
+
+- wastes the context window on irrelevant instructions,
+- causes skill misfires (wrong skill triggers for a task),
+- slows response time, and
+- creates conflicting instructions between skills.
+
+## Architecture
+
+```
+skill-router/
+├── SKILL.md                    # Orchestration logic
+├── references/
+│   ├── stack-signatures.md     # File/config → stack id
+│   ├── skill-stack-matrix.md   # Which skills serve which stacks
+│   └── marketplace-registry.md # Known marketplaces
+└── scripts/
+    ├── scan_repo.py            # Scanner → stack profile JSON
+    ├── resolve_skills.py       # Stack → skill set
+    └── skill_loader.py         # Load/unload skills into session
+```
+
+## Flow
+
+1. Repo opens (or Claude detects a `cd`).
+2. `scan_repo.py` produces a stack profile.
+3. `resolve_skills.py` maps the profile to a skill set using the
+   [skill-stack matrix](../skill-stack-matrix.md).
+4. `skill_loader.py` loads selected skills, unloads anything not in the
+   set, and records the choice in the LLM Wiki catalog.
+
+## Reference pages
+
+- [Stack signatures](../stack-signatures.md) — the file/config patterns
+  the scanner uses to identify stacks.
+- [Skill-stack matrix](../skill-stack-matrix.md) — the mapping from stack
+  identifiers to skill sets.
+- [Marketplace registry](../marketplace-registry.md) — known skill
+  marketplaces and query patterns.

docs/skill-stack-matrix.md

@@ -1,165 +1,165 @@
-# Skill-Stack Matrix
-
-> Maps stack identifiers to the skills that serve them.
-> Used by resolve_skills.py to determine what to load.
-
-## Table of Contents
-1. [Matrix Format](#matrix-format)
-2. [The Matrix](#the-matrix)
-3. [Companion Rules](#companion-rules)
-4. [Conflict Rules](#conflict-rules)
-
----
-
-## Matrix Format
-
-Each entry:
-- **Stack IDs**: which detected stacks trigger this skill
-- **Skill**: skill name (matches directory name in /mnt/skills/)
-- **Priority Base**: starting priority before signal boosts
-- **Required**: must-load if stack detected, vs nice-to-have
-- **Companions**: skills that should co-load
-- **Conflicts**: skills that should not co-load
-
-## The Matrix
-
-### Document Creation Skills
-
-| Skill | Stack IDs | Priority | Required | Path Pattern |
-|-------|-----------|----------|----------|--------------|
-| docx | (any -- triggered by user request) | 2 | no | /mnt/skills/public/docx/ |
-| pdf | (any -- triggered by user request) | 2 | no | /mnt/skills/public/pdf/ |
-| pptx | (any -- triggered by user request) | 2 | no | /mnt/skills/public/pptx/ |
-| xlsx | (any -- triggered by user request) | 2 | no | /mnt/skills/public/xlsx/ |
-
-> Note: document skills are demand-loaded, not stack-loaded. They activate on user
-> request ("make a presentation") not on repo content. The router keeps them in a
-> "standby" pool -- not loaded into context, but available for instant load.
-
-### Frontend Skills
-
-| Skill | Stack IDs | Priority | Required |
-|-------|-----------|----------|----------|
-| frontend-design | react, vue, angular, svelte, nextjs, nuxt, html, css | 8 | yes |
-| react | react, nextjs | 7 | yes |
-| vue | vue, nuxt | 7 | yes |
-| angular | angular | 7 | yes |
-| svelte | svelte | 7 | yes |
-| tailwind | tailwindcss | 5 | no |
-| css-modules | css-modules | 4 | no |
-
-### Backend Skills
-
-| Skill | Stack IDs | Priority | Required |
-|-------|-----------|----------|----------|
-| fastapi | fastapi | 8 | yes |
-| django | django | 8 | yes |
-| flask | flask | 7 | yes |
-| express | express | 8 | yes |
-| nestjs | nestjs | 8 | yes |
-| rails | rails | 8 | yes |
-| gin | gin | 7 | yes |
-| actix | actix | 7 | yes |
-
-### Data Skills
-
-| Skill | Stack IDs | Priority | Required |
-|-------|-----------|----------|----------|
-| sqlalchemy | sqlalchemy, alembic | 6 | yes |
-| prisma | prisma | 6 | yes |
-| typeorm | typeorm | 6 | yes |
-| drizzle | drizzle | 6 | yes |
-| redis | redis | 4 | no |
-| kafka | kafka | 5 | no |
-| dbt | dbt | 6 | yes |
-
-### Infrastructure Skills
-
-| Skill | Stack IDs | Priority | Required |
-|-------|-----------|----------|----------|
-| docker | docker, docker-compose | 6 | yes |
-| kubernetes | kubernetes, helm, kustomize | 6 | yes |
-| terraform | terraform | 7 | yes |
-| github-actions | github-actions | 5 | yes |
-| gitlab-ci | gitlab-ci | 5 | yes |
-| aws | aws-cdk, aws-sam | 7 | yes |
-| vercel | vercel | 4 | no |
-
-### AI/Agent Skills
-
-| Skill | Stack IDs | Priority | Required |
-|-------|-----------|----------|----------|
-| langchain | langchain | 7 | yes |
-| llamaindex | llamaindex | 7 | yes |
-| mcp-dev | mcp | 7 | yes |
-| pytorch | pytorch | 6 | yes |
-| huggingface | huggingface | 6 | yes |
-| openai-sdk | openai-sdk | 5 | no |
-| anthropic-sdk | anthropic-sdk | 5 | no |
-
-### Quality Skills
-
-| Skill | Stack IDs | Priority | Required |
-|-------|-----------|----------|----------|
-| pytest | pytest | 5 | yes |
-| jest | jest, vitest | 5 | yes |
-| cypress | cypress | 4 | no |
-| playwright | playwright | 4 | no |
-| eslint | eslint | 3 | no |
-| ruff | ruff | 3 | no |
-
-### Documentation Skills
-
-| Skill | Stack IDs | Priority | Required |
-|-------|-----------|----------|----------|
-| openapi | openapi | 5 | yes |
-| graphql | graphql | 5 | yes |
-| mkdocs | mkdocs | 4 | no |
-| docusaurus | docusaurus | 4 | no |
-
-### Meta Skills (always available, never unloaded)
-
-| Skill | Stack IDs | Priority | Required | Notes |
-|-------|-----------|----------|----------|-------|
-| skill-router | * | 99 | yes | This skill -- always loaded |
-| file-reading | * | 50 | yes | Core capability |
-| skill-creator | * | 10 | no | Standby pool |
-| product-self-knowledge | * | 10 | no | Standby pool |
-
----
-
-## Companion Rules
-
-When skill A is loaded, also load skill B if its stack is detected:
-
-| Primary Skill | Companion | Condition |
-|---------------|-----------|-----------|
-| fastapi | sqlalchemy | DB migrations detected |
-| fastapi | openapi | OpenAPI spec file exists |
-| django | django-orm | (always with django) |
-| react | tailwind | tailwind.config.* exists |
-| docker | docker-compose | docker-compose.yml exists |
-| kubernetes | helm | Chart.yaml exists |
-| terraform | aws | provider "aws" in *.tf |
-| langchain | openai-sdk | openai in deps |
-| pytest | coverage | .coveragerc or coverage config exists |
-
-## Conflict Rules
-
-These skills should not be co-loaded (pick the one with higher confidence/priority):
-
-| Skill A | Skill B | Resolution |
-|---------|---------|------------|
-| flask | fastapi | Higher confidence wins |
-| flask | django | Higher confidence wins |
-| jest | vitest | Higher confidence wins |
-| webpack | vite | Higher confidence wins |
-| npm | yarn | Check lock file |
-| npm | pnpm | Check lock file |
-| yarn | pnpm | Check lock file |
-| react | vue | Both can coexist in monorepo |
-| sqlalchemy | prisma | Both can coexist if different services |
-
-> Conflict resolution: check if the repo is a monorepo. In monorepos, "conflicting"
-> skills may serve different packages and should both load. In single-package repos,
-> pick the one with higher confidence.
+# Skill-Stack Matrix
+
+> Maps stack identifiers to the skills that serve them.
+> Used by resolve_skills.py to determine what to load.
+
+## Table of Contents
+1. [Matrix Format](#matrix-format)
+2. [The Matrix](#the-matrix)
+3. [Companion Rules](#companion-rules)
+4. [Conflict Rules](#conflict-rules)
+
+---
+
+## Matrix Format
+
+Each entry:
+- **Stack IDs**: which detected stacks trigger this skill
+- **Skill**: skill name (matches directory name in /mnt/skills/)
+- **Priority Base**: starting priority before signal boosts
+- **Required**: must-load if stack detected, vs nice-to-have
+- **Companions**: skills that should co-load
+- **Conflicts**: skills that should not co-load
+
+## The Matrix
+
+### Document Creation Skills
+
+| Skill | Stack IDs | Priority | Required | Path Pattern |
+|-------|-----------|----------|----------|--------------|
+| docx | (any -- triggered by user request) | 2 | no | /mnt/skills/public/docx/ |
+| pdf | (any -- triggered by user request) | 2 | no | /mnt/skills/public/pdf/ |
+| pptx | (any -- triggered by user request) | 2 | no | /mnt/skills/public/pptx/ |
+| xlsx | (any -- triggered by user request) | 2 | no | /mnt/skills/public/xlsx/ |
+
+> Note: document skills are demand-loaded, not stack-loaded. They activate on user
+> request ("make a presentation") not on repo content. The router keeps them in a
+> "standby" pool -- not loaded into context, but available for instant load.
+
+### Frontend Skills
+
+| Skill | Stack IDs | Priority | Required |
+|-------|-----------|----------|----------|
+| frontend-design | react, vue, angular, svelte, nextjs, nuxt, html, css | 8 | yes |
+| react | react, nextjs | 7 | yes |
+| vue | vue, nuxt | 7 | yes |
+| angular | angular | 7 | yes |
+| svelte | svelte | 7 | yes |
+| tailwind | tailwindcss | 5 | no |
+| css-modules | css-modules | 4 | no |
+
+### Backend Skills
+
+| Skill | Stack IDs | Priority | Required |
+|-------|-----------|----------|----------|
+| fastapi | fastapi | 8 | yes |
+| django | django | 8 | yes |
+| flask | flask | 7 | yes |
+| express | express | 8 | yes |
+| nestjs | nestjs | 8 | yes |
+| rails | rails | 8 | yes |
+| gin | gin | 7 | yes |
+| actix | actix | 7 | yes |
+
+### Data Skills
+
+| Skill | Stack IDs | Priority | Required |
+|-------|-----------|----------|----------|
+| sqlalchemy | sqlalchemy, alembic | 6 | yes |
+| prisma | prisma | 6 | yes |
+| typeorm | typeorm | 6 | yes |
+| drizzle | drizzle | 6 | yes |
+| redis | redis | 4 | no |
+| kafka | kafka | 5 | no |
+| dbt | dbt | 6 | yes |
+
+### Infrastructure Skills
+
+| Skill | Stack IDs | Priority | Required |
+|-------|-----------|----------|----------|
+| docker | docker, docker-compose | 6 | yes |
+| kubernetes | kubernetes, helm, kustomize | 6 | yes |
+| terraform | terraform | 7 | yes |
+| github-actions | github-actions | 5 | yes |
+| gitlab-ci | gitlab-ci | 5 | yes |
+| aws | aws-cdk, aws-sam | 7 | yes |
+| vercel | vercel | 4 | no |
+
+### AI/Agent Skills
+
+| Skill | Stack IDs | Priority | Required |
+|-------|-----------|----------|----------|
+| langchain | langchain | 7 | yes |
+| llamaindex | llamaindex | 7 | yes |
+| mcp-dev | mcp | 7 | yes |
+| pytorch | pytorch | 6 | yes |
+| huggingface | huggingface | 6 | yes |
+| openai-sdk | openai-sdk | 5 | no |
+| anthropic-sdk | anthropic-sdk | 5 | no |
+
+### Quality Skills
+
+| Skill | Stack IDs | Priority | Required |
+|-------|-----------|----------|----------|
+| pytest | pytest | 5 | yes |
+| jest | jest, vitest | 5 | yes |
+| cypress | cypress | 4 | no |
+| playwright | playwright | 4 | no |
+| eslint | eslint | 3 | no |
+| ruff | ruff | 3 | no |
+
+### Documentation Skills
+
+| Skill | Stack IDs | Priority | Required |
+|-------|-----------|----------|----------|
+| openapi | openapi | 5 | yes |
+| graphql | graphql | 5 | yes |
+| mkdocs | mkdocs | 4 | no |
+| docusaurus | docusaurus | 4 | no |
+
+### Meta Skills (always available, never unloaded)
+
+| Skill | Stack IDs | Priority | Required | Notes |
+|-------|-----------|----------|----------|-------|
+| skill-router | * | 99 | yes | This skill -- always loaded |
+| file-reading | * | 50 | yes | Core capability |
+| skill-creator | * | 10 | no | Standby pool |
+| product-self-knowledge | * | 10 | no | Standby pool |
+
+---
+
+## Companion Rules
+
+When skill A is loaded, also load skill B if its stack is detected:
+
+| Primary Skill | Companion | Condition |
+|---------------|-----------|-----------|
+| fastapi | sqlalchemy | DB migrations detected |
+| fastapi | openapi | OpenAPI spec file exists |
+| django | django-orm | (always with django) |
+| react | tailwind | tailwind.config.* exists |
+| docker | docker-compose | docker-compose.yml exists |
+| kubernetes | helm | Chart.yaml exists |
+| terraform | aws | provider "aws" in *.tf |
+| langchain | openai-sdk | openai in deps |
+| pytest | coverage | .coveragerc or coverage config exists |
+
+## Conflict Rules
+
+These skills should not be co-loaded (pick the one with higher confidence/priority):
+
+| Skill A | Skill B | Resolution |
+|---------|---------|------------|
+| flask | fastapi | Higher confidence wins |
+| flask | django | Higher confidence wins |
+| jest | vitest | Higher confidence wins |
+| webpack | vite | Higher confidence wins |
+| npm | yarn | Check lock file |
+| npm | pnpm | Check lock file |
+| yarn | pnpm | Check lock file |
+| react | vue | Both can coexist in monorepo |
+| sqlalchemy | prisma | Both can coexist if different services |
+
+> Conflict resolution: check if the repo is a monorepo. In monorepos, "conflicting"
+> skills may serve different packages and should both load. In single-package repos,
+> pick the one with higher confidence.

docs/skills-health.md

@@ -18,7 +18,7 @@ For each skill (`~/.claude/skills/<name>/SKILL.md`) and each agent
 | `frontmatter-missing-name` | error | Frontmatter has no `name:` field |
 | `frontmatter-missing-description` | warning | Missing `description:` (router relevance suffers) |
 | `empty-body` | error | Fewer than `min_body_lines` non-blank lines |
-| `over-threshold` | warning | Line count exceeds `skill_transformer.line_threshold`; the packaged default is 180 and users can override it in `~/.claude/skill-system-config.json` |
+| `over-threshold` | warning | Line count exceeds `skill_transformer.line_threshold`; the packaged default is 180 and users can override it in `~/.claude/skill-system-config.json` |
 
 ## Drift detection
 

docs/stack-signatures.md

@@ -1,164 +1,164 @@
-# Stack Signatures Reference
-
-> Maps file patterns and config markers to stack identifiers.
-> The scanner uses this to classify what a repo contains.
-> Organized by detection category. Each entry: pattern -> stack identifier + confidence.
-
-## Table of Contents
-1. [Languages](#languages)
-2. [Web Frameworks](#web-frameworks)
-3. [AI/ML Frameworks](#aiml-frameworks)
-4. [Infrastructure](#infrastructure)
-5. [Data & Storage](#data-storage)
-6. [Testing](#testing)
-7. [Build & Package](#build-package)
-8. [Documentation](#documentation)
-9. [AI/Agent Tooling](#aiagent-tooling)
-
----
-
-## Languages
-
-| Pattern | Stack ID | Confidence | Notes |
-|---------|----------|------------|-------|
-| `*.py` + `pyproject.toml` | python | 1.0 | Check `python_requires` for version |
-| `*.py` + `requirements.txt` | python | 0.95 | Older pattern, still common |
-| `*.py` + `Pipfile` | python | 0.95 | |
-| `*.py` + `poetry.lock` | python | 1.0 | |
-| `*.ts` + `tsconfig.json` | typescript | 1.0 | |
-| `*.js` + `package.json` | javascript | 0.9 | Could be TS compiled |
-| `*.rs` + `Cargo.toml` | rust | 1.0 | |
-| `*.go` + `go.mod` | go | 1.0 | |
-| `*.java` + `pom.xml` | java | 1.0 | Maven |
-| `*.java` + `build.gradle` | java | 1.0 | Gradle |
-| `*.kt` + `build.gradle.kts` | kotlin | 1.0 | |
-| `*.rb` + `Gemfile` | ruby | 1.0 | |
-| `*.swift` + `Package.swift` | swift | 1.0 | |
-| `*.cs` + `*.csproj` | csharp | 1.0 | |
-| `*.php` + `composer.json` | php | 1.0 | |
-
-## Web Frameworks
-
-| Pattern | Stack ID | Confidence | Notes |
-|---------|----------|------------|-------|
-| `next.config.*` | nextjs | 1.0 | Check for app/ vs pages/ |
-| `nuxt.config.*` | nuxt | 1.0 | |
-| `angular.json` | angular | 1.0 | |
-| `svelte.config.*` | svelte | 1.0 | |
-| `vite.config.*` + react in deps | react | 0.95 | Confirm via package.json |
-| `package.json` has `"react"` | react | 0.9 | Check version for 18 vs 19 |
-| `package.json` has `"vue"` | vue | 0.9 | |
-| `package.json` has `"express"` | express | 0.95 | |
-| `package.json` has `"fastify"` | fastify | 0.95 | |
-| pyproject/req has `fastapi` | fastapi | 0.99 | |
-| pyproject/req has `django` | django | 0.99 | Check for DRF too |
-| pyproject/req has `flask` | flask | 0.95 | |
-| `Gemfile` has `rails` | rails | 1.0 | |
-| `go.mod` has `gin-gonic` | gin | 0.95 | |
-| `Cargo.toml` has `actix-web` | actix | 0.95 | |
-| `Cargo.toml` has `axum` | axum | 0.95 | |
-
-## AI/ML Frameworks
-
-| Pattern | Stack ID | Confidence | Notes |
-|---------|----------|------------|-------|
-| deps has `torch` or `pytorch` | pytorch | 0.95 | |
-| deps has `tensorflow` | tensorflow | 0.95 | |
-| deps has `transformers` | huggingface | 0.9 | |
-| deps has `langchain` | langchain | 0.95 | Check core vs community |
-| deps has `llama-index` | llamaindex | 0.95 | |
-| deps has `crewai` | crewai | 0.95 | |
-| deps has `autogen` | autogen | 0.95 | |
-| deps has `semantic-kernel` | semantic-kernel | 0.95 | |
-| deps has `openai` | openai-sdk | 0.8 | Could be indirect |
-| deps has `anthropic` | anthropic-sdk | 0.8 | |
-| deps has `dspy` | dspy | 0.95 | |
-| `*.ipynb` files present | jupyter | 0.85 | |
-
-## Infrastructure
-
-| Pattern | Stack ID | Confidence | Notes |
-|---------|----------|------------|-------|
-| `Dockerfile` | docker | 1.0 | |
-| `docker-compose.yml` | docker-compose | 1.0 | |
-| `.github/workflows/*.yml` | github-actions | 1.0 | |
-| `.gitlab-ci.yml` | gitlab-ci | 1.0 | |
-| `Jenkinsfile` | jenkins | 1.0 | |
-| `.circleci/config.yml` | circleci | 1.0 | |
-| `*.tf` files | terraform | 1.0 | |
-| `pulumi.*` or `Pulumi.yaml` | pulumi | 1.0 | |
-| `cdk.json` | aws-cdk | 1.0 | |
-| `template.yaml` (SAM) | aws-sam | 0.9 | Disambiguate from other templates |
-| `serverless.yml` | serverless | 1.0 | |
-| `k8s/` or `kubernetes/` dir | kubernetes | 0.95 | |
-| `helm/` or `Chart.yaml` | helm | 1.0 | |
-| `kustomization.yaml` | kustomize | 1.0 | |
-| `ansible/` or `playbook.yml` | ansible | 0.9 | |
-| `fly.toml` | fly-io | 1.0 | |
-| `vercel.json` | vercel | 1.0 | |
-| `netlify.toml` | netlify | 1.0 | |
-| `render.yaml` | render | 1.0 | |
-| `railway.json` | railway | 1.0 | |
-
-## Data & Storage
-
-| Pattern | Stack ID | Confidence | Notes |
-|---------|----------|------------|-------|
-| `alembic/` or `alembic.ini` | sqlalchemy | 0.95 | |
-| `prisma/schema.prisma` | prisma | 1.0 | |
-| deps has `typeorm` | typeorm | 0.95 | |
-| deps has `drizzle-orm` | drizzle | 0.95 | |
-| deps has `sequelize` | sequelize | 0.95 | |
-| `migrations/` + Django | django-orm | 0.9 | |
-| deps has `redis` or `ioredis` | redis | 0.85 | |
-| deps has `kafka` or `confluent-kafka` | kafka | 0.9 | |
-| deps has `celery` | celery | 0.95 | |
-| `dags/` directory | airflow | 0.9 | |
-| `dbt_project.yml` | dbt | 1.0 | |
-| `*.sql` migration files | sql | 0.7 | Generic |
-
-## Testing
-
-| Pattern | Stack ID | Confidence | Notes |
-|---------|----------|------------|-------|
-| `pytest.ini` or `conftest.py` | pytest | 1.0 | |
-| `jest.config.*` | jest | 1.0 | |
-| `vitest.config.*` | vitest | 1.0 | |
-| `cypress.config.*` or `cypress/` | cypress | 1.0 | |
-| `playwright.config.*` | playwright | 1.0 | |
-| `.mocharc.*` | mocha | 1.0 | |
-
-## Build & Package
-
-| Pattern | Stack ID | Confidence | Notes |
-|---------|----------|------------|-------|
-| `webpack.config.*` | webpack | 1.0 | |
-| `vite.config.*` | vite | 1.0 | |
-| `esbuild.*` in scripts | esbuild | 0.8 | |
-| `turbo.json` | turborepo | 1.0 | |
-| `nx.json` | nx | 1.0 | |
-| `lerna.json` | lerna | 1.0 | |
-| `pnpm-workspace.yaml` | pnpm-workspace | 1.0 | |
-| `yarn.lock` + `workspaces` in pkg.json | yarn-workspace | 0.95 | |
-
-## Documentation
-
-| Pattern | Stack ID | Confidence | Notes |
-|---------|----------|------------|-------|
-| `mkdocs.yml` | mkdocs | 1.0 | |
-| `docusaurus.config.*` | docusaurus | 1.0 | |
-| `conf.py` + `index.rst` | sphinx | 0.95 | |
-| `.vitepress/` | vitepress | 1.0 | |
-| `openapi.yaml` or `swagger.yaml` | openapi | 0.95 | |
-| `*.graphql` or `schema.graphql` | graphql | 0.9 | |
-
-## AI/Agent Tooling
-
-| Pattern | Stack ID | Confidence | Notes |
-|---------|----------|------------|-------|
-| `mcp.json` or `.mcp/` | mcp | 1.0 | |
-| `CLAUDE.md` | claude-code | 0.95 | |
-| `.cursorrules` | cursor | 0.9 | |
-| `.windsurfrules` | windsurf | 0.9 | |
-| `prompts/` directory | prompt-management | 0.7 | |
-| `.env` with `*_API_KEY` | api-keys | 0.6 | Names only, never values |
+# Stack Signatures Reference
+
+> Maps file patterns and config markers to stack identifiers.
+> The scanner uses this to classify what a repo contains.
+> Organized by detection category. Each entry: pattern -> stack identifier + confidence.
+
+## Table of Contents
+1. [Languages](#languages)
+2. [Web Frameworks](#web-frameworks)
+3. [AI/ML Frameworks](#aiml-frameworks)
+4. [Infrastructure](#infrastructure)
+5. [Data & Storage](#data-storage)
+6. [Testing](#testing)
+7. [Build & Package](#build-package)
+8. [Documentation](#documentation)
+9. [AI/Agent Tooling](#aiagent-tooling)
+
+---
+
+## Languages
+
+| Pattern | Stack ID | Confidence | Notes |
+|---------|----------|------------|-------|
+| `*.py` + `pyproject.toml` | python | 1.0 | Check `python_requires` for version |
+| `*.py` + `requirements.txt` | python | 0.95 | Older pattern, still common |
+| `*.py` + `Pipfile` | python | 0.95 | |
+| `*.py` + `poetry.lock` | python | 1.0 | |
+| `*.ts` + `tsconfig.json` | typescript | 1.0 | |
+| `*.js` + `package.json` | javascript | 0.9 | Could be TS compiled |
+| `*.rs` + `Cargo.toml` | rust | 1.0 | |
+| `*.go` + `go.mod` | go | 1.0 | |
+| `*.java` + `pom.xml` | java | 1.0 | Maven |
+| `*.java` + `build.gradle` | java | 1.0 | Gradle |
+| `*.kt` + `build.gradle.kts` | kotlin | 1.0 | |
+| `*.rb` + `Gemfile` | ruby | 1.0 | |
+| `*.swift` + `Package.swift` | swift | 1.0 | |
+| `*.cs` + `*.csproj` | csharp | 1.0 | |
+| `*.php` + `composer.json` | php | 1.0 | |
+
+## Web Frameworks
+
+| Pattern | Stack ID | Confidence | Notes |
+|---------|----------|------------|-------|
+| `next.config.*` | nextjs | 1.0 | Check for app/ vs pages/ |
+| `nuxt.config.*` | nuxt | 1.0 | |
+| `angular.json` | angular | 1.0 | |
+| `svelte.config.*` | svelte | 1.0 | |
+| `vite.config.*` + react in deps | react | 0.95 | Confirm via package.json |
+| `package.json` has `"react"` | react | 0.9 | Check version for 18 vs 19 |
+| `package.json` has `"vue"` | vue | 0.9 | |
+| `package.json` has `"express"` | express | 0.95 | |
+| `package.json` has `"fastify"` | fastify | 0.95 | |
+| pyproject/req has `fastapi` | fastapi | 0.99 | |
+| pyproject/req has `django` | django | 0.99 | Check for DRF too |
+| pyproject/req has `flask` | flask | 0.95 | |
+| `Gemfile` has `rails` | rails | 1.0 | |
+| `go.mod` has `gin-gonic` | gin | 0.95 | |
+| `Cargo.toml` has `actix-web` | actix | 0.95 | |
+| `Cargo.toml` has `axum` | axum | 0.95 | |
+
+## AI/ML Frameworks
+
+| Pattern | Stack ID | Confidence | Notes |
+|---------|----------|------------|-------|
+| deps has `torch` or `pytorch` | pytorch | 0.95 | |
+| deps has `tensorflow` | tensorflow | 0.95 | |
+| deps has `transformers` | huggingface | 0.9 | |
+| deps has `langchain` | langchain | 0.95 | Check core vs community |
+| deps has `llama-index` | llamaindex | 0.95 | |
+| deps has `crewai` | crewai | 0.95 | |
+| deps has `autogen` | autogen | 0.95 | |
+| deps has `semantic-kernel` | semantic-kernel | 0.95 | |
+| deps has `openai` | openai-sdk | 0.8 | Could be indirect |
+| deps has `anthropic` | anthropic-sdk | 0.8 | |
+| deps has `dspy` | dspy | 0.95 | |
+| `*.ipynb` files present | jupyter | 0.85 | |
+
+## Infrastructure
+
+| Pattern | Stack ID | Confidence | Notes |
+|---------|----------|------------|-------|
+| `Dockerfile` | docker | 1.0 | |
+| `docker-compose.yml` | docker-compose | 1.0 | |
+| `.github/workflows/*.yml` | github-actions | 1.0 | |
+| `.gitlab-ci.yml` | gitlab-ci | 1.0 | |
+| `Jenkinsfile` | jenkins | 1.0 | |
+| `.circleci/config.yml` | circleci | 1.0 | |
+| `*.tf` files | terraform | 1.0 | |
+| `pulumi.*` or `Pulumi.yaml` | pulumi | 1.0 | |
+| `cdk.json` | aws-cdk | 1.0 | |
+| `template.yaml` (SAM) | aws-sam | 0.9 | Disambiguate from other templates |
+| `serverless.yml` | serverless | 1.0 | |
+| `k8s/` or `kubernetes/` dir | kubernetes | 0.95 | |
+| `helm/` or `Chart.yaml` | helm | 1.0 | |
+| `kustomization.yaml` | kustomize | 1.0 | |
+| `ansible/` or `playbook.yml` | ansible | 0.9 | |
+| `fly.toml` | fly-io | 1.0 | |
+| `vercel.json` | vercel | 1.0 | |
+| `netlify.toml` | netlify | 1.0 | |
+| `render.yaml` | render | 1.0 | |
+| `railway.json` | railway | 1.0 | |
+
+## Data & Storage
+
+| Pattern | Stack ID | Confidence | Notes |
+|---------|----------|------------|-------|
+| `alembic/` or `alembic.ini` | sqlalchemy | 0.95 | |
+| `prisma/schema.prisma` | prisma | 1.0 | |
+| deps has `typeorm` | typeorm | 0.95 | |
+| deps has `drizzle-orm` | drizzle | 0.95 | |
+| deps has `sequelize` | sequelize | 0.95 | |
+| `migrations/` + Django | django-orm | 0.9 | |
+| deps has `redis` or `ioredis` | redis | 0.85 | |
+| deps has `kafka` or `confluent-kafka` | kafka | 0.9 | |
+| deps has `celery` | celery | 0.95 | |
+| `dags/` directory | airflow | 0.9 | |
+| `dbt_project.yml` | dbt | 1.0 | |
+| `*.sql` migration files | sql | 0.7 | Generic |
+
+## Testing
+
+| Pattern | Stack ID | Confidence | Notes |
+|---------|----------|------------|-------|
+| `pytest.ini` or `conftest.py` | pytest | 1.0 | |
+| `jest.config.*` | jest | 1.0 | |
+| `vitest.config.*` | vitest | 1.0 | |
+| `cypress.config.*` or `cypress/` | cypress | 1.0 | |
+| `playwright.config.*` | playwright | 1.0 | |
+| `.mocharc.*` | mocha | 1.0 | |
+
+## Build & Package
+
+| Pattern | Stack ID | Confidence | Notes |
+|---------|----------|------------|-------|
+| `webpack.config.*` | webpack | 1.0 | |
+| `vite.config.*` | vite | 1.0 | |
+| `esbuild.*` in scripts | esbuild | 0.8 | |
+| `turbo.json` | turborepo | 1.0 | |
+| `nx.json` | nx | 1.0 | |
+| `lerna.json` | lerna | 1.0 | |
+| `pnpm-workspace.yaml` | pnpm-workspace | 1.0 | |
+| `yarn.lock` + `workspaces` in pkg.json | yarn-workspace | 0.95 | |
+
+## Documentation
+
+| Pattern | Stack ID | Confidence | Notes |
+|---------|----------|------------|-------|
+| `mkdocs.yml` | mkdocs | 1.0 | |
+| `docusaurus.config.*` | docusaurus | 1.0 | |
+| `conf.py` + `index.rst` | sphinx | 0.95 | |
+| `.vitepress/` | vitepress | 1.0 | |
+| `openapi.yaml` or `swagger.yaml` | openapi | 0.95 | |
+| `*.graphql` or `schema.graphql` | graphql | 0.9 | |
+
+## AI/Agent Tooling
+
+| Pattern | Stack ID | Confidence | Notes |
+|---------|----------|------------|-------|
+| `mcp.json` or `.mcp/` | mcp | 1.0 | |
+| `CLAUDE.md` | claude-code | 0.95 | |
+| `.cursorrules` | cursor | 0.9 | |
+| `.windsurfrules` | windsurf | 0.9 | |
+| `prompts/` directory | prompt-management | 0.7 | |
+| `.env` with `*_API_KEY` | api-keys | 0.6 | Names only, never values |

docs/toolbox/hooks.md

@@ -1,80 +1,80 @@
-# Hooks & triggers
-
-[`src/toolbox_hooks.py`](https://github.com/stevesolun/ctx/blob/main/src/toolbox_hooks.py)
-is the bridge between Claude Code's hook system and the toolbox runner.
-It listens for four events plus one explicit slash command.
-
-## Event model
-
-| Event | Fires on | Typical toolbox |
-|---|---|---|
-| `session-start` | New Claude Code session | Skill preloaders, intent suggestions |
-| `file-save` | File written to disk | Linters, quick reviewers |
-| `pre-commit` | `git commit` before write | Guardrail councils (`ship-it`, `security-sweep`) |
-| `session-end` | Session closes | Digest, behavior miner, retro |
-| `slash:/toolbox run <name>` | User-initiated | Anything |
-
-Each trigger in a toolbox's `trigger` map enables that toolbox on that
-event. Events with no matching toolbox emit nothing.
-
-## Emission format
-
-One JSON line per matching toolbox, on stdout:
-
-```jsonc
-{
-  "trigger": "pre-commit",
-  "toolbox": "ship-it",
-  "plan_file": "/Users/steve/.claude/toolbox-runs/abc123.json",
-  "agents": ["code-reviewer", "security-reviewer", "architect-review"],
-  "files": ["src/toolbox_verdict.py", "src/tests/test_toolbox_verdict.py"],
-  "source": "pre-commit",
-  "guardrail": true
-}
-```
-
-Claude Code's hook handler reads these lines and dispatches each agent
-against the listed files.
-
-## Exit codes
-
-| Code | Meaning |
-|---|---|
-| `0` | Success; zero or more toolboxes emitted |
-| `1` | Unknown trigger or config error |
-| `2` | `pre-commit` + `guardrail=true` + verdict level is HIGH/CRITICAL |
-
-The `2` exit from `pre-commit` is what actually blocks `git commit`.
-
-## Installation
-
-`pip install claude-ctx` exposes `ctx-toolbox` on PATH; wire it into
-`.githooks/pre-commit` directly:
-
-```bash
-# .githooks/pre-commit
-#!/bin/sh
-ctx-toolbox run --event pre-commit
-```
-
-Then point git at the directory once: `git config core.hooksPath .githooks`.
-
-Then `git config core.hooksPath .githooks`.
-
-## file-save path matching
-
-`file-save` triggers honor `scope.files` globs. Without a `--path` arg
-the event matches nothing (there's no file to test). This is intentional:
-file-save toolboxes must be path-scoped.
-
-## session-end digest
-
-On `session-end`, the hook also calls
-[`behavior_miner.build_profile`](behavior-miner.md), saves the updated
-profile, and prints any new suggestions. This is informational only —
-the digest never blocks and never changes the return code.
-
-## Reference
-
-- [Council runner](council-runner.md) — how plans are built.
-- [Verdicts & guardrails](verdicts.md) — how blocking is decided.
+# Hooks & triggers
+
+[`src/toolbox_hooks.py`](https://github.com/stevesolun/ctx/blob/main/src/toolbox_hooks.py)
+is the bridge between Claude Code's hook system and the toolbox runner.
+It listens for four events plus one explicit slash command.
+
+## Event model
+
+| Event | Fires on | Typical toolbox |
+|---|---|---|
+| `session-start` | New Claude Code session | Skill preloaders, intent suggestions |
+| `file-save` | File written to disk | Linters, quick reviewers |
+| `pre-commit` | `git commit` before write | Guardrail councils (`ship-it`, `security-sweep`) |
+| `session-end` | Session closes | Digest, behavior miner, retro |
+| `slash:/toolbox run <name>` | User-initiated | Anything |
+
+Each trigger in a toolbox's `trigger` map enables that toolbox on that
+event. Events with no matching toolbox emit nothing.
+
+## Emission format
+
+One JSON line per matching toolbox, on stdout:
+
+```jsonc
+{
+  "trigger": "pre-commit",
+  "toolbox": "ship-it",
+  "plan_file": "/Users/steve/.claude/toolbox-runs/abc123.json",
+  "agents": ["code-reviewer", "security-reviewer", "architect-review"],
+  "files": ["src/toolbox_verdict.py", "src/tests/test_toolbox_verdict.py"],
+  "source": "pre-commit",
+  "guardrail": true
+}
+```
+
+Claude Code's hook handler reads these lines and dispatches each agent
+against the listed files.
+
+## Exit codes
+
+| Code | Meaning |
+|---|---|
+| `0` | Success; zero or more toolboxes emitted |
+| `1` | Unknown trigger or config error |
+| `2` | `pre-commit` + `guardrail=true` + verdict level is HIGH/CRITICAL |
+
+The `2` exit from `pre-commit` is what actually blocks `git commit`.
+
+## Installation
+
+`pip install claude-ctx` exposes `ctx-toolbox` on PATH; wire it into
+`.githooks/pre-commit` directly:
+
+```bash
+# .githooks/pre-commit
+#!/bin/sh
+ctx-toolbox run --event pre-commit
+```
+
+Then point git at the directory once: `git config core.hooksPath .githooks`.
+
+Then `git config core.hooksPath .githooks`.
+
+## file-save path matching
+
+`file-save` triggers honor `scope.files` globs. Without a `--path` arg
+the event matches nothing (there's no file to test). This is intentional:
+file-save toolboxes must be path-scoped.
+
+## session-end digest
+
+On `session-end`, the hook also calls
+[`behavior_miner.build_profile`](behavior-miner.md), saves the updated
+profile, and prints any new suggestions. This is informational only —
+the digest never blocks and never changes the return code.
+
+## Reference
+
+- [Council runner](council-runner.md) — how plans are built.
+- [Verdicts & guardrails](verdicts.md) — how blocking is decided.

docs/toolbox/index.md

@@ -50,11 +50,11 @@ toolboxes:
     guardrail: true
 ```
 
-Run it manually:
-
-```bash
-ctx-toolbox run --event pre-commit
-```
+Run it manually:
+
+```bash
+ctx-toolbox run --event pre-commit
+```
 
 Or let the `pre-commit` hook fire it automatically — see
 [Hooks & triggers](hooks.md).

docs/toolbox/templates/docs-review.json

@@ -1,30 +1,30 @@
-{
-  "description": "Documentation pass: accuracy, completeness, clarity, and API parity",
-  "pre": ["docs-lookup"],
-  "post": [
-    "technical-writer",
-    "docs-architect",
-    "api-documenter",
-    "tutorial-engineer"
-  ],
-  "scope": {
-    "projects": ["*"],
-    "signals": ["documentation"],
-    "analysis": "diff"
-  },
-  "trigger": {
-    "slash": true,
-    "pre_commit": false,
-    "session_end": false,
-    "file_save": "**/*.md"
-  },
-  "budget": {
-    "max_tokens": 120000,
-    "max_seconds": 240
-  },
-  "dedup": {
-    "window_seconds": 300,
-    "policy": "cached"
-  },
-  "guardrail": false
-}
+{
+  "description": "Documentation pass: accuracy, completeness, clarity, and API parity",
+  "pre": ["docs-lookup"],
+  "post": [
+    "technical-writer",
+    "docs-architect",
+    "api-documenter",
+    "tutorial-engineer"
+  ],
+  "scope": {
+    "projects": ["*"],
+    "signals": ["documentation"],
+    "analysis": "diff"
+  },
+  "trigger": {
+    "slash": true,
+    "pre_commit": false,
+    "session_end": false,
+    "file_save": "**/*.md"
+  },
+  "budget": {
+    "max_tokens": 120000,
+    "max_seconds": 240
+  },
+  "dedup": {
+    "window_seconds": 300,
+    "policy": "cached"
+  },
+  "guardrail": false
+}

docs/toolbox/templates/fresh-repo-init.json

@@ -1,29 +1,29 @@
-{
-  "description": "New-repo bootstrap: run the intent interview, scaffold plan, pick initial toolbox",
-  "pre": [],
-  "post": [
-    "planner",
-    "architect",
-    "tdd-guide"
-  ],
-  "scope": {
-    "projects": ["*"],
-    "signals": [],
-    "analysis": "diff"
-  },
-  "trigger": {
-    "slash": true,
-    "pre_commit": false,
-    "session_end": false,
-    "file_save": null
-  },
-  "budget": {
-    "max_tokens": 100000,
-    "max_seconds": 300
-  },
-  "dedup": {
-    "window_seconds": 0,
-    "policy": "fresh"
-  },
-  "guardrail": false
-}
+{
+  "description": "New-repo bootstrap: run the intent interview, scaffold plan, pick initial toolbox",
+  "pre": [],
+  "post": [
+    "planner",
+    "architect",
+    "tdd-guide"
+  ],
+  "scope": {
+    "projects": ["*"],
+    "signals": [],
+    "analysis": "diff"
+  },
+  "trigger": {
+    "slash": true,
+    "pre_commit": false,
+    "session_end": false,
+    "file_save": null
+  },
+  "budget": {
+    "max_tokens": 100000,
+    "max_seconds": 300
+  },
+  "dedup": {
+    "window_seconds": 0,
+    "policy": "fresh"
+  },
+  "guardrail": false
+}

docs/toolbox/templates/refactor-safety.json

@@ -1,31 +1,31 @@
-{
-  "description": "Graph-informed refactor review with regression and dead-code checks",
-  "pre": ["architect-review", "refactor-cleaner"],
-  "post": [
-    "architect-review",
-    "refactor-cleaner",
-    "code-reviewer",
-    "test-automator",
-    "dependency-manager"
-  ],
-  "scope": {
-    "projects": ["*"],
-    "signals": [],
-    "analysis": "graph-blast"
-  },
-  "trigger": {
-    "slash": true,
-    "pre_commit": false,
-    "session_end": true,
-    "file_save": null
-  },
-  "budget": {
-    "max_tokens": 180000,
-    "max_seconds": 360
-  },
-  "dedup": {
-    "window_seconds": 900,
-    "policy": "cached"
-  },
-  "guardrail": false
-}
+{
+  "description": "Graph-informed refactor review with regression and dead-code checks",
+  "pre": ["architect-review", "refactor-cleaner"],
+  "post": [
+    "architect-review",
+    "refactor-cleaner",
+    "code-reviewer",
+    "test-automator",
+    "dependency-manager"
+  ],
+  "scope": {
+    "projects": ["*"],
+    "signals": [],
+    "analysis": "graph-blast"
+  },
+  "trigger": {
+    "slash": true,
+    "pre_commit": false,
+    "session_end": true,
+    "file_save": null
+  },
+  "budget": {
+    "max_tokens": 180000,
+    "max_seconds": 360
+  },
+  "dedup": {
+    "window_seconds": 900,
+    "policy": "cached"
+  },
+  "guardrail": false
+}

docs/toolbox/templates/security-sweep.json

@@ -1,31 +1,31 @@
-{
-  "description": "Full-repo security audit with blocking guardrail on HIGH findings",
-  "pre": [],
-  "post": [
-    "security-reviewer",
-    "security-auditor",
-    "penetration-tester",
-    "compliance-auditor",
-    "threat-detection-engineer"
-  ],
-  "scope": {
-    "projects": ["*"],
-    "signals": ["security", "auth", "crypto"],
-    "analysis": "full"
-  },
-  "trigger": {
-    "slash": true,
-    "pre_commit": true,
-    "session_end": false,
-    "file_save": "**/auth/**"
-  },
-  "budget": {
-    "max_tokens": 300000,
-    "max_seconds": 600
-  },
-  "dedup": {
-    "window_seconds": 0,
-    "policy": "fresh"
-  },
-  "guardrail": true
-}
+{
+  "description": "Full-repo security audit with blocking guardrail on HIGH findings",
+  "pre": [],
+  "post": [
+    "security-reviewer",
+    "security-auditor",
+    "penetration-tester",
+    "compliance-auditor",
+    "threat-detection-engineer"
+  ],
+  "scope": {
+    "projects": ["*"],
+    "signals": ["security", "auth", "crypto"],
+    "analysis": "full"
+  },
+  "trigger": {
+    "slash": true,
+    "pre_commit": true,
+    "session_end": false,
+    "file_save": "**/auth/**"
+  },
+  "budget": {
+    "max_tokens": 300000,
+    "max_seconds": 600
+  },
+  "dedup": {
+    "window_seconds": 0,
+    "policy": "fresh"
+  },
+  "guardrail": true
+}

docs/toolbox/templates/ship-it.json

@@ -1,33 +1,33 @@
-{
-  "description": "Professional council of 7 experts for end-of-feature review",
-  "pre": [],
-  "post": [
-    "code-reviewer",
-    "security-reviewer",
-    "architect-review",
-    "test-automator",
-    "performance-engineer",
-    "accessibility-tester",
-    "docs-lookup"
-  ],
-  "scope": {
-    "projects": ["*"],
-    "signals": ["python", "typescript", "rust", "go", "java"],
-    "analysis": "dynamic"
-  },
-  "trigger": {
-    "slash": true,
-    "pre_commit": true,
-    "session_end": true,
-    "file_save": null
-  },
-  "budget": {
-    "max_tokens": 200000,
-    "max_seconds": 420
-  },
-  "dedup": {
-    "window_seconds": 600,
-    "policy": "fresh"
-  },
-  "guardrail": false
-}
+{
+  "description": "Professional council of 7 experts for end-of-feature review",
+  "pre": [],
+  "post": [
+    "code-reviewer",
+    "security-reviewer",
+    "architect-review",
+    "test-automator",
+    "performance-engineer",
+    "accessibility-tester",
+    "docs-lookup"
+  ],
+  "scope": {
+    "projects": ["*"],
+    "signals": ["python", "typescript", "rust", "go", "java"],
+    "analysis": "dynamic"
+  },
+  "trigger": {
+    "slash": true,
+    "pre_commit": true,
+    "session_end": true,
+    "file_save": null
+  },
+  "budget": {
+    "max_tokens": 200000,
+    "max_seconds": 420
+  },
+  "dedup": {
+    "window_seconds": 600,
+    "policy": "fresh"
+  },
+  "guardrail": false
+}

graph/README.md

@@ -1,6 +1,6 @@
 # Knowledge Graph
 
-Pre-built knowledge graph of **104,079 nodes** and **2,960,215 edges** across **53 communities** (Louvain). The curated core is **13,233 nodes** (1,969 curated skills + 464 agents + 10,787 MCP servers + 13 cataloged harnesses). The Skills.sh catalog contributes **90,846 first-class `skill` nodes**, **90,846 skill entity pages under `entities/skills/skills-sh-*.md`**, and **89,461 hydrated installable Skills.sh `SKILL.md` files** under `converted/skills-sh-*/`, with the **28,611** long entries converted to gated micro-skill orchestrators. Edges are blended from three signals: semantic cosine (**1,707,435** edges, default weight 0.70), explicit `tags:` overlap (**920,686** candidate pairs, weight 0.15), and sparse slug-token overlap (**442,556** candidate pairs, weight 0.15). Skills.sh is full-body semantic: **1,525,295** Skills.sh-incident edges have non-zero `semantic_sim`, including **1,437,138** Skills.sh-to-Skills.sh semantic edges. Rebuild with `python -m ctx.core.wiki.wiki_graphify`, add harnesses with `ctx-harness-add`, then refresh the Skills.sh catalog with `python src/import_skills_sh_catalog.py --from-api-union <raw.json> --update-wiki-tar`.
+Pre-built knowledge graph of **104,079 nodes** and **2,960,215 edges** across **53 communities** (Louvain). The curated core is **13,233 nodes** (1,969 curated skills + 464 agents + 10,787 MCP servers + 13 cataloged harnesses). The Skills.sh catalog contributes **90,846 first-class `skill` nodes**, **90,846 skill entity pages under `entities/skills/skills-sh-*.md`**, and **89,462 hydrated installable Skills.sh `SKILL.md` files** under `converted/skills-sh-*/`, with the **28,611** long entries converted to gated micro-skill orchestrators. Edges are blended from three signals: semantic cosine (**1,707,435** edges, default weight 0.70), explicit `tags:` overlap (**920,686** candidate pairs, weight 0.15), and sparse slug-token overlap (**442,556** candidate pairs, weight 0.15). Skills.sh is full-body semantic: **1,525,295** Skills.sh-incident edges have non-zero `semantic_sim`, including **1,437,138** Skills.sh-to-Skills.sh semantic edges. Rebuild with `python -m ctx.core.wiki.wiki_graphify`, add harnesses with `ctx-harness-add`, then refresh the Skills.sh catalog with `python src/import_skills_sh_catalog.py --from-api-union <raw.json> --update-wiki-tar`.
 
 Runtime recommendation is intentionally split into two paths: execution
 surfaces recommend only skills, agents, and MCP servers; custom/API/local model
@@ -34,7 +34,7 @@ harness match floor in `config.json`.
 
 | File | Size | Contents |
 |------|------|----------|
-| `wiki-graph.tar.gz` | ~336 MiB | **Full wiki** - entity cards, 91,234 converted skill bodies, 430 mirrored agent bodies, 104K-node / 3.0M-edge knowledge graph, concept pages, catalog, 13 cataloged harnesses, and first-class hydrated Skills.sh installable pages |
+| `wiki-graph.tar.gz` | ~336 MiB | **Full wiki** - entity cards, 91,235 converted skill bodies, 430 mirrored agent bodies, 104K-node / 3.0M-edge knowledge graph, concept pages, catalog, 13 cataloged harnesses, and first-class hydrated Skills.sh installable pages |
 | `skills-sh-catalog.json.gz` | ~11.3 MiB | Compressed Skills.sh catalog (90,846 observed entries, install commands, detail URLs, inferred tags, overlap metadata) |
 | `communities.json` | ~6.6 MiB | 53 detected communities (Louvain) with labels + member lists |
 | `viz-overview.html` / `.png` | — | Plotly-rendered overview of the full graph |
@@ -50,7 +50,7 @@ harness match floor in `config.json`.
 - `entities/mcp-servers/<shard>/` — **10,787** MCP entity pages (sharded by first-char to keep dirs scannable)
 - `entities/harnesses/` - **13** harness entity pages
 - `concepts/` - community concept pages generated from the current Louvain labels
-- `converted/` - **91,234** skill bodies ready for `ctx-skill-install`, including **89,461** hydrated Skills.sh `SKILL.md` files. Long entries over the configured loader threshold are gated micro-skill orchestrators; no `SKILL.md.original` backups are shipped
+- `converted/` - **91,235** skill bodies ready for `ctx-skill-install`, including **89,462** hydrated Skills.sh `SKILL.md` files. Long entries over the configured loader threshold are gated micro-skill orchestrators; no `SKILL.md.original` backups are shipped
 - `converted-agents/` — **430** agent bodies ready for `ctx-agent-install`
 - `graphify-out/graph.json` - full knowledge graph (104,079 nodes, 2,960,215 edges), including the curated core, cataloged harnesses, and full-body semantic Skills.sh skill nodes
 - `graphify-out/communities.json` - community detection results (53 communities, Louvain)
@@ -76,7 +76,7 @@ tar xzf graph/wiki-graph.tar.gz -C ~/.claude/skill-wiki/
 
 This gives you:
 - Every curated entity (skill / agent / MCP / harness) plus every remote-cataloged Skills.sh skill page browsable as frontmatter-rich markdown
-- Installable content for every curated short/long skill, 89,461 hydrated Skills.sh `SKILL.md` files, and every mirrored agent (`ctx-skill-install`, `ctx-agent-install`)
+- Installable content for every curated short/long skill, 89,462 hydrated Skills.sh `SKILL.md` files, and every mirrored agent (`ctx-skill-install`, `ctx-agent-install`)
 - The full knowledge graph (`graphify-out/graph.json`) and community detection (`communities.json`)
 - An Obsidian vault — open the extracted dir in Obsidian and the graph view renders directly
 

graph/skills-sh-catalog.json.gz

@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:0478308583c69dfcb35327188363b78b756f277ff23d9593bb947b95da2f9689
-size 11801628
+oid sha256:314195a6165e2288d4fd10a72d0b5455790d6103d0ca264c2af977a6c69d20f3
+size 11801277

graph/wiki-graph.tar.gz

@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:e73b507de9770f7fb61d4260c22514b5cc79dace56be81589e81fa4ca8258667
-size 351897751
+oid sha256:5747d77eea2f36d0e7860a5ef397e7d671357b70168008909512a6645e85bd50
+size 351900191

hooks/backup_on_change.py

@@ -1,166 +1,166 @@
-#!/usr/bin/env python3
-"""
-backup_on_change.py -- PostToolUse hook that snapshots on config changes.
-
-Designed to be registered in ``~/.claude/settings.json`` under:
-
-    "hooks": {
-      "PostToolUse": [
-        {
-          "matcher": "Edit|Write|MultiEdit",
-          "hooks": [
-            {
-              "type": "command",
-              "command": "python <repo>/hooks/backup_on_change.py"
-            }
-          ]
-        }
-      ]
-    }
-
-Claude Code delivers each PostToolUse event as a JSON payload on stdin.
-This script:
-
-  1. Parses the payload.
-  2. Checks whether the tool edited a file that BackupConfig tracks
-     (top_files, trees, or projects/*/memory when memory_glob is on).
-  3. If so, shells out to ``python src/backup_mirror.py snapshot-if-changed
-     --reason <tool>:<basename>`` so the snapshot name records what fired it.
-  4. Never blocks the tool: any error is logged to stderr and the hook
-     exits 0 so a bug here can't stall the user's session.
-
-Snapshots only happen when content *actually* changed (SHA diff against
-the last snapshot's manifest) — so a no-op Edit won't create a folder.
-"""
-
-from __future__ import annotations
-
-import json
-import os
-import subprocess
-import sys
-from pathlib import Path
-from typing import Any
-
-
-REPO_ROOT = Path(__file__).resolve().parent.parent
-SRC = REPO_ROOT / "src"
-if str(SRC) not in sys.path:
-    sys.path.insert(0, str(SRC))
-
-
-def _load_payload() -> dict[str, Any]:
-    """Read the PostToolUse payload from stdin. Empty on error."""
-    try:
-        raw = sys.stdin.read()
-        if not raw.strip():
-            return {}
-        data = json.loads(raw)
-        return data if isinstance(data, dict) else {}
-    except (json.JSONDecodeError, OSError):
-        return {}
-
-
-def _extract_touched_path(payload: dict[str, Any]) -> Path | None:
-    """Pull the file path out of an Edit / Write / MultiEdit payload."""
-    tool_input = payload.get("tool_input") or {}
-    if not isinstance(tool_input, dict):
-        return None
-    # Edit, Write, MultiEdit all use ``file_path``.
-    candidate = tool_input.get("file_path")
-    if isinstance(candidate, str) and candidate:
-        try:
-            return Path(candidate).expanduser().resolve(strict=False)
-        except (OSError, ValueError):
-            return None
-    return None
-
-
-def _is_tracked(path: Path, claude_home: Path) -> bool:
-    """True when ``path`` is one of the files BackupConfig mirrors."""
-    # Lazy import: hook must still function even when the rest of the
-    # repo's dependency graph is in a weird state (e.g. during install).
-    try:
-        from backup_config import from_ctx_config  # noqa: PLC0415
-    except ImportError:
-        return False
-
-    cfg = from_ctx_config()
-
-    try:
-        path_resolved = path.resolve(strict=False)
-        home_resolved = claude_home.resolve(strict=False)
-    except OSError:
-        return False
-
-    try:
-        rel = path_resolved.relative_to(home_resolved)
-    except ValueError:
-        return False
-
-    rel_posix = rel.as_posix()
-
-    # Top-level files: match by basename against cfg.top_files.
-    if rel_posix in cfg.top_files:
-        return True
-
-    # Trees: match any file under a tracked tree's src prefix.
-    for tree in cfg.trees:
-        prefix = tree.src.rstrip("/") + "/"
-        if rel_posix == tree.src or rel_posix.startswith(prefix):
-            return True
-
-    # Memory glob: projects/<slug>/memory/...
-    if cfg.memory_glob:
-        parts = rel.parts
-        if len(parts) >= 3 and parts[0] == "projects" and parts[2] == "memory":
-            return True
-
-    return False
-
-
-def _invoke_snapshot(reason: str) -> int:
-    """Shell out to snapshot-if-changed. Returns child exit code (or 0)."""
-    mirror = SRC / "backup_mirror.py"
-    if not mirror.is_file():
-        print(f"[backup_on_change] missing {mirror}", file=sys.stderr)
-        return 0
-    try:
-        result = subprocess.run(
-            [sys.executable, str(mirror), "snapshot-if-changed",
-             "--reason", reason],
-            capture_output=True,
-            text=True,
-            timeout=60,
-            check=False,
-        )
-        if result.stdout.strip():
-            print(result.stdout.strip(), file=sys.stderr)
-        if result.returncode != 0 and result.stderr.strip():
-            print(result.stderr.strip(), file=sys.stderr)
-        return result.returncode
-    except (OSError, subprocess.TimeoutExpired) as exc:
-        print(f"[backup_on_change] snapshot failed: {exc}", file=sys.stderr)
-        return 0
-
-
-def main() -> int:
-    payload = _load_payload()
-    tool_name = str(payload.get("tool_name") or "unknown")
-
-    touched = _extract_touched_path(payload)
-    if touched is None:
-        return 0
-
-    claude_home = Path(os.path.expanduser("~/.claude"))
-    if not _is_tracked(touched, claude_home):
-        return 0
-
-    reason = f"{tool_name}:{touched.name}"
-    _invoke_snapshot(reason)
-    # Always exit 0: hook failures must not block the user's tool.
-    return 0
-
-
-if __name__ == "__main__":
-    sys.exit(main())
+#!/usr/bin/env python3
+"""
+backup_on_change.py -- PostToolUse hook that snapshots on config changes.
+
+Designed to be registered in ``~/.claude/settings.json`` under:
+
+    "hooks": {
+      "PostToolUse": [
+        {
+          "matcher": "Edit|Write|MultiEdit",
+          "hooks": [
+            {
+              "type": "command",
+              "command": "python <repo>/hooks/backup_on_change.py"
+            }
+          ]
+        }
+      ]
+    }
+
+Claude Code delivers each PostToolUse event as a JSON payload on stdin.
+This script:
+
+  1. Parses the payload.
+  2. Checks whether the tool edited a file that BackupConfig tracks
+     (top_files, trees, or projects/*/memory when memory_glob is on).
+  3. If so, shells out to ``python src/backup_mirror.py snapshot-if-changed
+     --reason <tool>:<basename>`` so the snapshot name records what fired it.
+  4. Never blocks the tool: any error is logged to stderr and the hook
+     exits 0 so a bug here can't stall the user's session.
+
+Snapshots only happen when content *actually* changed (SHA diff against
+the last snapshot's manifest) — so a no-op Edit won't create a folder.
+"""
+
+from __future__ import annotations
+
+import json
+import os
+import subprocess
+import sys
+from pathlib import Path
+from typing import Any
+
+
+REPO_ROOT = Path(__file__).resolve().parent.parent
+SRC = REPO_ROOT / "src"
+if str(SRC) not in sys.path:
+    sys.path.insert(0, str(SRC))
+
+
+def _load_payload() -> dict[str, Any]:
+    """Read the PostToolUse payload from stdin. Empty on error."""
+    try:
+        raw = sys.stdin.read()
+        if not raw.strip():
+            return {}
+        data = json.loads(raw)
+        return data if isinstance(data, dict) else {}
+    except (json.JSONDecodeError, OSError):
+        return {}
+
+
+def _extract_touched_path(payload: dict[str, Any]) -> Path | None:
+    """Pull the file path out of an Edit / Write / MultiEdit payload."""
+    tool_input = payload.get("tool_input") or {}
+    if not isinstance(tool_input, dict):
+        return None
+    # Edit, Write, MultiEdit all use ``file_path``.
+    candidate = tool_input.get("file_path")
+    if isinstance(candidate, str) and candidate:
+        try:
+            return Path(candidate).expanduser().resolve(strict=False)
+        except (OSError, ValueError):
+            return None
+    return None
+
+
+def _is_tracked(path: Path, claude_home: Path) -> bool:
+    """True when ``path`` is one of the files BackupConfig mirrors."""
+    # Lazy import: hook must still function even when the rest of the
+    # repo's dependency graph is in a weird state (e.g. during install).
+    try:
+        from backup_config import from_ctx_config  # noqa: PLC0415
+    except ImportError:
+        return False
+
+    cfg = from_ctx_config()
+
+    try:
+        path_resolved = path.resolve(strict=False)
+        home_resolved = claude_home.resolve(strict=False)
+    except OSError:
+        return False
+
+    try:
+        rel = path_resolved.relative_to(home_resolved)
+    except ValueError:
+        return False
+
+    rel_posix = rel.as_posix()
+
+    # Top-level files: match by basename against cfg.top_files.
+    if rel_posix in cfg.top_files:
+        return True
+
+    # Trees: match any file under a tracked tree's src prefix.
+    for tree in cfg.trees:
+        prefix = tree.src.rstrip("/") + "/"
+        if rel_posix == tree.src or rel_posix.startswith(prefix):
+            return True
+
+    # Memory glob: projects/<slug>/memory/...
+    if cfg.memory_glob:
+        parts = rel.parts
+        if len(parts) >= 3 and parts[0] == "projects" and parts[2] == "memory":
+            return True
+
+    return False
+
+
+def _invoke_snapshot(reason: str) -> int:
+    """Shell out to snapshot-if-changed. Returns child exit code (or 0)."""
+    mirror = SRC / "backup_mirror.py"
+    if not mirror.is_file():
+        print(f"[backup_on_change] missing {mirror}", file=sys.stderr)
+        return 0
+    try:
+        result = subprocess.run(
+            [sys.executable, str(mirror), "snapshot-if-changed",
+             "--reason", reason],
+            capture_output=True,
+            text=True,
+            timeout=60,
+            check=False,
+        )
+        if result.stdout.strip():
+            print(result.stdout.strip(), file=sys.stderr)
+        if result.returncode != 0 and result.stderr.strip():
+            print(result.stderr.strip(), file=sys.stderr)
+        return result.returncode
+    except (OSError, subprocess.TimeoutExpired) as exc:
+        print(f"[backup_on_change] snapshot failed: {exc}", file=sys.stderr)
+        return 0
+
+
+def main() -> int:
+    payload = _load_payload()
+    tool_name = str(payload.get("tool_name") or "unknown")
+
+    touched = _extract_touched_path(payload)
+    if touched is None:
+        return 0
+
+    claude_home = Path(os.path.expanduser("~/.claude"))
+    if not _is_tracked(touched, claude_home):
+        return 0
+
+    reason = f"{tool_name}:{touched.name}"
+    _invoke_snapshot(reason)
+    # Always exit 0: hook failures must not block the user's tool.
+    return 0
+
+
+if __name__ == "__main__":
+    sys.exit(main())

hooks/quality_on_session_end.py

@@ -1,223 +1,223 @@
-#!/usr/bin/env python3
-"""
-quality_on_session_end.py -- Stop hook that recomputes quality for the slugs
-this session touched.
-
-Designed for ``~/.claude/settings.json``:
-
-    "hooks": {
-      "Stop": [
-        {
-          "hooks": [
-            {
-              "type": "command",
-              "command": "python <repo>/hooks/quality_on_session_end.py"
-            }
-          ]
-        }
-      ]
-    }
-
-Why incremental instead of ``recompute --all``:
-
-  - Full recompute walks every installed skill + agent (2,000+ pages) and
-    runs four signal extractors per page. That's ~30s on a warm cache and
-    dominates the tail of every session.
-  - The only signals that *changed* since last session are telemetry
-    (we logged new loads) and maybe intake (if the user edited a skill
-    file). Every other signal moves on a slower clock.
-  - So we compute the set of slugs that showed up in the telemetry event
-    stream since the last time this hook ran, and rescore just those.
-
-Always exits 0: a hook that blocks session shutdown is worse than a
-slightly stale quality score.
-"""
-
-from __future__ import annotations
-
-import json
-import os
-import subprocess
-import sys
-from datetime import datetime, timedelta, timezone
-from pathlib import Path
-from typing import Any
-
-
-REPO_ROOT = Path(__file__).resolve().parent.parent
-SRC = REPO_ROOT / "src"
-if str(SRC) not in sys.path:
-    sys.path.insert(0, str(SRC))
-
-
-# How far back to look for touched slugs if no marker file exists.
-# Matches ``recent_window_days`` default in ``QualityConfig`` so a
-# freshly-installed system scores every recently-loaded skill on first run.
-_DEFAULT_LOOKBACK_HOURS = 24
-
-# State file: stores the ISO timestamp of the last successful run. Lives
-# under ~/.claude so it persists across repo clones and venv moves.
-_STATE_PATH = Path(os.path.expanduser("~/.claude/skill-quality/.hook-state.json"))
-_EVENTS_PATH = Path(os.path.expanduser("~/.claude/skill-events.jsonl"))
-
-# Upper bound on how many slugs we'll hand to the recompute subcommand in
-# one invocation. Pathological: a user loads 500 distinct skills in one
-# session. We'd rather recompute the top 50 than stall on session-end.
-_MAX_SLUGS_PER_RUN = 50
-
-
-def _load_payload() -> dict[str, Any]:
-    try:
-        raw = sys.stdin.read()
-        if not raw.strip():
-            return {}
-        data = json.loads(raw)
-        return data if isinstance(data, dict) else {}
-    except (json.JSONDecodeError, OSError):
-        return {}
-
-
-def _read_cutoff() -> datetime:
-    """Return the 'since' cutoff for scanning events."""
-    if _STATE_PATH.is_file():
-        try:
-            data = json.loads(_STATE_PATH.read_text(encoding="utf-8"))
-            ts = data.get("last_run_at")
-            if isinstance(ts, str):
-                parsed = datetime.fromisoformat(ts)
-                if parsed.tzinfo is None:
-                    parsed = parsed.replace(tzinfo=timezone.utc)
-                return parsed.astimezone(timezone.utc)
-        except (json.JSONDecodeError, ValueError, OSError):
-            pass
-    return datetime.now(timezone.utc) - timedelta(hours=_DEFAULT_LOOKBACK_HOURS)
-
-
-def _write_state(now: datetime) -> None:
-    try:
-        _STATE_PATH.parent.mkdir(parents=True, exist_ok=True)
-        _STATE_PATH.write_text(
-            json.dumps({"last_run_at": now.isoformat(timespec="seconds")}),
-            encoding="utf-8",
-        )
-    except OSError as exc:
-        print(f"[quality_on_session_end] could not write state: {exc}",
-              file=sys.stderr)
-
-
-def _touched_slugs_since(cutoff: datetime, events_path: Path) -> list[str]:
-    """Return a deduplicated list of skill slugs that appear after ``cutoff``."""
-    if not events_path.is_file():
-        return []
-    seen: dict[str, None] = {}
-    try:
-        with events_path.open(encoding="utf-8") as fh:
-            for raw in fh:
-                line = raw.strip()
-                if not line:
-                    continue
-                try:
-                    obj = json.loads(line)
-                except json.JSONDecodeError:
-                    continue
-                if not isinstance(obj, dict):
-                    continue
-                slug = obj.get("skill")
-                ts_raw = obj.get("timestamp")
-                if not isinstance(slug, str) or not isinstance(ts_raw, str):
-                    continue
-                try:
-                    parsed = datetime.fromisoformat(ts_raw)
-                except ValueError:
-                    continue
-                if parsed.tzinfo is None:
-                    parsed = parsed.replace(tzinfo=timezone.utc)
-                if parsed < cutoff:
-                    continue
-                # Insertion order preserved by dict in Python 3.7+.
-                seen.setdefault(slug, None)
-    except OSError:
-        return []
-    return list(seen.keys())[:_MAX_SLUGS_PER_RUN]
-
-
-def _invoke_recompute(slugs: list[str], session_id: str | None = None) -> int:
-    if not slugs:
-        return 0
-    script = SRC / "skill_quality.py"
-    if not script.is_file():
-        print(f"[quality_on_session_end] missing {script}", file=sys.stderr)
-        return 0
-    # Propagate session_id via environment so the per-slug
-    # skill.score_updated audit rows carry it. Without this the
-    # dashboard's per-session timeline drops the middle event in the
-    # load -> score_updated -> unload triad.
-    env = dict(os.environ)
-    if session_id:
-        env["CTX_SESSION_ID"] = session_id
-    try:
-        result = subprocess.run(
-            [sys.executable, str(script), "recompute",
-             "--slugs", ",".join(slugs)],
-            capture_output=True,
-            text=True,
-            timeout=120,
-            check=False,
-            env=env,
-        )
-        if result.stderr.strip():
-            print(result.stderr.strip(), file=sys.stderr)
-        return result.returncode
-    except (OSError, subprocess.TimeoutExpired) as exc:
-        print(f"[quality_on_session_end] recompute failed: {exc}",
-              file=sys.stderr)
-        return 0
-
-
-def main() -> int:
-    payload = _load_payload()  # consume stdin even if we don't use it
-    now = datetime.now(timezone.utc)
-    cutoff = _read_cutoff()
-    slugs = _touched_slugs_since(cutoff, _EVENTS_PATH)
-
-    # Resolve session_id up-front so it can flow into both the
-    # recompute subprocess (via CTX_SESSION_ID env) AND the session.ended
-    # audit record below. Previously the score_updated rows had no
-    # session_id, breaking the dashboard's per-session timeline.
-    session_id: str | None = None
-    if isinstance(payload, dict):
-        session_id = payload.get("session_id") or payload.get("sessionId")
-    if not session_id:
-        session_id = f"session-{now.strftime('%Y%m%dT%H%M%SZ')}"
-
-    _invoke_recompute(slugs, session_id=session_id)
-    _write_state(now)
-
-    # Unified audit: one line per session boundary + rotate if big.
-    # Guarded with try/except because a hook that fails on audit is
-    # worse than one that runs without telemetry.
-    try:
-        # ctx_audit_log lives in src/. Add src/ to path so this hook
-        # (which runs out of hooks/) can import it regardless of whether
-        # the user is on the editable install or the pip-installed copy.
-        _SRC = Path(__file__).parent.parent / "src"
-        if str(_SRC) not in sys.path:
-            sys.path.insert(0, str(_SRC))
-        from ctx_audit_log import log_session_event, rotate_if_needed
-
-        # session_id resolved above — reuse it so the audit record
-        # agrees with the CTX_SESSION_ID that score_updated rows carry.
-        log_session_event(
-            "session.ended", session_id, actor="hook",
-            meta={"recomputed_slugs": len(slugs), "cutoff": cutoff.isoformat()},
-        )
-        rotate_if_needed()
-    except Exception:  # noqa: BLE001 — audit is advisory
-        pass
-
-    # Always exit 0: hook errors must not stall session shutdown.
-    return 0
-
-
-if __name__ == "__main__":
-    sys.exit(main())
+#!/usr/bin/env python3
+"""
+quality_on_session_end.py -- Stop hook that recomputes quality for the slugs
+this session touched.
+
+Designed for ``~/.claude/settings.json``:
+
+    "hooks": {
+      "Stop": [
+        {
+          "hooks": [
+            {
+              "type": "command",
+              "command": "python <repo>/hooks/quality_on_session_end.py"
+            }
+          ]
+        }
+      ]
+    }
+
+Why incremental instead of ``recompute --all``:
+
+  - Full recompute walks every installed skill + agent (2,000+ pages) and
+    runs four signal extractors per page. That's ~30s on a warm cache and
+    dominates the tail of every session.
+  - The only signals that *changed* since last session are telemetry
+    (we logged new loads) and maybe intake (if the user edited a skill
+    file). Every other signal moves on a slower clock.
+  - So we compute the set of slugs that showed up in the telemetry event
+    stream since the last time this hook ran, and rescore just those.
+
+Always exits 0: a hook that blocks session shutdown is worse than a
+slightly stale quality score.
+"""
+
+from __future__ import annotations
+
+import json
+import os
+import subprocess
+import sys
+from datetime import datetime, timedelta, timezone
+from pathlib import Path
+from typing import Any
+
+
+REPO_ROOT = Path(__file__).resolve().parent.parent
+SRC = REPO_ROOT / "src"
+if str(SRC) not in sys.path:
+    sys.path.insert(0, str(SRC))
+
+
+# How far back to look for touched slugs if no marker file exists.
+# Matches ``recent_window_days`` default in ``QualityConfig`` so a
+# freshly-installed system scores every recently-loaded skill on first run.
+_DEFAULT_LOOKBACK_HOURS = 24
+
+# State file: stores the ISO timestamp of the last successful run. Lives
+# under ~/.claude so it persists across repo clones and venv moves.
+_STATE_PATH = Path(os.path.expanduser("~/.claude/skill-quality/.hook-state.json"))
+_EVENTS_PATH = Path(os.path.expanduser("~/.claude/skill-events.jsonl"))
+
+# Upper bound on how many slugs we'll hand to the recompute subcommand in
+# one invocation. Pathological: a user loads 500 distinct skills in one
+# session. We'd rather recompute the top 50 than stall on session-end.
+_MAX_SLUGS_PER_RUN = 50
+
+
+def _load_payload() -> dict[str, Any]:
+    try:
+        raw = sys.stdin.read()
+        if not raw.strip():
+            return {}
+        data = json.loads(raw)
+        return data if isinstance(data, dict) else {}
+    except (json.JSONDecodeError, OSError):
+        return {}
+
+
+def _read_cutoff() -> datetime:
+    """Return the 'since' cutoff for scanning events."""
+    if _STATE_PATH.is_file():
+        try:
+            data = json.loads(_STATE_PATH.read_text(encoding="utf-8"))
+            ts = data.get("last_run_at")
+            if isinstance(ts, str):
+                parsed = datetime.fromisoformat(ts)
+                if parsed.tzinfo is None:
+                    parsed = parsed.replace(tzinfo=timezone.utc)
+                return parsed.astimezone(timezone.utc)
+        except (json.JSONDecodeError, ValueError, OSError):
+            pass
+    return datetime.now(timezone.utc) - timedelta(hours=_DEFAULT_LOOKBACK_HOURS)
+
+
+def _write_state(now: datetime) -> None:
+    try:
+        _STATE_PATH.parent.mkdir(parents=True, exist_ok=True)
+        _STATE_PATH.write_text(
+            json.dumps({"last_run_at": now.isoformat(timespec="seconds")}),
+            encoding="utf-8",
+        )
+    except OSError as exc:
+        print(f"[quality_on_session_end] could not write state: {exc}",
+              file=sys.stderr)
+
+
+def _touched_slugs_since(cutoff: datetime, events_path: Path) -> list[str]:
+    """Return a deduplicated list of skill slugs that appear after ``cutoff``."""
+    if not events_path.is_file():
+        return []
+    seen: dict[str, None] = {}
+    try:
+        with events_path.open(encoding="utf-8") as fh:
+            for raw in fh:
+                line = raw.strip()
+                if not line:
+                    continue
+                try:
+                    obj = json.loads(line)
+                except json.JSONDecodeError:
+                    continue
+                if not isinstance(obj, dict):
+                    continue
+                slug = obj.get("skill")
+                ts_raw = obj.get("timestamp")
+                if not isinstance(slug, str) or not isinstance(ts_raw, str):
+                    continue
+                try:
+                    parsed = datetime.fromisoformat(ts_raw)
+                except ValueError:
+                    continue
+                if parsed.tzinfo is None:
+                    parsed = parsed.replace(tzinfo=timezone.utc)
+                if parsed < cutoff:
+                    continue
+                # Insertion order preserved by dict in Python 3.7+.
+                seen.setdefault(slug, None)
+    except OSError:
+        return []
+    return list(seen.keys())[:_MAX_SLUGS_PER_RUN]
+
+
+def _invoke_recompute(slugs: list[str], session_id: str | None = None) -> int:
+    if not slugs:
+        return 0
+    script = SRC / "skill_quality.py"
+    if not script.is_file():
+        print(f"[quality_on_session_end] missing {script}", file=sys.stderr)
+        return 0
+    # Propagate session_id via environment so the per-slug
+    # skill.score_updated audit rows carry it. Without this the
+    # dashboard's per-session timeline drops the middle event in the
+    # load -> score_updated -> unload triad.
+    env = dict(os.environ)
+    if session_id:
+        env["CTX_SESSION_ID"] = session_id
+    try:
+        result = subprocess.run(
+            [sys.executable, str(script), "recompute",
+             "--slugs", ",".join(slugs)],
+            capture_output=True,
+            text=True,
+            timeout=120,
+            check=False,
+            env=env,
+        )
+        if result.stderr.strip():
+            print(result.stderr.strip(), file=sys.stderr)
+        return result.returncode
+    except (OSError, subprocess.TimeoutExpired) as exc:
+        print(f"[quality_on_session_end] recompute failed: {exc}",
+              file=sys.stderr)
+        return 0
+
+
+def main() -> int:
+    payload = _load_payload()  # consume stdin even if we don't use it
+    now = datetime.now(timezone.utc)
+    cutoff = _read_cutoff()
+    slugs = _touched_slugs_since(cutoff, _EVENTS_PATH)
+
+    # Resolve session_id up-front so it can flow into both the
+    # recompute subprocess (via CTX_SESSION_ID env) AND the session.ended
+    # audit record below. Previously the score_updated rows had no
+    # session_id, breaking the dashboard's per-session timeline.
+    session_id: str | None = None
+    if isinstance(payload, dict):
+        session_id = payload.get("session_id") or payload.get("sessionId")
+    if not session_id:
+        session_id = f"session-{now.strftime('%Y%m%dT%H%M%SZ')}"
+
+    _invoke_recompute(slugs, session_id=session_id)
+    _write_state(now)
+
+    # Unified audit: one line per session boundary + rotate if big.
+    # Guarded with try/except because a hook that fails on audit is
+    # worse than one that runs without telemetry.
+    try:
+        # ctx_audit_log lives in src/. Add src/ to path so this hook
+        # (which runs out of hooks/) can import it regardless of whether
+        # the user is on the editable install or the pip-installed copy.
+        _SRC = Path(__file__).parent.parent / "src"
+        if str(_SRC) not in sys.path:
+            sys.path.insert(0, str(_SRC))
+        from ctx_audit_log import log_session_event, rotate_if_needed
+
+        # session_id resolved above — reuse it so the audit record
+        # agrees with the CTX_SESSION_ID that score_updated rows carry.
+        log_session_event(
+            "session.ended", session_id, actor="hook",
+            meta={"recomputed_slugs": len(slugs), "cutoff": cutoff.isoformat()},
+        )
+        rotate_if_needed()
+    except Exception:  # noqa: BLE001 — audit is advisory
+        pass
+
+    # Always exit 0: hook errors must not stall session shutdown.
+    return 0
+
+
+if __name__ == "__main__":
+    sys.exit(main())

imported-skills/designdotmd/ATTRIBUTION.md

@@ -1,121 +1,121 @@
-# designdotmd.directory — Attribution & Usage
-
-This directory mirrors the design-token catalog from
-[designdotmd.directory](https://designdotmd.directory) — a curated set of
-DESIGN.md files describing visual identities (color, typography, spacing,
-component tokens, rationale) that any coding agent can read.
-
-## Provenance
-
-| Field | Value |
-|---|---|
-| Upstream site | https://designdotmd.directory |
-| List API | https://designdotmd.directory/api/designs |
-| Detail API | https://designdotmd.directory/api/designs/{id} |
-| Fetched on | 2026-04-27 |
-| Total designs | 156 |
-| Curated by | [@bidah](https://twitter.com/bidah) (Twitter creator handle from site meta tags); attributed author per design is **Rofi** |
-| License | **No explicit license posted on the site.** Treat as public reference material with upstream attribution. Review before redistributing. |
-
-## What's in here
-
-- `designs/<slug>.md` — verbatim copy of each upstream design markdown
-  (YAML frontmatter with name + description + design tokens, plus a
-  short prose `## Overview` body).
-- `designs/<slug>.meta.json` — listing metadata (id, name, author, tags,
-  tagline) the upstream API returns for each design but doesn't ship
-  inside the markdown itself.
-- `designs-listing.json` — full upstream listing in one file.
-- `MANIFEST.json` — machine-readable catalog generated by
-  `build_manifest.py` (slug, name, tagline, author, tags, source path,
-  line count). Tags are pulled from the listing API and written into
-  the deployed `SKILL.md` because the upstream `.md` doesn't include
-  them at the YAML level.
-- `build_manifest.py` — manifest regenerator.
-
-## How to integrate
-
-```bash
-python imported-skills/designdotmd/build_manifest.py    # rebuild MANIFEST.json
-python src/import_designdotmd_skills.py --dry-run       # preview
-python src/import_designdotmd_skills.py --install       # deploy as designdotmd-<slug>
-```
-
-The importer:
-- Deploys each design to `~/.claude/skills/designdotmd-<slug>/SKILL.md`.
-- Preserves the upstream YAML frontmatter (colors, typography, spacing,
-  components, rationale) verbatim.
-- **Injects** a `tags: [...]` line right after `description:` so the
-  recommender's tag signal can match design tokens to user queries
-  ("dark editorial typography" → `serif` + `dark` + `editorial` tags).
-- Prepends a one-line attribution comment so the upstream URL is
-  visible inline in every deployed file.
-
-After install, refresh the wiki + graph:
-
-```bash
-python src/catalog_builder.py
-python src/wiki_batch_entities.py --all
-python -m ctx.core.wiki.wiki_graphify
-```
-
-## Why this set
-
-Most agent skills cover *behavior* (TDD, code review, debugging).
-Designs are different: they're **reference data** the agent reads when
-asked to produce a UI. A query like "build me a dashboard with a calm,
-research-paper feel" should surface `ai-labs`, `clinical`, or
-`paper-white` — visual identities, not coding playbooks.
-
-Adding 156 of these to the graph gives a clean second category of
-recommendations alongside the 1,800+ behavior skills, with no overlap
-risk because none of them describe agent actions — they're token sets
-plus rationale.
-
-## Categorisation (selected)
-
-| Category | Designs |
-|---|---|
-| Editorial / serif | heritage, terracotta, sunset-magazine, broadsheet-01, magazine-rouge, atelier-noir, wine-country |
-| Brutalist / bold | brutalist-office, concrete-lemon, streetwear-block, bauhaus |
-| Technical / dark | terminal, obsidian, graphite, zed-dev, devops-graphite, cyber-matrix |
-| Playful / retro | risograph, neon-arcade, y2k-chrome, candy-shop, pixel-quest, arcade-neon-pop |
-| Minimal | swiss-grid, paper-white, gallery-white, clinical, ai-labs, clinic-sage |
-| Finance | defi-chrome, neobank-mint, wealth-noir |
-| Healthcare | clinic-sage, wellness-coral |
-| Music / fashion | record-sleeve, rave-poster, atelier-noir |
-| Sports / gaming HUD | sports-hud, dungeon-crawl, candy-tap |
-
-The full set spans ~30 visual categories crossed with ~10 industry verticals.
-
-## License caveat
-
-I could not find an explicit license on the site (no LICENSE link,
-no terms page, no robots/about endpoint, no licensing metadata in the
-API response). The site explicitly says "Browse, preview, and install
-visual identities any coding agent can read" — that's a clear
-public-distribution intent for *reading and using*, but not a formal
-permission to redistribute under a known license.
-
-This import treats the corpus as **public reference material with
-upstream attribution preserved inline** (the HTML comment header on
-every deployed file links back to designdotmd.directory). If you plan
-to redistribute this catalog (e.g. ship the wiki tarball publicly),
-contact the upstream creator first to confirm permissions.
-
-## Limitations
-
-- **Frontmatter shape** — the designs use rich YAML (colors, typography,
-  spacing, components, rationale) that's idiomatic for design tokens
-  but goes beyond the `name` + `description` + `tags` shape Claude Code's
-  skill loader requires. Extra fields are tolerated and unused; they
-  remain readable when an agent loads the skill.
-- **No body conversion** — the `## Overview` prose body in each upstream
-  file is preserved verbatim. The wiki's micro-skill pipeline does
-  *not* run on these (they're not behavioral skills with implementation
-  steps).
-- **Tag accuracy** — tags come from the upstream listing API and are
-  lowercased. They're a sensible starting point but not exhaustive
-  (e.g. `paper-white` is tagged `minimal serif reading` — accurate but
-  doesn't capture "library", "research", "monograph" connotations).
-  The recommender's slug-token + semantic signals fill in the gap.
+# designdotmd.directory — Attribution & Usage
+
+This directory mirrors the design-token catalog from
+[designdotmd.directory](https://designdotmd.directory) — a curated set of
+DESIGN.md files describing visual identities (color, typography, spacing,
+component tokens, rationale) that any coding agent can read.
+
+## Provenance
+
+| Field | Value |
+|---|---|
+| Upstream site | https://designdotmd.directory |
+| List API | https://designdotmd.directory/api/designs |
+| Detail API | https://designdotmd.directory/api/designs/{id} |
+| Fetched on | 2026-04-27 |
+| Total designs | 156 |
+| Curated by | [@bidah](https://twitter.com/bidah) (Twitter creator handle from site meta tags); attributed author per design is **Rofi** |
+| License | **No explicit license posted on the site.** Treat as public reference material with upstream attribution. Review before redistributing. |
+
+## What's in here
+
+- `designs/<slug>.md` — verbatim copy of each upstream design markdown
+  (YAML frontmatter with name + description + design tokens, plus a
+  short prose `## Overview` body).
+- `designs/<slug>.meta.json` — listing metadata (id, name, author, tags,
+  tagline) the upstream API returns for each design but doesn't ship
+  inside the markdown itself.
+- `designs-listing.json` — full upstream listing in one file.
+- `MANIFEST.json` — machine-readable catalog generated by
+  `build_manifest.py` (slug, name, tagline, author, tags, source path,
+  line count). Tags are pulled from the listing API and written into
+  the deployed `SKILL.md` because the upstream `.md` doesn't include
+  them at the YAML level.
+- `build_manifest.py` — manifest regenerator.
+
+## How to integrate
+
+```bash
+python imported-skills/designdotmd/build_manifest.py    # rebuild MANIFEST.json
+python src/import_designdotmd_skills.py --dry-run       # preview
+python src/import_designdotmd_skills.py --install       # deploy as designdotmd-<slug>
+```
+
+The importer:
+- Deploys each design to `~/.claude/skills/designdotmd-<slug>/SKILL.md`.
+- Preserves the upstream YAML frontmatter (colors, typography, spacing,
+  components, rationale) verbatim.
+- **Injects** a `tags: [...]` line right after `description:` so the
+  recommender's tag signal can match design tokens to user queries
+  ("dark editorial typography" → `serif` + `dark` + `editorial` tags).
+- Prepends a one-line attribution comment so the upstream URL is
+  visible inline in every deployed file.
+
+After install, refresh the wiki + graph:
+
+```bash
+python src/catalog_builder.py
+python src/wiki_batch_entities.py --all
+python -m ctx.core.wiki.wiki_graphify
+```
+
+## Why this set
+
+Most agent skills cover *behavior* (TDD, code review, debugging).
+Designs are different: they're **reference data** the agent reads when
+asked to produce a UI. A query like "build me a dashboard with a calm,
+research-paper feel" should surface `ai-labs`, `clinical`, or
+`paper-white` — visual identities, not coding playbooks.
+
+Adding 156 of these to the graph gives a clean second category of
+recommendations alongside the 1,800+ behavior skills, with no overlap
+risk because none of them describe agent actions — they're token sets
+plus rationale.
+
+## Categorisation (selected)
+
+| Category | Designs |
+|---|---|
+| Editorial / serif | heritage, terracotta, sunset-magazine, broadsheet-01, magazine-rouge, atelier-noir, wine-country |
+| Brutalist / bold | brutalist-office, concrete-lemon, streetwear-block, bauhaus |
+| Technical / dark | terminal, obsidian, graphite, zed-dev, devops-graphite, cyber-matrix |
+| Playful / retro | risograph, neon-arcade, y2k-chrome, candy-shop, pixel-quest, arcade-neon-pop |
+| Minimal | swiss-grid, paper-white, gallery-white, clinical, ai-labs, clinic-sage |
+| Finance | defi-chrome, neobank-mint, wealth-noir |
+| Healthcare | clinic-sage, wellness-coral |
+| Music / fashion | record-sleeve, rave-poster, atelier-noir |
+| Sports / gaming HUD | sports-hud, dungeon-crawl, candy-tap |
+
+The full set spans ~30 visual categories crossed with ~10 industry verticals.
+
+## License caveat
+
+I could not find an explicit license on the site (no LICENSE link,
+no terms page, no robots/about endpoint, no licensing metadata in the
+API response). The site explicitly says "Browse, preview, and install
+visual identities any coding agent can read" — that's a clear
+public-distribution intent for *reading and using*, but not a formal
+permission to redistribute under a known license.
+
+This import treats the corpus as **public reference material with
+upstream attribution preserved inline** (the HTML comment header on
+every deployed file links back to designdotmd.directory). If you plan
+to redistribute this catalog (e.g. ship the wiki tarball publicly),
+contact the upstream creator first to confirm permissions.
+
+## Limitations
+
+- **Frontmatter shape** — the designs use rich YAML (colors, typography,
+  spacing, components, rationale) that's idiomatic for design tokens
+  but goes beyond the `name` + `description` + `tags` shape Claude Code's
+  skill loader requires. Extra fields are tolerated and unused; they
+  remain readable when an agent loads the skill.
+- **No body conversion** — the `## Overview` prose body in each upstream
+  file is preserved verbatim. The wiki's micro-skill pipeline does
+  *not* run on these (they're not behavioral skills with implementation
+  steps).
+- **Tag accuracy** — tags come from the upstream listing API and are
+  lowercased. They're a sensible starting point but not exhaustive
+  (e.g. `paper-white` is tagged `minimal serif reading` — accurate but
+  doesn't capture "library", "research", "monograph" connotations).
+  The recommender's slug-token + semantic signals fill in the gap.

imported-skills/designdotmd/build_manifest.py

@@ -1,60 +1,60 @@
-#!/usr/bin/env python3
-"""Generate MANIFEST.json for the imported designdotmd.directory set.
-
-Each entry pairs a markdown file under ``designs/<id>.md`` (fetched
-directly from the upstream API) with the listing-API metadata
-(``id``, ``name``, ``author``, ``tags``, ``tagline``).
-"""
-
-from __future__ import annotations
-
-import datetime
-import json
-from pathlib import Path
-
-ROOT = Path(__file__).parent
-DESIGNS_DIR = ROOT / "designs"
-LISTING_PATH = ROOT / "designs-listing.json"
-UPSTREAM = "https://designdotmd.directory"
-UPSTREAM_API = f"{UPSTREAM}/api/designs"
-
-
-def build() -> dict:
-    listing = json.loads(LISTING_PATH.read_text(encoding="utf-8"))
-    entries: list[dict] = []
-    for d in listing:
-        slug = d["id"]
-        md_path = DESIGNS_DIR / f"{slug}.md"
-        if not md_path.is_file():
-            continue
-        text = md_path.read_text(encoding="utf-8")
-        entries.append({
-            "name": d.get("name") or slug,
-            "tagline": d.get("tagline", "").strip(),
-            "author": d.get("author", "").strip(),
-            "tags": [str(t).strip().lower() for t in d.get("tags", []) if str(t).strip()],
-            "slug": slug,
-            "source_path": (md_path.relative_to(ROOT)).as_posix(),
-            "lines": len(text.splitlines()),
-        })
-    entries.sort(key=lambda e: e["slug"])
-    return {
-        "upstream": UPSTREAM,
-        "upstream_api": UPSTREAM_API,
-        "fetched_on": datetime.date.today().isoformat(),
-        "license": "unknown (see ATTRIBUTION.md)",
-        "namespace": "designdotmd",
-        "total": len(entries),
-        "entries": entries,
-    }
-
-
-def main() -> None:
-    manifest = build()
-    out = ROOT / "MANIFEST.json"
-    out.write_text(json.dumps(manifest, indent=2) + "\n", encoding="utf-8")
-    print(f"Manifest written: {manifest['total']} designs")
-
-
-if __name__ == "__main__":
-    main()
+#!/usr/bin/env python3
+"""Generate MANIFEST.json for the imported designdotmd.directory set.
+
+Each entry pairs a markdown file under ``designs/<id>.md`` (fetched
+directly from the upstream API) with the listing-API metadata
+(``id``, ``name``, ``author``, ``tags``, ``tagline``).
+"""
+
+from __future__ import annotations
+
+import datetime
+import json
+from pathlib import Path
+
+ROOT = Path(__file__).parent
+DESIGNS_DIR = ROOT / "designs"
+LISTING_PATH = ROOT / "designs-listing.json"
+UPSTREAM = "https://designdotmd.directory"
+UPSTREAM_API = f"{UPSTREAM}/api/designs"
+
+
+def build() -> dict:
+    listing = json.loads(LISTING_PATH.read_text(encoding="utf-8"))
+    entries: list[dict] = []
+    for d in listing:
+        slug = d["id"]
+        md_path = DESIGNS_DIR / f"{slug}.md"
+        if not md_path.is_file():
+            continue
+        text = md_path.read_text(encoding="utf-8")
+        entries.append({
+            "name": d.get("name") or slug,
+            "tagline": d.get("tagline", "").strip(),
+            "author": d.get("author", "").strip(),
+            "tags": [str(t).strip().lower() for t in d.get("tags", []) if str(t).strip()],
+            "slug": slug,
+            "source_path": (md_path.relative_to(ROOT)).as_posix(),
+            "lines": len(text.splitlines()),
+        })
+    entries.sort(key=lambda e: e["slug"])
+    return {
+        "upstream": UPSTREAM,
+        "upstream_api": UPSTREAM_API,
+        "fetched_on": datetime.date.today().isoformat(),
+        "license": "unknown (see ATTRIBUTION.md)",
+        "namespace": "designdotmd",
+        "total": len(entries),
+        "entries": entries,
+    }
+
+
+def main() -> None:
+    manifest = build()
+    out = ROOT / "MANIFEST.json"
+    out.write_text(json.dumps(manifest, indent=2) + "\n", encoding="utf-8")
+    print(f"Manifest written: {manifest['total']} designs")
+
+
+if __name__ == "__main__":
+    main()

imported-skills/mattpocock/ATTRIBUTION.md

@@ -1,103 +1,103 @@
-# Mattpocock Skills Import — Attribution & Usage
-
-This directory mirrors Matt Pocock's personal `.claude/` skill set — opinionated
-agent skills covering TDD, domain modelling, codebase architecture review,
-github triage, and meta-workflows for working with Claude Code.
-
-## Provenance
-
-| Field | Value |
-|---|---|
-| Upstream repo | https://github.com/mattpocock/skills |
-| Revision | `90ea8eec03d4ae8f43427aaf6fe4722653561a42` |
-| Revision date | 2026-04-26 |
-| Upstream license | MIT (see `LICENSE`) |
-| Imported on | 2026-04-27 |
-| Skill count | 21 |
-
-## What's in here
-
-Each top-level directory is one skill, with `SKILL.md` as the entry point and
-optional supporting `.md` / `.sh` files alongside it (e.g. `tdd/deep-modules.md`,
-`domain-model/ADR-FORMAT.md`, `git-guardrails-claude-code/scripts/block-dangerous-git.sh`).
-
-| Skill | Purpose |
-|---|---|
-| `tdd` | Red-green-refactor TDD discipline (with deep-modules / mocking / refactoring sidecars) |
-| `qa` | Interactive QA conversation that files GitHub issues using project domain language |
-| `caveman` | Ultra-compressed communication mode (~75% token reduction) |
-| `domain-model` | Stress-test plans against existing domain model + ADRs (with `ADR-FORMAT.md` + `CONTEXT-FORMAT.md`) |
-| `ubiquitous-language` | DDD-style shared vocabulary discipline |
-| `design-an-interface` | Generate multiple radically different API designs via parallel sub-agents |
-| `improve-codebase-architecture` | Architecture review playbook (with `DEEPENING.md`, `INTERFACE-DESIGN.md`, `LANGUAGE.md` sidecars) |
-| `github-triage` | Triage GitHub issues with agent-brief + out-of-scope guardrails |
-| `triage-issue` | Single-issue triage workflow |
-| `to-issues` | Convert plans/notes into well-formed issues |
-| `to-prd` | Convert sketches into a product requirements document |
-| `request-refactor-plan` | Plan a refactor before touching code |
-| `migrate-to-shoehorn` | Migration playbook to the `shoehorn` library |
-| `setup-pre-commit` | Pre-commit hook bootstrap |
-| `scaffold-exercises` | Scaffold programming exercises |
-| `git-guardrails-claude-code` | Block dangerous git ops in Claude Code (with hook script) |
-| `obsidian-vault` | Obsidian vault management workflow |
-| `edit-article` | Editing pass for article drafts |
-| `grill-me` | Adversarial questioning to stress-test a plan |
-| `write-a-skill` | Meta: how to write a skill |
-| `zoom-out` | Force a higher-altitude review of current work |
-
-## License compliance
-
-Per the MIT license:
-- Upstream `LICENSE` text is preserved alongside the imported files.
-- Files are imported verbatim. The deployed copies (under `~/.claude/skills/`) prepend
-  an HTML-comment attribution header before the original `---` frontmatter so
-  provenance is visible inline; the original content below is unmodified.
-
-## How to integrate
-
-Skills are staged in this directory and **not** deployed to `~/.claude/skills/`
-until you run the importer:
-
-```bash
-python imported-skills/mattpocock/build_manifest.py    # rebuild MANIFEST.json
-python src/import_mattpocock_skills.py --dry-run       # preview
-python src/import_mattpocock_skills.py --install       # deploy as mattpocock-<slug>
-```
-
-Each skill lands as `~/.claude/skills/mattpocock-<slug>/` with all its support
-files copied alongside `SKILL.md`. Directory namespacing prevents collisions
-with same-named skills already in the wiki (e.g. existing `tdd-orchestrator`
-agent + `python-testing` skill coexist with `mattpocock-tdd`).
-
-After install, refresh the wiki + graph:
-
-```bash
-python src/catalog_builder.py
-python src/wiki_batch_entities.py --all
-python -m ctx.core.wiki.wiki_graphify
-```
-
-## Why this set
-
-mattpocock's skills are short, opinionated, and prose-style — closer to
-checklists or playbooks than reference manuals. They complement the larger
-catalogue (which leans dense + comprehensive) by providing crisp,
-single-purpose workflows for everyday engineering tasks.
-
-The `tdd`, `domain-model`, `ubiquitous-language`, and
-`improve-codebase-architecture` set in particular form a cohesive DDD-leaning
-toolkit. The `caveman`, `grill-me`, `zoom-out` set are useful behavioural
-modes for steering a Claude Code session.
-
-## Limitations
-
-- **Frontmatter format** — uses YAML frontmatter with `name:` + `description:`;
-  some entries use `disable-model-invocation: true` (Claude Code reads this).
-  The importer preserves these fields as-is.
-- **Tool assumptions** — `git-guardrails-claude-code` ships a `block-dangerous-git.sh`
-  hook that expects POSIX `bash` on PATH; on Windows it requires Git-Bash or
-  WSL. The hook is copied but not wired into your Claude Code settings — wire
-  manually if you want it active.
-- **Opinionated** — these reflect one engineer's workflow. Treat them as
-  starting points; nothing here is universally correct (e.g. `grill-me`'s
-  adversarial style isn't right for every team).
+# Mattpocock Skills Import — Attribution & Usage
+
+This directory mirrors Matt Pocock's personal `.claude/` skill set — opinionated
+agent skills covering TDD, domain modelling, codebase architecture review,
+github triage, and meta-workflows for working with Claude Code.
+
+## Provenance
+
+| Field | Value |
+|---|---|
+| Upstream repo | https://github.com/mattpocock/skills |
+| Revision | `90ea8eec03d4ae8f43427aaf6fe4722653561a42` |
+| Revision date | 2026-04-26 |
+| Upstream license | MIT (see `LICENSE`) |
+| Imported on | 2026-04-27 |
+| Skill count | 21 |
+
+## What's in here
+
+Each top-level directory is one skill, with `SKILL.md` as the entry point and
+optional supporting `.md` / `.sh` files alongside it (e.g. `tdd/deep-modules.md`,
+`domain-model/ADR-FORMAT.md`, `git-guardrails-claude-code/scripts/block-dangerous-git.sh`).
+
+| Skill | Purpose |
+|---|---|
+| `tdd` | Red-green-refactor TDD discipline (with deep-modules / mocking / refactoring sidecars) |
+| `qa` | Interactive QA conversation that files GitHub issues using project domain language |
+| `caveman` | Ultra-compressed communication mode (~75% token reduction) |
+| `domain-model` | Stress-test plans against existing domain model + ADRs (with `ADR-FORMAT.md` + `CONTEXT-FORMAT.md`) |
+| `ubiquitous-language` | DDD-style shared vocabulary discipline |
+| `design-an-interface` | Generate multiple radically different API designs via parallel sub-agents |
+| `improve-codebase-architecture` | Architecture review playbook (with `DEEPENING.md`, `INTERFACE-DESIGN.md`, `LANGUAGE.md` sidecars) |
+| `github-triage` | Triage GitHub issues with agent-brief + out-of-scope guardrails |
+| `triage-issue` | Single-issue triage workflow |
+| `to-issues` | Convert plans/notes into well-formed issues |
+| `to-prd` | Convert sketches into a product requirements document |
+| `request-refactor-plan` | Plan a refactor before touching code |
+| `migrate-to-shoehorn` | Migration playbook to the `shoehorn` library |
+| `setup-pre-commit` | Pre-commit hook bootstrap |
+| `scaffold-exercises` | Scaffold programming exercises |
+| `git-guardrails-claude-code` | Block dangerous git ops in Claude Code (with hook script) |
+| `obsidian-vault` | Obsidian vault management workflow |
+| `edit-article` | Editing pass for article drafts |
+| `grill-me` | Adversarial questioning to stress-test a plan |
+| `write-a-skill` | Meta: how to write a skill |
+| `zoom-out` | Force a higher-altitude review of current work |
+
+## License compliance
+
+Per the MIT license:
+- Upstream `LICENSE` text is preserved alongside the imported files.
+- Files are imported verbatim. The deployed copies (under `~/.claude/skills/`) prepend
+  an HTML-comment attribution header before the original `---` frontmatter so
+  provenance is visible inline; the original content below is unmodified.
+
+## How to integrate
+
+Skills are staged in this directory and **not** deployed to `~/.claude/skills/`
+until you run the importer:
+
+```bash
+python imported-skills/mattpocock/build_manifest.py    # rebuild MANIFEST.json
+python src/import_mattpocock_skills.py --dry-run       # preview
+python src/import_mattpocock_skills.py --install       # deploy as mattpocock-<slug>
+```
+
+Each skill lands as `~/.claude/skills/mattpocock-<slug>/` with all its support
+files copied alongside `SKILL.md`. Directory namespacing prevents collisions
+with same-named skills already in the wiki (e.g. existing `tdd-orchestrator`
+agent + `python-testing` skill coexist with `mattpocock-tdd`).
+
+After install, refresh the wiki + graph:
+
+```bash
+python src/catalog_builder.py
+python src/wiki_batch_entities.py --all
+python -m ctx.core.wiki.wiki_graphify
+```
+
+## Why this set
+
+mattpocock's skills are short, opinionated, and prose-style — closer to
+checklists or playbooks than reference manuals. They complement the larger
+catalogue (which leans dense + comprehensive) by providing crisp,
+single-purpose workflows for everyday engineering tasks.
+
+The `tdd`, `domain-model`, `ubiquitous-language`, and
+`improve-codebase-architecture` set in particular form a cohesive DDD-leaning
+toolkit. The `caveman`, `grill-me`, `zoom-out` set are useful behavioural
+modes for steering a Claude Code session.
+
+## Limitations
+
+- **Frontmatter format** — uses YAML frontmatter with `name:` + `description:`;
+  some entries use `disable-model-invocation: true` (Claude Code reads this).
+  The importer preserves these fields as-is.
+- **Tool assumptions** — `git-guardrails-claude-code` ships a `block-dangerous-git.sh`
+  hook that expects POSIX `bash` on PATH; on Windows it requires Git-Bash or
+  WSL. The hook is copied but not wired into your Claude Code settings — wire
+  manually if you want it active.
+- **Opinionated** — these reflect one engineer's workflow. Treat them as
+  starting points; nothing here is universally correct (e.g. `grill-me`'s
+  adversarial style isn't right for every team).

imported-skills/mattpocock/build_manifest.py

@@ -1,98 +1,98 @@
-#!/usr/bin/env python3
-"""Generate MANIFEST.json for the imported mattpocock/skills set.
-
-Each top-level directory under imported-skills/mattpocock/ is one skill.
-SKILL.md is the entry point; sibling .md/.sh files travel with the skill
-and are deployed into the same target directory.
-"""
-
-from __future__ import annotations
-
-import json
-import re
-import subprocess
-from pathlib import Path
-
-ROOT = Path(__file__).parent
-FRONTMATTER_RE = re.compile(r"^---\s*\n(.*?)\n---\s*\n", re.DOTALL)
-UPSTREAM = "https://github.com/mattpocock/skills"
-LICENSE = "MIT"
-
-
-def parse_frontmatter(text: str) -> dict[str, str]:
-    m = FRONTMATTER_RE.match(text)
-    if not m:
-        return {}
-    out: dict[str, str] = {}
-    pending_key: str | None = None
-    for raw in m.group(1).splitlines():
-        if pending_key and raw.startswith((" ", "\t")):
-            out[pending_key] = (out[pending_key] + " " + raw.strip()).strip()
-            continue
-        pending_key = None
-        if ":" not in raw:
-            continue
-        k, _, v = raw.partition(":")
-        v = v.strip()
-        if v in {"", ">", "|"}:
-            pending_key = k.strip()
-            out[pending_key] = ""
-        else:
-            out[k.strip()] = v.strip('"').strip("'")
-    return out
-
-
-def support_files(skill_dir: Path) -> list[str]:
-    out: list[str] = []
-    for p in sorted(skill_dir.rglob("*")):
-        if not p.is_file() or p.name == "SKILL.md":
-            continue
-        out.append(p.relative_to(skill_dir).as_posix())
-    return out
-
-
-def upstream_revision() -> str:
-    try:
-        return subprocess.check_output(
-            ["git", "-C", str(ROOT), "rev-parse", "HEAD"],
-            text=True,
-        ).strip()
-    except Exception:
-        return "unknown"
-
-
-def build() -> dict:
-    entries: list[dict] = []
-    for skill_dir in sorted(p for p in ROOT.iterdir() if p.is_dir() and (p / "SKILL.md").exists()):
-        skill_md = skill_dir / "SKILL.md"
-        text = skill_md.read_text(encoding="utf-8")
-        fm = parse_frontmatter(text)
-        slug = skill_dir.name
-        entries.append({
-            "name": fm.get("name", slug),
-            "description": fm.get("description", "").strip(),
-            "slug": slug,
-            "source_path": (skill_dir.relative_to(ROOT) / "SKILL.md").as_posix(),
-            "support_files": support_files(skill_dir),
-            "lines": len(text.splitlines()),
-        })
-    rev = upstream_revision()
-    return {
-        "upstream": UPSTREAM,
-        "upstream_revision": rev,
-        "license": LICENSE,
-        "namespace": "mattpocock",
-        "total": len(entries),
-        "entries": entries,
-    }
-
-
-def main() -> None:
-    manifest = build()
-    out = ROOT / "MANIFEST.json"
-    out.write_text(json.dumps(manifest, indent=2) + "\n", encoding="utf-8")
-    print(f"Manifest written: {manifest['total']} skills @ {manifest['upstream_revision'][:12]}")
-
-
-if __name__ == "__main__":
-    main()
+#!/usr/bin/env python3
+"""Generate MANIFEST.json for the imported mattpocock/skills set.
+
+Each top-level directory under imported-skills/mattpocock/ is one skill.
+SKILL.md is the entry point; sibling .md/.sh files travel with the skill
+and are deployed into the same target directory.
+"""
+
+from __future__ import annotations
+
+import json
+import re
+import subprocess
+from pathlib import Path
+
+ROOT = Path(__file__).parent
+FRONTMATTER_RE = re.compile(r"^---\s*\n(.*?)\n---\s*\n", re.DOTALL)
+UPSTREAM = "https://github.com/mattpocock/skills"
+LICENSE = "MIT"
+
+
+def parse_frontmatter(text: str) -> dict[str, str]:
+    m = FRONTMATTER_RE.match(text)
+    if not m:
+        return {}
+    out: dict[str, str] = {}
+    pending_key: str | None = None
+    for raw in m.group(1).splitlines():
+        if pending_key and raw.startswith((" ", "\t")):
+            out[pending_key] = (out[pending_key] + " " + raw.strip()).strip()
+            continue
+        pending_key = None
+        if ":" not in raw:
+            continue
+        k, _, v = raw.partition(":")
+        v = v.strip()
+        if v in {"", ">", "|"}:
+            pending_key = k.strip()
+            out[pending_key] = ""
+        else:
+            out[k.strip()] = v.strip('"').strip("'")
+    return out
+
+
+def support_files(skill_dir: Path) -> list[str]:
+    out: list[str] = []
+    for p in sorted(skill_dir.rglob("*")):
+        if not p.is_file() or p.name == "SKILL.md":
+            continue
+        out.append(p.relative_to(skill_dir).as_posix())
+    return out
+
+
+def upstream_revision() -> str:
+    try:
+        return subprocess.check_output(
+            ["git", "-C", str(ROOT), "rev-parse", "HEAD"],
+            text=True,
+        ).strip()
+    except Exception:
+        return "unknown"
+
+
+def build() -> dict:
+    entries: list[dict] = []
+    for skill_dir in sorted(p for p in ROOT.iterdir() if p.is_dir() and (p / "SKILL.md").exists()):
+        skill_md = skill_dir / "SKILL.md"
+        text = skill_md.read_text(encoding="utf-8")
+        fm = parse_frontmatter(text)
+        slug = skill_dir.name
+        entries.append({
+            "name": fm.get("name", slug),
+            "description": fm.get("description", "").strip(),
+            "slug": slug,
+            "source_path": (skill_dir.relative_to(ROOT) / "SKILL.md").as_posix(),
+            "support_files": support_files(skill_dir),
+            "lines": len(text.splitlines()),
+        })
+    rev = upstream_revision()
+    return {
+        "upstream": UPSTREAM,
+        "upstream_revision": rev,
+        "license": LICENSE,
+        "namespace": "mattpocock",
+        "total": len(entries),
+        "entries": entries,
+    }
+
+
+def main() -> None:
+    manifest = build()
+    out = ROOT / "MANIFEST.json"
+    out.write_text(json.dumps(manifest, indent=2) + "\n", encoding="utf-8")
+    print(f"Manifest written: {manifest['total']} skills @ {manifest['upstream_revision'][:12]}")
+
+
+if __name__ == "__main__":
+    main()