CtrlK
BlogDocsLog inGet started
Tessl Logo

pleaseai/fetch

Fetch web content in multiple formats - HTML, JSON, plain text, Markdown, readable articles, and YouTube transcripts

79

Quality

99%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

Overview
Quality
Evals
Security
Files

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a concise, well-organized overview that maps concrete fetch MCP tools to content types with a clear selection guide and fallback guidance. It respects token budget while remaining fully actionable for this simple, single-purpose skill.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it uses compact tables and short lists without explaining what URLs, HTML, or APIs are; every section earns its place.

3 / 3

Actionability

It gives concrete, copy-paste-ready guidance by naming exact MCP tools and mapping each to a content type; per rubric notes, an instruction-only skill without code is not penalized when guidance is actionable.

3 / 3

Workflow Clarity

For this simple single-purpose skill, the three-step sequence (choose format, call tool, process result) is unambiguous and no destructive/batch validation is required, so it qualifies for the top simple-skill anchor.

3 / 3

Progressive Disclosure

The body is under 50 lines with no external references needed and is organized into clear, well-signaled sections (When to Use, Available Tools, How to Use, Format Selection), meeting the top anchor for small self-contained skills.

3 / 3

Total

12

/

12

Passed

Description

100%

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 is concise, uses third person, and clearly states both capabilities and trigger conditions with concrete format examples and natural user keywords. It is a strong, well-scoped description.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions/formats: 'fetching HTML pages, JSON APIs, plain text, readable article content, or YouTube transcripts', matching the top anchor for listing several specific concrete actions.

3 / 3

Completeness

It explicitly answers both 'what' (fetch web content in multiple formats via fetch MCP tools) and 'when' with a 'Use when...' clause plus a 'Triggers on...' clause, matching the top anchor.

3 / 3

Trigger Term Quality

It enumerates natural user phrases ('fetching URLs, web scraping, reading web pages, downloading content, or accessing online resources') giving good coverage of terms users would actually say.

3 / 3

Distinctiveness Conflict Risk

It targets a clear niche (fetch MCP tools as fallback for WebFetch failures and specific content formats) with distinct triggers, making conflicts with other skills unlikely.

3 / 3

Total

12

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents