CtrlK
BlogDocsLog inGet started
Tessl Logo

openalex

Search academic papers via OpenAlex API for open citation data, institutional affiliations, and funding information. Use when user says "openalex search", "search openalex", "open citation graph", or wants comprehensive academic metadata beyond arXiv/Semantic Scholar.

64

Quality

80%

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/openalex/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 highly actionable, well-sequenced search skill with copy-paste-ready commands and a real validation checkpoint for script resolution. Its main weaknesses are redundant comparison sections that hurt conciseness and a lack of progressive file-splitting for the heavier reference material.

Suggestions

Collapse the "Role & Positioning" table and the "OpenAlex vs Other Sources" table into a single comparison section to remove redundancy and tighten the body.

Move the detailed "OpenAlex vs Other Sources" feature matrix and "When to use OpenAlex over S2" guidance into a references/ file (e.g. COMPARISON.md) and link to it, improving progressive disclosure.

Add an explicit validation branch in the workflow for empty result sets or API errors (e.g., "if results empty, broaden filters or fall back to /semantic-scholar") to close the workflow-clarity validation gap.

DimensionReasoningScore

Conciseness

Mostly efficient operational detail, but the "Role & Positioning" table and the later "OpenAlex vs Other Sources" table overlap heavily, and "Key Rules" reiterates points already made ("OpenAlex is fully open", "Comprehensive metadata"), so it could be tightened.

3 / 5

Actionability

Fully executable, copy-paste-ready bash commands with real flags, concrete filter examples, DOI/OpenAlex-ID lookups, and a complete script-resolution chain with explicit remediation — common cases are well covered.

5 / 5

Workflow Clarity

A clear six-step sequence (Parse → Locate → Execute → Parse results → Present → Follow-up) with an explicit script-resolution validation checkpoint and error remediation; minor gaps are no in-workflow handling of empty results or API-error recovery.

4 / 5

Progressive Disclosure

No bundle files exist, so all content is inline; sections are well organized, but the large comparison tables and the "vs Other Sources" material that could live in a separate reference are inlined in a ~230-line file rather than split out.

3 / 5

Total

15

/

20

Passed

Description

83%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, well-targeted description that clearly states capabilities and provides concrete natural-language triggers, with explicit positioning against sibling academic-search skills. The only weakness is minor overlap risk within the academic-search skill family and a few missing trigger synonyms.

DimensionReasoningScore

Specificity

Names the domain and several specific capabilities ("open citation data, institutional affiliations, and funding information"), but does not enumerate the full action surface (e.g., DOI/ID lookups, cross-referencing), leaving minor gaps in coverage.

4 / 5

Completeness

Explicitly answers both what ("Search academic papers via OpenAlex API for open citation data, institutional affiliations, and funding information") and when with concrete trigger phrases ("Use when user says 'openalex search', 'search openalex', 'open citation graph'..."), matching the top anchor.

5 / 5

Trigger Term Quality

Includes several natural trigger phrases a user would say ("openalex search", "search openalex", "open citation graph"), but misses some common variations and synonyms; no file-extension equivalents apply to an API service.

4 / 5

Distinctiveness Conflict Risk

Clear niche with distinct triggers and an explicit boundary ("beyond arXiv/Semantic Scholar"), but it lives within a family of academic-search skills (arxiv, semantic-scholar, research-lit) so minor overlap risk remains.

4 / 5

Total

17

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 2 suspicious

Warning

Total

13

/

16

Passed

Repository
wanshuiyin/Auto-claude-code-research-in-sleep
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.