CtrlK
BlogDocsLog inGet started
Tessl Logo

paper-source-curator

Curate search results and BibTeX entries into a reliable source pack for a long research paper.

57

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./src/opensquilla/skills/bundled/paper-source-curator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

80%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 concise and well-structured for a simple instruction-only curation skill, with a crisp output contract and hard rules. Its main gap is the absence of an explicit verification step for the batch selection of 20-40 sources, which caps workflow clarity. Adding a brief validation/check step would raise that dimension.

Suggestions

Add an explicit verification step before output (e.g., 'Confirm refN keys are unchanged and 20-40 usable references are selected; if not, adjust before emitting SOURCE_PACK').

Include one short worked example showing the SOURCE_PACK format with a couple of refN lines.

Optionally note how to handle the edge case where fewer than 20 usable references are available.

DimensionReasoningScore

Conciseness

The body is lean and efficient with no concept explanations or padding; every line (inputs, output contract, hard rules) earns its place and assumes Claude's competence.

5 / 5

Actionability

An exact output template and concrete rules (20-40 references, preserve refN keys, no invented sources) give mostly executable guidance, though a small worked example would close the gap to fully copy-paste-ready.

4 / 5

Workflow Clarity

Inputs, output contract, and hard rules are clearly laid out, but this batch selection operation (20-40 sources) has no validation/verification checkpoint, which caps workflow clarity at 3 per the batch-operation guideline.

3 / 5

Progressive Disclosure

Under 50 lines, single-purpose, no external references needed, with well-organized sections (Inputs, Output contract, Hard rules), qualifying for the simple-skill exception at anchor 5.

5 / 5

Total

17

/

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 conveys a clear purpose and specific domain but omits any explicit "Use when..." trigger guidance, which caps completeness and leaves trigger-term coverage incomplete. It is reasonably distinct from sibling skills. Adding a concrete trigger clause with natural user phrases would lift the weakest dimensions.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers (e.g., 'Use when gathering references, citations, or literature for a long research paper').

Include natural synonyms users say ('references', 'citations', 'literature search') alongside 'BibTeX' and 'search results'.

List 1-2 more concrete actions (e.g., 'selects, classifies, and excludes sources') to raise specificity.

DimensionReasoningScore

Specificity

"Curate search results and BibTeX entries into a reliable source pack" names the domain plus 1-2 concrete actions (curate, assemble a pack) but does not enumerate multiple specific actions, matching anchor 3.

3 / 5

Completeness

It clearly states what the skill does but provides no "Use when..." trigger clause; per the guidelines a missing explicit trigger caps completeness at 3.

3 / 5

Trigger Term Quality

Relevant terms like "search results", "BibTeX", "source pack", and "research paper" appear, but common natural variations users would say ("references", "citations", "literature", "find sources") are missing.

3 / 5

Distinctiveness Conflict Risk

The niche (curating BibTeX/search-result source packs for long research papers) is fairly distinct with limited overlap risk, sitting noticeably above the somewhat-generic anchor 3 but below the fully-distinct anchor 5.

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.

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