chore: post-merge sync — plugins, audits, docs, cross-platform indexes

New skills integrated:
- engineering/behuman, code-tour, demo-video, data-quality-auditor

Plugins & marketplace:
- Add plugin.json for code-tour, demo-video, data-quality-auditor
- Add all 3 to marketplace.json (31 total plugins)
- Update marketplace counts to 248 skills, 332 tools, 460 refs

Skill fixes:
- Move data-quality-auditor from data-analysis/ to engineering/
- Fix cross-refs: code-tour, demo-video, data-quality-auditor
- Add evals.json for code-tour (5 scenarios) and demo-video (4 scenarios)
- demo-video: add output artifacts, prereqs check, references extraction
- code-tour: add default persona, parallel discovery, trivial repo guidance
- Fix Python 3.9 compat (from __future__ import annotations)

product-analytics audit fixes:
- Expand SKILL.md from 82 to 147 lines (anti-patterns, cross-refs, examples)
- Add --format json to all metrics_calculator.py subcommands
- Add error handling (FileNotFoundError, KeyError)

Docs & indexes:
- Update CLAUDE.md, README.md, docs/index.md, docs/getting-started.md counts
- Sync Codex (192 skills) and Gemini (280 items) indexes
- Regenerate MkDocs pages (279 pages, 311 HTML)
- Add 3 new nav entries to mkdocs.yml
- Update mkdocs.yml site_description

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

engineering/code-tour/.claude-plugin/plugin.json

@@ -0,0 +1,13 @@
+{
+  "name": "code-tour",
+  "description": "Create CodeTour .tour files — persona-targeted, step-by-step walkthroughs that link to real files and line numbers. Supports 10 developer personas (vibecoder, new joiner, architect, security reviewer, etc.), all CodeTour step types, and SMIG description formula.",
+  "version": "2.2.0",
+  "author": {
+    "name": "Alireza Rezvani",
+    "url": "https://alirezarezvani.com"
+  },
+  "homepage": "https://github.com/alirezarezvani/claude-skills/tree/main/engineering/code-tour",
+  "repository": "https://github.com/alirezarezvani/claude-skills",
+  "license": "MIT",
+  "skills": "./"
+}

engineering/code-tour/SKILL.md

@@ -23,10 +23,11 @@ A great tour is a **narrative** — a story told to a specific person about what
 ### 1. Discover the repo
 
 Before asking anything, explore the codebase:
-- List root directory, read README, check config files
-- Identify language(s), framework(s), project purpose
-- Map folder structure 1-2 levels deep
-- Find entry points — every path in the tour must be real
+
+In parallel: list root directory, read README, check config files.
+Then: identify language(s), framework(s), project purpose. Map folder structure 1-2 levels deep. Find entry points — every path in the tour must be real.
+
+If the repo has fewer than 5 source files, create a quick-depth tour regardless of persona — there's not enough to warrant a deep one.
 
 ### 2. Infer the intent
 
@@ -40,6 +41,9 @@ One message should be enough. Infer persona, depth, and focus silently.
 | "quick tour" / "vibe check" | vibecoder | quick |
 | "architecture" | architect | deep |
 | "security" / "auth review" | security-reviewer | standard |
+| (no qualifier) | new-joiner | standard |
+
+When intent is ambiguous, default to **new-joiner** persona at **standard** depth — it's the most generally useful.
 
 ### 3. Read actual files
 
@@ -54,7 +58,7 @@ Save to `.tours/<persona>-<focus>.tour`.
   "$schema": "https://aka.ms/codetour-schema",
   "title": "Descriptive Title — Persona / Goal",
   "description": "Who this is for and what they'll understand after.",
-  "ref": "main",
+  "ref": "<current-branch-or-commit>",
   "steps": []
 }
 ```
@@ -94,7 +98,7 @@ Save to `.tours/<persona>-<focus>.tour`.
 - [ ] At most 2 content-only steps
 - [ ] `nextTour` matches another tour's `title` exactly if set
 
-## The 20 Personas
+## Personas
 
 | Persona | Goal | Must cover |
 |---------|------|------------|
@@ -131,6 +135,6 @@ Save to `.tours/<persona>-<focus>.tour`.
 ## Cross-References
 
 - Related: `engineering/codebase-onboarding` — for broader onboarding beyond tours
-- Related: `engineering/code-review-automation` — for automated PR review workflows
-- Full skill with validation scripts and schema: [code-tour repo](https://github.com/vaddisrinivas/code-tour)
+- Related: `engineering/pr-review-expert` — for automated PR review workflows
+- CodeTour extension: [microsoft/codetour](https://github.com/microsoft/codetour)
 - Real-world tours: [coder/code-server](https://github.com/coder/code-server/blob/main/.tours/contributing.tour)

engineering/code-tour/evals.json

@@ -0,0 +1,32 @@
+[
+  {
+    "id": 1,
+    "prompt": "I just hired a junior dev who starts Monday. Can you create an onboarding tour for this repo so they can get oriented on their own?",
+    "expected_output": "Agent infers new-joiner persona, standard depth (9-13 steps). Produces .tours/new-joiner-onboarding.tour with verified paths/lines, SMIG descriptions, narrative arc starting with orientation directory step.",
+    "scenario_type": "happy_path"
+  },
+  {
+    "id": 2,
+    "prompt": "Give me a quick vibe check tour of this codebase — I just cloned it and want to understand the shape before diving in.",
+    "expected_output": "Agent infers vibecoder persona, quick depth (5-8 steps). Tour hits entry point and main modules only. File saved to .tours/vibecoder-overview.tour.",
+    "scenario_type": "happy_path"
+  },
+  {
+    "id": 3,
+    "prompt": "We had an outage last night because the payment webhook handler silently swallowed errors. Can you build an RCA tour tracing how webhooks flow through the system?",
+    "expected_output": "Agent infers rca-investigator persona, standard depth. Tour follows causality chain from webhook entry point through handler to error handling. Steps anchored to specific lines showing the fault path.",
+    "scenario_type": "happy_path"
+  },
+  {
+    "id": 4,
+    "prompt": "Create a tour for this repo.",
+    "expected_output": "Agent defaults to new-joiner persona at standard depth without asking clarifying questions. Produces a general-purpose onboarding tour.",
+    "scenario_type": "edge_case"
+  },
+  {
+    "id": 5,
+    "prompt": "Make an onboarding tour for this repo, but I want it to also cover the deployment pipeline and our monitoring setup in Grafana.",
+    "expected_output": "Agent includes deployment pipeline files as normal file+line steps. Uses URI step type for Grafana link if user provides URL, or skips with explanation. Does not hallucinate files.",
+    "scenario_type": "edge_case"
+  }
+]