CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

interpro-database

Identify domains, families, and sites in proteins; find all proteins in a family or sharing a domain; explore species distribution for a domain; annotate genomes with protein families and GO terms. InterPro combines 14 databases (e.g., Pfam, CDD) into one searchable resource. InterPro-N significantly expands annotation and sequence coverage with deep learning. Includes domain architecture (IDA) search.

Quality

74%

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/interpro_database/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 well-engineered API skill body: concrete commands, a clearly sequenced two-step IDA workflow, and genuine guardrails (rate-limit wrapper, count-not-iterate rule, InterPro-N fallback) with real, well-signaled reference files. The main costs are marketing-style prose, background explanation Claude does not need, an inline parameter list that duplicates the API reference, and a handful of non-copy-paste command examples.

Suggestions

Trim the Overview prose, Entry Types definitions, and 'panoptic segmentation' background to one line each, and shrink the inline parameter list to the few most-used params per endpoint, delegating the rest to references/api_reference.md.

Fix the example commands so every one is copy-paste executable: add 'uv run' to the /structure, /taxonomy, /proteome, and /set examples and add shell line continuations (or single-line form) to the multi-line IDA and fetch examples.

Reference references/citation.bib from the body (e.g., a one-line 'Cite InterPro as: ...' note) so every bundle file is discoverable.

DimensionReasoningScore

Conciseness

The bulk is dense, actionable reference material, but there is measurable padding: the Overview paragraph ('capitalises on their individual strengths to produce a powerful diagnostic tool') is marketing prose, the Entry Types section explains concepts at length, the InterPro-N 'panoptic segmentation' background is not needed to use the flag, and the ~70-line inline parameter listing substantially duplicates references/api_reference.md. This sits between anchors 3 and 4 but closer to 3 because several sections could be trimmed or moved without losing actionability.

3 / 5

Actionability

Guidance is mostly executable: concrete CLI invocations with flags, Python import examples, the four endpoint-construction patterns, and correct-vs-wrong count examples. It misses a 5 because several example commands are not copy-paste runnable — the IDA and multi-line examples omit shell line-continuation backslashes, and the /structure, /taxonomy, /proteome, and /set examples drop the 'uv run' prefix.

4 / 5

Workflow Clarity

Multi-step processes are clearly sequenced: the IDA search is an explicit two-step workflow (find architectures, then fetch proteins by ida_id), and the InterPro-N fallback rule ('if standard queries return no results you MUST retry with the interpro_n flag') plus the never-iterate-to-count rule act as validation checkpoints for a batch-prone API. Minor gaps remain — e.g., no guidance on verifying output files were written correctly before processing — so it does not reach the explicit validate/fix/retry standard of a 5.

4 / 5

Progressive Disclosure

Structure is good: SKILL.md serves as an overview with clearly signaled, one-level-deep, verified links to references/api_reference.md ('For a complete, exhaustive list...') and references/example_responses.tsv, and the inline quick-reference subset is a reasonable digest rather than a duplicate dump. It falls short of 5 because references/citation.bib exists in the bundle but is never referenced or navigable from the body, and the inline parameter listing is long enough that it arguably belongs in the reference file.

4 / 5

Total

15

/

20

Passed

Description

71%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 specific, action-dense description with strong natural keywords for the protein-domain-analysis niche. Its main structural weakness is the complete absence of explicit 'when to use' trigger guidance, which both caps completeness and slightly weakens its routing reliability against adjacent bioinformatics skills.

Suggestions

Append an explicit trigger clause, e.g., 'Use when the user mentions InterPro, Pfam, protein domains or families, domain architecture, or wants GO-term annotation of proteins/genomes.'

Add one or two common synonyms users actually say (e.g., 'protein annotation', 'sequence analysis') to broaden natural trigger coverage.

Clarify the InterPro-N sentence so it reads as a capability ('Identify remote homologs in uncharacterised proteins via InterPro-N deep-learning predictions') rather than a database fact, keeping triggers actionable.

DimensionReasoningScore

Specificity

The description lists multiple concrete, verbatim actions — 'Identify domains, families, and sites in proteins', 'find all proteins in a family or sharing a domain', 'explore species distribution for a domain', 'annotate genomes with protein families and GO terms', plus 'Includes domain architecture (IDA) search' — giving comprehensive coverage of the skill's capabilities. It exceeds the score-4 anchor ('several specific actions; minor gaps') because every major capability of the skill is named concretely.

5 / 5

Completeness

The 'what' is clearly and concretely answered, but there is no 'Use when...' clause or equivalent explicit trigger guidance anywhere in the description — per the judging guidelines this caps completeness at 3. It does not reach 4 because the 'when' is not even weakly implied by a usage clause, only inferable from the domain language itself.

3 / 5

Trigger Term Quality

Good keyword coverage: 'domains', 'families', 'protein family', 'species distribution', 'GO terms', 'annotate genomes', 'Pfam', 'CDD', 'InterPro', 'InterPro-N' are all natural terms users would say. It falls short of the score-5 anchor because common variations like 'protein annotation', 'sequence analysis', 'UniProt', or file/format terms users often mention are absent.

4 / 5

Distinctiveness Conflict Risk

The description names its clear niche — InterPro specifically, with member databases like Pfam and CDD and the distinctive InterPro-N and IDA-search features — so triggers are distinct. It is not a 5 because phrases like 'annotate genomes with protein families and GO terms' could overlap with closely related bioinformatics skills (e.g., a UniProt or GO annotation skill).

4 / 5

Total

16

/

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

google-deepmind/science-skills

Path

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