CtrlK
BlogDocsLog inGet started
Tessl Logo

mlava/scholar-sidekick-api

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 — 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.

78

Quality

98%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

Overview
Quality
Evals
Security
Files

Quality

Content

100%

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

The body is a lean, executable API reference: complete curl examples, explicit response schemas, validation guidance for batch operations, and clearly signaled pointers to deeper external documentation. It avoids concept-padding and provides clear navigation throughout.

DimensionReasoningScore

Conciseness

Dense API-reference prose that assumes Claude's competence — no concept explanations of DOIs or citations — with only minor, purposeful redundancy between the Quick Reference table and per-endpoint Procedure detail.

3 / 3

Actionability

Every endpoint ships a complete, executable curl command with a real example payload and a documented response shape, making the guidance copy-paste ready rather than descriptive pseudocode.

3 / 3

Workflow Clarity

Per-task procedures are clear, and the batch audit path includes explicit validation reporting (truncated, per-entry status, 502 outage) alongside a Verification section and Pitfalls feedback directing the agent to report failures rather than fabricate.

3 / 3

Progressive Disclosure

A single, well-organized SKILL.md that clearly signals one-level-deep external contract references (llms.txt, AGENTS.md, openapi.yml) and the companion MCP skill, with no nested local references and easy section navigation.

3 / 3

Total

12

/

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.

A strong, specific description that clearly states capabilities and provides explicit natural-language use triggers, written in third-person voice. It is comprehensive without resorting to vague fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — resolving scholarly identifiers into formatted citations and bibliography exports (BibTeX, RIS, EndNote, CSV…) plus retraction, open-access, and fabrication checks — far beyond a vague domain statement.

3 / 3

Completeness

Explicitly answers both 'what' (resolve identifiers → citations/exports, integrity checks) and 'when' via a dedicated 'Use when the user has … and asks to …' trigger clause.

3 / 3

Trigger Term Quality

Mirrors natural user phrasing throughout — 'format a citation', 'build or export a bibliography', 'is this retracted/open-access/fabricated', 'audit every reference in a .bib/.ris/CSL-JSON bibliography' — with full coverage of identifier variations.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (scholarly citation integrity keyed off specific identifier types) with distinct triggers, making it unlikely to fire for the wrong skill.

3 / 3

Total

12

/

12

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.

Validation13 / 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

Table of Contents