CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

nature-academic-search

Search literature across sources, verify or manage citations, and build MeSH strategies or citation-impact audits. Use for 文献检索、引文核对、参考文献管理、严格他引 and evidence-backed citer profiles; not for translating a paper or drafting manuscript prose.

Quality

79%

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

Quality

Content

63%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-structured, token-efficient router whose progressive-disclosure design is sound in principle. Its execution is undermined by the bundle: the manifest and the entire always-load core layer it instructs Claude to read first are missing, leaving the first two steps of the protocol dangling.

Suggestions

Add the missing files (manifest.yaml, static/core/tools.md, static/core/routing-and-ops.md) or correct their paths — the routing protocol's first two steps and the wf5/wf6 deep links currently resolve to nothing in the bundle.

Have SKILL.md reference every script it ships: scripts/converters.py exists in the bundle but is never mentioned, while sibling scripts are; either wire it into the on-demand table or remove it.

Trim step 5's inline file enumeration to a pointer to the manifest's references.on_demand table (or vice versa) so the on-demand inventory lives in exactly one place.

DimensionReasoningScore

Conciseness

The router body is lean and assumes Claude's competence — no space is spent explaining concepts Claude already knows. It loses a point because step 5's enumerated on-demand file list ('for example references/source-tiers.md ... scripts/academic_search.py ... / scripts/preflight.py') duplicates what the manifest's references.on_demand table already declares, and the wf6 workflow bullet is wordier than its siblings.

4 / 5

Actionability

Instructions are concrete and file-specific ('Read [manifest.yaml](manifest.yaml)', 'load references/workflows/wf4-citation-file-mgmt.md'), but the foundational artifacts the first two steps depend on — manifest.yaml, static/core/tools.md, and static/core/routing-and-ops.md — are absent from the bundle, so the protocol cannot be executed as written. It is not score 4 because executable guidance with minor gaps would require the referenced paths to resolve; it stays above score 2 because the workflow fragments, shared modules, and scripts that do exist carry usable, specific steps (e.g., 'fall back to manual generation from MCP-fetched metadata if a script fails twice').

3 / 5

Workflow Clarity

A clear five-step sequence (load core → detect workflow → load fragments → run in priority order → on-demand references) with explicit error-recovery loops ('Report specific tool failures and continue with remaining tools; broaden terms when there are no results; fall back to manual generation ... if a script fails twice'). Not score 5 because there are no output validation checkpoints for the batch-like citation-file conversion workflow, only failure fallbacks.

4 / 5

Progressive Disclosure

The on-demand layering is well designed (router → workflow fragments → shared modules/scripts, each clearly signaled), but scoring against the actual bundle shows three referenced paths — manifest.yaml (the declared navigation hub), static/core/tools.md, and static/core/routing-and-ops.md (both listed under always_load and also linked from wf5/wf6) — do not exist, breaking navigation at step 1. It is not score 4 because good structure requires referenced paths to resolve; it is above score 2 because the workflow fragments and shared modules are present, clearly signaled, and independently navigable.

3 / 5

Total

14

/

20

Passed

Description

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

A strong description: concrete capabilities, an explicit bilingual 'Use for' trigger clause, and a well-chosen negative boundary. The only gap is a few natural English trigger variations and file-extension terms.

DimensionReasoningScore

Specificity

'Search literature across sources, verify or manage citations, and build MeSH strategies or citation-impact audits' plus 'evidence-backed citer profiles' lists multiple specific concrete actions covering every workflow the skill routes to. Not score 4 because coverage is comprehensive rather than having minor gaps; the actions are concrete, not generic.

5 / 5

Completeness

Explicitly answers both 'what' (search, verify/manage citations, MeSH strategies, citation-impact audits) and 'when' (an explicit 'Use for ...' clause with concrete trigger phrases), and adds a negative boundary ('not for translating a paper or drafting manuscript prose'). Both halves are concrete and explicit, matching the top anchor.

5 / 5

Trigger Term Quality

'Use for 文献检索、引文核对、参考文献管理、严格他引 and evidence-backed citer profiles' supplies natural trigger phrases in two languages, and terms like 'MeSH strategies' and 'citation-impact audits' are what domain users would say. Not score 5 because common English variations and file extensions users would naturally mention — 'PubMed', 'systematic review', 'bibliography', '.nbib/.ris/.bib' — are absent.

4 / 5

Distinctiveness Conflict Risk

A clear academic-literature niche with specialized triggers (MeSH, 严格他引, citer profiles) and an explicit exclusion of manuscript writing/translation. Not score 5 because 'Search literature across sources' is broad enough to overlap with general search or reference-formatting skills, keeping minor conflict risk.

4 / 5

Total

18

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 missing

Warning

referenced_paths_exist

Referenced path issues: 1 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository

Yuan1z0825/nature-skills

Path

skills/nature-academic-search/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.