CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

literature-close-read

Produce a structured close-reading report from a paper's full PDF-to-Markdown text (with `## Page XX` pagination and image references) when you need to systematically extract background, research questions, methods, results, limitations, and reproducible experimental details.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Evidence Insight/literature-close-read/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

60%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 delivers a clear, well-sequenced workflow with explicit validation checkpoints at both ends and correctly referenced, existing one-level-deep bundle files. Its main weakness is verbosity — roughly a third of the sections are generic boilerplate or redundant restatements — plus minor inconsistencies (conflicting output filenames, a placeholder pdf-extract command) that slightly dilute actionability.

Suggestions

Cut the generic boilerplate sections (Required Inputs, Quick Validation, User Checkpoints, Input Validation) that merely restate Validation and Safety Rules, and state each rule once — e.g., the "write 'Not specified', never fabricate" rule is repeated three times and can live only in Step 6; this directly targets the conciseness score.

Resolve the conflicting output filenames: the example shows "outputs/paper_close_reading.md" while Steps 7 and the Output Contract mandate "outputs/literature_close_read_result.md" — pick one deterministic name and use it everywhere to close the actionability gap.

Either specify the pdf-extract dependency version and a real conversion command, or drop the Dependencies section and the placeholder "pdf-extract paper.pdf > paper.md" example that is flagged as depending on the local installation.

DimensionReasoningScore

Conciseness

The body is noticeably padded with generic boilerplate sections that add no skill-specific value: "Required Inputs" ("A clearly specified task goal aligned with the documented scope", "All required files, identifiers, parameters, or environment variables before execution"), "Quick Validation" ("No local script validation step is required for this skill"), "User Checkpoints", and "Input Validation" largely duplicate "Validation and Safety Rules" and "When Not to Use". The same rules are also restated within the workflow ("Not specified" — never fabricate appears in Steps 3 and 6 and again in Implementation Details; the UTF-8/valid-Markdown requirement appears three times). Not a 1 because it never explains concepts Claude already knows and the core workflow content is on-topic; more than a 3 because at least four sections are template filler rather than a single instance of over-explanation.

2 / 5

Actionability

The guidance is mostly concrete and directly followable: "Use `assets/deep_reading_template.md` as your output structure", "Save to `outputs/literature_close_read_result.md`", and an explicit fallback rule ("If any field is not explicitly stated, write 'Not specified' — do NOT infer"). Minor gaps keep it from a 5: the example command "pdf-extract paper.pdf > paper.md" is a placeholder ("exact command/options depend on your local pdf-extract installation"), the dependency is listed as "version: not specified", and the example output name "outputs/paper_close_reading.md" conflicts with the mandated "literature_close_read_result.md". It is above a 3 because these are detail-level gaps, not missing key steps — the 7-step instruction path is specific and executable as written.

4 / 5

Workflow Clarity

A clear 7-step sequence runs from "Step 1: Validate Input" ("Confirm the user has provided the paper content") through "Step 7: Quality Check" ("Verify every claim traces back to explicit paper content"), with a Failure Handling section covering recovery. Not a 5 because there is no explicit loop-back instruction when the Step 7 quality check fails (the feedback loop is only implicit via Failure Handling), and the validation checkpoints, while present at both ends, do not include intermediate checkpoints. Not a 3 because validation is explicit rather than absent or merely implicit, and the sequence has no gaps.

4 / 5

Progressive Disclosure

The body cleanly signals two one-level-deep references that both exist in the bundle — "Requirements/checklist: `references/guide.md`" and "Output template: `assets/deep_reading_template.md`" — repeated under "Files used" and inside the relevant workflow steps, making navigation easy. Not a 5 because content is not optimally split: the body inlines much of what guide.md already contains (input/output checklists, quality checks, format rules), creating duplication between SKILL.md and the reference rather than a lean overview pointing to details. Not a 3 because references are clearly signaled, shallow, and well organized.

4 / 5

Total

14

/

20

Passed

Description

83%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 produces and when to use it, with concrete input-format details and good domain keywords. Minor deductions come from second-person phrasing ("when you need to") and missing natural synonyms like "literature" or "summarize" that users might say.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "Produce a structured close-reading report" and "systematically extract background, research questions, methods, results, limitations, and reproducible experimental details" — which is comprehensive coverage matching the 5 anchor. However, the second-person phrasing "when you need to systematically extract" triggers the explicit third-person-voice penalty (reduce specificity by 1), landing it at 4. It is not a 3 because the actions named are specific and comprehensive, not just 1-2 generic ones.

4 / 5

Completeness

It explicitly answers both parts: what it does ("Produce a structured close-reading report from a paper's full PDF-to-Markdown text") and when to use it ("when you need to systematically extract background, research questions, methods, results, limitations, and reproducible experimental details"), with concrete triggering needs and input-format details ("## Page XX pagination and image references"). Not a 4 because the "when" clause is explicit and enumerates concrete trigger conditions rather than being merely implied or generic.

5 / 5

Trigger Term Quality

Good keyword coverage including "close-reading report", "paper", "PDF-to-Markdown", "methods", "results", "limitations", and "reproducible experimental details". It falls short of the 5 anchor because natural synonyms users would say are missing — e.g., "literature", "academic paper", "summarize" — and there are no file-extension triggers. It is above a 3 because it goes well beyond a couple of generic keywords with domain-relevant terms.

4 / 5

Distinctiveness Conflict Risk

It occupies a clear niche — close-reading of research papers from PDF-to-Markdown text with pagination markers — with distinct triggers that would not fire for unrelated skills. It is not a 5 because general paper-summarization or literature-review requests could plausibly overlap with it, and the description does not sharply distinguish itself from those adjacent skills. It is well above a 3 because the specialized input format and deliverable make confusion with generic document skills unlikely.

4 / 5

Total

17

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 2 suspicious

Warning

Total

14

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Evidence Insight/literature-close-read/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.