CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

figure-reference-checker

Use figure reference checker for academic writing workflows that need structured execution, explicit assumptions, and clear output boundaries.

Quality

56%

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/figure-reference-checker/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 body has a sound skeleton (real commands, a genuine one-level-deep reference bundle, and clear script parameters) but is buried under heavy governance boilerplate that duplicates itself across many sections and inflates token cost for a simple 37-line script. The core execution guidance is also incomplete: the documented usage example does not match the script's actual text-vs-file behavior.

Suggestions

Cut the boilerplate sections (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status, Response Template, Output Contract, Failure Handling, User Checkpoints) — they restate the same rules already in Error Handling and could shrink the file by more than half without losing skill-specific guidance.

Fix the usage documentation to match script behavior: main.py treats --manuscript as literal text, not a file path, so either document 'python scripts/main.py --manuscript "...Figure 3 shows..."' or update the script to read files.

Turn the abstract Workflow steps into a concrete executable sequence (run py_compile check, run the checker, report found references vs labels), and specify what the script's output looks like.

DimensionReasoningScore

Conciseness

The body is ~190 lines for a 37-line script, with many padded boilerplate sections (Risk Assessment table, Security Checklist, Evaluation Criteria, Lifecycle Status, Response Template, Output Contract, User Checkpoints) that add no skill-specific knowledge. The same error-handling rules ('state exactly which fields are missing', 'do not fabricate') are restated across Error Handling, Failure Handling, Input Validation, and Output Contract, matching anchor 2 (several unnecessary/padded sections) rather than 1, since no basic concepts are explained.

2 / 5

Actionability

Concrete commands exist ('python -m py_compile scripts/main.py', 'python scripts/main.py --manuscript paper.docx'), but key details are missing or wrong: the bundled script treats --manuscript as literal text rather than reading a file, so the documented usage example would print nothing useful; output format is never specified; and the Features (orphaned references, label consistency, missing citations) are not connected to any command. This matches anchor 3 (some concrete guidance but incomplete, missing key details) rather than 4.

3 / 5

Workflow Clarity

The Workflow section lists a sequence and the Quick Check provides one real validation checkpoint (py_compile before deeper execution), but the steps are abstract governance prose ('Confirm the user objective', 'Validate that the request matches the documented scope') with no concrete run-parse-report sequence for the actual script. This matches anchor 3 (sequence present, checkpoints implicit/missing) — the read-only nature of the skill avoids the destructive-operation cap.

3 / 5

Progressive Disclosure

The bundle structure is good: scripts/main.py and references/audit-reference.md both exist, the reference is linked once with a clear description ('Supported scope, audit commands, and fallback boundaries'), and references are exactly one level deep with no nested indirection. This matches anchor 4 (good structure, references mostly clear, minor organization gaps) — it falls short of 5 because large amounts of boilerplate (security checklists, risk tables, response templates) are inlined in SKILL.md rather than split out or removed, slightly bloating the overview.

4 / 5

Total

12

/

20

Passed

Description

48%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 identifies a real niche (figure references in academic writing) but is circular about what the skill does and padded with process boilerplate that serves no trigger purpose. Concrete actions and natural trigger terms (manuscript, figure labels, citations) would lift it substantially.

Suggestions

Replace the circular 'Use figure reference checker for academic writing workflows...' with concrete actions from the body: 'Detect orphaned figure references, check figure-label consistency, and flag missing citations in manuscripts.'

Add natural trigger terms users would actually say, e.g. 'Use when checking a manuscript or paper for figure references, figure labels (e.g. "Figure 3"), or missing citations.'

Remove the boilerplate tail ('structured execution, explicit assumptions, and clear output boundaries') — it is not a capability and not a trigger term.

DimensionReasoningScore

Specificity

The description names the domain ('figure reference checker', 'academic writing workflows') but states no concrete actions — 'Use figure reference checker for academic writing workflows' is circular, and 'structured execution, explicit assumptions, and clear output boundaries' is process boilerplate rather than a capability. It sits between anchor 2 (domain named, generic actions) and anchor 3 (1-2 concrete actions); it does not reach 3 because no actual checking action (detect orphaned references, validate labels) is ever stated.

2 / 5

Completeness

The 'what' is only weakly implied by the circular skill-name reference ('Use figure reference checker...') and the 'when' is present but fuzzy ('for academic writing workflows that need structured execution...'). A 'Use...for...' trigger clause exists (so it is not capped below by its absence), but neither what nor when is explicit, so it does not reach anchor 4; it sits above anchor 2 because both elements are at least discernible.

3 / 5

Trigger Term Quality

'figure reference checker' and 'academic writing workflows' are relevant natural keywords, but common variations a user would actually say — 'manuscript', 'Figure 3', 'figure captions', 'citations', '.docx' — are absent, and 'structured execution, explicit assumptions, clear output boundaries' is jargon no user would utter as a trigger. It matches anchor 3 (some relevant keywords, missing variations/synonyms) rather than 4, which requires broad natural-term coverage.

3 / 5

Distinctiveness Conflict Risk

'figure reference checker' with 'academic writing' is a fairly clear niche with distinct triggers and low conflict risk, matching anchor 4. It falls short of anchor 5 because the generic tail ('structured execution, explicit assumptions, and clear output boundaries') could describe almost any workflow skill, creating minor overlap with other academic-writing skills.

4 / 5

Total

12

/

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/figure-reference-checker/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.