CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

scholar-research

Search, screen, synthesize, and cite scholarly literature and author metadata.

57

Quality

72%

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 ./resources/bundled-skills/scholar-research/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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.

A well-organized, token-efficient instruction-only skill with a clearly sequenced research workflow and explicit verification gates and boundaries. Its main weakness is actionability: guidance states what to extract and verify but not where to search or how to verify, leaving execution details to guesswork.

Suggestions

Name concrete scholarly sources in the tool routing or workflow (e.g., Crossref/OpenAlex APIs, PubMed, arXiv, Google Scholar) and map each to web_fetch or browser_use.

Add one example search-query formulation showing how to combine concepts, synonyms, and year filters.

Add a recovery rule to the completion gates, e.g. "If a DOI does not resolve, search the title on Crossref or the venue record before citing."

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it never explains what a preprint, DOI, or peer review is — matching the 'efficient with minor trimmable instances' anchor. It falls short of 5 because the "Purpose" section ("Search, screen, synthesize, and cite scholarly literature and author metadata") verbatim repeats the frontmatter description and the copyright line is non-instructional boilerplate.

4 / 5

Actionability

Concrete specifics exist ("Verify DOI, title, authors, venue, and year"; "Extract design, population, intervention or exposure, outcomes, limitations, and identifiers"; the tool routing table for web_fetch/browser_use), but key execution details are missing: no named portals or APIs (Crossref, OpenAlex, PubMed, arXiv), no example query formulations, and no method for verifying a citation. This matches the anchor for some concrete guidance that is incomplete.

3 / 5

Workflow Clarity

The workflow is a clearly sequenced five-step process ("Translate the question into concepts, synonyms, exclusions, years, and study types" through "Synthesize agreements, conflicts, gaps, and confidence") with a "Completion gates" verification section — matching the anchor for a clear sequence with most checkpoints present. It is not 5 because there is no error-recovery loop (e.g., what to do when a DOI fails to resolve or records conflict).

4 / 5

Progressive Disclosure

The skill is under 50 lines, needs no external references (none exist in references/, scripts/, or assets/ and none are dangled), and is organized into clear sections (Purpose, Tool routing, Workflow, Completion gates, Boundaries, Delivery). This meets the simple-skill exception: well-organized sections alone earn a 5.

5 / 5

Total

16

/

20

Passed

Description

58%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, concrete, and in third-person voice, clearly stating four domain-specific actions. Its main weaknesses are the complete absence of a "Use when..." trigger clause and limited natural vocabulary (no mention of papers, articles, journals, literature reviews, or well-known portals/identifiers users would say).

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks for a literature review, wants to find or verify academic papers, or needs citations with DOIs."

Include natural synonyms and named resources users would actually mention: papers, articles, journals, literature review, Google Scholar, PubMed, arXiv, DOI.

Mention the output form (e.g., verified citations with DOIs and venue/year metadata) to sharpen the "what".

DimensionReasoningScore

Specificity

"Search, screen, synthesize, and cite" lists four concrete verbs tied to a defined domain ("scholarly literature and author metadata"), matching the anchor for several specific actions with minor gaps in coverage. It falls short of 5 because it omits adjacent actions (e.g., formatting bibliographies, exporting citations) and includes no synonyms or file-type terms.

4 / 5

Completeness

The description has a clear "what" ("Search, screen, synthesize, and cite scholarly literature and author metadata") but no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. This matches the anchor for a clear what with the when missing or only weakly implied.

3 / 5

Trigger Term Quality

"scholarly literature", "cite", and "author metadata" are relevant keywords, but the common phrases users actually say — "papers", "articles", "journals", "literature review", "PubMed", "Google Scholar", "DOI" — are absent. This matches the anchor for some relevant keywords missing common variations or synonyms rather than the 'a few missing' level.

3 / 5

Distinctiveness Conflict Risk

"Scholarly literature and author metadata" carves a mostly distinct academic-research niche, distinct from generic document or writing skills. It is not 5 because without explicit trigger phrases it retains minor overlap risk with general web-search or research skills.

4 / 5

Total

14

/

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

KunAgent/Kun

Path

resources/bundled-skills/scholar-research/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.