paper-citation-planner

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

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

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

Quality

Content

87%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 content is lean, highly actionable, and well-structured for a simple instruction-only skill, with the only meaningful gap being the absence of a validation/verification loop for its batch citation-assignment operation.

Suggestions

Add an explicit verification step the model runs before replying, e.g. cross-check that every cited key exists in source_pack or bibliography and that >=20 distinct keys are used when >=20 are available.

Add a feedback instruction to fix and re-verify when the check fails (e.g. swap in valid keys or add missing citations) so the batch operation has a validate->fix->retry loop.

Optionally include a brief duplicate-stuffing check (no key repeated purely to pad density) as part of the verification sequence.

Dimension	Reasoning	Score
Conciseness	The body is lean: a one-line intro, a compact inputs list, a tight output-contract template, and hard rules, with no padding or explanation of concepts Claude already knows; every token earns its place.	5 / 5
Actionability	The output contract is copy-paste-ready with exact section names, field syntax, and enumerated role vocabularies, and the hard rules are specific and testable (e.g. "at least 20 distinct citation keys when at least 20 are available"), giving fully concrete executable guidance for an instruction-only skill.	5 / 5
Workflow Clarity	This batch citation-assignment operation has no validation or verification checkpoint (e.g. confirm every cited key exists in source_pack/bibliography, confirm >=20 keys used when available, confirm no duplicate stuffing), so per the batch-operation cap workflow clarity cannot exceed 3 despite the single action being unambiguous.	3 / 5
Progressive Disclosure	At under 50 lines with no need for external references, the content is well organized into clear sections (Inputs, Output contract, Hard rules) and is appropriately self-contained, satisfying the simple-skill exception for a top score.	5 / 5
	Total	18 / 20 Passed

Description

62%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 is clear and domain-specific, naming a concrete action and a workflow timing cue, but it omits an explicit "Use when..." trigger clause and broader natural synonyms that would improve trigger-term coverage and distinctiveness.

Suggestions

Add an explicit trigger clause, e.g. "Use when drafting paper sections that need citations mapped to a known BibTeX key set."

Broaden trigger terms with natural synonyms users say, such as "references," "bibliography," and "citations," so the skill surfaces for those phrasings.

List one or two more concrete actions (e.g. "assigns citation roles and checks keys against the available bibliography") to lift specificity from a single action to comprehensive coverage.

Dimension	Reasoning	Score
Specificity	"Map paper claims to available BibTeX citation keys" names the academic citation domain and one concrete action (mapping claims to keys), matching the anchor that names a domain plus 1-2 concrete actions without comprehensive coverage.	3 / 5
Completeness	It states both the "what" (map claims to citation keys) and a "when" ("before section drafting"), with the timing tied to a concrete writing stage; it falls short of a 5 only because there is no explicit "Use when..." trigger clause.	4 / 5
Trigger Term Quality	Terms like "paper claims," "BibTeX citation keys," and "section drafting" are relevant domain keywords, but common natural synonyms ("citations," "references," "bibliography") and file extensions are missing, fitting the anchor for some relevant keywords with missing variations.	3 / 5
Distinctiveness Conflict Risk	The niche of pre-draft citation planning against a BibTeX key set is mostly distinct from generic writing skills with only minor overlap risk, though it lacks the explicit trigger phrases that would secure a 5.	4 / 5
	Total	14 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: TokenRhythm/opensquilla
Path: src/opensquilla/skills/bundled/paper-citation-planner/SKILL.md
Commit: 94ac35e

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.