Bot 组合看板：每个 Bot 的职责、技能、例行汇成一页

（作者英文原文）Build me a living Bot Portfolio Dashboard as a Page I will return to and keep updated.

## What I want
A single operable view of my Grok Bot portfolio so I can see, at a glance:
- Bot name
- What it is for (role / durable outcome / scope)
- Which Skills it lands on (skill placements)
- Main Routines it runs (names + enabled/disabled)
- Operating status (status, lifecycle, operating mode)

This is an operations board, not a one-off org chart. Prefer a filterable wide Page over a long chat dump.

## Before you build
1. Restate in your own words what you think my goal and problem are. Wait for corrections if anything is off.
2. Find the Canonical / authoritative Bot Portfolio Registry (or the closest structured source of truth). Prefer that over free-text bot descriptions when they conflict.
3. Say clearly which fields come from the Registry and which must be overlaid from elsewhere.

## Source-of-truth rules (do not invent)
- Registry = source of truth for identity, role/scope, status/lifecycle/operating mode, primary routines, handoff/topology when present.
- Skills are usually NOT a Registry row field. Overlay Skill placements only from evidence (that Bot’s Getting started / named workflows / SKILL.md ownership). Label weak guesses or omit them. Shared Skills used by several Bots may list multiple owners with a “shared pattern” note.
- Do not invent: last successful run, acceptance, agent IDs, owners, handoff contracts, or “green” health when timestamps are null/stale.
- Empty Routines on an on-demand Bot are not automatically “inactive.” Zero Routines can be intentional—call that out if evidence says so.
- Distinguish freshness clocks if your Registry has them (e.g. last verified vs last live observation). Show as-of dates; never imply live verification you did not do.

## Dashboard shape
- Wide Page with filters (lifecycle / operating mode / status; default-hide retired/stub).
- Columns: Name · Function/scope · Skills (overlay) · Main Routines · Status · Routine on/off summary.
- Short caveat callout: what is Registry fact vs Skill overlay; what is unknown.
- Embed a dated snapshot JSON path/notes so future refreshes can diff SHA / last_verified_at instead of rebuilding from scratch.

## Keep it up to date
After the first Page ships, propose how to refresh it (owner Bot + cadence). Prefer editing the same Page in place—never spawn duplicate Pages for the same subject. Do not create a Routine that contradicts an existing governance HOLD (e.g. “this Bot keeps zero Routines”) without my explicit override.

## Delivery
- Chat: one or two lines + the Page link only (not the full table body).
- Report counts: operating / on_demand / retired / stub, Skill coverage gaps (Bots with 0 evidenced Skills), and any Registry vs live name mismatches.