CtrlK
BlogDocsLog inGet started
Tessl Logo

web-reader

Read web pages, articles, and document links by converting URLs into Markdown text. Use the `read_url` tool directly, without bash.

64

Quality

76%

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

Fix and improve this skill with Tessl

tessl review fix ./a_全网优秀资源/10_大模型/07_skill包/vibe_trading_skills/web-reader/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%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 a tight, executable, well-organized guide for a simple tool skill, with copy-paste examples, useful failure-mode notes, and clean sectioning; its only blemish is a duplicated example between Usage and Common Usage.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, but the 'Common Usage' section repeats the same tushare URL example already shown in Usage, which is minor redundancy that could be trimmed, fitting the 'efficient with minor over-explanation' anchor rather than a clean 5.

4 / 5

Actionability

It provides copy-paste-ready, fully executable tool calls (read_url(url=...)) with the JSON return shape and concrete examples spanning API docs, articles, and GitHub, matching the 'fully executable; copy-paste ready; covers common cases' anchor.

5 / 5

Workflow Clarity

This is a simple single-purpose skill whose single action (call read_url) is unambiguous, and it documents a fallback (HTTP 451 -> bash+requests), so per the simple-skill exception workflow clarity scores 5.

5 / 5

Progressive Disclosure

At under 50 lines with no need for external references, the body is organized into clear, well-signaled sections (Purpose, Usage, Notes, Common Usage) with no nested references, meeting the simple-skill bar of 5 for progressive disclosure.

5 / 5

Total

19

/

20

Passed

Description

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

The description is clear and reasonably specific about converting URLs to Markdown, with decent trigger terms, but it omits an explicit 'when to use' trigger clause, which caps its completeness and leaves it short of the top tier.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when the user asks to read a web page, article, or document link, or fetch URL content as text.'

Expand the action coverage beyond a single verb (e.g. mention extracting content, retrieving docs) to lift specificity toward a 5.

Include a couple of natural synonyms users say ('fetch a URL', 'scrape a page', 'web content') to round out trigger-term coverage.

DimensionReasoningScore

Specificity

The description names the domain ('web pages, articles, and document links') and one concrete action ('converting URLs into Markdown text'), but offers only that single action rather than a comprehensive set, matching the anchor for naming a domain with 1-2 concrete actions.

3 / 5

Completeness

It clearly states what the skill does ('Read web pages... by converting URLs into Markdown text') but lacks an explicit 'Use when...' trigger clause; the phrase 'Use the read_url tool directly, without bash' describes how, not when, so per the guideline completeness caps at 3.

3 / 5

Trigger Term Quality

It includes natural terms users would say ('web pages', 'articles', 'document links', 'URLs', 'Markdown') with good coverage, though it omits common synonyms like 'fetch', 'scrape', or 'web content', fitting the 'good coverage with a few terms missing' anchor.

4 / 5

Distinctiveness Conflict Risk

The URL-to-Markdown conversion niche is mostly distinct with only minor overlap risk against generic fetch/scrape skills, matching the 'mostly distinct; minor overlap risk' anchor rather than the broader score-3 anchor.

4 / 5

Total

14

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
charliedream1/ai_quant_trade
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.