finalize
Use when the quest is ready to consolidate final claims, limitations, recommendations, summary state, and graph exports before stopping or archiving.
Best for Quest workflows needing cle…Works with GitHubLow risk
⌘source
- author
@ResearAI- language
- TypeScript
★2.3kstars
246forks
Apr 19, 2026
✦overview.md
Key Features
- ·Consolidates final claims, limitations, and recommendations
- ·Exports graph data before archiving
- ·Leaves a stable stopping point for resumption
- ·Provides concise progress updates at meaningful intervals
- ·Sends milestone artifacts for closure decisions
Use Cases
- →Closing a quest after completing core objectives
- →Pausing long-running work to resume later
- →Documenting final state before archiving a project
- →Providing a summary update after significant progress
Best for
- ✓Quest workflows needing clean pause/resume
- ✓Teams requiring documented closure states
Not ideal for
- !Immediate task execution
- !Real-time continuous interaction
FAQs
name
finalize
description
Use when the quest is ready to consolidate final claims, limitations, recommendations, summary state, and graph exports before stopping or archiving.
skill_role:stage
Finalize
Use this skill to close or pause a quest responsibly. The goal is to leave a stable stopping point and a clean resume path, not to keep rediscovering work that is already done.
Interaction discipline
- Follow the shared interaction contract injected by the system prompt.
- For ordinary active work, prefer a concise progress update once work has crossed roughly 6 tool calls with a human-meaningful delta, and do not drift beyond roughly 12 tool calls or about 8 minutes without a user-visible update.
- Do not emit another finalize progress update when the user-visible state is unchanged.
- If the runtime starts an auto-continue turn with no new user message, keep finalizing from the durable quest state and active requirements instead of replaying the previous user turn.
- If a threaded user reply arrives, interpret it relative to the latest finalize progress update before assuming the task changed completely.
- When finalize reaches a real closure state, pause-ready packet, or route-back decision, send one threaded
artifact.interact(kind='milestone', ...)update that names the recommendation, why it is the right call, and any reopen condition that still matters.
$install
1-click copynpx skills add ResearAI/DeepScientist --skill finalizeSafety assessment
★
Clarity score
How clear and easy to understand the SKILL.md instructions are, rated from 1 to 5.
3/ 5
goodMostly clear, but there are still a few confusing or poorly structured parts.
◎
Actionability score
How directly an agent can act on the SKILL.md instructions, rated from 1 to 5.
3/ 5
mediumPartially actionable with several concrete steps, but still missing important details.