observe
GitHub用于审查 Agent 近期会话是否遵循规则,读取本地钩子事件报告页面编辑、停止钩子及未关闭发现项等合规情况。
触发场景
安装
npx skills add plugin87/ux-ui-agent-skills --skill observe -g -y
SKILL.md
Frontmatter
{
"name": "observe",
"description": "Show whether the agent followed the kit's rules in recent sessions: pages edited and measured, Stop hook blocks, findings left open. Reads local hook events only.",
"disable-model-invocation": true
}
Step 0 - is the kit here? Check once:
ls ${CLAUDE_SKILL_DIR}/../../../scripts/observe.mjs >/dev/null 2>&1 && echo KIT_OK || echo KIT_MISSINGOnKIT_MISSINGonly the skill folders were installed. Say so, point the user at the plugin install ornpx ux-ui-agent-skills init, and stop.
Report what the hooks recorded - never a reconstruction from memory.
- Run
node ${CLAUDE_SKILL_DIR}/../../../scripts/observe.mjs --project "$CLAUDE_PROJECT_DIR"(or without--projectwhen the user asks about every project, and with--days Nwhen they name a window). - Quote the summary lines it prints. If it says no session edited UI, say that and stop: there is nothing to judge.
- For each session marked
BROKE A RULE, run it again with--session <id>and say which rule failed and the timeline line that shows it. - If the user wants the page, run it with
--html <path>and give the path.
What it measures, and what it does not: three counted rules per session -
every edited page had a passing gate before the end, no fast-gate finding was
left on a file's latest version, and the agent never finished while the Stop
hook still had pages open. It says nothing about design quality, and an
unfinished session is not counted for or against.
版本历史
- def84a7 当前 2026-11-03 02:21


