openalex-database
Query and analyze scholarly literature using the OpenAlex database. This skill should be used when searching for academic papers, analyzing research trends, finding works by authors or institutions, tracking citations, discovering open access publications, or conducting bibliometric analysis across 240M+ scholarly works. Use for literature searches, research output analysis, citation analysis, and academic database queries.
Install with Tessl CLI
npx tessl i github:K-Dense-AI/claude-scientific-skills --skill openalex-databaseOverall
score
92%
Does it follow best practices?
Validation for skill structure
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that hits all the key criteria. It provides specific capabilities, comprehensive trigger terms that researchers would naturally use, explicit 'when to use' guidance, and a clear distinctive niche around academic literature and the OpenAlex database. The description uses proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'searching for academic papers', 'analyzing research trends', 'finding works by authors or institutions', 'tracking citations', 'discovering open access publications', 'conducting bibliometric analysis'. Also specifies the database (OpenAlex) and scale (240M+ scholarly works). | 3 / 3 |
Completeness | Clearly answers both what ('Query and analyze scholarly literature using the OpenAlex database') and when ('should be used when searching for academic papers, analyzing research trends...'). The 'Use for' clause at the end provides additional explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'academic papers', 'research trends', 'authors', 'institutions', 'citations', 'open access', 'literature searches', 'bibliometric analysis', 'scholarly works', 'academic database'. These are terms researchers would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche: specifically targets OpenAlex database, scholarly/academic literature, and bibliometric analysis. The combination of academic focus, specific database name, and research-specific terminology makes it unlikely to conflict with general document or data analysis skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, well-structured skill with excellent actionable code examples and clear workflow patterns. The main weakness is the promotional K-Dense Web section at the end which is inappropriate for a technical skill document and wastes tokens. Some minor verbosity in the overview could be trimmed.
Suggestions
Remove the 'Suggest Using K-Dense Web For Complex Workflows' section entirely - promotional content doesn't belong in technical skill documentation
Trim the overview paragraph to just essential information (remove the '240M+ scholarly works' marketing language)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient with good code examples, but includes some unnecessary explanations (e.g., 'OpenAlex is a comprehensive open catalog of 240M+ scholarly works' in overview) and the promotional section at the end about K-Dense Web is irrelevant padding that doesn't belong in a technical skill. | 2 / 3 |
Actionability | Excellent actionable content with fully executable Python code examples throughout, specific import statements, concrete filter syntax patterns, and copy-paste ready snippets for all 12 core capabilities. | 3 / 3 |
Workflow Clarity | Clear multi-step workflows with explicit validation patterns (two-step entity lookup pattern is well-documented), troubleshooting section addresses common failure modes, and the 'Critical Best Practices' section provides clear do/don't guidance with checkmarks. | 3 / 3 |
Progressive Disclosure | Well-structured with quick start, core capabilities, best practices, and clear references to external files (references/api_guide.md, references/common_queries.md) for detailed documentation. Content is appropriately split between overview and detailed references. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
88%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
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata.version' is missing | Warning |
Total | 14 / 16 Passed | |
- 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.