CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

literature-management

Import local literature into a managed library; trigger when you need offline deduplication, tagging, and a searchable index.

Quality

64%

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/Other/literature-management/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

38%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 documents a genuinely well-specified tool (clear dedup priority, index schema, file organization rules) but is undermined by a broken bundle — every referenced script and reference file is missing — and by ~60 lines of generic compliance/boilerplate sections that add no skill-specific value. Workflow guidance exists but lacks a real feedback loop for a batch import operation.

Suggestions

Ship the referenced bundle files (scripts/import_library.py, scripts/requirements.txt, references/examples.md) or remove the references; as written, none of the commands can actually be executed.

Delete or collapse the generic template sections (Required Inputs, Recommended Workflow, Output Contract, Validation and Safety Rules, Failure Handling, Input Validation) into a few skill-specific bullets — they restate universal behavior rather than anything about literature import.

Replace the Quick Validation block with a real check, e.g. run the import on a two-file sample and confirm the dedup rule and index.jsonl fields, instead of an inaccurate `--help` expected-output listing.

DimensionReasoningScore

Conciseness

Roughly a third of the body is generic template boilerplate Claude does not need: "Required Inputs" ("A clearly specified task goal aligned with the documented scope"), "Recommended Workflow", "Output Contract" ("Return a structured deliverable that is directly usable without reformatting"), "Validation and Safety Rules", "Failure Handling", and "Input Validation" are all skill-agnostic padding, and "Key Features" repeats "When to Use". This matches the noticeably-verbose anchor with several padded sections, not the mostly-efficient anchor-3 where only some trimming is needed.

2 / 5

Actionability

The core import command with repeatable --tag flags, the dedup priority order, and the index field list are concrete, but the guidance is not actually executable: the bundle contains no scripts/ or references/ directories, so `scripts/import_library.py`, `scripts/requirements.txt`, and `references/examples.md` are all dangling, and the "Quick Validation" block asserts a nonsensical expected output for `--help` (a result-file path and PASS/FAIL summary instead of a usage message). This lands between the incomplete anchor-3 and the minor-gaps anchor-4, closer to 3 because the central dependency is missing.

3 / 5

Workflow Clarity

A real sequence exists (choose SOURCE_DIR/LIBRARY_DIR, run import, then verify organized files, index.jsonl, and the printed summary), which puts it above the gaps-heavy anchor-2. However, this is a batch operation and the only validation is a post-hoc verification list plus a weak `--help` pre-check — there is no validate→fix→retry loop, and the "Recommended Workflow" section is generic text ("Select the documented execution path") rather than skill steps — so per the batch-operation cap it cannot exceed 3, and it lacks the explicit checkpoints of anchor-4.

3 / 5

Progressive Disclosure

The actual bundle is a single SKILL.md with no references/, scripts/, or assets/ directories, yet the body points to three files (`scripts/import_library.py`, `scripts/requirements.txt`, `references/examples.md`) that do not exist, so every reference is a dead end and the promised split of content across files is not realized. In-body section headers are decent, which keeps it above the monolithic anchor-1, but the broken bundle structure fits the minimal-structure anchor-2 better than anchor-3, whose flaw (references present but poorly signaled) is not the issue here.

2 / 5

Total

10

/

20

Passed

Description

75%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 solid, third-person description that clearly states what the skill does and includes an explicit trigger clause. Its main weakness is that the "when" clause mirrors the feature list instead of describing user situations, and it omits the concrete artifacts (papers, PDF, BibTeX, RIS) users would most naturally mention.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "Import local literature into a managed library", "offline deduplication", "tagging", and a "searchable index" — which goes well beyond the 1-2 actions of the anchor-3 example. It is not a 5 because coverage has minor gaps: no mention of the supported file formats (PDF/BibTeX/RIS/CSV/TXT) or the library file organization that the body documents.

4 / 5

Completeness

It answers both questions: the "what" ("Import local literature into a managed library" plus dedup/tag/index) and an explicit "when" clause ("trigger when you need offline deduplication, tagging, and a searchable index"), so it is above the anchor-3 case where "when" is missing. It is not a 5 because the "when" clause merely restates the feature list rather than naming concrete trigger situations or inputs (e.g., "use when you have a batch of downloaded papers to organize").

4 / 5

Trigger Term Quality

Terms like "literature", "deduplication", "tagging", "import", "library", and "offline" are natural phrases a user managing a research collection would say, matching the good-coverage anchor. It falls short of the 5 anchor because common synonyms and extensions users actually type — "papers", "PDFs", "bibliography", "citations", ".bib", "RIS" — are absent.

4 / 5

Distinctiveness Conflict Risk

The local/offline literature-library niche with dedup-by-DOI and a JSONL index is fairly distinct, matching the mostly-distinct anchor with only minor overlap risk against general reference-manager or PDF-organization skills. It is not a 5 because "literature" and "library" are broad enough that a user asking about a citation manager or bibliography formatting could plausibly pull this skill in.

4 / 5

Total

16

/

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

referenced_paths_exist

Referenced path issues: 4 missing

Warning

Total

14

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Other/literature-management/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.