CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

openalex-db

Access the OpenAlex database (240M+ scholarly works) for bibliometric analysis, literature search, and citation tracking; use when you need to query works/authors/institutions/concepts without an API key.

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 ./scientific-skills/Evidence Insight/openalex-db/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 compact, well-structured overview with a runnable code example and properly signaled, verified one-level-deep bundle references. The main weaknesses are redundant restatement across 'When to Use', 'Key Features', and 'Implementation Details' sections, and coverage of only the works-search case out of the four advertised entity types.

Suggestions

Merge the overlapping 'Key Features' and 'Implementation Details' bullets (Polite Pool, filtering, no-API-key) into one section — the Polite Pool point alone currently appears three times — to cut roughly a third of the body.

Add short copy-paste snippets for the other advertised entity methods (lookup author, compare institutions, explore concepts) so the code examples cover the common cases for all four entity types, not just works search.

Replace the hedging comment '# Field names depend on OpenAlex response schema' with the actual response shape or a pointer to the specific api_guide.md section covering pagination and error handling.

DimensionReasoningScore

Conciseness

The body is mostly efficient — no padding explaining concepts Claude already knows — but three sections overlap heavily: 'When to Use', 'Key Features', and 'Implementation Details' each restate citation tracking, trends, the no-key design, and Polite Pool (the email/Polite Pool point appears three times), and the search+filter mechanics are described twice (Example Usage and Implementation Details). This fits 'mostly efficient but could be tightened' (score 3) better than score 4, where over-explanation would be only minor.

3 / 5

Actionability

Provides a complete, executable example — client instantiation with a real parameter, a concrete filter_params value, install command for the dependency, and correct import path matching scripts/openalex_client.py. Falls short of score 5 because the example covers only works search while the skill claims authors, institutions, and concepts support with no usage shown, and the response handling hedges ('Field names depend on OpenAlex response schema') rather than instructing.

4 / 5

Workflow Clarity

For this single-action read-only skill the flow is unambiguous: install requests, instantiate OpenAlexClient (optionally with email), call search_works with search plus filter_params, and consult references/api_guide.md for filters/pagination. It sits at score 4 rather than 5 because pagination and error/rate-limit handling are deferred to the reference without any in-body checkpoint (e.g., checking response count or handling empty results beyond the minimal 'if works:').

4 / 5

Progressive Disclosure

The body is a well-organized overview with clearly signaled, one-level-deep references: 'refer to references/api_guide.md' (a real 17-line file, no nesting) and the real scripts/openalex_client.py entry point. It misses score 5 because filter details (e.g., {"is_oa": "true"}) are duplicated inline in both the example and Implementation Details while also living in api_guide.md, and only a single reference file exists, leaving the split slightly under-differentiated.

4 / 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 description: concrete, third-person, with an explicit 'use when' clause naming the queryable entities and the no-API-key differentiator. Keyword coverage is good but omits common synonyms like 'papers' and 'publications', and the broad 'literature search' trigger carries slight overlap risk with sibling scholarly-database skills.

DimensionReasoningScore

Specificity

Names several concrete actions — 'bibliometric analysis, literature search, and citation tracking' plus querying 'works/authors/institutions/concepts' — but coverage has minor gaps (no mention of filtering, trend analysis over time, or venue/year queries that the skill actually supports). It lists several specific actions with minor gaps, matching the score-4 anchor rather than the comprehensive score-5 anchor.

4 / 5

Completeness

Explicitly answers both: what — 'Access the OpenAlex database (240M+ scholarly works) for bibliometric analysis, literature search, and citation tracking' — and when — 'use when you need to query works/authors/institutions/concepts without an API key', with concrete trigger entities. This matches the score-5 anchor (both what and when with concrete trigger phrases); it is above score 4 because the 'when' clause is explicit and specific, not merely present or weakly implied.

5 / 5

Trigger Term Quality

Includes natural phrases users would say such as 'literature search', 'citation tracking', 'scholarly works', and entity names 'authors/institutions'. Missing common synonyms like 'papers', 'publications', or 'research articles', and 'works' is OpenAlex jargon rather than a user-natural term — good coverage with a few natural terms missing, fitting the score-4 anchor.

4 / 5

Distinctiveness Conflict Risk

The OpenAlex/bibliometrics niche with named entities and the 'without an API key' hook is mostly distinct with minimal conflict against generic skills. Minor overlap risk remains with other scholarly-database skills (e.g., PubMed or Semantic Scholar skills from the same medical-research collection) via the broad trigger 'literature search', so it fits the score-4 anchor rather than the minimal-conflict score-5 anchor.

4 / 5

Total

17

/

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

aipoch/medical-research-skills

Path

scientific-skills/Evidence Insight/openalex-db/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.