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, or a whole-bibliography audit of a .bib/.ris/CSL-JSON file.

75

Quality

94%

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

Overview
Quality
Evals
Security
Files

Quality

Content

92%

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

The body is lean, highly actionable, and provides clear sequenced workflows with validation for the risky verify/audit operations. The one weakness is progressive disclosure: it points to a REFERENCE.md that is not present among the bundle files.

Suggestions

Ship the referenced REFERENCE.md (or move its promised content — keys, --base-url/--timeout, exit-code table — inline) so the [REFERENCE.md](REFERENCE.md) link resolves.

Tighten the verify-verdict explanations slightly; the mismatch/ambiguous distinction could be one line each without the parenthetical citations.

DimensionReasoningScore

Conciseness

The body is dense but every section earns its place with non-obvious CLI specifics (subcommands, flags, verdict semantics, exit codes, pitfalls) and does not explain concepts Claude already knows; it could only be marginally tighter in the verify-verdict prose.

3 / 3

Actionability

Commands are fully executable and copy-paste ready — e.g. 'scholar format 10.1038/nphys1170 --style vancouver' and 'scholar audit refs.bib --json | jq '.summary'' — with concrete flags and real identifiers.

3 / 3

Workflow Clarity

The 'Error-recovery loop (verify)' is an explicit numbered sequence with validation checkpoints (check exit code, re-run with --json, distinguish mismatch/not_found from network errors), and a Verification section is present for the batch/risky audit/verify operations.

3 / 3

Progressive Disclosure

Sections are well-organized and the detail pointer to [REFERENCE.md](REFERENCE.md) is clearly signaled and one level deep, but no bundle files exist so the referenced REFERENCE.md is missing, breaking navigation; not a 3 because the offloaded target is absent.

2 / 3

Total

11

/

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.

The description is specific, trigger-rich, and complete, answering both what the skill does and when to use it in third person. It is clearly distinguishable from sibling skills via concrete identifier-based triggers.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Resolve scholarly identifiers… into formatted citations (10,000+ CSL styles) and bibliography exports (BibTeX, RIS, EndNote, CSV…)' and 'check retraction, open-access, and citation-fabrication status' — matching the top anchor.

3 / 3

Completeness

Clearly answers both what (resolve/format/export/verify scholarly identifiers) and when via an explicit 'Use when…' trigger clause, hitting the top anchor.

3 / 3

Trigger Term Quality

The 'Use when the user wants to look up, cite, export, or verify a reference… from the terminal' clause covers natural terms a user would actually say, plus concrete identifier types.

3 / 3

Distinctiveness Conflict Risk

A clear niche — terminal-based scholarly citation/integrity tool keyed on specific identifiers (DOI, PMID, arXiv, ADS bibcode, WHO IRIS URL) — with distinct triggers and explicit sibling-skill disambiguation, unlikely to conflict.

3 / 3

Total

12

/

12

Passed

Validation

75%

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

Validation12 / 16 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

relative_links

Relative link issues: 1 missing

Warning

Total

12

/

16

Passed

Reviewed

Table of Contents