CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

fulltext-fetcher

Fetch and save the original HTML of scientific literature webpages when given a URL, DOI, or PubMed PMID (triggered when you need archival-grade page HTML for downstream parsing or review).

Quality

73%

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 ./scientific-skills/Other/fulltext-fetcher/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

56%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 core skill-specific content (sections 1–5 of the numbered doc) is genuinely strong: executable commands matching the real script, explicit inputs/outputs, allowlist behavior, and a concrete verification checklist. However, it is buried in a second, generic template document that duplicates every section and includes a fabricated expected-output format, costing it conciseness and navigability.

Suggestions

Delete the duplicated generic template sections (the leading 'When to Use / Key Features / Dependencies / Example Usage / Implementation Details / Validation Shortcut' scaffold and the trailing 'When Not to Use / Required Inputs / Recommended Workflow / Output Contract / ...' boilerplate), keeping only the concrete numbered fulltext-fetcher content.

Remove or correct the fabricated "Expected output format" block under Quick Validation — the script writes one .html file per input to the output directory, not a fulltext_fetcher_result.md with a PASS/FAIL validation summary.

Merge the overlapping validation sections (Validation Shortcut, Verification checklist, Quick Validation, Completion Checklist) into one authoritative checklist so a single workflow path is unambiguous.

DimensionReasoningScore

Conciseness

The body concatenates two parallel documents (a generic scaffold plus a numbered '# fulltext-fetcher' doc) with heavy vacuous filler such as "Use this skill when the request matches its documented task boundary" and "Produce the expected output using the documented file format, schema, or narrative structure", and duplicated When-to-Use / Example-Usage / Validation-Shortcut sections — noticeably verbose with several padded sections (anchor 2). It is not anchor 1 because it never explains concepts Claude already knows (e.g., no 'what is a DOI' primer).

2 / 5

Actionability

The examples are concrete, copy-paste-ready commands matching the actual script's interface (`--url "https://example.org/page"`, `--doi "10.1038/s41586-020-2649-2"`, `--pmid "23273568"`, `--out-dir "outputs"`, `--allow-all`) and cover the common cases. It falls short of anchor 5 because the "Expected output format" block ("Result file: fulltext_fetcher_result.md / Validation summary: PASS/FAIL") is fabricated — the script writes .html files, not a result markdown — and the actual output filename convention is never stated.

4 / 5

Workflow Clarity

This is a batch skill, but validation is present ("Generated `.html` files exist and are **non-empty**", "ensure output paths do not collide (use distinct `--out-dir` values)"), so the batch cap does not apply; the verification checklist is explicit and the run-then-verify sequence is unambiguous. It stays at anchor 4 rather than 5 because the duplicated generic workflow sections and the fabricated expected-output block create minor validation confusion.

4 / 5

Progressive Disclosure

Bundle references check out (scripts/fulltext_fetcher.py and validate_skill.py both exist and are accurately referenced), and sections have headers, but two parallel document structures — the generic 'When to Use / Key Features / Example Usage' scaffold alongside the numbered '# fulltext-fetcher' sections — leave it ambiguously organized, matching anchor 3 (could be better organized) rather than the well-organized anchor 4.

3 / 5

Total

13

/

20

Passed

Description

78%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, specific description that clearly states what the skill does and when to use it, with good natural trigger keywords. Its main flaws are the second-person "when you need" phrasing (which costs specificity under the third-person-voice rule) and missing common synonyms like "fulltext" or "article".

Suggestions

Rewrite the trigger clause in third person, e.g. "Use when archival-grade page HTML is needed for downstream parsing or review, or when the user provides a URL, DOI, or PubMed PMID".

Add natural trigger terms users would actually say, such as "fulltext", "full text", "article", "paper", or "landing page".

DimensionReasoningScore

Specificity

"Fetch and save the original HTML of scientific literature webpages when given a URL, DOI, or PubMed PMID" lists several concrete actions with named input types (raw anchor 4), but the second-person clause "when you need archival-grade page HTML" triggers the rubric's third-person-voice penalty, reducing specificity by 1.

3 / 5

Completeness

The description explicitly answers both what ("Fetch and save the original HTML of scientific literature webpages when given a URL, DOI, or PubMed PMID") and when ("triggered when you need archival-grade page HTML for downstream parsing or review") with concrete trigger phrases, matching anchor 5 rather than anchor 4 where the when-clause would only be weakly specified.

5 / 5

Trigger Term Quality

Natural keywords users would say are present ("URL", "DOI", "PubMed PMID", "HTML", "archival-grade", "parsing", "review"), but common variations such as "fulltext", "full text", "article", "paper", or "landing page" are missing, so it matches anchor 4 rather than a comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

The DOI/PMID/PubMed/archival-HTML framing gives it a clear literature-fetching niche, but the core action "fetch and save" HTML could overlap with a generic web-fetching or scraping skill, matching anchor 4 (minor overlap risk) rather than the minimal-conflict anchor 5.

4 / 5

Total

16

/

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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Other/fulltext-fetcher/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.