CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

mlava/scholar-sidekick-api

Resolve scholarly identifiers (DOI including shortDOI aliases, 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 — for one citation or a whole bibliography at once. Calls a documented REST API over plain HTTP — no install, no API key needed for the free tier. Use when the user has a DOI, PMID, PMCID, ISBN, arXiv ID, ISSN, ADS bibcode, or WHO IRIS URL and asks to format a citation, build or export a bibliography, check whether a paper is retracted, open-access, or a fabricated citation, or audit every reference in a .bib/.ris/CSL-JSON bibliography.

Quality

91%

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

82%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 dense, highly actionable single-file skill: copy-paste curl commands, exact request bodies, response schemas, and per-endpoint field warnings leave no ambiguity about what to run. The remaining gaps are minor — some trimmable prose around auth tiers and the MCP alternative, no explicit recovery step for batch-audit errors, and an inline endpoint reference that could live in a separate file.

Suggestions

Trim the authentication/RapidAPI paragraph and the Optional MCP-server section to one line each (or move them to a reference file) to tighten the token budget.

Add an explicit error-recovery step for batch audits: instruct what to do when `parseErrors` or `truncated` is non-empty (e.g., report affected entries to the user and re-submit failed entries individually).

Consider moving the per-endpoint request/response reference into a references/ file, keeping the Quick Reference table and one worked example inline in SKILL.md.

DimensionReasoningScore

Conciseness

Largely efficient — every endpoint gets a copy-paste curl plus only non-obvious operational details (field names, limits, verdict semantics). It sits at level 4 rather than 5 because sections like the RapidAPI tiering paragraph ("Scholar Sidekick is also offered on RapidAPI for paid/managed tiers: subscribe at …") and the MCP-server tail could be trimmed, though nothing is concept padding Claude already knows.

4 / 5

Actionability

Fully executable and copy-paste ready: complete curl commands with exact JSON bodies for all seven endpoints (e.g. `-d '{"claimed": {"title": "…", "doi": "10.xxxx/xxxxx"}}'`), response shapes, defaults ("options.checks defaults to [\"retraction\"]"), and limits ("Max 25 entries per call"). This matches the level-5 anchor covering the common cases.

5 / 5

Workflow Clarity

Each task maps to one unambiguous call with per-endpoint field warnings ("One identifier per call — field is `id`") and a Verification section ("`curl -sS https://scholar-sidekick.com/api/health` returns `{ "ok": true, … }`") plus failure guidance ("if a call fails or returns ok:false, report that"). The batch-audit cap at 3 does not apply since validation is present; it is not 5 because there is no explicit validate→fix→retry loop — e.g. what to do when `parseErrors` or `truncated` is non-empty is described but not acted upon.

4 / 5

Progressive Disclosure

Well-organized single-file skill: a Quick Reference table, per-task Procedure sections, Pitfalls, and Verification, with external references (llms.txt, AGENTS.md, openapi.yml) clearly signaled one level deep. It is level 4 rather than 5 because the full endpoint request/response reference is inlined rather than split out — reasonable at ~157 lines, but not exemplary content splitting.

4 / 5

Total

17

/

20

Passed

Description

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

An exemplary description: third-person voice, comprehensive concrete capabilities, and an explicit 'Use when' clause with natural trigger phrases, identifier synonyms, and file extensions. Both the 'what' and 'when' questions are answered with no vagueness or over-claiming.

DimensionReasoningScore

Specificity

Multiple concrete third-person actions with comprehensive coverage: "Resolve scholarly identifiers … into formatted citations (10,000+ CSL styles) and bibliography exports (BibTeX, RIS, EndNote, CSV…)", "check retraction, open-access, and citation-fabrication status", "audit every reference in a .bib/.ris/CSL-JSON bibliography". It exceeds the level-4 anchor ('several specific actions; minor gaps') because formatting, export, and all three integrity checks are named with no coverage gaps.

5 / 5

Completeness

Explicitly answers both questions: the opening sentence states what the skill does, and "Use when the user has a DOI, … and asks to format a citation, build or export a bibliography, check whether a paper is retracted, open-access, or a fabricated citation, or audit every reference" provides concrete 'when' trigger phrases. This is the level-5 anchor exactly; level 4 ('when could be more explicit') does not apply.

5 / 5

Trigger Term Quality

Natural phrases users would actually say are comprehensively covered: "format a citation", "build or export a bibliography", "check whether a paper is retracted, open-access, or a fabricated citation", "audit every reference", plus identifier vocabulary (DOI, PMID, arXiv) and file extensions ".bib/.ris/CSL-JSON". This matches the level-5 anchor (synonyms and extensions included), not level 4 ('a few natural terms missing').

5 / 5

Distinctiveness Conflict Risk

Clear niche — identifier-based citation formatting and integrity checking — with distinct triggers ("retracted", "fabricated citation", ".bib", ADS bibcode) unlikely to fire a wrong skill. Overlap risk is minimal, matching the level-5 anchor rather than level 4's 'minor overlap risk with closely related skills'.

5 / 5

Total

20

/

20

Passed

Validation

81%

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

Validation — 13 / 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

Total

13

/

16

Passed

Reviewed

On this page