CtrlK
BlogDocsLog inGet started
Tessl Logo

resilient-research-workflow

Unified workflow that delegates failed web searches to shell_agent for resilient data gathering, then applies anchored spreadsheet proof gates for verified Excel output

60

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./benchmarks/gdpval/skills/spreadsheet-proof-gate-merged/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

70%

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

The body is highly actionable with a clear gated workflow, but it is a monolithic ~450-line document with no progressive disclosure of detail into reference files. Splitting the verification template and criteria catalog into bundled references would improve navigation and token efficiency.

Suggestions

Move the verification script template and the criterion-type catalog into bundled reference files (e.g., references/verification_template.py, references/criteria.md) and link to them from the body.

Tighten repeated gate/restatement prose across the phases to reduce length and redundancy.

DimensionReasoningScore

Conciseness

Mostly procedural and actionable, but at ~450 lines it includes explanatory padding and restated gate logic that could be tightened; not every token earns its place.

2 / 3

Actionability

Provides fully executable code (search_web, shell_agent, an openpyxl verification script), concrete criterion types, and copy-paste-ready examples rather than pseudocode.

3 / 3

Workflow Clarity

Clear phased sequence (A/B/C) with explicit go/no-go gates (A, B, C4, C7) and feedback loops (verify, fix, re-run), matching the checklist-with-checkpoints anchor.

3 / 3

Progressive Disclosure

No bundle files exist and the skill is a monolithic single file with no references or navigation pointers; content that could be split (verification template, criteria catalog) is all inline.

1 / 3

Total

9

/

12

Passed

Description

67%

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

The description is specific and occupies a clear niche, but it omits an explicit "Use when..." trigger clause and leans on internal terminology over natural user keywords. Adding an explicit trigger clause would raise the completeness and trigger-term scores.

Suggestions

Append an explicit "Use when..." clause stating the situations that should trigger this skill (e.g., web research needed before building a verified Excel workbook).

Soften jargon ("anchored spreadsheet proof gates", "shell_agent") with natural user-facing keywords like "reliable web lookup", "Excel workbook", and "verified spreadsheet output".

DimensionReasoningScore

Specificity

Lists multiple concrete actions: "delegates failed web searches to shell_agent", "applies anchored spreadsheet proof gates for verified Excel output", matching the multi-action anchor.

3 / 3

Completeness

Clearly answers the "what" but lacks an explicit "Use when..." clause for the "when", which per the guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

Includes some natural terms ("web searches", "Excel", "spreadsheet") but leans on internal jargon like "shell_agent" and "anchored spreadsheet proof gates" rather than common user phrasings.

2 / 3

Distinctiveness Conflict Risk

The combined resilient-research plus spreadsheet-proof-gate niche is distinct and unlikely to trigger for unrelated skills.

3 / 3

Total

10

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
HKUDS/OpenSpace
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.