pleaseai/fetch
Fetch web content in multiple formats - HTML, JSON, plain text, Markdown, readable articles, and YouTube transcripts
72
90%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
92%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly articulates specific capabilities, provides explicit trigger conditions, and includes natural user-facing keywords. Its main weakness is potential overlap with WebFetch or similar web-fetching skills, though the description partially addresses this by positioning itself as a fallback. The description is well-structured and concise.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: fetching HTML pages, JSON APIs, plain text, readable article content, YouTube transcripts, and handling 403/access errors as a fallback to WebFetch. | 3 / 3 |
Completeness | Clearly answers both what ('Fetch web content in multiple formats using fetch MCP tools') and when ('Use when WebFetch fails with 403/access errors, when fetching HTML pages...') with explicit trigger guidance ('Triggers on mentions of fetching URLs, web scraping...'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'fetching URLs', 'web scraping', 'reading web pages', 'downloading content', 'accessing online resources', 'YouTube transcripts', 'JSON APIs', 'HTML pages'. These are terms users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | The description explicitly differentiates from WebFetch by mentioning it as a fallback for 403 errors, which helps. However, terms like 'fetching URLs', 'web scraping', and 'reading web pages' could overlap with other web-fetching skills. The relationship to WebFetch is clarified but could still cause confusion about when to use which. | 2 / 3 |
Total | 11 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, concise skill that efficiently maps out the available fetch MCP tools and when to use each one. Its main weakness is the lack of concrete invocation examples — showing at least one actual tool call with parameters would elevate actionability. The format selection guide and fallback guidance are practical additions that add value without bloat.
Suggestions
Add 1-2 concrete tool invocation examples showing actual parameters (e.g., a fetch_json call to an API endpoint and a fetch_markdown call to a web page) to make the skill fully copy-paste actionable.
Consider adding a brief note on common parameters these tools accept (e.g., headers, timeout) if any exist, or explicitly state that only a URL is required.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It avoids explaining what web fetching is or how MCP works, assumes Claude's competence, and every section serves a clear purpose. The table format is an efficient way to present tool options. | 3 / 3 |
Actionability | The tool names are concrete and the format selection guide is helpful, but there are no actual invocation examples showing parameters or expected responses. A single concrete example call (e.g., `mcp__fetch__fetch_json` with a URL and showing the returned structure) would make this fully actionable. | 2 / 3 |
Workflow Clarity | This is a simple, single-purpose skill (choose a tool, call it with a URL). The three-step process is clear and unambiguous. There are no destructive or batch operations requiring validation checkpoints, so the simple workflow is appropriate. | 3 / 3 |
Progressive Disclosure | For a simple skill under 50 lines with no need for external references, the content is well-organized into logical sections (when to use, available tools, how to use, format selection, fallback). No external files are needed and the structure supports easy scanning. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
Total | 10 / 11 Passed | |
Reviewed
Table of Contents