spinosa-evaluator

Audits completed research routes and recommends scoped framework edits.

7|Updated May 13, 2026
One-click install
npx skills add https://github.com/medialab/spinosa --skill spinosa-evaluator-medialab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spinosa-evaluator
Source: https://github.com/medialab/spinosa/tree/main/workspace-template/.opencode/skills/spinosa-evaluator
Command: npx skills add https://github.com/medialab/spinosa --skill spinosa-evaluator-medialab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After an AI research route finishes answering a question over a document collection, there is no built-in way to judge whether the process itself was sound or whether the framework should improve for future requests. This Skill closes that loop by auditing completed routes and recording process-quality findings. ## Core Features & Use Cases - Route Process Audit: Reads the original prompt, goal artifact, chain, produced artifacts, and verifier outcome, then classifies findings under categories like integrity_issue, route_selection_issue, evidence_handling_issue, and efficiency_issue. - Edit Decisioning: Decides between no_edit and edit_recommended, naming the exact control or doc files and the smallest safe change when an edit is justified. - Provenance Footer & Cleanup: Appends a Search Provenance footer built from the session evidence packet to the verified report, archives evidence packets to .spinosa/archive/, and moves session-scoped intermediate files to .trash/. - Use Case: After a verified answer report is produced for a research question over interview transcripts, run this Skill to write an audit report to agent_reports/e_{session_id}.md and decide whether the framework's routing or evidence-handling rules need a targeted fix. ## Quick Start Audit the completed route for this session and write the evaluation report with an edit decision to agent_reports.

Frequently Asked Questions about spinosa-evaluator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit a completed research route in Spinosa?▼

Run the evaluator after a non-fast-path route completes and its answer report is verified. It reads the prompt, goal artifact, chain, artifacts, and verifier outcome, then writes a structured audit report to agent_reports/e_{session_id}.md with a no_edit or edit_recommended decision.

What findings does the route evaluator classify?▼

Findings are classified under integrity_issue, route_selection_issue, sequence_issue, evidence_handling_issue, report_quality_issue, efficiency_issue, or contract_doc_drift. Each finding must be tied to concrete route evidence, and weak or speculative findings default to no_edit.

Can the evaluator edit framework files directly?▼

No. The evaluator never edits framework, control, raw, map, or dictionary files itself. It only recommends the smallest safe change and names the target control or doc files when it decides edit_recommended.

What files does the evaluator clean up after a route?▼

It archives evidence packets and appendices to .spinosa/archive/ and moves session-scoped intermediates like g_, analysis_, serendipity_, and janitor_ files to .trash/. Final reports (NN_*.md), audit reports, and extraction files are never moved.

When should the evaluator not recommend a framework edit?▼

It should prefer no_edit when findings are weak, speculative, or not actionable through control or doc changes. Recommendations apply only to future requests and never modify the already completed answer.