CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

research-lit

Search and analyze research papers, find related work, summarize key ideas. Use when user says "find papers", "related work", "literature review", "what does this paper say", or needs to understand academic papers.

Quality

74%

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 ./skills/skills-codex/research-lit/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 body is highly actionable and well-sequenced with genuine validation checkpoints, but token efficiency is poor: massive verbatim repetition of the fetcher-resolution stanza, redundant example listings, and heavy inlining of content that belongs in separate reference files. The external shared-references it links to are not part of this bundle, so deep detail lives entirely in a monolithic file.

Suggestions

Factor the repeated $ARIS_REPO/$FETCHER resolution stanza into a single shared snippet (or one small section referenced by each source block) and collapse the 16-line example invocation listing in Source Selection, since the Source Table already encodes the same rules.

Move per-source detail (Semantic Scholar, DeepXiv, Exa, Gemini, OpenAlex blocks and their per-source dedup rules) into a references/ file per optional source, leaving SKILL.md as an overview with the source table and one-level-deep, clearly signaled links.

Trim rationale asides ("Zotero annotations are gold", "Obsidian notes represent the user's processed understanding", "Why use Gemini/OpenAlex?" paragraphs) to one-line notes or move them into the per-source reference files, keeping the core workflow lean.

DimensionReasoningScore

Conciseness

The $ARIS_REPO/$FETCHER resolution stanza is repeated verbatim six times, the source-selection section lists 16 example invocations duplicating the Source Table, and rationale asides ("Zotero annotations are gold", "Why use Gemini?") pad the text — several unnecessary/redundant sections matching the score-2 anchor. It is not a 1 because it never explains concepts Claude already knows; the material is operational, just repetitive.

2 / 5

Actionability

Concrete executable bash blocks with full fallback chains, exact MCP tool patterns, specific API flags (e.g. --fields title,authors,year,venue,citationCount,externalIds,tldr,url), and literal WARN strings to emit provide mostly copy-paste-ready guidance. Placeholders like "QUERY"/"ARXIV_ID" and dependence on external fetcher scripts not present in the bundle keep it at 4 rather than 5.

4 / 5

Workflow Clarity

Steps 0a-0c, 1, 1.6, and 2-6 are clearly sequenced with real validation checkpoints: a coverage receipt reconciling frozen vs. covered paper IDs, PDF size verification (>10 KB), UNPROCESSABLE_NO_LOCAL_EVIDENCE handling, a one-sequential-fallback rule, and "ask before writing; do not invent a wiki location". Minor gaps (no validation of the synthesized output, some implicit transitions in the sprawl) hold it at 4 rather than 5.

4 / 5

Progressive Disclosure

No references/, scripts/, or assets/ directories exist in the bundle, and the three linked files (fan-out-pattern.md, integration-contract.md, output-composition.md) point outside the skill directory and are absent. Roughly 500 lines of per-source detail (six near-identical fetcher blocks, per-source dedup rules) are inlined in SKILL.md where one reference file per optional source clearly belongs — structure and signaled references exist, but substantial separable content is inline, matching the score-3 anchor.

3 / 5

Total

13

/

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 with an explicit "Use when" clause, natural user-quoted triggers, and a clear academic niche. Its only weaknesses are minor: a few missing action capabilities and trigger synonyms.

DimensionReasoningScore

Specificity

"Search and analyze research papers, find related work, summarize key ideas" lists several concrete domain actions, matching the score-4 anchor of several specific actions with minor gaps; it falls short of 5 because it omits capabilities like citation export, local PDF libraries, and synthesis output.

4 / 5

Completeness

It explicitly answers both "what" (search, analyze, find related work, summarize key ideas) and "when" ("Use when user says \"find papers\", \"related work\", \"literature review\"...") with concrete quoted trigger phrases, mirroring the score-5 anchor example almost exactly.

5 / 5

Trigger Term Quality

Natural trigger phrases "find papers", "related work", "literature review", "what does this paper say", and "understand academic papers" are exactly what a user would say, but a few common synonyms ("lit review", "survey", "prior work") are missing, fitting the good-coverage-with-gaps anchor at 4 rather than the comprehensive anchor at 5.

4 / 5

Distinctiveness Conflict Risk

Triggers like "literature review", "related work", and "what does this paper say" carve a clear academic niche, but "find papers"/"search research papers" carries minor overlap risk with generic document-search or PDF skills, fitting the mostly-distinct anchor at 4 rather than minimal-conflict at 5.

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

skill_md_line_count

SKILL.md is long (502 lines); consider splitting into references/ and linking

Warning

relative_links

Relative link issues: 4 suspicious

Warning

Total

14

/

16

Passed

Repository

wanshuiyin/Auto-claude-code-research-in-sleep

Path

skills/skills-codex/research-lit/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.