CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

crossref-database

Access CrossRef metadata for scholarly works; use when you need to resolve a DOI or search CrossRef to retrieve bibliographic details, citation/reference counts, or funder information for research and citation management.

Quality

73%

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 ./scientific-skills/Evidence Insight/crossref-database/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

46%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 core documentation (usage examples, inputs, returned fields, dependencies) is concrete and accurate to the bundled script, but roughly half the body is generic template boilerplate that adds no CrossRef-specific value, and the Quick Validation section presents a fabricated expected output. The result is a padded, partly vague workflow despite a solid executable core.

Suggestions

Delete the generic template sections (When Not to Use, Required Inputs, Output Contract, Validation and Safety Rules, Deterministic Output Rules, Completion Checklist, and the duplicate Quick Validation) — they restate behavior any competent model already knows and double the file's token cost without adding CrossRef-specific guidance.

Replace the fabricated "Expected output format" under Quick Validation with the actual output of `python scripts/query_crossref.py --help` (argparse usage text), and add one real example of the script's output so users can verify results against the documented format.

Rewrite "Recommended Workflow" as concrete CrossRef-specific steps (e.g., 1. resolve/search via query_crossref.py, 2. inspect returned fields such as title/author/is-referenced-by-count, 3. explicitly note when funder or citation-count fields are absent from the record) instead of abstract platitudes.

DimensionReasoningScore

Conciseness

The first half (Validation Shortcut, When to Use, Key Features, Dependencies, Example Usage, Implementation Details) is efficient, but roughly half the body — "When Not to Use", "Required Inputs", "Output Contract", "Validation and Safety Rules", "Deterministic Output Rules", "Completion Checklist" — is generic template padding ("Do not use this skill when the user asks for fabricated results", "Keep the output safe, reproducible, and within the documented scope") that restates what any competent model already knows, and "Quick Validation" duplicates "Validation Shortcut". This is noticeably verbose with several padded sections, matching anchor 2 rather than the mostly-efficient anchor 3.

2 / 5

Actionability

The usage commands are copy-paste ready and match the real script's flags (verified: --doi, --query, --limit exist in scripts/query_crossref.py), but the "Quick Validation" expected output is fabricated — `--help` prints argparse usage, not "Result file: crossref_database_result.md" — and there is no sample of the script's actual output. Concrete guidance is present but incomplete with a key-detail miss, fitting anchor 3 rather than the mostly-executable anchor 4.

3 / 5

Workflow Clarity

"Recommended Workflow" lists a 4-step sequence, but the steps are abstract platitudes ("Select the documented execution path", "Run a final validation pass") rather than CrossRef-specific operations, and validation checkpoints are implicit rather than concrete commands; "Failure Handling" gestures at recovery but provides no executable retry loop. Sequence present with implicit checkpoints matches anchor 3, not the clear-checkpoints anchor 4.

3 / 5

Progressive Disclosure

The body is organized into clear sections, and its single bundle reference (scripts/query_crossref.py) is real, one level deep, and used consistently. Minor gaps keep it below the top anchor: scripts/validate_skill.py exists in the bundle but is never referenced, and the inline boilerplate is content that should be deleted rather than restructured into separate files. This fits "good structure; most content appropriately placed; minor organization gaps".

4 / 5

Total

12

/

20

Passed

Description

88%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: it states concrete capabilities in third-person voice and includes an explicit "use when" clause with concrete trigger phrases. The only weaknesses are a few missing natural synonyms and minor overlap risk with sibling scholarly-lookup skills.

DimensionReasoningScore

Specificity

The description lists multiple specific concrete actions — "resolve a DOI", "search CrossRef", "retrieve bibliographic details, citation/reference counts, or funder information" — comprehensively covering the CrossRef feature surface (resolution, search, metadata, metrics, funding). It matches the comprehensive-coverage anchor rather than the minor-gaps anchor.

5 / 5

Completeness

It explicitly answers both "what" ("Access CrossRef metadata for scholarly works" plus enumerated capabilities) and "when" ("use when you need to resolve a DOI or search CrossRef to retrieve bibliographic details, citation/reference counts, or funder information") with concrete trigger phrases, matching the top anchor's example structure. The when-clause enumerates concrete triggers rather than merely implying them, so it is not the score-4 anchor.

5 / 5

Trigger Term Quality

Good keyword coverage with natural phrases users would say ("resolve a DOI", "bibliographic details", "citation/reference counts", "funder information", "citation management"), but a few common natural terms are missing (e.g., "citation lookup", "who cited a paper", "paper metadata"). This fits the good-coverage-with-a-few-missing anchor, not the comprehensive-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

The named niche (CrossRef API, DOI resolution) has distinct triggers, but the skill originates from a medical-research-skills bundle where sibling literature-lookup skills (e.g., PubMed search) could overlap on "retrieve bibliographic details for research", and "research and citation management" is slightly broad. This fits "mostly distinct; minor overlap risk with closely related skills" rather than the minimal-conflict top anchor.

4 / 5

Total

18

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Evidence Insight/crossref-database/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.