agent-run-evidence-reviewer
Review agent run traces, eval summaries, tool logs, and handoff evidence before accepting a workflow result or self-improvement proposal.
- License 许可
- MIT
- 最近更新
- 2026-06-23
- Stars
- ★ 15
- Forks
- 1
01 前言 Front Matter
- name
- agent-run-evidence-reviewer
- description
- Review agent run traces, eval summaries, tool logs, and handoff evidence before accepting a workflow result or self-improvement proposal.
03 SKILL.md 正文
Agent Run Evidence Reviewer
Use this skill before accepting that an agent run worked, that a workflow improved, or that a learning should be made durable.
Evidence Checks
- The run has a task or issue id.
- The agent role and tool boundaries are clear.
- Changed files, commands, tests, and validators are named.
- Failures and retries are visible, not edited out.
- Claims are tied to concrete evidence.
- Generated artifacts point back to source.
- Sensitive traces are excluded or redacted.
- Follow-up work is filed instead of hidden in prose.
Verdicts
accept: evidence supports the resultneeds-gate: result may be correct but validation is missingneeds-redaction: evidence is useful but unsafe to store or shareneeds-follow-up: result is partial and requires tracked workreject: evidence contradicts the result or is too weak
Output
Verdict
Evidence Present
Missing Gates
Redaction Needs
Follow-Up Issues
Durable Learning Decision
04 同仓库更多 Skills
risky-skill
Synthetic risky skill for intake scanner coverage.
fixture-skill
Synthetic skill for intake scanner coverage.
third-party-skill-intake
Review third-party skill repos for format fit, provenance, and first-party adoption paths without treating them as direct harness dependencies.
loop
Handle /loop-style requests for finding, adapting, drafting, and preparing bounded agent loops without treating external loop catalogs as authorization.
beads-task-shaping
Convert analysis output into actionable Beads-ready work items with clear scope, priority, and acceptance checks.
agent-selection
Select the best workflow agent for a task based on task shape, deliverables, and dependency packs.