CtrlK
BlogDocsLog inGet started
Tessl Logo

search-fallback-workflow

Graceful degradation workflow for continuing tasks when web search tools fail, using internal knowledge with verification caveats

48

Quality

60%

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

Fix and improve this skill with Tessl

tessl review fix ./benchmarks/gdpval/skills/search-fallback-workflow/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

58%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.

The content is a well-structured, self-contained workflow with a clear sequence and verification checkpoint, but it relies on pseudocode and repeated template material rather than fully executable guidance, which caps actionability and adds some verbosity.

Suggestions

Replace the pseudocode block with executable code (or explicitly justify why pseudocode is appropriate) to lift actionability above 3.

Consolidate the three overlapping markdown templates (Implementation Template, Example Output Structure, Flag for Verification) into one canonical structure to reduce repetition.

Add a small validate/fix/retry loop (e.g. re-attempt search once before fully committing to the fallback) to push workflow clarity toward 5.

DimensionReasoningScore

Conciseness

Mostly efficient with clear sections, but the template, pseudocode, example output, and best-practices list repeat the same verification-flagging idea multiple times, adding padding that could be tightened.

3 / 5

Actionability

It provides templates and a labeled pseudocode block, but the code is explicitly 'Pseudocode for search fallback detection' rather than executable, and the guidance stays high-level with placeholders like [specific reference].

3 / 5

Workflow Clarity

The five-step Core Pattern is clearly sequenced with a detection threshold (2 failures) and an explicit verification-flagging checkpoint; it stops just short of 5 because there is no validate/fix/retry loop for the produced output.

4 / 5

Progressive Disclosure

The body is well-organized into focused sections with no bundle files to reference; for a self-contained skill under 50 logical lines of guidance this is good structure, with only minor inline template bulk keeping it from 5.

4 / 5

Total

14

/

20

Passed

Description

41%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.

The description identifies a clear niche (search-tool failure fallback) but lacks an explicit 'Use when...' trigger and concrete actions, and its natural trigger terms are sparse. It is more abstract than the strong exemplars, which cap specificity and trigger quality.

Suggestions

Add an explicit 'Use when ...' clause naming natural trigger phrases (e.g. 'Use when web search is unavailable, rate-limited, or repeatedly failing').

Replace abstract phrasing with concrete actions the skill performs (e.g. 'Detects repeated search failures, continues with verified internal knowledge, and flags unverified claims for follow-up').

Include common synonyms a user might say ('search down', 'no internet access', 'offline', 'answer without search') to improve trigger term coverage.

DimensionReasoningScore

Specificity

The description names a workflow domain but actions are minimal and generic ('degradation workflow', 'continuing tasks') with no concrete mechanism named beyond 'using internal knowledge'.

2 / 5

Completeness

It conveys the 'what' (fallback workflow using internal knowledge) but lacks an explicit 'Use when...' trigger clause, capping completeness at 3 per the missing-trigger guidance.

3 / 5

Trigger Term Quality

It mentions 'web search tools fail' and 'verification caveats' but omits the natural phrases a user would say ('search is down', 'no internet', 'answer without search'); coverage is thin and lacks synonyms.

2 / 5

Distinctiveness Conflict Risk

The trigger (search tool failure) is a fairly distinct niche with limited overlap risk against typical skills; only minor overlap with general error-handling skills keeps it just below 5.

4 / 5

Total

11

/

20

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.

Validation — 16 / 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.