CtrlK
BlogDocsLog inGet started
Tessl Logo

anki-card-creator

Use anki-card-creator for academic writing workflows that need structured execution, explicit assumptions, and clear output boundaries for study-card generation.

47

Quality

50%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Academic Writing/anki-card-creator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%

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

The body is well-sectioned and provides real commands, a parameter table, and an explicit workflow with error-handling fallbacks, but it is padded with redundant sections and a thin headline example. The one-level reference is correctly signaled, though much content stays inline.

Suggestions

Remove redundancy: drop the verbatim description echo in 'Key Features', merge 'Quick Check' and 'Audit-Ready Commands', and delete the empty 'See ## ... above' cross-reference lines.

Make the 'Example' section executable: show an actual `python scripts/main.py --input ... --output ...` invocation and the resulting TSV lines, instead of a lone Q/A fragment.

Tighten the Workflow's script-vs-manual decision into an explicit conditional gate (e.g. 'If --input is a Q/A file, run the script; otherwise produce a manual card blueprint').

DimensionReasoningScore

Conciseness

The body is mostly operational but carries clear redundancy: 'Key Features' repeats the description verbatim, 'Quick Check' and 'Audit-Ready Commands' duplicate the same py_compile command, and cross-references like 'See ## Prerequisites above' / 'See ## Workflow above' add little, fitting 'mostly efficient but could be tightened'.

2 / 3

Actionability

Real commands (py_compile, --help) and a concrete Parameters table are present, but the headline 'Example' section shows only 'Q: What is the mechanism of metformin?' with no invocation or expected output, and the run plan is abstract, matching 'some concrete guidance but incomplete; missing key details'.

2 / 3

Workflow Clarity

The 5-step Workflow plus Error Handling provide validation checkpoints and fallback paths, but the decision gate between 'use the packaged script' and 'produce a manual card plan' is implicit rather than a clean conditional checkpoint, fitting 'steps listed but validation gaps; checkpoints implicit'.

2 / 3

Progressive Disclosure

The single reference (references/audit-reference.md) is real, one level deep, and clearly signaled under ## References, but substantial material (risk assessment, security checklist, lifecycle) is inline that could be split out, matching 'some structure; references present but content that should be separate is inline'.

2 / 3

Total

8

/

12

Passed

Description

50%

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 niche (study-card generation) but leads with the unnatural and misleading phrase 'academic writing workflows', which weakens trigger terms and conflict resistance. It states a 'what' and an implied 'when' but lacks an explicit, natural 'Use when...' trigger clause.

Suggestions

Lead with concrete actions, e.g. 'Generates Anki-importable study cards from Q/A text and structured drug/anatomy fields', replacing the generic 'academic writing workflows' framing.

Add an explicit trigger clause using natural user terms: 'Use when the user wants flashcards, Anki cards, or study cards from notes, lecture summaries, or drug/anatomy material.'

Drop buzzword qualities ('structured execution, explicit assumptions, clear output boundaries') that do not help a user recognize when to invoke the skill.

DimensionReasoningScore

Specificity

Names the domain ('study-card generation') and workflow qualities ('structured execution, explicit assumptions, clear output boundaries') but lists no concrete card-building actions, matching the 'names domain and some actions, but not comprehensive' anchor.

2 / 3

Completeness

The 'what' (study-card generation) is present but weak, and the 'when' is only implied via 'academic writing workflows that need...' with no explicit 'Use when...' trigger clause, which per the guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

Contains a relevant term ('study-card generation') but leads with the unnatural phrase 'academic writing workflows' and omits common user terms like 'flashcards' or 'Anki', fitting 'some relevant keywords but missing common variations'.

2 / 3

Distinctiveness Conflict Risk

Study-card generation is a recognizable niche, but framing the skill around 'academic writing workflows' overlaps with general academic-writing skills and could misroute, matching 'somewhat specific but could still overlap with similar skills'.

2 / 3

Total

8

/

12

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.

Validation15 / 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
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.