uniprot-database
Direct REST API access to UniProt. Protein searches, FASTA retrieval, ID mapping, Swiss-Prot/TrEMBL. For Python workflows with multiple databases, prefer bioservices (unified interface to 40+ services). Use this for direct HTTP/REST work or UniProt-specific control.
Install with Tessl CLI
npx tessl i github:K-Dense-AI/claude-scientific-skills --skill uniprot-databaseOverall
score
86%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation 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 clearly articulates specific capabilities (protein searches, FASTA retrieval, ID mapping), uses domain-appropriate trigger terms that users would naturally say, and explicitly addresses both when to use this skill and when to prefer an alternative. The description is concise yet comprehensive, and the differentiation from bioservices reduces potential skill conflicts.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Protein searches, FASTA retrieval, ID mapping, Swiss-Prot/TrEMBL' - these are distinct, actionable capabilities in the bioinformatics domain. | 3 / 3 |
Completeness | Clearly answers both what ('Protein searches, FASTA retrieval, ID mapping') and when ('Use this for direct HTTP/REST work or UniProt-specific control'), plus provides helpful guidance on when to prefer an alternative (bioservices for Python workflows). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'UniProt', 'REST API', 'Protein searches', 'FASTA', 'ID mapping', 'Swiss-Prot', 'TrEMBL', 'HTTP/REST' - these are exactly what bioinformatics users would mention. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche: specifically targets UniProt REST API access and explicitly differentiates from bioservices skill for Python workflows, reducing conflict risk with related bioinformatics skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
73%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides solid, actionable guidance for UniProt API access with good examples and well-organized progressive disclosure. However, it suffers from some verbosity (promotional content, obvious use cases) and lacks validation/error handling guidance for API operations that could fail. The workflow clarity would benefit from explicit error recovery patterns.
Suggestions
Remove the 'When to Use This Skill' section - these use cases are self-evident from the content
Remove the promotional 'Suggest Using K-Dense Web' section entirely - it adds no value to the skill
Add error handling guidance for API operations: rate limit responses (429), validation of returned data, retry logic for failed requests
Add a validation step to the ID mapping workflow showing how to verify mapping results before proceeding
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some unnecessary sections like 'When to Use This Skill' which lists obvious use cases Claude would infer. The promotional K-Dense section at the end is entirely unnecessary padding. | 2 / 3 |
Actionability | Provides concrete, executable examples throughout - real API endpoints, actual query syntax, specific field names, and clear Python function signatures. The code examples are copy-paste ready with real URLs and parameters. | 3 / 3 |
Workflow Clarity | The ID mapping workflow has clear steps (submit, check status, retrieve), but lacks validation checkpoints. No error handling guidance for failed API calls, rate limiting responses, or validation of returned data. Batch operations lack feedback loops. | 2 / 3 |
Progressive Disclosure | Well-structured with clear overview, organized sections, and appropriate references to external files (api_fields.md, id_mapping_databases.md, query_syntax.md). References are one level deep and clearly signaled with descriptive labels. | 3 / 3 |
Total | 10 / 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.