open-source-license-check
Veto GatesRequired pass for any deployment consideration
| Dimension | Result | Detail |
|---|---|---|
| Scientific Integrity | PASS | The archived audit treated this workflow as hypothesis or protocol support, not as a source of validated results. |
| Practice Boundaries | PASS | The legacy review kept this workflow on the evidence-access side of the boundary, not the advice-giving side. |
| Methodological Ground | PASS | The legacy audit preserved a method-grounded interpretation of the Check if referenced bioinformatics software/code licenses allow commercial use (GPL vs MIT, etc.) workflow. |
| Code Usability | PASS | The legacy audit did not flag code-usability issues for the packaged open-source-license-check workflow. |
Core Capability88 / 100 — 8 Categories
Medical TaskExecution Average: 83.6 / 100 — Assertions: 18/20 Passed
The Check if referenced bioinformatics software/code licenses allow... scenario completed within the documented Check if referenced bioinformatics software/code licenses allow commercial use (GPL vs MIT,... boundary.
Use this skill for evidence insight tasks that require explicit... remained well-aligned with the documented contract in the preserved audit.
The archived run for Check if referenced bioinformatics software/code licenses allow... 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 preserved weakness for End-to-end case for Scope-focused workflow aligned to: Check if referenced bioinformatics software/code licenses allow commercial use (GPL vs MIT, etc.) was concentrated in one point: 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