CtrlK
BlogDocsLog inGet started
Tessl Logo

mlava/scholar-sidekick-cli

Resolve scholarly identifiers (DOI, PMID, PMCID, ISBN, arXiv, ISSN, ADS bibcode, WHO IRIS URL) into formatted citations (10,000+ CSL styles) and bibliography exports (BibTeX, RIS, EndNote, CSV…), and check retraction, open-access, and citation-fabrication status — from the terminal via the `scholar` CLI. Wraps the public REST API; needs Node ≥20 but no API key for the free tier. Use when the user wants to look up, cite, export, or verify a reference by DOI, PMID, PMCID, ISBN, arXiv ID, ISSN, ADS bibcode, or WHO IRIS URL from the terminal — including retraction, open-access, and fabricated-citation checks.

70

Quality

88%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

Overview
Quality
Evals
Security
Files

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A strong, actionable skill with excellent executable examples and good safety guardrails (never fabricate results, check exit codes). The verify workflow's error-recovery loop is particularly well done. Minor weaknesses include some verbosity in the 'When to Use' section and explanatory prose that Claude doesn't need, plus the inability to verify the referenced REFERENCE.md exists.

Suggestions

Trim the 'When to Use' section — Claude can infer when NOT to use the skill; focus on positive triggers only.

Remove the sibling-skills callout block or reduce it to a single line, as the 'When to Use' section already covers fallback guidance.

DimensionReasoningScore

Conciseness

Generally efficient but includes some unnecessary context like the sibling-skills callout, the 'When to Use' section with negative guidance Claude could infer, and some explanatory prose (e.g., explaining what 'mismatch' means in the fabrication context). The command table and procedure sections are well-structured but could be tighter.

2 / 3

Actionability

Excellent executable examples throughout — install commands, format/export/verify invocations with real DOIs, redirect patterns, jq parsing, and flag combinations are all copy-paste ready. The verify error-recovery loop gives specific steps with exit codes.

3 / 3

Workflow Clarity

The verify workflow has an explicit error-recovery loop with exit code checking and clear instructions to never fabricate results. The export workflow shows stdout redirection. Validation is covered via `scholar health` and exit code checking. The bold 'never invent' guardrails are appropriate safety checkpoints.

3 / 3

Progressive Disclosure

References REFERENCE.md for authentication/limits/exit-codes detail, which is good progressive disclosure. However, no bundle files are provided so we can't verify REFERENCE.md exists. The main file is fairly long (~150 lines) and some content (like the full command table) could potentially be split out, but it's reasonably organized with clear sections.

2 / 3

Total

10

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is an excellent skill description that thoroughly covers specific capabilities, includes comprehensive trigger terms spanning multiple scholarly identifier types and output formats, and clearly delineates both what the skill does and when to use it. The description is detailed without being padded, uses third-person voice throughout, and occupies a very distinct niche that minimizes conflict risk with other skills.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: resolve scholarly identifiers, format citations in 10,000+ CSL styles, export bibliographies in multiple formats (BibTeX, RIS, EndNote, CSV), check retraction/open-access/citation-fabrication status. Also specifies the tool (`scholar` CLI), runtime requirements (Node ≥20), and API details.

3 / 3

Completeness

Clearly answers both 'what' (resolve identifiers into formatted citations, export bibliographies, check retraction/OA/fabrication status) and 'when' (explicit 'Use when the user wants to look up, cite, export, or verify a reference by DOI, PMID...' clause with specific trigger scenarios).

3 / 3

Trigger Term Quality

Excellent coverage of natural terms users would say: DOI, PMID, PMCID, ISBN, arXiv, ISSN, ADS bibcode, WHO IRIS URL, cite, export, reference, BibTeX, RIS, EndNote, retraction, open-access, fabricated-citation. These are precisely the terms a researcher or academic user would use.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive niche: scholarly identifier resolution via a specific CLI tool (`scholar`). The combination of specific identifier types, citation formatting, bibliography export formats, and verification checks makes it very unlikely to conflict with other skills.

3 / 3

Total

12

/

12

Passed

Validation

72%

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

Validation8 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

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

Warning

Total

8

/

11

Passed

Reviewed

Table of Contents