CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

string-database

Query the STRING database for protein-protein interactions (PPIs), functional enrichment, and homology. Use when the user asks about interactions between specific proteins, interaction evidence, confidence scores, protein interaction partners, or pathway enrichments.

Quality

85%

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

SKILL.md
Quality
Evals
Security

Quality

Content

78%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-structured, appropriately lean skill body with excellent progressive disclosure — every referenced bundle file exists and is clearly signposted. The main gaps are the absence of a consolidated numbered workflow and of a single concrete example command in SKILL.md itself.

Suggestions

Consolidate the operating sequence (uv setup, license notification, ask species, map identifiers, run command, post-process output) into a single numbered workflow so the order of operations is explicit rather than implied across sections.

Include one copy-paste-ready example invocation with a real subcommand (e.g., a minimal 'map' call) in SKILL.md so the CLI's usage pattern is concrete before the reader jumps to a reference file.

Trim the repetitive MUST-emphasis in Core Rule 1 to a single unambiguous statement (e.g., 'Never guess the species — if unstated, ask for the NCBI Taxon ID first') to save tokens without losing the behavioral constraint.

DimensionReasoningScore

Conciseness

The body is lean with no explanations of concepts Claude already knows, but Rule 1's layered emphasis ("MANDATORY", "You MUST NOT guess", "you MUST stop and ask", "you MUST still ask — do not default to Human") repeats the same instruction several times and could be tightened. It is above level 3 (only one padded passage) but not level 5's every-token-earns-its-place.

4 / 5

Actionability

The body provides a concrete executable template ("uv run scripts/string_cli.py <command> [options] --output /tmp/out.tsv"), exact file paths, and pointed navigation to reference files that contain full command examples. It falls short of level 5 because no fully concrete worked invocation (with a real subcommand and arguments) appears in SKILL.md itself — the command remains a placeholder.

4 / 5

Workflow Clarity

A clear sequence is discernible (prerequisites, license check, mandatory species checkpoint, map identifiers first, run with --output, post-process via jq/grep) with one hard validation checkpoint (the species question). It is not level 5 because the steps are distributed across sections rather than consolidated into an ordered workflow, and there is no explicit output-verification step; the destructive/batch cap does not apply since these are non-destructive read-only queries.

4 / 5

Progressive Disclosure

The body is a clear overview with four well-signaled, one-level-deep references (mapping.md, interactions.md, enrichment.md, valuesranks.md), each annotated with when to read it, plus explicit guidance to start with the most appropriate file. All referenced files exist with real content, and scripts/string_cli.py is present, so navigation is complete and easy.

5 / 5

Total

17

/

20

Passed

Description

87%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 with an explicit and well-constructed 'Use when' trigger clause and a clear, distinctive niche. The only weaknesses are minor: the identifier-mapping capability is unmentioned and a few natural synonyms are absent.

DimensionReasoningScore

Specificity

The description lists several concrete capability areas — "protein-protein interactions (PPIs), functional enrichment, and homology" — but omits the identifier-mapping capability the skill itself documents, leaving minor gaps in coverage. It is above level 3 (more than 1-2 actions named) but short of level 5's comprehensive coverage.

4 / 5

Completeness

It clearly answers both questions: the "what" is "Query the STRING database for protein-protein interactions (PPIs), functional enrichment, and homology" and the "when" is an explicit "Use when the user asks about..." clause enumerating concrete trigger conditions. This matches the level 5 anchor with concrete trigger phrases, exceeding level 4's looser 'when'.

5 / 5

Trigger Term Quality

Triggers like "interactions between specific proteins", "confidence scores", "protein interaction partners", and "pathway enrichments" are phrases users would naturally say, and the PPI acronym is included. It falls short of level 5 because natural synonyms such as "PPI network", "binding partners", or "STRING" are missing.

4 / 5

Distinctiveness Conflict Risk

The named STRING database plus domain-specific triggers (protein interaction partners, confidence scores, pathway enrichments) establish a clear niche with minimal conflict risk against generic skills. It is not level 4 because the triggers are distinctive to this specific bioinformatics domain rather than overlapping closely related skills.

5 / 5

Total

18

/

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/string_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.