CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ds-finalize

Use when the quest is ready to consolidate final claims, limitations, recommendations, summary state, and graph exports before stopping or archiving.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

73%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured process skill with an explicitly gated, feedback-looped workflow and unusually concrete tool-call guidance for an instruction-only skill. Its weaknesses are length and redundancy — several sections restate one another and dense enumerations (the manifest path list, memory rules) are inlined in SKILL.md instead of living in the existing references.

Suggestions

Move the 16-item paper-bundle manifest path inventory out of Workflow step 1 and into a references file (or fold it into finalization-checklist.md), keeping only the gate decision — 'verify the manifest inventory explicitly' — in SKILL.md.

Delete or merge the "Finalization-quality rules" good/weak lists with the workflow steps they restate (e.g., the claim-ledger and limitations steps already encode 'preserves negative evidence' and 'names open questions honestly'), keeping only the rules that add new information.

If the runtime's "Interaction discipline" contract is already injected by the system prompt (as the skill itself states), reduce that section to the finalize-specific deltas — the milestone-emission rule and the no-repeated-update rule — rather than restating the shared cadence rules.

DimensionReasoningScore

Conciseness

The body is mostly efficient, tight bullet prose with no explanations of concepts Claude already knows, but at ~340 lines it has noticeable redundancy: "Finalization-quality rules" (good/weak lists) restates the workflow's own guidance, "Required durable outputs" overlaps "Refresh the durable quest view", and the 16-line manifest path inventory (lines 134-149) plus the runtime-generic "Interaction discipline" block are detail that could be trimmed or moved to a reference file. It is above a 2 because there is no conceptual padding or filler — nearly every line is task-specific instruction — but below a 4 because several sections could be materially tightened.

3 / 5

Actionability

The guidance is highly concrete for an instruction-only skill: exact tool calls with parameters (`artifact.get_paper_contract_health(detail='full')`, `memory.list_recent(scope='quest', limit=5)`, `artifact.arxiv(paper_id=..., full_text=False)`), concrete file paths (`paper/paper_bundle_manifest.json`, `release/open_source/cleanup_plan.md`), an explicit claim taxonomy (supported / partially supported / unsupported / deferred), and named blocked-state labels. Not a 5 because several tool calls appear with elided signatures (`artifact.read_quest_documents(...)`, `memory.search(...)`) and no worked example of a claim-ledger or belief-change-log entry is shown inline; it is clearly above a 3 since the given commands are executable as written rather than pseudocode.

4 / 5

Workflow Clarity

The 7-step workflow is clearly sequenced (consolidate inventory → claim ledger → limitations → recommendation → resume packet → refresh views → record decision) and validation is explicit at every gate: the "Preconditions and gate" section hard-blocks finalization on enumerated open conditions, premature closure routes back through `decision` with named blocked finalize states, and the "Exit criteria" section defines durably-true completion conditions. This matches the 5 anchor — clear sequence, explicit validation, and a feedback loop for error recovery — so it sits above a 4, which would require missing checkpoints.

5 / 5

Progressive Disclosure

Structure is good: both bundle references exist, are cited in a dedicated "Extra references" section with a clear purpose ("denser closure checklist"), and are one level deep with no nested chasing. It falls short of a 5 because the SKILL.md itself is long and inlines dense detail that belongs in the bundle — notably the 16-path manifest inventory and the granular memory/artifact rules — where the 5 anchor expects that bulk detail to be split out; it is above a 3 because references are clearly signaled and the main file remains a navigable overview.

4 / 5

Total

16

/

20

Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that explicitly pairs a concrete consolidation capability list with clear closure-time triggers, in a distinct research-quest niche. Its only real limitation is modest keyword variation (no "finalize"/"wrap up"/"handoff" synonyms) and a single all-purpose verb.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "consolidate final claims, limitations, recommendations, summary state, and graph exports" — naming the domain and multiple specific deliverables. It falls short of a 5 because all actions hang off the single generic verb "consolidate" and coverage is incomplete (no mention of the claim ledger, resume/handoff packet, or final decision artifact that the body treats as core outputs); it is above a 3 because more than 1-2 specific actions are enumerated.

4 / 5

Completeness

It explicitly answers both parts: what it does ("consolidate final claims, limitations, recommendations, summary state, and graph exports") and when to use it ("Use when the quest is ready ... before stopping or archiving"), with concrete trigger phrasing around closure readiness. The 'when' clause is explicit and specific rather than weakly implied, matching the 5 anchor; it is written without first or second person, so no voice penalty applies.

5 / 5

Trigger Term Quality

Good keyword coverage with natural closure-oriented terms: "final claims", "limitations", "recommendations", "summary state", "stopping or archiving" — phrases a user would plausibly say when closing out a quest. Not a 5 because common variations like "finalize", "final report", "wrap up", "conclude", or "handoff" are missing; not a 3 because the present terms go beyond one or two generic keywords and capture multiple natural phrasings.

4 / 5

Distinctiveness Conflict Risk

It occupies a clear niche — research-quest closure with distinctive triggers like "quest", "graph exports", and "stopping or archiving" — that would not naturally fire for unrelated skills. The terms are domain-specific enough that overlap risk with generic summary or document skills is minimal, matching the 5 anchor.

5 / 5

Total

18

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

OpenLAIR/dr-claw

Path

skills/ds-finalize/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.