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

94%

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

100%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 an exemplary compact reference: copy-paste ready examples, a precise parameter table, explicit anti-patterns and exclusions, and clean cross-links to sibling skills. There is no wasted token budget and no content that needs offloading to bundle files.

DimensionReasoningScore

Conciseness

The body is lean throughout: a compact intro line, a Quick Reference of six one-line JSON examples, a parameters table, and terse Anti-Patterns/When-NOT-to-use sections with no padding and no explanation of concepts Claude already knows. Every token earns its place, matching the 5 anchor.

5 / 5

Actionability

The Quick Reference provides copy-paste ready invocations covering the common cases (basic fetch, force_refresh, use_auth, section targeting, max_content_chars, browser actions), and the Parameters table specifies types and exact when-to-use guidance per flag. This matches the 5 anchor for fully executable, common-case-covering examples.

5 / 5

Workflow Clarity

This is a simple single-purpose skill where the single action (invoke with a URL plus optional parameters) is unambiguous, so the simple-skill exception applies. There are no destructive or batch operations requiring validation, and parameter selection is guided by the When-to-use table, Anti-Patterns, and When NOT to use sections.

5 / 5

Progressive Disclosure

The skill has no bundle files, and the ~70-line body is entirely overview-level content that is well organized into clear sections with nothing inlined that belongs in a separate file. The See Also links are one-level-deep pointers to sibling skills, keeping navigation simple and flat, matching the 5 anchor for a short skill with no need for external references.

5 / 5

Total

20

/

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 states concrete capabilities, gives explicit natural-language triggers for when to use the skill, and positions it against the built-in WebFetch alternative. The only gaps are missing trigger synonyms (e.g., "scrape") and incomplete boundary-drawing against closely related sibling skills.

DimensionReasoningScore

Specificity

"Local-first URL fetch with clean markdown, structured metadata, JS-rendered SPA support, authenticated browser sessions, PDFs, and content change detection" lists six concrete capabilities with comprehensive coverage. It exceeds the 4 anchor ('several specific actions; minor gaps') because no significant capability area is missing for a URL-fetch tool.

5 / 5

Completeness

The description explicitly answers both what ("Local-first URL fetch with clean markdown, structured metadata, JS-rendered SPA support...") and when ("Use when the user provides a URL, says 'fetch', 'get this page', 'read this URL'...") with concrete trigger phrases, matching the 5 anchor exactly. The "Prefer over built-in WebFetch" clause adds further usage guidance beyond the anchor example.

5 / 5

Trigger Term Quality

Natural phrasings like "says 'fetch', 'get this page', 'read this URL'" and "wants content from a specific webpage" are what users would actually say. It falls short of the 5 anchor because common synonyms such as "scrape", "open this link", or "download this page" are missing.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche (URL fetching) and explicitly differentiates from built-in WebFetch ("Prefer over built-in WebFetch for local cache reuse, browser-session auth"), but sibling skills like wigolo-extract and wigolo-crawl also operate on URLs, leaving minor overlap risk with closely related skills. This matches the 4 anchor better than 5, since the description alone doesn't fully delineate the boundary with those siblings.

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.