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

95%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

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

An exemplary lean tool-skill body: concrete, copy-paste-ready invocation examples, a complete parameter table, explicit anti-patterns and negative scope, and well-organized sections with clean cross-navigation. The only gap is missing when-to-use guidance for the render_js and mode option values.

Suggestions

Add a short 'when to use' note for each render_js value (auto/always/never) and mode value (cache/default/stealth), e.g. in the Parameters table or one line each.

Consider stating the default behavior when section matching fails or the heading is not found, so callers know whether to retry with section_index.

Dimension	Reasoning	Score
Conciseness	The body is a lean parameter table, six commented JSON examples, and terse anti-pattern/negative-scope sections; it assumes Claude's competence and contains no padding or explanation of known concepts. Every section earns its tokens.	5 / 5
Actionability	The Quick Reference JSON calls are copy-paste ready and cover the common cases (basic, cache bypass, auth, section targeting, truncation, browser actions), and the Parameters table maps every key to its type and when to use it.	5 / 5
Workflow Clarity	As a single-action tool skill, invocation is unambiguous (pass url, choose flags), but render_js ('auto/always/never') and mode ('cache/default/stealth') enumerate values without when-to-use guidance, leaving decision points at non-default values implicit. Not 3 because there is no destructive or batch operation requiring validation and the single action is fully clear; not 5 because those option choices are underspecified.	4 / 5
Progressive Disclosure	There are no bundle files; all content (parameter table, examples, scope boundaries) is appropriately inline for a compact tool skill, and the only references are one-level, clearly-signaled cross-links to sibling skills under 'See Also'.	5 / 5
	Total	19 / 20 Passed

Description

96%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 clearly and explicitly states both what the skill does and when to use it, with concrete natural-language triggers and explicit differentiation from the built-in WebFetch. The only weakness is minor overlap risk with sibling web-fetch/extract skills from the generic 'fetch' trigger.

Dimension	Reasoning	Score
Specificity	The description enumerates six concrete capabilities ('clean markdown, structured metadata, JS-rendered SPA support, authenticated browser sessions, PDFs, and content change detection'), matching the comprehensive-coverage anchor; not 4 because no capability area is left as a gap.	5 / 5
Completeness	The first sentence explicitly states what the skill does and the 'Use when...' clause states when to use it with concrete trigger phrases, exactly matching the anchor-5 example pattern.	5 / 5
Trigger Term Quality	'Use when the user provides a URL, says "fetch", "get this page", "read this URL", or wants content from a specific webpage' covers the natural phrasings users would actually say, including command-style and conversational synonyms. Not below 5 since no common variation is missing.	5 / 5
Distinctiveness Conflict Risk	It carves a clear niche and explicitly distinguishes itself from built-in WebFetch ('Prefer over built-in WebFetch for local cache reuse...'), but the bare trigger 'fetch' and shared web-domain vocabulary overlap with closely related sibling skills (wigolo-search/extract/crawl), fitting 'mostly distinct; minor overlap risk' rather than the minimal-conflict 5 anchor.	4 / 5
	Total	19 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
relative_links	Relative link issues: 3 suspicious	Warning

	Total	15 / 16 Passed

Repository: KnockOutEZ/wigolo
Path: skills/wigolo-fetch/SKILL.md
Commit: da59eee

Reviewed: 9 days ago

Table of Contents

Discovery Implementation Validation

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.