CtrlK
BlogDocsLog inGet started
Tessl Logo

web-researcher

Research topics across the web and compile structured insights for content creation.

59

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 ./apps/desktop/electron/default-skills/web-researcher/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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 body is a lean, well-structured instruction set with a clear sequenced workflow, explicit validation checkpoints (corroboration, flagging unverified claims), and a concrete output brief. It assumes Claude's intelligence throughout and organizes content cleanly for a skill that needs no external references.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — no padding about what the web is or how research works, every section (principles, approach, output format) earns its place. Not a 4 because there are no noticeable instances of over-explanation to trim.

5 / 5

Actionability

As an instruction-only skill it gives concrete guidance — a six-step research process and a fully specified output brief (Summary, Key findings, Stats & quotes, Angles, Gaps & caveats, Sources). Not a 5 because steps like 'Search broadly, then narrow' remain somewhat abstract without specifying concrete methods, and not a 3 because the output format and per-finding capture (claim + source + caveat) are concrete and actionable.

4 / 5

Workflow Clarity

The six numbered steps are clearly sequenced, with validation checkpoints in 'Corroborate before you report' (cross-reference two sources) and step 6 ('flag anything you couldn't verify or where sources disagree'). Not a 5 because there is no explicit error-recovery feedback loop (validate -> fix -> retry), and not a 3 because checkpoints are explicit rather than merely implicit.

4 / 5

Progressive Disclosure

At under 50 lines with no external references needed, the body is well-organized into clearly delineated sections (When to use, Research principles, How to approach, Output format), meeting the simple-skill exception for a top score. Not a 4 because organization is clean with no inline content that belongs in a separate file.

5 / 5

Total

18

/

20

Passed

Description

50%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 states a clear purpose and two concrete actions but omits any explicit 'Use when...' trigger guidance, capping completeness and limiting trigger-term coverage. It is reasonably specific but not sharply distinguished from adjacent research skills.

Suggestions

Add an explicit 'Use when...' clause with concrete trigger phrases (e.g., 'Use when backing a claim with data, surveying published material, or finding statistics and quotes for content').

Include natural synonyms users actually say — 'look up', 'find sources', 'gather information', 'fact-check' — alongside 'research' to broaden trigger coverage.

Add a one-line boundary statement distinguishing this from related skills (e.g., trend spotting or deep-dive fact-checking) to reduce conflict risk.

DimensionReasoningScore

Specificity

The phrase 'Research topics across the web and compile structured insights' names the domain and two concrete actions (research, compile) but is not comprehensive — no specifics on verification, sourcing, or output structure. Not a 2 because it names more than just the domain, and not a 4 because the actions remain generic rather than enumerating several specific concrete operations.

3 / 5

Completeness

It clearly answers 'what' ('Research topics across the web and compile structured insights for content creation') but has no 'Use when...' clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 3. Not a 4 because the 'when' is only weakly implied by 'for content creation', not explicitly stated.

3 / 5

Trigger Term Quality

Natural terms 'research topics', 'web', and 'content creation' are present, but common variations users actually say ('look up', 'find sources', 'gather information', 'fact-check') are missing. Not a 4 because coverage of natural synonyms is thin, and not a 2 because the keywords present are relevant rather than purely generic.

3 / 5

Distinctiveness Conflict Risk

'Web research for content creation' is somewhat specific but overlaps with general research, fact-checking, and trend-spotting skills (the body itself hands off to 'Trend Spotter', signalling overlap). Not a 4 because the niche is not sharply distinguished by the description alone, and not a 2 because it is more specific than a generic 'research' skill.

3 / 5

Total

12

/

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
holaboss-ai/holaOS
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.