patent-claim-mapper
Use when mapping patent claims to products, analyzing patent infringement, or preparing freedom-to-operate analyses. Compares patent claims against product features for biotech and pharmaceutical IP assessment.
Veto GatesRequired pass for any deployment consideration
| Dimension | Result | Detail |
|---|---|---|
| Scientific Integrity | PASS | The legacy review kept patent-claim-mapper tied to supported scientific content rather than invented findings. |
| Practice Boundaries | PASS | The package stayed in retrieval, extraction, or evidence-organization scope rather than drifting into unsupported interpretation. |
| Methodological Ground | PASS | The workflow stayed grounded in its declared rubric or scale-selection logic rather than improvised criteria. |
| Code Usability | PASS | The legacy audit did not flag code-usability issues for the packaged patent-claim-mapper workflow. |
Core Capability88 / 100 — 8 Categories
Medical TaskExecution Average: 83.6 / 100 — Assertions: 18/20 Passed
The archived evaluation treated Use when mapping patent claims to products, analyzing patent... as a clean in-scope run.
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 Use when mapping patent claims to products, analyzing patent... 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.
This stress case was mostly intact, but the archived review centered its concern on: 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