Agent Skills › uw-syfi/vibesys › report-progress

report-progress

GitHub

为长期多智能体任务生成定期进度报告,向读者清晰展示变更、信任度及决策。适用于调度汇报、节点暂停或查询状态场景。

skills/search/report-progress/SKILL.md uw-syfi/vibesys

Trigger Scenarios

收到状态查询请求 达到预定汇报时间点 任务执行到达关键节点

Install

npx skills add uw-syfi/vibesys --skill report-progress -g -y
More Options

Non-standard path

npx skills add https://github.com/uw-syfi/vibesys/tree/main/skills/search/report-progress -g -y

Use without installing

npx skills use uw-syfi/vibesys@report-progress

指定 Agent (Claude Code)

npx skills add uw-syfi/vibesys --skill report-progress -a claude-code -g -y

安装 repo 全部 skill

npx skills add uw-syfi/vibesys --all -g -y

预览 repo 内 skill

npx skills add uw-syfi/vibesys --list

SKILL.md

Frontmatter
{
    "name": "report-progress",
    "description": "Write a periodic progress report for a long-running multi-agent effort, so the reader can tell what changed, what to trust and what was decided for them. Use when an orchestrating lead reports on a schedule, at a stop, or when asked for status."
}

Report progress

The reader was away. A report tells them what changed since the last one, how much to trust it, and what you decided without them. It is not a log of what you did.

Steps

  1. Read the state, not your memory: plan files, measurement records, the agent list, git heads. Anything you cannot confirm from them is not reported as fact.
  2. Find the last report's time. Report only what happened since, and name that window.
  3. Write in this order:
    1. Headline: the current best result and how it moved, in a sentence a newcomer follows.
    2. Changed: each promotion or finding, in plain words, code name in parentheses.
    3. In flight: each running item, what it waits on, and when it should finish.
    4. Decisions made for the user: each choice, with the reason, so they can reverse it.
    5. Open for the user: choices you already made that they may want to reverse, and what only they can supply (access, credentials). Work continues meanwhile; never wait on a reply.
    6. Self-check: the checklist of the skill that asked for the report.
  4. Cut every line the reader cannot act on or use to judge trust.

Rules

  • The main text reads at a high level: what was done, why it matters, what it gained. Keep worker or agent ids, commit SHAs, record ids and plan numbers out of sentences. They appear only as a parenthetical reference after the item, such as "(plan-004, record 14, a1b2c3d)".
  • Every number is backed by a record, and says how many samples and against what base; the record and commit go in the parenthetical.
  • A number from an earlier head is labeled with that head. Never present it as current.
  • Separate verified (judged, recorded) from claimed (a worker's own number) from planned.
  • State caveats that change trust: shared hosts, few samples, unrun tests, checks not made.
  • An interim notice from an agent is not a result. Report a result only when it is final.
  • A failure is reported with its cause and what happens next, in the same place as a win.
  • If nothing changed, say so in one line and why; do not pad.
  • Idle capacity is reported with its reason.
  • Name work by what it does ("faster decode matrix multiplies"), never by an identifier.

Version History

  • 3a50e8b Current 2026-11-02 13:57

Same Skill Collection

.agents/skills/add-agent-provider/SKILL.md
.agents/skills/add-bundled-skill/SKILL.md
.agents/skills/build-client-feature/SKILL.md
.agents/skills/change-container-images/SKILL.md
.agents/skills/create-issue/SKILL.md
.agents/skills/enforce-rules/SKILL.md
.agents/skills/open-pr/SKILL.md
.agents/skills/review-pr/SKILL.md
.agents/skills/software-design/SKILL.md
.agents/skills/testing/SKILL.md
.agents/skills/vs-init/SKILL.md
.agents/skills/write-agent-prompt/SKILL.md
.agents/skills/write-docs/SKILL.md
.agents/skills/write-skills/SKILL.md
.agents/skills/write-vibesys-tests/SKILL.md
resources/chat-skills/reading-ideas/SKILL.md
resources/chat-skills/results-against-base/SKILL.md
resources/chat-skills/run-roles/SKILL.md
resources/chat-skills/steering-a-run/SKILL.md
resources/skills/dial9-tokio/skills/dial9-diagnose-long-poll/SKILL.md
resources/skills/dial9-tokio/skills/dial9-red-flags/SKILL.md
resources/skills/dial9-tokio/skills/dial9-runtime/SKILL.md
resources/skills/dial9-tokio/skills/dial9-toolkit/SKILL.md
resources/skills/dial9-tokio/skills/dial9-trace-analysis/SKILL.md
resources/skills/dial9-tokio/skills/dial9-trace-loading/SKILL.md
resources/skills/dial9-tokio/skills/dial9-trace-recipes/SKILL.md
resources/skills/dial9-tokio/skills/dial9-zoom-window/SKILL.md
resources/skills/kernel-correctness/SKILL.md
resources/skills/kernel-ncu-analysis/SKILL.md
resources/skills/kernel-performance/SKILL.md
resources/skills/kernel-rocprof-analysis/SKILL.md
resources/skills/microservice-optimization/SKILL.md
resources/skills/neuron-agentic-development/skills/neuron-nki-debugging/SKILL.md
resources/skills/neuron-agentic-development/skills/neuron-nki-docs/SKILL.md
resources/skills/neuron-agentic-development/skills/neuron-nki-profiling/SKILL.md
resources/skills/serving-systems/SKILL.md
skills/domains/dial9-tokio/dial9-rank-bottlenecks/SKILL.md
skills/domains/dial9-tokio/skills/dial9-diagnose-long-poll/SKILL.md
skills/domains/dial9-tokio/skills/dial9-red-flags/SKILL.md
skills/domains/dial9-tokio/skills/dial9-runtime/SKILL.md
skills/domains/dial9-tokio/skills/dial9-toolkit/SKILL.md
skills/domains/dial9-tokio/skills/dial9-trace-analysis/SKILL.md
skills/domains/dial9-tokio/skills/dial9-trace-loading/SKILL.md
skills/domains/dial9-tokio/skills/dial9-trace-recipes/SKILL.md
skills/domains/dial9-tokio/skills/dial9-zoom-window/SKILL.md
skills/domains/kernel-correctness/SKILL.md
skills/domains/kernel-ncu-analysis/SKILL.md
skills/domains/kernel-performance/SKILL.md
skills/domains/kernel-rocprof-analysis/SKILL.md
skills/domains/kernel-timeline-analysis/SKILL.md

Metadata

Files
0
Version
3a50e8b
Hash
7712f740
Indexed
2026-11-02 13:57

Accueil - Wiki
Copyright © 2011-2026 iteam. Current version is 2.156.0. UTC+08:00, 2026-11-18 09:08
浙ICP备14020137号-1