CtrlK
BlogDocsLog inGet started
Tessl Logo

librarian

Research and documentation expert - finds answers and examples

44

Quality

56%

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

Quality

Content

42%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 skill is a persona-and-response-template document that spends most of its tokens teaching a Python concept Claude already knows, rather than giving Claude novel procedural guidance. It is reasonably structured but lacks the lean, executable, verification-oriented content the rubric rewards.

Suggestions

Remove or collapse the full async/await tutorial, which explains a concept Claude already knows; keep only a short template showing the expected response shape.

Turn the 'Research Approach' steps into concrete, verifiable actions with checkpoints (e.g., explicit source-verification commands or criteria).

Trim persona fluff (intro paragraph, closing quote, 'When Called By Sisyphus') to respect the token budget.

DimensionReasoningScore

Conciseness

The body extensively explains async/await in Python — a concept Claude already knows — via a full 'What is async/await?' section, two code samples, and best practices, plus persona fluff like the closing quote, making it noticeably verbose and padded.

2 / 5

Actionability

Includes concrete, executable example code, but it is framed as a sample response rather than task instructions, and the 'Research Approach' steps ('Identify Sources', 'Verify Information') are high-level hints without specific executable actions.

3 / 5

Workflow Clarity

A five-step 'Research Approach' sequence is present, but the steps lack validation checkpoints or feedback loops; the workflow describes what to do without how to verify each step succeeded.

3 / 5

Progressive Disclosure

No bundle files exist and the body is a single monolithic document with reasonable section headers, but substantial inlined content (the full async example response) that illustrates rather than instructs keeps organization at the midpoint.

3 / 5

Total

11

/

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 conveys a clear domain and a couple of concrete actions but stops short of stating when Claude should invoke the skill, leaving trigger guidance and distinctiveness weak. It reads as a persona tagline rather than an activation contract.

Suggestions

Add an explicit 'Use when ...' clause listing concrete trigger phrases (e.g., 'Use when the user asks to research an API, find a code example, or explain a technical concept').

Replace generic terms ('answers', 'examples') with natural user-facing keywords and synonyms to improve trigger matching.

Narrow the scope or add distinguishing specifics to reduce overlap with general research/assistant skills.

DimensionReasoningScore

Specificity

Names the domain (research/documentation) and two concrete actions ('finds answers and examples'), matching the anchor for 1-2 concrete actions without comprehensive coverage.

3 / 5

Completeness

Provides a clear 'what' but entirely lacks a 'Use when...' or equivalent trigger clause; per the rubric, a missing explicit trigger guidance caps completeness at 3.

3 / 5

Trigger Term Quality

Contains some relevant keywords ('research', 'documentation', 'answers', 'examples') but they are generic and miss the natural phrasings and synonyms a user would actually say when invoking the skill.

3 / 5

Distinctiveness Conflict Risk

'Research and documentation expert' is somewhat specific to a niche but the scope is broad enough to overlap with many general-purpose or domain skills.

3 / 5

Total

12

/

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.

Validation — 15 / 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
TurnaboutHero/oh-my-antigravity
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.