菜单
Use when refreshing ai-skill-hub as a capability system and the output must stay layer-oriented instead of file-oriented.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Adapter entry for bootstrapping agent rules, contracts, validation, task packages, reports, and handoff boundaries for financial data engineering or operations projects. Canonical source is in skills/financial-data-agent-bootstrap.
Use when bootstrapping agent rules, contracts, validation, task packages, reports, and handoff boundaries for financial data engineering or operations projects.
Use when evaluating, scoring, diagnosing, or explicitly refactoring a single skill under controlled governance.
Use when onboarding a new maintainer or AI agent, scanning an unfamiliar repository, or generating a takeover packet.
Use when preparing a handoff task package, bounded execution, or execution report across AI agents.
Use when assessing migration readiness for a financial-data Python project with script sprawl, Excel assets, or Wind/Desktop coupling.
| name | system-status-update |
| description | Use when refreshing ai-skill-hub as a capability system and the output must stay layer-oriented instead of file-oriented. |
| metadata | {"triggers":["refresh ai-skill-hub system status","update skill-hub layer status and phase","generate a capability-system status summary","produce layer-oriented status for ai-skill-hub","summarize canonical distribution governance and tooling layers"],"side_effects":["read_only","write_files","requires_git"]} |
This execution-focused skill definition keeps the behavior, invocation shape, and adapter-facing contract unchanged while moving explanation-oriented content into supporting assets.
这个 pattern 的核心是：
update-project-status 收集近期系统信号Input:
ai-skill-hub 根目录skills/、.agents/、.github/、tools/、docs/status/Process:
scanunderstandstructureoutputOutput:
Layer StatusCurrent PhaseCapabilitiesStabilitymaturity_score这样组织的原因是，system status 的价值在于说明系统边界和成熟度，而不是把最近提交翻译成文件级流水账。底层刷新能力继续由 canonical skill update-project-status 提供，这个 wrapper 只负责 system-oriented 收口。
先复用 canonical status engine，再收口到 system output。
Reuse the canonical status engine before adding system-level framing.
输出必须按层表达，而不是按文件表达。
Express status by layers, not by files.
phase、capabilities 和 stability 是主口径。
Make phase, capabilities, and stability the primary vocabulary.
不把 system status 退化成项目日报。
Do not degrade system status into a project activity report.
写入动作仍保持最小化。
Keep writes minimal and scoped to system status artifacts.
读取 system context。
先把目标对象确认为 ai-skill-hub 自身，并读取 docs/status/skill-hub-status.md、README.md、skills/、distribution surfaces 和 tooling 入口。
调用 canonical status logic。
复用 update-project-status 的 scan -> understand -> structure -> output 方法收集 Git、working tree 和系统资产信号，但不要沿用普通项目视角输出。
建立 layer mapping。
把近期变化映射到 Canonical Skill Layer、Distribution Layer、Governance Layer、Tooling Layer 四层，并判断 phase 与 stability。
组织 system-oriented output。
输出必须至少包含 Layer Status、Current Phase、Capabilities、Stability；若需要写入状态文档，也应按这个结构落盘。
执行 freshness gate（时效门槛检查）。
读取状态文档中的 Updated at 时间；若距离当前日期超过 14 天，必须在输出中显式增加 Staleness 提示，并把该项写入 Risks / Gaps。若在门槛内，也应说明本次刷新已满足时效门槛。
回传风险与未确认项。
若证据不足，应明确说明哪些判断来自代码与文档证据，哪些仍需后续验证，避免把推断写成确定事实。状态输出可引用 shared assessment output protocol 的 evidence、open_questions、risk_priority 口径，并保留本 skill 的 phase_risk / freshness_risk 判断；不要强制使用 maturity_score。
处理与 system-handoff 的联动。
若本轮还要更新 docs/HANDOFF.md，应先完成 status 刷新，再把 Current Phase 和关键边界提供给 system-handoff；handoff 落盘前必须通过 phase consistency 检查。
update-project-status 作为 canonical dependency，不得复制出第二套状态刷新逻辑14 天未刷新，主输出必须显式包含 Staleness 提示system-handoff 联动执行，必须先更新 status，再校验 handoff phase 一致性ai-skill-hub 自身的状态，并强制输出 layer / phase / capability / stability 结构时使用。