database-lookup

Query documented public database APIs with explicit endpoints, filters, pagination, and provenance. Use when a scientific, regulatory, financial, or other database-backed fact must be retrieved reproducibly from a named source rather than inferred from general knowledge.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

92%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-architected reference skill: actionable, sequenced with validation checkpoints for batch retrieval, and cleanly split across one-level-deep reference files. The only weakness is mild verbosity in a few overview tables.

Dimension	Reasoning	Score
Conciseness	The body is information-dense and avoids explaining concepts Claude already knows, but at ~380 lines some tables and guidance could be tightened; mostly efficient with minor over-explanation.	4 / 5
Actionability	Provides executable curl commands, concrete endpoint URLs, worked identifier-format examples with real IDs, specific rate limits, and named pagination patterns covering common cases.	5 / 5
Workflow Clarity	A 7-step Core Workflow is clearly sequenced with explicit validation checkpoints (count first, reconcile counts, fail visibly) plus a dedicated error-recovery feedback loop, satisfying the batch-operation validation requirement.	5 / 5
Progressive Disclosure	SKILL.md is a well-signaled overview pointing to 80 one-level-deep reference files (e.g. references/alphafold.md, references/database_selection_guide.md); all referenced paths resolve and per-database detail lives in separate files.	5 / 5
	Total	19 / 20 Passed

Description

92%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, third-person description that states concrete capabilities and an explicit, multi-domain trigger clause. It cleanly distinguishes the skill from inference-based answering and is unlikely to fire for the wrong skill.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions — 'explicit endpoints, filters, pagination, and provenance' — giving comprehensive coverage of the retrieval capability rather than vague language.	5 / 5
Completeness	Explicitly answers both what ('Query documented public database APIs with explicit endpoints, filters, pagination, and provenance') and when ('Use when a scientific, regulatory, financial, or other database-backed fact must be retrieved reproducibly').	5 / 5
Trigger Term Quality	Includes natural domain terms users would say ('scientific, regulatory, financial... database-backed fact', 'public database APIs') with good cross-domain coverage, though a few common synonyms are absent.	4 / 5
Distinctiveness Conflict Risk	Carves a clear niche — reproducible retrieval from a named source 'rather than inferred from general knowledge' — minimizing overlap with general-knowledge or search skills.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: K-Dense-AI/scientific-agent-skills
Path: skills/database-lookup/SKILL.md
Commit: b2a92ba

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.