chore: import upstream snapshot with attribution

.claude/claudex/log

@@ -0,0 +1,10 @@
+[2026-05-02T19:56:41Z] Hook fired. Input bytes: 1694
+[2026-05-02T19:56:41Z] ERR trap at line 67; failing open
+[2026-05-02T20:01:48Z] Hook fired. Input bytes: 1323
+[2026-05-02T20:01:48Z] ERR trap at line 67; failing open
+[2026-05-02T20:14:49Z] Hook fired. Input bytes: 1638
+[2026-05-02T20:14:49Z] ERR trap at line 67; failing open
+[2026-05-02T20:33:10Z] Hook fired. Input bytes: 11247
+[2026-05-02T20:33:10Z] ERR trap at line 67; failing open
+[2026-05-02T20:34:42Z] Hook fired. Input bytes: 1846
+[2026-05-02T20:34:42Z] ERR trap at line 67; failing open

.claude/commands/README.md

@@ -0,0 +1,351 @@
+# Claude Skills Slash Commands
+
+**Git workflow and quality assurance commands for the claude-skills repository.**
+
+---
+
+## 🎯 Essential Commands
+
+### Git Workflow
+
+```
+/git:cm         → Stage and commit (no push)
+/git:cp         → Stage, commit, and push
+/git:pr         → Create pull request
+/git:clean      → Delete merged branches (local + remote)
+```
+
+### Quality Gates
+
+```
+/review         → Run local quality checks
+/security-scan  → Run security validation
+/update-docs    → Post-creation sync (CLI platforms, marketplace, docs, GitHub Pages)
+```
+
+---
+
+## 📋 Git Commands
+
+### /git:cm - Commit (No Push)
+
+**Purpose**: Stage changes and create a conventional commit without pushing
+
+**Usage**:
+```
+/git:cm
+```
+
+**What it does**:
+1. Shows `git status --short`
+2. Reviews each file diff for secrets
+3. Stages files intentionally
+4. Generates conventional commit message
+5. Creates commit (no push)
+
+**When to use**: When you want to commit locally before pushing
+
+---
+
+### /git:cp - Commit and Push
+
+**Purpose**: Complete git workflow with quality checks
+
+**Usage**:
+```
+/git:cp
+```
+
+**What it does**:
+1. Runs `/review` for quality checks
+2. Stages changes
+3. Creates conventional commit
+4. Pushes to origin
+5. Triggers CI workflows
+
+**When to use**: When ready to publish changes
+
+---
+
+### /git:pr - Create Pull Request
+
+**Purpose**: Create a PR from current branch
+
+**Usage**:
+```
+/git:pr              # PR to main
+/git:pr dev          # PR to dev branch
+```
+
+**What it does**:
+1. Verifies quality checks passed
+2. Creates PR using template
+3. Adds appropriate labels
+4. Shares PR link
+
+**When to use**: After pushing changes and ready for review
+
+---
+
+## 🔒 Quality Commands
+
+### /review - Local Quality Gate
+
+**Purpose**: Run all quality checks before pushing
+
+**Usage**:
+```
+/review
+```
+
+**What it checks**:
+- ✅ YAML linting (workflows)
+- ✅ GitHub workflow schema validation
+- ✅ Python syntax (all skill directories)
+- ✅ Markdown link validation
+- ✅ Dependency security audit (optional)
+
+**When to use**: Before committing/pushing changes
+
+---
+
+### /security-scan - Security Validation
+
+**Purpose**: Scan for security issues
+
+**Usage**:
+```
+/security-scan
+```
+
+**What it checks**:
+- 🔍 Gitleaks (committed secrets detection)
+- 🔍 Safety (Python dependency vulnerabilities)
+
+**When to use**: Before pushing, especially with new dependencies
+
+---
+
+## 🔄 Complete Workflow
+
+### Standard Feature Development
+
+```
+# 1. Make changes to skills
+[Edit files in marketing-skill/, product-team/, etc.]
+
+# 2. Run quality checks
+/review
+
+# 3. Run security scan
+/security-scan
+
+# 4. Commit and push
+/git:cp
+
+# 5. Create pull request
+/git:pr
+
+# 6. Wait for:
+   - ✅ Claude Code Review comment
+   - ✅ CI Quality Gate passing
+   - ✅ Human approval
+
+# 7. Merge PR
+   - Issue auto-closes (if linked)
+   - Project board updates
+```
+
+---
+
+## 💡 Quick Reference
+
+| Command | Stage | Commit | Push | Quality Check | Create PR |
+|---------|-------|--------|------|---------------|-----------|
+| **/git:cm** | ✅ | ✅ | ❌ | ❌ | ❌ |
+| **/git:cp** | ✅ | ✅ | ✅ | ✅ | ❌ |
+| **/git:pr** | ❌ | ❌ | ❌ | Verify | ✅ |
+| **/review** | ❌ | ❌ | ❌ | ✅ | ❌ |
+| **/security-scan** | ❌ | ❌ | ❌ | ✅ | ❌ |
+
+---
+
+## 📊 Commit Message Format
+
+All commits follow **Conventional Commits**:
+
+```
+<type>(<scope>): <subject>
+
+## Context
+- Why this change was needed
+- What problem it solves
+
+## Testing
+- [ ] All Python scripts tested
+- [ ] Skills validated with Claude
+- [ ] /review passed
+- [ ] /security-scan passed
+
+## Reviewers
+- [ ] @username
+```
+
+**Types**: `feat`, `fix`, `docs`, `style`, `refactor`, `perf`, `test`, `build`, `ci`, `chore`, `revert`
+
+**Scopes**: `marketing-skill`, `product-team`, `c-level-advisor`, `engineering-team`, `ra-qm-team`, `workflows`, `docs`, `ci`
+
+**Examples**:
+```
+feat(marketing-skill): add LinkedIn content framework
+fix(product-team): correct RICE prioritization calculation
+docs(README): update skill installation instructions
+ci(workflows): add auto-close issues on PR merge
+```
+
+---
+
+## 🎯 Use Cases
+
+### Quick Fix
+
+```
+# Fix typo in skill
+[Edit file]
+/review              # Quick check
+/git:cp              # Commit + push
+```
+
+### New Skill Addition
+
+```
+# Create new skill
+[Create skill directory and files]
+/review              # Validate structure
+/security-scan       # Check for issues
+/git:cm              # Commit locally
+[Test skill activation]
+/git:cp              # Push when ready
+/git:pr              # Create PR for review
+```
+
+### Major Feature with Multiple Skills
+
+```
+# Work on branch
+git checkout -b feature/enterprise-skills
+
+# Add multiple skills
+[Create skill 1]
+/git:cm
+
+[Create skill 2]
+/git:cm
+
+[Create skill 3]
+/git:cm
+
+# Final quality check
+/review
+/security-scan
+
+# Push and create PR
+git push origin feature/enterprise-skills
+/git:pr
+
+# Or use /git:cp if you want to push single commit
+```
+
+---
+
+## 🚨 Emergency Bypass
+
+### Skip Reviews (Emergency Only)
+
+If you need to bypass checks:
+
+```bash
+# Method 1: Use --no-verify flag
+git push --no-verify
+
+# Method 2: PR title bypass
+[EMERGENCY] Fix critical bug
+
+# Method 3: PR label
+Add label: emergency, skip-review, or hotfix
+```
+
+**Note**: These bypass automated reviews but manual review is still recommended.
+
+---
+
+## 📖 Integration with Automation
+
+These commands work seamlessly with the GitHub automation:
+
+**After running `/git:cp`**:
+- Triggers CI Quality Gate workflow
+- Shows results in GitHub Actions
+
+**After running `/git:pr`**:
+- Triggers Claude Code Review
+- Runs CI Quality Gate
+- Updates project board status
+
+**After merging PR**:
+- Auto-closes linked issues
+- Updates project board to "Done"
+- Posts completion comments
+
+---
+
+## 🔗 Related Documentation
+
+- **Automation Setup**: `.github/AUTOMATION_SETUP.md`
+- **PR Template**: `.github/pull_request_template.md`
+- **Commit Template**: `.github/commit-template.txt`
+- **Workflow Guide**: See factory project for detailed reference
+
+---
+
+## 📍 Command Locations
+
+```
+.claude/commands/
+├── git/
+│   ├── cm.md           # Commit (no push)
+│   ├── cp.md           # Commit and push
+│   └── pr.md           # Create PR
+├── review.md           # Quality checks
+├── security-scan.md    # Security validation
+└── README.md           # This file
+```
+
+---
+
+## 💡 Tips
+
+**Before committing**:
+- ✅ Run `/review` to catch issues early
+- ✅ Run `/security-scan` if adding dependencies
+- ✅ Test skills with Claude before pushing
+
+**When creating PRs**:
+- ✅ Link related issues (`Fixes #123`)
+- ✅ Fill out PR template completely
+- ✅ Add appropriate labels
+- ✅ Request specific reviewers
+
+**For quality**:
+- ✅ Keep commits focused and atomic
+- ✅ Write clear, descriptive commit messages
+- ✅ Follow conventional commit format
+- ✅ Update documentation with changes
+
+---
+
+**Last Updated**: 2025-11-04
+**Version**: 1.0.0
+**Status**: ✅ Ready to use
+
+**Streamline your Git workflow with simple commands!** 🚀

.claude/commands/focused-fix.md

@@ -0,0 +1,17 @@
+---
+description: Deep-dive feature repair — systematically fix an entire feature/module. Usage: /focused-fix <feature-path>
+---
+
+Systematically repair the feature/module at `$ARGUMENTS` using the focused-fix 5-phase protocol.
+
+If `$ARGUMENTS` is empty, ask which feature/module to fix.
+
+Read `engineering/focused-fix/SKILL.md` and execute ALL 5 phases IN ORDER:
+
+1. **SCOPE** — Map the feature boundary (all files, entry points, internal files)
+2. **TRACE** — Map inbound + outbound dependencies across the entire codebase
+3. **DIAGNOSE** — Check code, runtime, tests, logs, config. Assign risk labels (HIGH/MED/LOW). Confirm root causes with evidence.
+4. **FIX** — Repair in order: deps → types → logic → tests → integration. One fix at a time, test after each. 3-strike escalation if fixes cascade.
+5. **VERIFY** — Run all feature tests + consumer tests. Summarize changes.
+
+**Iron Law:** No fixes before completing Phase 3. No exceptions.

.claude/commands/git/clean.md

@@ -0,0 +1,59 @@
+---
+description: Clean up merged branches locally and on remote, keeping only main, dev, and gh-pages.
+---
+
+Clean up stale branches that have been merged or are no longer needed.
+
+## Steps
+
+1. **List local branches** to delete (excluding `main`, `dev`, `gh-pages`):
+
+```bash
+git branch | grep -v -E '^\*|main$|dev$|gh-pages$'
+```
+
+Report what will be deleted. If no branches found, say "No local branches to clean" and skip to step 3.
+
+2. **Delete local branches** that are fully merged:
+
+```bash
+git branch -d <branch-name>
+```
+
+If a branch is not fully merged, report it to the user and ask whether to force-delete. Do NOT force-delete without confirmation.
+
+3. **List remote branches** to delete (excluding `main`, `dev`, `gh-pages`, `HEAD`):
+
+```bash
+git branch -r | grep -v -E 'origin/main$|origin/dev$|origin/gh-pages$|origin/HEAD'
+```
+
+Report what will be deleted. If no branches found, say "No remote branches to clean" and skip to step 5.
+
+4. **Confirm with the user** before deleting remote branches. Show the full list and wait for approval. Then delete:
+
+```bash
+git push origin --delete <branch-names>
+```
+
+5. **Prune stale remote refs**:
+
+```bash
+git remote prune origin
+```
+
+6. **Report final state**:
+
+```bash
+git branch        # local
+git branch -r     # remote
+```
+
+Present a summary:
+
+| Item | Count |
+|------|-------|
+| Local branches deleted | N |
+| Remote branches deleted | N |
+| Remaining local | main, dev |
+| Remaining remote | origin/main, origin/dev, origin/gh-pages |

.claude/commands/git/cm.md

@@ -0,0 +1,14 @@
+---
+description: Stage working tree changes and create a Conventional Commit (no push).
+---
+
+1. Run `git status --short` to review pending changes.
+2. For each file, open a diff (`git diff -- path/to/file`) and ensure no secrets or credentials are present.
+3. Stage the files intentionally (`git add path/to/file`). Avoid `git add .` unless every change was reviewed.
+4. Generate a Conventional Commit message (types: feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert).
+   - Commit subject ≤ 72 chars.
+   - Scope uses kebab-case (e.g., `feat(marketing-skill): ...`).
+   - Use `.github/commit-template.txt` for Context / Testing / Reviewers sections.
+5. Run `git commit` and paste the generated message + context from the template.
+6. Show the resulting commit (`git log -1 --stat`) and keep the commit hash handy.
+7. **Do not push** in this command. Use `git/cp.md` when you're ready to publish.

.claude/commands/git/cp.md

@@ -0,0 +1,14 @@
+---
+description: Stage, commit, and push the current branch following git governance rules.
+---
+
+1. Run `/review` to ensure lint/tests/security checks pass locally.
+2. Review and stage changes with `git add` (avoid staging generated or secret files).
+3. Craft a Conventional Commit message (types: feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert).
+   - Use `.github/commit-template.txt` and include Context / Testing / Reviewers blocks.
+   - Never add AI attribution strings to commits.
+4. Commit with `git commit` using the prepared message. If commitlint fails, fix the message and retry.
+5. Push to origin: `git push origin $(git branch --show-current)`.
+6. Trigger remote checks for visibility:
+   - `gh workflow run ci-quality-gate.yml --ref $(git branch --show-current)`
+7. Wait for workflow to finish (`gh run watch --workflow ci-quality-gate.yml`) before opening a pull request.

.claude/commands/git/pr.md

@@ -0,0 +1,25 @@
+---
+description: Create a pull request from the current branch.
+argument-hint: [target-branch]
+---
+
+## Variables
+
+TARGET_BRANCH: $1 (defaults to `main`)
+SOURCE_BRANCH: current branch (`git branch --show-current`)
+
+## Workflow
+
+1. Ensure `/review` and `/security-scan` have passed locally.
+2. Confirm `ci-quality-gate` workflow succeeded for `SOURCE_BRANCH`.
+3. Create the PR using GitHub CLI:
+   ```bash
+   gh pr create \
+     --base "$TARGET_BRANCH" \
+     --head "$SOURCE_BRANCH" \
+     --title "<Conventional PR title>" \
+     --body-file .github/pull_request_template.md
+   ```
+   If no template exists, provide a summary referencing Context, Testing, and Security results.
+4. Add labels (`gh pr edit --add-label "status: in-review"`).
+5. Share the PR link with reviewers and ensure at least one human approval is obtained.

.claude/commands/plugin-audit.md

@@ -0,0 +1,153 @@
+---
+description: Run the full 8-phase plugin audit pipeline on a skill directory.
+---
+
+Run the comprehensive plugin audit pipeline on the skill at `$ARGUMENTS`. If no argument provided, ask the user for the skill path.
+
+Execute all 8 phases sequentially. Auto-fix non-critical issues. Only prompt the user for critical decisions (external dependencies, security findings, breaking changes).
+
+## Phase 1: Discovery
+
+1. Verify `$ARGUMENTS` exists and contains `SKILL.md`. If not, error and stop.
+2. Read `SKILL.md` frontmatter — extract `name`, `description`, `Category`, `Tier`.
+3. Detect components:
+   - `scripts/*.py` → Python tools (count them)
+   - `references/*.md` → reference docs (count them)
+   - `assets/` → templates/samples
+   - `expected_outputs/` → test fixtures
+   - `agents/*.md` → embedded agents
+   - `skills/*/SKILL.md` → sub-skills (compound skill)
+   - `.claude-plugin/plugin.json` → standalone plugin
+   - `settings.json` → command registrations
+4. Detect domain from path (`engineering/`, `product-team/`, `marketing-skill/`, etc.)
+5. Search `commands/` for a `.md` file matching the skill name.
+6. Display discovery summary.
+
+## Phase 2: Structure Validation
+
+Run:
+```bash
+python3 engineering/skill-tester/scripts/skill_validator.py $ARGUMENTS --json
+```
+
+Parse JSON. If score < 75:
+- Auto-fix missing frontmatter fields, missing section headings, missing directories.
+- Re-run. If still < 75, mark as FAIL but continue collecting results.
+
+## Phase 3: Quality Scoring
+
+Run:
+```bash
+python3 engineering/skill-tester/scripts/quality_scorer.py $ARGUMENTS --detailed --json
+```
+
+Parse JSON. If score < 60, report improvement roadmap items.
+
+## Phase 4: Script Testing
+
+If `$ARGUMENTS/scripts/` contains `.py` files, run:
+```bash
+python3 engineering/skill-tester/scripts/script_tester.py $ARGUMENTS --json --verbose
+```
+
+All scripts must PASS. If any script uses external imports, **ask the user** whether the dependency is acceptable.
+
+## Phase 5: Security Audit
+
+Run:
+```bash
+python3 engineering/skill-security-auditor/scripts/skill_security_auditor.py $ARGUMENTS --strict --json
+```
+
+Zero CRITICAL or HIGH findings required. **Do NOT auto-fix security issues** — report them to the user with file, line, pattern, and recommended fix.
+
+## Phase 6: Marketplace & Plugin Compliance
+
+### 6a. plugin.json
+If `$ARGUMENTS/.claude-plugin/plugin.json` exists:
+- Must be valid JSON
+- Only allowed fields: `name`, `description`, `version`, `author`, `homepage`, `repository`, `license`, `skills`
+- Version must be `2.1.2`
+- Auto-fix version mismatches and remove extra fields.
+
+### 6b. settings.json
+If `$ARGUMENTS/settings.json` exists:
+- Must be valid JSON
+- Version must match repo version
+- Each command in `commands` field must have a matching `commands/*.md` file
+
+### 6c. Marketplace entry
+Check `.claude-plugin/marketplace.json` for an entry with `source` matching `./$ARGUMENTS`. Verify version and name match.
+
+### 6d. Domain plugin.json
+Check the parent domain's `.claude-plugin/plugin.json` — verify skill count in description matches actual count. Auto-fix stale counts.
+
+## Phase 7: Ecosystem Integration
+
+### 7a. Cross-platform sync
+Verify skill appears in `.codex/skills-index.json` and `.gemini/skills-index.json`. If missing:
+```bash
+python3 scripts/sync-codex-skills.py --verbose
+python3 scripts/sync-gemini-skills.py --verbose
+```
+
+### 7b. Command integration
+If the skill has associated commands, verify:
+- Command `.md` has valid frontmatter
+- Command references the correct skill
+- Command is in `mkdocs.yml` nav
+Auto-fix missing nav entries.
+
+### 7c. Agent integration
+Check for embedded agents in `$ARGUMENTS/agents/`. Search `agents/` for cs-* agents that reference this skill. Verify references resolve.
+
+### 7d. Cross-skill dependencies
+Read SKILL.md for references to other skills (`../` paths, "Related Skills" sections). Verify each referenced skill exists.
+
+## Phase 8: Domain Code Review
+
+Based on the domain, apply the appropriate agent's review criteria:
+
+| Domain | Agent | Focus |
+|--------|-------|-------|
+| `engineering/` or `engineering-team/` | cs-senior-engineer | Architecture, code quality, CI/CD |
+| `product-team/` | cs-product-manager | PRD quality, user stories, RICE |
+| `marketing-skill/` | cs-content-creator | Content quality, SEO, brand voice |
+| `ra-qm-team/` | cs-quality-regulatory | Compliance, audit trail, regulatory |
+| `business-growth/` | cs-growth-strategist | Growth metrics, revenue impact |
+| `finance/` | cs-financial-analyst | Model accuracy, metric definitions |
+| Other | cs-senior-engineer | General code review |
+
+Read the agent's `.md` file for review criteria. Apply those criteria to the skill's SKILL.md, scripts, and references. Check:
+- Workflows are actionable and complete
+- Scripts solve the stated problem
+- References contain accurate domain knowledge
+- No broken internal links
+- Attribution present where required
+
+## Final Report
+
+Present all results in a structured summary:
+
+```
+╔══════════════════════════════════════════════════════════════╗
+║  PLUGIN AUDIT REPORT: {skill_name}                         ║
+╠══════════════════════════════════════════════════════════════╣
+║  Phase 1 — Discovery          ✅ {type}, {domain}           ║
+║  Phase 2 — Structure          ✅ {score}/100 ({level})       ║
+║  Phase 3 — Quality            ✅ {score}/100 ({grade})       ║
+║  Phase 4 — Scripts            ✅ {n}/{n} PASS                ║
+║  Phase 5 — Security           ✅ PASS (0 critical, 0 high)   ║
+║  Phase 6 — Marketplace        ✅ plugin.json valid            ║
+║  Phase 7 — Ecosystem          ✅ synced                       ║
+║  Phase 8 — Code Review        ✅ passed                       ║
+║                                                              ║
+║  VERDICT: ✅ PASS                                            ║
+║  Auto-fixes: {n} | Warnings: {n} | Action items: {n}        ║
+╚══════════════════════════════════════════════════════════════╝
+```
+
+**Verdict rules:**
+- All phases pass → **PASS**
+- Only warnings → **PASS WITH WARNINGS**
+- Any blocker (structure <75, quality <60, script FAIL, security CRITICAL/HIGH, invalid plugin.json) → **FAIL**

.claude/commands/review.md

@@ -0,0 +1,33 @@
+---
+description: Run the local review gate before pushing.
+---
+
+Perform a complete review pass:
+
+1. Save work in progress and ensure the working tree is clean except for intentional changes.
+2. Install tooling (only first run):
+   ```bash
+   pip install --upgrade pip
+   pip install yamllint==1.35.1 check-jsonschema==0.28.4 safety==3.2.4
+   npm install --global markdown-link-check@3.12.2
+   ```
+3. Lint GitHub workflows:
+   ```bash
+   yamllint -d '{extends: default, rules: {line-length: {max: 160}}}' .github/workflows
+   check-jsonschema --schema github-workflow --base-dir . .github/workflows/*.yml
+   ```
+4. Python syntax check:
+   ```bash
+   python -m compileall marketing-skill product-team c-level-advisor engineering-team ra-qm-team
+   ```
+5. Markdown sanity check:
+   ```bash
+   markdown-link-check README.md
+   ```
+6. Optional dependency audit (if `requirements*.txt` present):
+   ```bash
+   for f in $(find . -name "requirements*.txt" 2>/dev/null); do
+       safety check --full-report --file "$f"
+   done
+   ```
+7. Summarize results in the commit template's Testing section. Fix any failures before continuing.

.claude/commands/security-scan.md

@@ -0,0 +1,22 @@
+---
+description: Run the security scan gate before pushing.
+---
+
+1. Ensure dependencies are installed:
+   ```bash
+   pip install safety==3.2.4
+   brew install gitleaks  # or appropriate package manager
+   ```
+2. Scan for committed secrets:
+   ```bash
+   gitleaks detect --verbose --redact
+   ```
+   - Resolve any findings before continuing.
+3. Audit Python dependencies (if requirements files exist):
+   ```bash
+   for f in $(find . -name "requirements*.txt" 2>/dev/null); do
+       safety check --full-report --file "$f"
+   done
+   ```
+4. Record results in the commit template's Testing section.
+5. After a clean pass, proceed with commit and push workflow.

.claude/commands/seo-auditor.md

@@ -0,0 +1,97 @@
+---
+description: Scan and optimize docs for SEO — meta tags, readability, keywords, broken links, sitemap.
+---
+
+Run the SEO auditor on documentation files. Target path: `$ARGUMENTS` (default: all docs/ and root README.md).
+
+If `$ARGUMENTS` is `--report-only`, scan without making changes.
+
+Execute all 7 phases. Auto-fix non-destructive issues. Never change URLs. Preserve content on high-ranking pages.
+
+## Phase 1: Discovery
+
+Find all target markdown files:
+- `docs/**/*.md` — all documentation pages
+- `README.md` files in domain root directories
+- If `$ARGUMENTS` specifies a path, scope to that path only
+
+For each file, extract current state: `title:` frontmatter, `description:` frontmatter, H1, H2s, word count, link count. Store as baseline for the report.
+
+Identify recently changed files: `git log --oneline -2 --name-only -- docs/ README.md`
+
+## Phase 2: Meta Tags
+
+For each file with YAML frontmatter:
+
+**Title** (`title:` field):
+- Must be 50-60 characters
+- Must contain a primary keyword
+- Must be unique across all pages
+- Auto-fix generic titles using domain context
+
+**Description** (`description:` field):
+- Must be 120-160 characters
+- Must contain primary keyword
+- Must be unique — no duplicates
+- Auto-fix from SKILL.md frontmatter or first paragraph
+
+Run SEO checker on built HTML pages:
+```bash
+python3 marketing-skill/skills/seo-audit/scripts/seo_checker.py --file site/{path}/index.html
+```
+
+## Phase 3: Content Quality
+
+**Heading structure:** One H1 per page, no skipped levels, keywords in headings.
+
+**Readability:** Run content scorer:
+```bash
+python3 marketing-skill/skills/content-production/scripts/content_scorer.py {file}
+```
+Target: readability ≥ 70, structure ≥ 60.
+
+**AI detection** (on non-generated files only):
+```bash
+python3 marketing-skill/skills/content-humanizer/scripts/humanizer_scorer.py {file}
+```
+Flag pages < 50. Fix AI clichés: "delve", "leverage", "it's important to note", "comprehensive".
+
+**Do NOT rewrite** pages ranking well — only fix critical issues on those.
+
+## Phase 4: Keywords
+
+Check each page has its primary keyword in: title, description, H1, first paragraph, at least one H2.
+
+Keyword density: 1-2% for primary. Flag and reduce if > 3%.
+
+**Never change existing URLs.** Only optimize content and meta tags.
+
+## Phase 5: Links
+
+**Internal links:** Verify all `[text](url)` targets exist. Fix broken links.
+
+**Duplicate content:**
+```bash
+grep -rh '^description:' docs/**/*.md | sort | uniq -d
+```
+Make each duplicate unique.
+
+**Orphan pages:** Find pages not in `mkdocs.yml` nav. Add them.
+
+## Phase 6: Sitemap
+
+Rebuild the site to regenerate sitemap:
+```bash
+mkdocs build
+```
+
+Analyze the sitemap:
+```bash
+python3 marketing-skill/skills/site-architecture/scripts/sitemap_analyzer.py site/sitemap.xml
+```
+
+Verify all pages appear, no duplicates, no broken URLs.
+
+## Phase 7: Report
+
+Present a summary showing: pages scanned, issues found, auto-fixes applied, manual review items, broken links fixed, orphans resolved, sitemap URL count. List preserved pages that were not modified.

.claude/commands/update-docs.md

@@ -0,0 +1,228 @@
+---
+description: Update all the documentation related files.
+---
+
+After completing any skill creation, agent creation, or command creation in this repository, run the full post-creation sync pipeline below. Execute every step — never skip a task. If something is unclear or a step fails, ask the user for guidance before continuing.
+
+---
+
+## Step 1: Inventory what changed
+
+Scan the working tree to identify what was added, modified, or deleted:
+
+```bash
+git status --short
+```
+
+Classify each change:
+- **New skill** — a new folder containing `SKILL.md` under a domain directory
+- **New agent** — a new `.md` file under `agents/`
+- **New command** — a new `.md` file under `commands/`
+- **Modified skill/agent/command** — updated existing files
+- **Deleted skill/agent/command** — removed files
+
+Report the inventory to the user before proceeding.
+
+---
+
+## Step 2: Cross-platform CLI sync
+
+Ensure all platforms have compatible versions of every skill, agent, and command.
+
+### 2a. Codex CLI
+
+Run the Codex sync script to regenerate symlinks and the skills index:
+
+```bash
+python3 scripts/sync-codex-skills.py --verbose
+```
+
+Verify the output: check `.codex/skills-index.json` for correct `total_skills` count and that new skills appear in the index.
+
+### 2b. Gemini CLI
+
+Run the Gemini sync script:
+
+```bash
+python3 scripts/sync-gemini-skills.py --verbose
+```
+
+Verify: check `.gemini/skills-index.json` for correct total count. New skills, agents, and commands should all have corresponding entries and symlinks under `.gemini/skills/`.
+
+### 2c. OpenClaw
+
+Verify that `scripts/openclaw-install.sh` will pick up the new skills. The install script uses the same directory structure, so no separate sync is needed — but confirm the new skill directories are not excluded by any filter in the script.
+
+Report sync results (skill counts per platform) to the user.
+
+---
+
+## Step 3: Claude Code plugin marketplace
+
+### 3a. Domain-level plugin.json
+
+For each domain that had changes, update the domain's `.claude-plugin/plugin.json`:
+- Update `description` with accurate skill/tool/reference counts
+- Update `version` if needed
+- Verify `source` paths are correct
+
+Domain plugin.json locations:
+- `marketing-skill/.claude-plugin/plugin.json`
+- `engineering-team/.claude-plugin/plugin.json`
+- `engineering/.claude-plugin/plugin.json`
+- `product-team/.claude-plugin/plugin.json`
+- `c-level-advisor/.claude-plugin/plugin.json`
+- `project-management/.claude-plugin/plugin.json`
+- `ra-qm-team/.claude-plugin/plugin.json`
+- `business-growth/.claude-plugin/plugin.json`
+- `finance/.claude-plugin/plugin.json`
+
+### 3b. Root marketplace.json
+
+Update `.claude-plugin/marketplace.json`:
+- Update the top-level `metadata.description` with accurate total counts (skills, tools, references, agents, commands)
+- If a new individual skill plugin entry is needed (for standalone install), add it to the `plugins` array following the existing pattern
+- Update `keywords` arrays if new domains or capabilities were added
+- Verify all `source` paths point to valid directories
+
+---
+
+## Step 4: Update documentation files
+
+### 4a. Root CLAUDE.md
+
+Update `/CLAUDE.md` (the root project instructions):
+- **Current Scope** line: update skill, tool, reference, agent, and command counts
+- **Repository Structure** comment counts (agents, commands, skills per domain)
+- **Navigation Map** table: verify all domain entries are current
+- **Current Version** section: add a bullet if significant changes were made
+- **Roadmap** section: update counts if needed
+
+### 4b. Domain-level CLAUDE.md files
+
+For each domain that had changes, update its `CLAUDE.md`:
+- Skill count and list
+- Script/tool count
+- Agent references
+- Command references
+- Any new cross-domain integrations
+
+Domain CLAUDE.md locations:
+- `agents/CLAUDE.md`
+- `marketing-skill/CLAUDE.md`
+- `product-team/CLAUDE.md`
+- `engineering-team/CLAUDE.md`
+- `c-level-advisor/CLAUDE.md`
+- `project-management/CLAUDE.md`
+- `ra-qm-team/CLAUDE.md`
+- `business-growth/CLAUDE.md`
+- `finance/CLAUDE.md`
+- `standards/CLAUDE.md`
+- `templates/CLAUDE.md`
+
+### 4c. Root README.md
+
+Update `/README.md`:
+- Badge counts (Skills, Agents, Commands)
+- Tagline/intro paragraph skill count
+- Skills Overview table (domain rows with correct counts)
+- Quick Install section (install commands, skill counts in comments)
+- Python Analysis Tools section (tool count, add examples for new tools)
+- FAQ section (update any counts mentioned)
+
+### 4d. docs/index.md (GitHub Pages homepage)
+
+Update `docs/index.md`:
+- `description` meta tag
+- Hero subtitle skill count
+- Grid cards (skills, tools, agents, commands counts)
+- Domain cards (skill counts per domain, links)
+
+### 4e. docs/getting-started.md
+
+Update `docs/getting-started.md`:
+- `description` meta tag
+- Available Bundles table (skill counts per bundle)
+- Python Tools section (tool count)
+- FAQ answers (any count references)
+
+---
+
+## Step 5: Regenerate GitHub Pages
+
+Run the docs generation script to create/update all MkDocs pages:
+
+```bash
+python3 scripts/generate-docs.py
+```
+
+This generates pages for:
+- Every skill (from SKILL.md files)
+- Every agent (from agents/*.md)
+- Every command (from commands/*.md)
+- Index pages for skills, agents, and commands sections
+
+### 5a. Update mkdocs.yml navigation
+
+Open `mkdocs.yml` and update the `nav:` section:
+- Add new skill pages under the correct domain section
+- Add new agent pages under the Agents section
+- Add new command pages under the Commands section
+- Update `site_description` with current counts
+
+### 5b. Verify the build
+
+```bash
+python3 -m mkdocs build 2>&1 | tail -5
+```
+
+The build should complete without errors. Warnings about relative links in SKILL.md files are expected and can be ignored (they reference skill-internal paths like `references/` and `scripts/`).
+
+Report the build result and page count to the user.
+
+---
+
+## Step 6: Consistency verification
+
+Run a final consistency check across all updated files:
+
+1. **Count consistency** — Verify the same skill/agent/command/tool counts appear in:
+   - Root CLAUDE.md
+   - Root README.md
+   - docs/index.md
+   - docs/getting-started.md
+   - .claude-plugin/marketplace.json
+
+2. **Path validation** — Verify all `source` paths in marketplace.json point to existing directories
+
+3. **New script verification** — If new Python scripts were added, verify they run:
+   ```bash
+   python3 path/to/new/script.py --help
+   ```
+
+4. **Frontmatter check** — Verify all new SKILL.md, agent, and command files have valid YAML frontmatter with at minimum `name` and `description` fields
+
+Report any inconsistencies found and fix them before finishing.
+
+---
+
+## Step 7: Summary report
+
+Present a summary to the user:
+
+| Item | Status |
+|------|--------|
+| New skills added | [list] |
+| New agents added | [list] |
+| New commands added | [list] |
+| Codex CLI sync | count |
+| Gemini CLI sync | count |
+| OpenClaw compatible | yes/no |
+| Marketplace updated | yes/no |
+| CLAUDE.md files updated | [count]/[total] |
+| README.md updated | yes/no |
+| GitHub Pages regenerated | [page count] pages |
+| MkDocs build | pass/fail |
+| Consistency check | pass/fail |
+
+Ask the user if they want to commit and push the changes.

.claude/settings.json

@@ -0,0 +1,14 @@
+{
+    "$schema": "https://json.schemastore.org/claude-code-settings.json",
+    "extraKnownMarketplaces": {
+        "ecc": {
+            "source": {
+                "source": "github",
+                "repo": "affaan-m/ECC"
+            }
+        }
+    },
+    "enabledPlugins": {
+        "ecc@ecc": true
+    }
+}

.codex-plugin/plugin.json

@@ -0,0 +1,47 @@
+{
+  "name": "claude-code-skills",
+  "version": "2.2.0",
+  "description": "223 production-ready skills, 23 agents, and 298 Python tools across 9 domains — engineering, marketing, product, compliance, C-level advisory, and more. The largest open-source skills library for AI coding agents.",
+  "author": {
+    "name": "Alireza Rezvani",
+    "url": "https://alirezarezvani.com"
+  },
+  "homepage": "https://alirezarezvani.github.io/claude-skills/",
+  "repository": "https://github.com/alirezarezvani/claude-skills",
+  "license": "MIT",
+  "keywords": [
+    "openai-codex",
+    "codex-plugin",
+    "claude-code",
+    "agent-skills",
+    "engineering",
+    "marketing",
+    "product",
+    "compliance",
+    "devops",
+    "security",
+    "ai-agents"
+  ],
+  "skills": "./.codex/skills/",
+  "interface": {
+    "type": "cli",
+    "composerIcon": "./assets/icon.png",
+    "displayName": "Claude Code Skills",
+    "shortDescription": "223 production-ready skills for AI coding agents across 9 domains",
+    "longDescription": "The largest open-source skills library for AI coding agents. 223 skills covering engineering (architecture, DevOps, security, AI/ML), marketing (SEO, CRO, content), product management, C-level advisory, regulatory compliance (ISO 13485, SOC 2, GDPR), project management, business growth, and finance. Includes 298 stdlib-only Python CLI tools, 416 reference guides, 23 orchestration agents, and 22 slash commands. Works with Codex, Claude Code, Gemini CLI, Cursor, Aider, Windsurf, and 5 more tools.",
+    "developerName": "Alireza Rezvani",
+    "category": "Coding",
+    "capabilities": [
+      "Read",
+      "Write"
+    ],
+    "websiteURL": "https://alirezarezvani.github.io/claude-skills/",
+    "defaultPrompt": [
+      "Design an AWS architecture for my project",
+      "Run a security pen test on this codebase",
+      "Create a product requirements document",
+      "Audit this page for accessibility (WCAG 2.2)"
+    ],
+    "brandColor": "#0969da"
+  }
+}

.codex/skills/a11y-audit

@@ -0,0 +1 @@
+../../engineering-team/a11y-audit/skills/a11y-audit

.codex/skills/ab-test-setup

@@ -0,0 +1 @@
+../../marketing-skill/skills/ab-test-setup

.codex/skills/ad-creative

@@ -0,0 +1 @@
+../../marketing-skill/skills/ad-creative

.codex/skills/adversarial-reviewer

@@ -0,0 +1 @@
+../../engineering-team/skills/adversarial-reviewer

.codex/skills/aeo

@@ -0,0 +1 @@
+../../marketing-skill/skills/aeo

.codex/skills/agent-decision-receipts

@@ -0,0 +1 @@
+../../ra-qm-team/skills/agent-decision-receipts

.codex/skills/agent-designer

@@ -0,0 +1 @@
+../../engineering/skills/agent-designer

.codex/skills/agent-harness

@@ -0,0 +1 @@
+../../engineering/agent-harness/skills/agent-harness

.codex/skills/agent-protocol

@@ -0,0 +1 @@
+../../c-level-advisor/skills/agent-protocol

.codex/skills/agent-workflow-designer

@@ -0,0 +1 @@
+../../engineering/skills/agent-workflow-designer

.codex/skills/agenthub

@@ -0,0 +1 @@
+../../engineering/agenthub/skills/agenthub

.codex/skills/agile-product-owner

@@ -0,0 +1 @@
+../../product-team/agile-product-owner/skills/agile-product-owner

.codex/skills/ai-act-readiness

@@ -0,0 +1 @@
+../../compliance-os/skills/ai-act-readiness

.codex/skills/ai-security

@@ -0,0 +1 @@
+../../engineering-team/skills/ai-security

.codex/skills/aims-audit

@@ -0,0 +1 @@
+../../compliance-os/skills/aims-audit

.codex/skills/analytics-tracking

@@ -0,0 +1 @@
+../../marketing-skill/skills/analytics-tracking

.codex/skills/andreessen

@@ -0,0 +1 @@
+../../productivity/andreessen/skills/andreessen

.codex/skills/api-design-reviewer

@@ -0,0 +1 @@
+../../engineering/skills/api-design-reviewer

.codex/skills/api-test-suite-builder

@@ -0,0 +1 @@
+../../engineering/skills/api-test-suite-builder

.codex/skills/app-store-optimization

@@ -0,0 +1 @@
+../../marketing-skill/skills/app-store-optimization

.codex/skills/apple-hig-expert

@@ -0,0 +1 @@
+../../product-team/apple-hig-expert/skills/apple-hig-expert

.codex/skills/arquiteto-de-empresa

@@ -0,0 +1 @@
+../../c-level-advisor/arquiteto-de-empresa/skills/arquiteto-de-empresa

.codex/skills/atlassian-admin

@@ -0,0 +1 @@
+../../project-management/skills/atlassian-admin

.codex/skills/atlassian-templates

@@ -0,0 +1 @@
+../../project-management/skills/atlassian-templates

.codex/skills/autoresearch-agent

@@ -0,0 +1 @@
+../../engineering/autoresearch-agent/skills/autoresearch-agent

.codex/skills/aws-solution-architect

@@ -0,0 +1 @@
+../../engineering-team/skills/aws-solution-architect

.codex/skills/azure-cloud-architect

@@ -0,0 +1 @@
+../../engineering-team/skills/azure-cloud-architect

.codex/skills/behuman

@@ -0,0 +1 @@
+../../engineering/behuman/skills/behuman

.codex/skills/board

@@ -0,0 +1 @@
+../../engineering/agenthub/skills/board

.codex/skills/board-deck-builder

@@ -0,0 +1 @@
+../../c-level-advisor/skills/board-deck-builder

.codex/skills/board-meeting

@@ -0,0 +1 @@
+../../c-level-advisor/skills/board-meeting

.codex/skills/board-prep

@@ -0,0 +1 @@
+../../c-level-advisor/executive-mentor/skills/board-prep

.codex/skills/boardroom

@@ -0,0 +1 @@
+../../c-level-advisor/c-level-agents/skills/boardroom

.codex/skills/brand-guidelines

@@ -0,0 +1 @@
+../../marketing-skill/skills/brand-guidelines

.codex/skills/brief

@@ -0,0 +1 @@
+../../c-level-advisor/c-level-agents/skills/brief

.codex/skills/browser-automation

@@ -0,0 +1 @@
+../../engineering/skills/browser-automation

.codex/skills/browserstack

@@ -0,0 +1 @@
+../../engineering-team/playwright-pro/skills/browserstack

.codex/skills/business-growth-skills

@@ -0,0 +1 @@
+../../business-growth/skills/business-growth-skills

.codex/skills/business-investment-advisor

@@ -0,0 +1 @@
+../../finance/business-investment-advisor/skills/business-investment-advisor

.codex/skills/business-operations-skills

@@ -0,0 +1 @@
+../../business-operations/skills/business-operations-skills

.codex/skills/c-level-agents

@@ -0,0 +1 @@
+../../c-level-advisor/c-level-agents/skills/c-level-agents

.codex/skills/c-level-skills

@@ -0,0 +1 @@
+../../c-level-advisor/skills/c-level-skills

.codex/skills/caio-review

@@ -0,0 +1 @@
+../../c-level-advisor/c-level-agents/skills/caio-review

.codex/skills/campaign-analytics

@@ -0,0 +1 @@
+../../marketing-skill/skills/campaign-analytics

.codex/skills/capa-officer

@@ -0,0 +1 @@
+../../ra-qm-team/skills/capa-officer

.codex/skills/capacity-planner

@@ -0,0 +1 @@
+../../business-operations/skills/capacity-planner

.codex/skills/capture

@@ -0,0 +1 @@
+../../productivity/capture/skills/capture

.codex/skills/caveman

@@ -0,0 +1 @@
+../../engineering/caveman/skills/caveman

.codex/skills/cco-review

@@ -0,0 +1 @@
+../../c-level-advisor/c-level-agents/skills/cco-review

.codex/skills/cdo-review

@@ -0,0 +1 @@
+../../c-level-advisor/c-level-agents/skills/cdo-review

.codex/skills/ceo-advisor

@@ -0,0 +1 @@
+../../c-level-advisor/skills/ceo-advisor

.codex/skills/cfo-advisor

@@ -0,0 +1 @@
+../../c-level-advisor/skills/cfo-advisor

.codex/skills/cfo-review

@@ -0,0 +1 @@
+../../c-level-advisor/c-level-agents/skills/cfo-review

.codex/skills/challenge

@@ -0,0 +1 @@
+../../c-level-advisor/executive-mentor/skills/challenge

.codex/skills/change-management

@@ -0,0 +1 @@
+../../c-level-advisor/skills/change-management

.codex/skills/changelog-generator

@@ -0,0 +1 @@
+../../engineering/skills/changelog-generator

.codex/skills/channel-economics

@@ -0,0 +1 @@
+../../commercial/skills/channel-economics

.codex/skills/chaos-engineering

@@ -0,0 +1 @@
+../../engineering/chaos-engineering/skills/chaos-engineering

.codex/skills/chief-ai-officer-advisor

@@ -0,0 +1 @@
+../../c-level-advisor/chief-ai-officer-advisor/skills/chief-ai-officer-advisor

.codex/skills/chief-customer-officer-advisor

@@ -0,0 +1 @@
+../../c-level-advisor/chief-customer-officer-advisor/skills/chief-customer-officer-advisor

.codex/skills/chief-data-officer-advisor

@@ -0,0 +1 @@
+../../c-level-advisor/chief-data-officer-advisor/skills/chief-data-officer-advisor

.codex/skills/chief-of-staff

@@ -0,0 +1 @@
+../../c-level-advisor/skills/chief-of-staff

.codex/skills/chro-advisor

@@ -0,0 +1 @@
+../../c-level-advisor/skills/chro-advisor

.codex/skills/churn-prevention

@@ -0,0 +1 @@
+../../marketing-skill/skills/churn-prevention

.codex/skills/ci-cd-pipeline-builder

@@ -0,0 +1 @@
+../../engineering/skills/ci-cd-pipeline-builder

.codex/skills/ciso-advisor

@@ -0,0 +1 @@
+../../c-level-advisor/skills/ciso-advisor

.codex/skills/ciso-review

@@ -0,0 +1 @@
+../../c-level-advisor/c-level-agents/skills/ciso-review

.codex/skills/claude-coach

@@ -0,0 +1 @@
+../../engineering/claude-coach/skills/claude-coach

.codex/skills/clinical-research

@@ -0,0 +1 @@
+../../research-ops/skills/clinical-research

.codex/skills/cloud-security

@@ -0,0 +1 @@
+../../engineering-team/skills/cloud-security

.codex/skills/cmo-advisor

@@ -0,0 +1 @@
+../../c-level-advisor/skills/cmo-advisor

.codex/skills/cmo-review

@@ -0,0 +1 @@
+../../c-level-advisor/c-level-agents/skills/cmo-review

.codex/skills/code-reviewer

@@ -0,0 +1 @@
+../../engineering-team/skills/code-reviewer

.codex/skills/code-to-prd

@@ -0,0 +1 @@
+../../product-team/code-to-prd/skills/code-to-prd

.codex/skills/code-tour

@@ -0,0 +1 @@
+../../engineering/code-tour/skills/code-tour

.codex/skills/codebase-onboarding

@@ -0,0 +1 @@
+../../engineering/skills/codebase-onboarding

.codex/skills/cold-email

@@ -0,0 +1 @@
+../../marketing-skill/skills/cold-email

.codex/skills/collab-proof

@@ -0,0 +1 @@
+../../engineering/collab-proof/skills/collab-proof

.codex/skills/commercial-forecaster

@@ -0,0 +1 @@
+../../commercial/skills/commercial-forecaster

.codex/skills/commercial-policy

@@ -0,0 +1 @@
+../../commercial/skills/commercial-policy

.codex/skills/commercial-skills

@@ -0,0 +1 @@
+../../commercial/skills/commercial-skills

.codex/skills/company-os

@@ -0,0 +1 @@
+../../c-level-advisor/skills/company-os

.codex/skills/competitive-intel

@@ -0,0 +1 @@
+../../c-level-advisor/skills/competitive-intel

.codex/skills/competitive-teardown

@@ -0,0 +1 @@
+../../product-team/skills/competitive-teardown