CtrlK
BlogDocsLog inGet started
Tessl Logo

paper-citation-planner

Map paper claims to available BibTeX citation keys before section drafting.

61

Quality

72%

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 ./src/opensquilla/skills/bundled/paper-citation-planner/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

87%Weight 40%Scale 1-3

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

The content is concise and highly actionable with a clear output contract, the only notable gap being a missing self-verification step for the constraint-heavy batch of citations.

Suggestions

Add a pre-output verification step, e.g. 'Before emitting CITATION_PLAN, confirm every cited key exists in source_pack or bibliography and that >=20 distinct keys are used when available.'

Optionally include a brief self-check for duplicate or filler citations to close the validation loop on the USAGE_RULES constraints.

DimensionReasoningScore

Conciseness

The body is lean: brief input definitions, a concrete output template, and tight hard rules with no over-explanation of concepts Claude already knows, matching 'lean and efficient; every token earns its place'.

3 / 3

Actionability

An explicit output-contract template with placeholders and role enums plus specific hard rules (>=20 keys, only keys from source_pack/bibliography, assign to claims not filler) gives copy-paste-ready, executable guidance for an instruction-only skill.

3 / 3

Workflow Clarity

The single-task structure and output format are unambiguous, but hard batch constraints (>=20 distinct keys, keys must exist in source_pack/bibliography) lack an explicit verification checkpoint before emitting the plan, fitting 'sequence present but checkpoints missing or implicit'.

2 / 3

Progressive Disclosure

At under 50 lines with no need for external references, the well-organized Inputs / Output contract / Hard rules sections satisfy the simple-skill carve-out for progressive disclosure at level 3.

3 / 3

Total

11

/

12

Passed

Description

57%Weight 40%Scale 1-3

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 is specific and occupies a distinct niche, but lacks an explicit use-when trigger and relies on somewhat technical terms, leaving completeness and trigger-term coverage at the mid level.

Suggestions

Add an explicit trigger clause, e.g. 'Use when drafting a paper and deciding which references support each claim before writing sections.'

Broaden trigger terms with natural user phrasings such as 'references', 'which papers to cite', and 'citation plan' alongside 'BibTeX citation keys'.

Consider naming additional concrete actions (e.g. 'assign citation roles and check key availability') to lift specificity toward level 3.

DimensionReasoningScore

Specificity

The phrase 'Map paper claims to available BibTeX citation keys' names the domain and one concrete action, but does not list multiple distinct actions, matching the 'names domain and some actions, but not comprehensive' anchor rather than the multi-action level 3.

2 / 3

Completeness

It clearly states what the skill does, but the 'when' is only implied via 'before section drafting' with no explicit 'Use when...' trigger clause, which per the judging guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

Terms like 'BibTeX citation keys', 'paper claims', and 'section drafting' are domain-relevant but lean technical and omit common natural variations a user might say ('references', 'which papers to cite', 'citation plan'), fitting 'some relevant keywords but missing common variations'.

2 / 3

Distinctiveness Conflict Risk

Academic citation planning against BibTeX keys is a clear, narrow niche with distinct triggers that is unlikely to conflict with other skills, matching the 'clear niche with distinct triggers' anchor.

3 / 3

Total

9

/

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