finalize

Consolidates research quest evidence into final claims, limitations, recommendations, and handoff packets.

Updated Apr 1, 2026
One-click install
npx skills add https://github.com/zniihgnexy/vid_tokenizer --skill finalize-zniihgnexy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: finalize
Source: https://github.com/zniihgnexy/vid_tokenizer/tree/main/.ds/codex-home/skills/deepscientist-finalize
Command: npx skills add https://github.com/zniihgnexy/vid_tokenizer --skill finalize-zniihgnexy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Long-running research quests often end ambiguously, with unclear claim status, lost negative results, and no clean stopping point. This Skill closes or pauses a quest responsibly by producing an accurate final state: what is supported, what failed, what remains open, and whether to stop, archive, publish, or continue later. ## Core Features & Use Cases - Claim Ledger Construction: Classifies every major outcome as supported, partially supported, unsupported, or deferred, with evidence paths, caveats, and a belief-change log preserving downgrade history. - Closure Gating: Blocks premature finalization when evidence gaps, unresolved outline items, or unmapped analysis remain, routing back through the decision stage instead of forcing closure. - Resume and Handoff Packets: Produces compact restart packets naming the accepted baseline, strongest evidence, top blockers, and do-not-repeat notes for future continuation. - Use Case: After a multi-week experiment campaign with a paper bundle, use this Skill to verify the bundle manifest, refresh SUMMARY.md and status.md, record the final stop-or-publish decision, and leave a recoverable checkpoint. ## Quick Start Ask the agent to finalize the current quest by consolidating the accepted evidence, building the claim ledger, and recording a final stop, archive, or continue-later recommendation.

Frequently Asked Questions about finalize

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

FAQPage Schema
How do I finalize a long-running research quest?▼

Gather the latest baseline, run, analysis, and writing states, then build a claim ledger classifying each outcome as supported, partial, unsupported, or deferred. Refresh SUMMARY.md and status.md, record an explicit final decision, and leave a resume packet if continuation is plausible.

What should a research final report include?▼

A strong final report includes the executive state, strongest supported findings, negative results worth preserving, limitations, packaging status, a clear recommendation, and reopen conditions. It should distinguish supported claims from hopes rather than claiming everything succeeded.

When should a quest not be finalized?▼

Do not finalize when major evidence gaps remain unresolved, required outline items are open, or completed analysis is unmapped into the paper contract. In those cases, route back through the decision stage instead of forcing closure.

How do I create a handoff packet for a paused project?▼

Record the current objective and stage, the accepted baseline with reproducibility status, the top two or three results with evidence paths, open blockers, the single best next action, and do-not-repeat notes covering failed branches and tooling pitfalls.

Why preserve negative results and failed branches in a final summary?▼

Negative results and failed branches prevent future agents from repeating dead ends and keep the claim ledger honest. Silently deleting downgrade history overclaims the work and corrupts the durable record needed for resumption or publication.