CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

79%

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

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.

A highly actionable, well-sequenced operational guide with executable commands, error remediation, and fallbacks. Its weaknesses are redundant positioning content that inflates token cost and an external dependency chain (integration contract, fetcher script) not shipped in the bundle.

Suggestions

Consolidate the duplicated positioning material: keep one comparison (either the 'Role & Positioning' table or the 'OpenAlex vs Other Sources' table plus 'When to use' bullets) and cut the other to reduce token cost.

Add an explicit post-search validation checkpoint in Step 4, e.g., check the JSON parses and results are non-empty before presenting, with a retry or fallback to /semantic-scholar if not.

Ship or inline the essentials of the integration-contract resolution policy (or include openalex_fetch.py in the bundle's scripts/) so the skill is not dependent on unresolvable external files.

DimensionReasoningScore

Conciseness

The workflow sections are efficient, but positioning content is duplicated: the 'Role & Positioning' table and 'Use OpenAlex when you want' bullets repeat the 'OpenAlex vs Other Sources' table and 'When to use' bullets at the bottom, and the description already covers much of it.

3 / 5

Actionability

Fully executable throughout: pip install, a verify command, a complete script-resolution chain with explicit error remediation, filtered search invocations, DOI and OpenAlex-ID work lookups, an enumerated result schema, and a presentation template — copy-paste ready and covering the common cases.

5 / 5

Workflow Clarity

Steps 1-6 are clearly sequenced with an explicit validation checkpoint in Step 2 (resolution failure terminates with remediation) and an API-failure fallback in Key Rules, but minor checkpoints like verifying non-empty/valid JSON results are only implicit.

4 / 5

Progressive Disclosure

A well-sectioned single file whose one external reference (shared-references/integration-contract.md §2) is clearly signaled with a link and section pointer, but that reference and the openalex_fetch.py helper live outside the bundle and are unresolvable here, leaving minor organization gaps.

4 / 5

Total

16

/

20

Passed

Description

78%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 with an explicit 'Use when' trigger clause, concrete data-type capabilities, and deliberate differentiation from sibling academic-search skills. Main gaps are a single action verb limiting specificity and a few missing natural trigger synonyms.

DimensionReasoningScore

Specificity

"Search academic papers via OpenAlex API" names the domain with one concrete action plus enumerated outputs ("open citation data, institutional affiliations, and funding information"), which matches the 1-2-concrete-actions anchor rather than the several-distinct-actions anchor above.

3 / 5

Completeness

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

5 / 5

Trigger Term Quality

Includes natural trigger phrases users would say ("openalex search", "search openalex", "open citation graph") but misses common research variations like "find papers", "citation lookup", or funding-related queries, fitting the good-coverage-with-a-few-missing anchor.

4 / 5

Distinctiveness Conflict Risk

The "beyond arXiv/Semantic Scholar" clause and OpenAlex-specific triggers give it a distinct niche, but the broader "comprehensive academic metadata" condition leaves minor overlap risk with closely related literature-search skills.

4 / 5

Total

16

/

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

Path

skills/openalex/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.