CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

reference-style-sync

One-click synchronization and standardization of reference formats in literature management tools, intelligently fixing metadata errors.

Quality

60%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Academic Writing/reference-style-sync/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%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 body contains genuinely useful executable material — CLI commands, a parameter table, and concrete before/after repair examples — but it is buried in a 369-line wall of duplicated generic boilerplate, contradictory dependency statements (Python 3.10+ vs 3.8+, dataclasses/requirements.txt vs regex/titlecase), and circular self-references. The structure is a stitched-together template rather than a lean, navigable skill document.

Suggestions

Cut the generic template sections (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status, Output Requirements, Input Validation, Response Template) and the duplicated Example Usage / Quick Check / Audit-Ready Commands sections — they consume tokens without domain value.

Resolve factual contradictions: Python 3.10+ vs 3.8+, and 'dataclasses declared in requirements.txt' vs 'regex, titlecase' — and remove the hardcoded 'cd "20260318/scientific-skills/..."' placeholder path.

Remove the circular 'See ## Features above for related details' pointers, and move detailed material (repair rules, parameter table) into references/ with explicit links per progressive-disclosure best practice.

DimensionReasoningScore

Conciseness

The 369-line body is heavily padded: roughly half the sections (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status, Output Requirements, Input Validation, Response Template, Implementation Details) are generic template boilerplate that teaches Claude nothing domain-specific, and content is duplicated (Example Usage vs Usage, Quick Check vs Audit-Ready Commands). This is noticeably below the midpoint — worse than 'some unnecessary explanation' (3) though it does not explain known concepts like what a PDF is (1), so an even score of 2 fits.

2 / 5

Actionability

The Usage section provides concrete, executable CLI commands with real flags matching an existing script ('python scripts/main.py --input library.bib --output fixed.bib --style apa'), a parameter table, a Python API example, and before/after repair examples. Minor gaps keep it from 5: the 'cd "20260318/scientific-skills/..."' path appears to be a hardcoded non-existent placeholder, the Python API example is unverified, and repair-rule examples sit in mislabeled ```python fences.

4 / 5

Workflow Clarity

Multiple competing 'workflow' sections exist (the generic 5-step 'Workflow', the 4-step 'Example run plan', 'Quick Check', 'Error Handling'), but the actual domain sequence (detect → fix metadata → convert style → dedupe → export) is only implicit through CLI flags. Validation checkpoints do exist (py_compile before running, --check-only mode, backup recommendation), but as a batch/destructive-capable operation (rewriting libraries, merging duplicates) the scattered, boilerplate workflow keeps this at anchor 3: steps listed but checkpoints implicit and fragmented.

3 / 5

Progressive Disclosure

The bundle has a real one-level-deep reference (references/audit-reference.md) linked once from the References section, plus scripts/main.py, so navigation depth is fine. However, the body inlines large amounts of content that belongs in reference files (repair rules, parameter table, security/evaluation boilerplate), references to 'references/' elsewhere are vague ('Reference material available in references/'), and circular 'See ## Features above' pointers add confusion — anchor 3: some structure but inline content that should be separate and weakly signaled references.

3 / 5

Total

12

/

20

Passed

Description

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

The description communicates a clear domain and a reasonable 'what', but it is marketing-flavored, lacks any 'use when' trigger guidance, and omits the concrete natural-language terms (Zotero, EndNote, BibTeX, citation styles) that would let it fire on real user requests. Anchor-level mid scores across dimensions reflect a functional but generic description.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user mentions Zotero, EndNote, BibTeX, RIS, .bib files, citations, bibliography formatting, or converting references to a specific style (APA, AMA, Vancouver).'

Replace buzzwords ('One-click', 'intelligently') with concrete capabilities: 'Converts references to target citation styles, repairs author/DOI/page metadata, completes missing fields, and merges duplicate entries.'

Name the supported tools and formats (Zotero, EndNote, BibTeX, RIS, CSL JSON) to sharpen distinctiveness and trigger-term coverage.

DimensionReasoningScore

Specificity

The description names the domain ("reference formats in literature management tools") and 1-2 actions ("synchronization and standardization of reference formats", "fixing metadata errors"), but the actions are generic and wrapped in buzzwords ("One-click", "intelligently") with no concrete capabilities like style conversion, deduplication, or DOI completion. It matches anchor 3 (domain + 1-2 concrete actions, not comprehensive), not anchor 4 which requires several specific actions.

3 / 5

Completeness

The 'what' is clear (synchronize/standardize reference formats, fix metadata errors) but there is no 'when' — no 'Use when...' clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3. Not anchor 4 because the 'when' is entirely absent rather than merely weak.

3 / 5

Trigger Term Quality

Relevant keywords exist ("reference formats", "literature management tools", "metadata") but the natural terms users would actually say — Zotero, EndNote, BibTeX, citations, bibliography, .bib, APA — are all missing. This matches anchor 3: some relevant keywords but missing common variations or synonyms.

3 / 5

Distinctiveness Conflict Risk

"Reference formats in literature management tools" carves out a fairly distinct niche with minimal overlap risk against generic document or citation-writing skills, though it could collide with closely related bibliography/citation skills since no specific tools or formats are named. Mostly distinct with minor overlap — anchor 4.

4 / 5

Total

13

/

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/Academic Writing/reference-style-sync/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.