docs: regenerate skill pages

[will-lynas]

What does this PR do?

Regenerates the committed website skill documentation from the current source so the generated pages, catalogs, and sidebar are synchronized.

This PR intentionally contains only the generated documentation update. A stacked follow-up will salvage the read-only check mode and CI validation from the existing upstream work.

Related Issue

Related upstream issue:

• Detect generated skill documentation drift without mutating CI #67325 — tracks generated skill-documentation drift and the need for a read-only CI check.

Related upstream PRs:

• fix(docs): detect generated skill documentation drift #67328 — focused implementation of check mode, output ownership, safe stale-page cleanup, CI validation, and a generated baseline; currently stale and conflicting.
• docs: re-sync stale file references, regenerate skill docs, and add guards for both #80722 — broader documentation resynchronization that also regenerates skill docs and adds both documentation-link and generated-doc guards; currently stale and conflicting.
• fix(docs): prune removed generated skill pages #71869 — adds marker-gated pruning of removed generated skill pages while preserving hand-written pages; stale but cleanly mergeable, with its specific page deletion already present on main.
• fix(docs): regenerate skill docs to fix stale cross-links, add tool-search to sidebar #49444 — earlier regeneration fixing stale cross-links; closed after its useful work was salvaged through docs: salvage 9 validated docs-update PRs (cluster) #49914.
• docs(skills): regenerate optional skill docs #21624 — earlier optional-skill docs regeneration; closed as superseded by later changes on main.
• fix(docs): generate missing creative-tldraw-offline doc page #71455 — earlier regeneration for a missing Tldraw page; closed after the page was implemented on main.

Type of Change

• 🐛 Bug fix (non-breaking change that fixes an issue)
• ✨ New feature (non-breaking change that adds functionality)
• 🔒 Security fix
• 📝 Documentation update
• ✅ Tests (adding or improving test coverage)
• ♻️ Refactor (no behavior change)
• 🎯 New skill (bundled or hub)

Changes Made

• Regenerated the website skill pages.
• Updated the bundled and optional skill catalogs.
• Updated the generated sidebar entries.

How to Test

1. Run uv run --with pyyaml python website/scripts/generate-skill-docs.py twice and confirm the second run is clean.
2. Run uv run --extra dev pytest -q tests/website/test_generate_skill_docs.py.
3. Run cd website && npm ci && npm run build:fast.

Checklist

Code

• I've read the Contributing Guide
• My commit messages follow Conventional Commits (fix(scope):, feat(scope):, etc.)
• I searched for existing PRs to make sure this isn't a duplicate
• My PR contains only changes related to this fix/feature (no unrelated commits)
• I've run pytest tests/ -q and all tests pass
• I've added tests for my changes (required for bug fixes, strongly encouraged for features)
• I've tested on my platform: macOS

Documentation & Housekeeping

• I've updated relevant documentation (README, docs/, docstrings) — or N/A
• I've updated cli-config.yaml.example if I added/changed config keys — or N/A
• I've updated CONTRIBUTING.md or AGENTS.md if I changed architecture or workflows — or N/A
• I've considered cross-platform impact (Windows, macOS) per the compatibility guide — or N/A
• I've updated tool descriptions/schemas if I changed tool behavior — or N/A

Screenshots / Logs

N/A

[alt-glitch]

This was generated by AI during triage.

@christian-byrne Tagging you on this ComfyUI item.