CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

citation-management

Comprehensive citation management for academic research; use when you need to discover papers (Google Scholar/PubMed), extract/verify metadata (DOI/PMID/arXiv/URL), and produce validated, clean BibTeX for manuscripts.

Quality

79%

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/citation-management/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 well-structured, largely executable skill body with a genuinely useful end-to-end example pipeline and a properly split reference bundle. Its weaknesses are ~70 lines of generic guard-rail boilerplate that pads the token budget, hedged parameter documentation that undercuts copy-paste confidence, and the absence of an explicit fix-and-revalidate retry loop after the validation step.

Suggestions

Collapse the overlapping generic sections (When Not to Use, Required Inputs, Output Contract, Failure Handling, User Checkpoints, Input Validation, Quick Validation) into one short guard-rails section, keeping only skill-specific guidance such as the DOI-resolution and duplicate-detection checks.

Remove hedging like "(if supported by the script)" and "(if implemented/used)" from Implementation Details by verifying each flag against the actual scripts, so the documented commands are trustworthy copy-paste material.

After the validation step, add an explicit feedback loop: inspect validation.json, fix or drop failing entries, re-run validate_citations.py, and only deliver the .bib file when the report is clean.

DimensionReasoningScore

Conciseness

The core material (When to Use, Example Usage, Implementation Details) is efficient, but the body carries ~70 lines of generic template boilerplate — "Required Inputs", "Output Contract", "Failure Handling", "User Checkpoints", "Input Validation", "Quick Validation" — with vague guidance like "Check that key scripts... exist" that Claude already knows to do. That padding and redundancy across five overlapping guard-rail sections places it at 'mostly efficient but includes some unnecessary explanation or could be tightened', not at the 4 anchor where only minor trimming would be needed.

3 / 5

Actionability

The Example Usage section is a fully executable 7-command bash pipeline with real flags and file names, and every referenced script exists in the bundle. However, Implementation Details hedges with "(if supported by the script)", "(if implemented/used)", and "(when supported)" — uncertainty about the tooling that keeps it just short of copy-paste-ready confidence at 5 while remaining well above the incomplete-guidance 3 anchor.

4 / 5

Workflow Clarity

The example workflow is clearly sequenced from search through extraction, formatting, deduplication, validation with "--auto-fix --report validation.json", and a final "Inspect validation results" step, so the batch-operation validation cap is satisfied. It falls short of the 5 anchor because there is no explicit fix-and-revalidate retry loop after inspecting the report — the feedback loop is implied (auto-fix) rather than an instructed error-recovery cycle.

4 / 5

Progressive Disclosure

Structure is good: five reference files cited inline as "(See: references/...)" — all of which exist and are one level deep — plus six scripts referenced by name, all present. It misses the 5 anchor because Implementation Details duplicates summaries of the reference files' content inline and the generic boilerplate sections dilute the overview's navigational clarity, leaving minor organization gaps.

4 / 5

Total

15

/

20

Passed

Description

83%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, information-dense description that names concrete capabilities, concrete identifier formats, and explicit trigger conditions with domain-specific vocabulary. Its only faults are the second-person "you" in the trigger clause (penalized under voice rules) and a modest overlap risk with generic literature-search skills, plus a few missing synonyms like ".bib" or "bibliography".

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "discover papers (Google Scholar/PubMed)", "extract/verify metadata (DOI/PMID/arXiv/URL)", "produce validated, clean BibTeX" — which would merit a 5, but the second-person phrasing "use when you need to" triggers the mandated 1-point voice penalty. Without the penalty this would be comprehensive coverage; with it, it sits clearly above the 'several specific actions; minor gaps' anchor rather than below.

4 / 5

Completeness

It explicitly answers both questions: the "what" is "discover papers... extract/verify metadata... produce validated, clean BibTeX" and the "when" is the explicit clause "use when you need to discover papers... and produce validated, clean BibTeX for manuscripts". This matches the anchor for clearly and explicitly answering both with concrete trigger phrases; the only weakness is the second-person voice in the trigger clause, which the rubric assigns to specificity, not completeness.

5 / 5

Trigger Term Quality

Strong natural keyword coverage: "citation management", "Google Scholar", "PubMed", "DOI", "PMID", "arXiv", "BibTeX", "manuscripts" — terms users would genuinely say. Missing a few common variations like ".bib file", "bibliography", and "references", which keeps it just below the comprehensive-synonyms anchor at 5.

4 / 5

Distinctiveness Conflict Risk

The BibTeX/DOI/PMID/arXiv vocabulary carves a clear niche with distinct triggers, but "discover papers (Google Scholar/PubMed)" and "academic research" overlap meaningfully with literature-review or paper-search skills. Mostly distinct with minor overlap risk against closely related skills — an exact fit for the 4 anchor, not the minimal-conflict 5 anchor.

4 / 5

Total

17

/

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/citation-management/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.