retraction-watcher
Veto GatesRequired pass for any deployment consideration
| Dimension | Result | Detail |
|---|---|---|
| Scientific Integrity | PASS | The legacy review kept outputs in proposal or planning mode rather than presenting them as completed experimental findings. |
| Practice Boundaries | PASS | Practice boundaries held because the package remained focused on source handling, lookup, or structured evidence use. |
| Methodological Ground | PASS | The legacy audit preserved a method-grounded interpretation of the Automatically scan document reference lists and check against Retraction workflow. |
| Code Usability | PASS | The archived review found the packaged execution path for retraction-watcher usable in its intended context. |
Core Capability88 / 100 — 8 Categories
Medical TaskExecution Average: 83.6 / 100 — Assertions: 18/20 Passed
The Automatically scan document reference lists and check against Retraction scenario completed within the documented Automatically scan document reference lists and check against Retraction boundary.
The Use this skill for evidence insight tasks that require explicit... scenario completed within the documented Automatically scan document reference lists and check against Retraction boundary.
The archived run for Automatically scan document reference lists and check against Retraction confirmed the helper entrypoint and left the workflow in a stable state.
Packaged executable path(s): scripts/main.py remained well-aligned with the documented contract in the preserved audit.
The main issue in this stress run was: The output stays within declared skill scope and target objective.
Key Strengths
- Primary routing is Evidence Insight with execution mode B
- Static quality score is 88/100 and dynamic average is 83.6/100
- Assertions and command execution outcomes are recorded per input for human review