CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

litbase

Academic paper reading and research development system for biomedical researchers. Finds papers via Semantic Scholar, reads with structured notes, tracks discussion insights, and synthesizes literature into a Research Foundation Document (RFD) for downstream protocol design skills. 8 commands: /setup /feed /read /discuss /recap /update /sync /propose

Quality

70%

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 ./awesome-med-research-skills/Evidence Insight/litbase/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-organized, largely actionable manifest with strong table-driven structure and a clear file layout, held back by redundant prose duplicating the description, absent explicit workflow sequencing/validation for batch operations, and weakly signaled references to bundle files. Tightening the duplication and adding validation steps for batch operations are the highest-leverage fixes.

Suggestions

Delete or drastically shorten the intro paragraph that repeats the frontmatter description, and state the Semantic Scholar free-tier fact once instead of twice.

Add explicit validation checkpoints for batch operations (e.g., dry-run/confirm before rename_pdfs.py, verify traceability after /feed recommendations), which would lift workflow clarity above 3.

Signal bundle references with markdown links and paths at point of use (e.g. 'rules in [core/references/LITERATURE_HARD_RULES.md](core/references/LITERATURE_HARD_RULES.md)') rather than relying on the file tree for discovery.

DimensionReasoningScore

Conciseness

Mostly efficient — tight tables and a quick start — but the intro paragraph nearly duplicates the frontmatter description, the Semantic Scholar 'free, no login required' fact appears twice (Paper source section and Dependencies section), and filler like 'no terminal commands needed' pads the Quick Start. Fits 'mostly efficient but includes some unnecessary explanation' rather than the minor-trim profile of a 4.

3 / 5

Actionability

Provides a copy-paste-ready config.json snippet, exact slash-command names, and concrete inputs ('Submit a PDF path, DOI, or abstract'). Mostly executable guidance with minor gaps — no sample command invocation, example note, or example RFD excerpt — so it falls short of the fully copy-paste-ready coverage of a 5.

4 / 5

Workflow Clarity

The Commands table implies a lifecycle sequence (setup → feed → read → discuss → recap → update → sync → propose) with cadence cues ('First use', 'Daily', 'Per paper'), but there is no explicit step-by-step workflow and validation checkpoints are only implicit (Literature Integrity rules, /sync audits). Batch operations like the PDF batch rename script have no described validation, which fits anchor 3.

3 / 5

Progressive Disclosure

Well-sectioned overview that appropriately defers detail to one-level-deep bundle files (core/commands/*.md, references, scripts) as shown in the file tree, with no inlined bulk content. Not 5 because the LITERATURE_HARD_RULES.md reference is mentioned inline without a link or path — its location is only discoverable by scanning the tree — and command-file references are implicit rather than clearly signaled per section.

4 / 5

Total

14

/

20

Passed

Description

66%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 specific, domain-anchored description with concrete actions and a distinctive output artifact, but it lacks any 'Use when...' trigger guidance, which both caps completeness and leaves natural trigger phrases (PDF, literature review) underrepresented. Adding an explicit usage-trigger clause would lift the two weakest dimensions.

Suggestions

Append a 'Use when...' clause, e.g. 'Use when the user wants to find papers, build a literature base, or prepare a research proposal' — this directly addresses the completeness cap.

Add natural trigger terms users would actually say: 'PDF', 'literature review', 'summarize a paper', 'citations', 'find papers on [topic]'.

Briefly gloss the 8 command names or drop the bare list in favor of 2-3 verbs describing what the commands achieve.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'Finds papers via Semantic Scholar, reads with structured notes, tracks discussion insights, and synthesizes literature into a Research Foundation Document (RFD)' — plus a named platform and output artifact. Not 5 because 'research development system' is abstract and the 8 commands are listed bare without explaining what each does.

4 / 5

Completeness

The 'what' is clear and multi-part (find → read → discuss → synthesize into RFD), but there is no 'Use when...' clause or equivalent explicit trigger guidance — only 'for biomedical researchers' weakly implies the audience, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Contains natural phrases users would say: 'papers', 'finds papers', 'reading', 'literature', 'research', plus the distinctive 'Semantic Scholar'. Missing common variations like 'PDF', 'literature review', 'summarize paper', or 'citation', which keeps it below the comprehensive synonym coverage of a 5.

4 / 5

Distinctiveness Conflict Risk

A clear niche (biomedical literature reading → RFD for downstream protocol design) with distinct vocabulary like 'Research Foundation Document' minimizes conflict. Not 5 because paper search and reading notes could still overlap with other research or PDF-summarization skills.

4 / 5

Total

15

/

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

awesome-med-research-skills/Evidence Insight/litbase/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.