CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

explore-references

Research how a feature works in reference libraries

Quality

70%

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 ./.opencode/skills/explore-references/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 is a well-structured, self-contained instruction skill: concrete library paths, a clear research process, and a complete output template with no padding or explanations of things Claude already knows. It would benefit only marginally from an example search invocation and a verify-findings step before writing the output document.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence — it never explains what PDFs or these libraries are, and project-specific constraints ("We target Node, Bun, and browsers equally") earn their tokens. Minor filler in the Guidelines section ("Be thorough", "Don't just describe; analyze and recommend") keeps it at anchor 4 rather than 5.

4 / 5

Actionability

Concrete guidance throughout: exact checkout paths for all three libraries, a specific output location (`.agents/scratch/<topic>-research.md`), and a complete copy-paste output template. Missing example search commands or an exemplar research snippet, so it fits anchor 4 (mostly executable with minor gaps) rather than 5.

4 / 5

Workflow Clarity

The sequence (understand request → search each library → compare → extract insights → write findings) is clearly laid out with per-step detail and an "ask the user if unclear" checkpoint. No output validation step exists, but this is read-only research writing to a scratch file, so the destructive/batch cap does not apply; it sits at anchor 4 rather than 5 for the missing feedback loop.

4 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent) and none are needed: the skill is self-contained with well-organized sections (Task, Research Process, Output Format, Guidelines, Begin) and nothing that belongs in a separate file. At ~90 lines it exceeds the under-50-line simple-skill exception, so anchor 4 is the best fit.

4 / 5

Total

16

/

20

Passed

Description

50%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 concise and grammatically clean but thin: it states a single generic action over a loosely-defined domain with no trigger guidance. Without a "Use when..." clause or the library names, it will be hard for Claude to know when to invoke it and easy to confuse with general research skills.

Suggestions

Add an explicit trigger clause, e.g. "Use when implementing a PDF feature and we need to see how existing libraries handle it."

Name the reference libraries (pdf.js, pdf-lib, PDFBox) as trigger terms so users who mention a library by name naturally match this skill.

State the deliverable in the description (a comparison research document) to sharpen the "what" beyond the generic verb "research".

DimensionReasoningScore

Specificity

"Research how a feature works in reference libraries" names the domain ("reference libraries") and one action ("research how a feature works"), matching the anchor for domain plus 1-2 concrete actions. It falls short of anchor 4 because it lists no specific libraries or deliverables, and above anchor 2 because the object of research is stated rather than purely generic.

3 / 5

Completeness

The "what" is clear (research how a feature works in reference libraries) but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is not a 2 because the "what" is concrete, and not a 4 because the "when" is entirely absent rather than just imprecise.

3 / 5

Trigger Term Quality

Some relevant keywords are present ("research", "feature", "reference libraries"), but the natural phrases a user would actually say — library names like pdf.js, pdf-lib, PDFBox, or "how does X implement Y" — are missing. This fits the anchor for some relevant keywords missing common variations or synonyms.

3 / 5

Distinctiveness Conflict Risk

"reference libraries" scopes the skill somewhat within this project, but "research how a feature works" overlaps broadly with generic code-exploration and research skills, matching the anchor for somewhat specific but still able to overlap with similar skills.

3 / 5

Total

12

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

LibPDF-js/core

Path

.opencode/skills/explore-references/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.