CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

wigolo-fetch

Local-first URL fetch with clean markdown, structured metadata, JS-rendered SPA support, authenticated browser sessions, PDFs, and content change detection. Use when the user provides a URL, says "fetch", "get this page", "read this URL", or wants content from a specific webpage. Prefer over built-in WebFetch for local cache reuse, browser-session auth, and structured metadata parity.

Quality

89%

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

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.

A tight, well-organized body that documents parameters and decision boundaries efficiently, with strong anti-pattern guidance and clear cross-skill navigation. The single notable weakness is that the actual invocation mechanism (how the JSON payloads are executed) is left implicit, which slightly caps both actionability and workflow clarity.

Suggestions

State the invocation entry point explicitly (e.g. the CLI command or tool name that consumes the Quick Reference JSON) so the examples are fully copy-paste executable.

Add a one-line note in the Output section on how to verify a fetch succeeded or handle failures (e.g. checking cached/error fields), tightening the workflow's feedback loop.

DimensionReasoningScore

Conciseness

Lean and efficient throughout: a table-based parameter reference, terse commented JSON quick-reference examples, and no explanations of concepts Claude already knows — every section earns its tokens, matching the anchor-5 profile.

5 / 5

Actionability

The Quick Reference provides concrete JSON examples covering the common cases (basic, refresh, auth, section targeting, actions), but the invocation entry point — what command or tool consumes this JSON — is never stated, a minor executability gap that keeps it below fully copy-paste-ready.

4 / 5

Workflow Clarity

As a single-action skill it has clear decision guidance (Anti-Patterns, 'When NOT to use', an explicit output contract), but the implicit invocation mechanism leaves the single action slightly ambiguous, so it falls just short of the unambiguous-single-action bar for a 5.

4 / 5

Progressive Disclosure

No bundle files exist and none are needed: the body is cleanly organized into Quick Reference, Parameters, Output, Anti-Patterns, When NOT to use, and See Also, with one-level, clearly-signaled cross-skill references and nothing inlined that belongs in a separate file — easy navigation throughout.

5 / 5

Total

18

/

20

Passed

Description

88%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 concretely enumerates capabilities and provides an explicit 'Use when' clause with natural quoted trigger phrases, plus a rare explicit conflict-resolution statement against the built-in WebFetch. The only gaps are a few missing natural synonyms and no in-description delineation from closely related sibling skills.

Suggestions

Add one or two common trigger synonyms (e.g. 'open this link', 'download this page') to the 'Use when' clause for fuller natural-term coverage.

Add a brief boundary clause distinguishing this from sibling skills (e.g. 'For structured data or multi-page crawls, use wigolo-extract / wigolo-crawl instead') to reduce overlap risk at the description level.

DimensionReasoningScore

Specificity

Lists six concrete capabilities ('clean markdown, structured metadata, JS-rendered SPA support, authenticated browser sessions, PDFs, and content change detection'), giving comprehensive coverage of what the skill does — matching the anchor-5 density rather than the minor-gaps profile of anchor 4.

5 / 5

Completeness

Explicitly answers both 'what' (the capability sentence) and 'when' ('Use when the user provides a URL, says "fetch", "get this page", "read this URL"...') with concrete trigger phrases, structurally identical to the anchor-5 example.

5 / 5

Trigger Term Quality

Includes natural quoted phrases users would actually say ('fetch', 'get this page', 'read this URL') plus 'provides a URL' and 'wants content from a specific webpage', but misses common synonyms such as 'open this link', 'download', or 'scrape', so coverage is good rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

The single-URL fetch niche is clear and it explicitly disambiguates against the built-in ('Prefer over built-in WebFetch...'), but closely related sibling skills (extract, crawl, search) share URL-adjacent triggers and are not delineated within the description itself — minor overlap risk, not the minimal-conflict profile of anchor 5.

4 / 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

relative_links

Relative link issues: 3 suspicious

Warning

Total

15

/

16

Passed

Repository

KnockOutEZ/wigolo

Path

skills/wigolo-fetch/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.