CtrlK
BlogDocsLog inGet started
Tessl Logo

research-fallback

Handle web research failures by pivoting to internal knowledge for content generation

49

Quality

62%

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/research-fallback/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

52%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 skill is well-structured with a clear pivot workflow and explicit failure-detection checkpoint, but it is notably verbose due to redundant restatements across Best Practices and Example sections. Actionability is decent for an instructional skill but lacks fully executable specifics.

Suggestions

Remove redundancy: collapse 'Best Practices' and 'Example Application' into the workflow steps they restate, since both largely duplicate Steps 3-4 and the decision flow.

Add an explicit verification checkpoint before file creation (e.g., 'review generated content for claims that require current sourcing before producing the deliverable').

Tighten Step 4's disclaimer list into a single concise checklist to reduce token overhead while preserving the guidance.

DimensionReasoningScore

Conciseness

The body is noticeably verbose: 'Best Practices' restates Steps 3-4 and the 'Example Application' duplicates the already-shown decision flow, adding several padded sections beyond 'some' over-explanation.

2 / 5

Actionability

Concrete sequence and failure signals are provided along with a worked example, but the guidance is instructional rather than executable code and stops short of fully copy-paste-ready specifics.

3 / 5

Workflow Clarity

A clear 5-step sequence with an explicit pivot checkpoint ('After 1-2 attempts, proceed to Step 3') is present; minor validation gap is the absence of an output-quality verification step before delivery.

4 / 5

Progressive Disclosure

No bundle files exist; the single-file skill is well-organized with clear section headers (When to Use, Workflow Steps, Best Practices, When NOT to Use) and no nested references, though it runs slightly long.

4 / 5

Total

13

/

20

Passed

Description

53%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 clearly states what the skill does but lacks an explicit 'Use when' trigger clause and natural user-facing keywords, capping completeness and trigger quality at 3. It occupies a reasonably distinct niche with minor overlap from the generic 'content generation' framing.

Suggestions

Add an explicit 'Use when...' clause naming concrete trigger situations (e.g., 'Use when search_web or read_webpage fail after retries').

Include natural user phrases such as 'web search failed', 'search unavailable', or 'can't reach the web' to improve trigger matching.

Tighten 'for content generation' to a more specific deliverable scope to reduce overlap with general content skills.

DimensionReasoningScore

Specificity

Names the domain ('web research failures') and 1-2 concrete actions ('pivoting to internal knowledge', 'content generation'), but coverage is not comprehensive.

3 / 5

Completeness

The 'what' is clearly stated but there is no explicit 'Use when...' clause; per rubric guidance a missing explicit trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Relevant domain keywords ('web research', 'research failures', 'internal knowledge') are present but natural user trigger phrases like 'web search isn't working' or 'search failed' are missing.

3 / 5

Distinctiveness Conflict Risk

The web-research-failure niche is mostly distinct with minor overlap risk from the broad 'content generation' phrasing; not a clean 5 because of that overlap.

4 / 5

Total

13

/

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.