CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

reactome-skill

Submit compact Reactome ContentService requests for pathway, event, participant, search, and diagram-related data. Use when a user wants concise Reactome summaries

68

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

85%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, token-efficient single-purpose skill body with fully executable request examples and an explicit input/output contract. The only weaknesses are minor duplication and unexemplified capabilities (search endpoints, save_raw flow).

Suggestions

Replace the duplicated Execution example with a search-endpoint example so the 'search' capability mentioned in the paths and description is concretely demonstrated.

Show one save_raw=true example (with raw_output_path) since the full-payload escape hatch is described but never illustrated.

Drop or compress the repeated 'Accept: application/json' headers in the pattern examples, since the Operating rules already instruct it, to trim redundancy.

DimensionReasoningScore

Conciseness

The body is lean and operational — base_url, max_items heuristics, truncation handling, stdin field schema, output contract — with essentially no explanation of concepts Claude already knows. It is not 5 because of minor redundancy: the Execution section repeats a request already shown in 'Common Reactome patterns', and the Accept-header note is restated in all three examples.

4 / 5

Actionability

Three complete copy-paste JSON request objects plus a runnable bash invocation give mostly fully-executable guidance, matching the 'concrete code or commands with minor gaps' anchor. It is not 5 because the search endpoint and the save_raw=true full-payload flow are named but never exemplified.

4 / 5

Workflow Clarity

This is a simple single-purpose skill (under 50 lines) whose single action is unambiguous: construct a JSON object and pipe it to scripts/rest_request.py. The failure shape (ok=false with error.code/error.message) and the full-payload fallback (save_raw=true with raw_output_path) provide explicit checkpoints, satisfying the simple-skill exception for a 5.

5 / 5

Progressive Disclosure

At ~35 lines with well-organized sections (Operating rules, Execution behavior, Input, Output, Execution, References), the body appropriately keeps everything in one file and explicitly limits the bundle to SKILL.md and scripts/rest_request.py, which is a verified real file. Per the simple-skill exception, this earns a 5 with no external references needed.

5 / 5

Total

18

/

20

Passed

Description

78%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: third-person, domain-specific, and structured with an explicit 'Use when' trigger clause. The main limitation is narrow trigger coverage — one trigger phrase and no synonyms or identifier-style terms users would naturally say.

Suggestions

Broaden the when-clause with concrete trigger variations, e.g., 'Use when a user asks about Reactome pathways, events, or participants, or mentions pathway identifiers (R-HSA-*) or UniProt accessions.'

Add natural synonyms users would say, such as 'pathway lookup', 'protein/gene to pathways', or 'Reactome diagram', to strengthen trigger term coverage.

Consider stating the outcome Claude should produce (e.g., 'Return concise markdown summaries') in the description to make the 'what' fully actionable at trigger time.

DimensionReasoningScore

Specificity

"Submit compact Reactome ContentService requests for pathway, event, participant, search, and diagram-related data" names the domain plus five concrete data categories, matching the 'several specific actions; minor gaps' anchor. It falls short of 5 because the capability is expressed through a single verb (submit requests) rather than multiple distinct concrete actions.

4 / 5

Completeness

It has both a clear what ("Submit compact Reactome ContentService requests for pathway, event, participant, search, and diagram-related data") and an explicit when ("Use when a user wants concise Reactome summaries"), so it clears the missing-trigger cap of 3. It is not 5 because the when-clause is a single narrow trigger phrase and lacks the concrete trigger variation of the 5-anchor examples.

4 / 5

Trigger Term Quality

Natural keywords like Reactome, pathway, event, participant, search, and diagram give good trigger coverage, matching the 'good keyword coverage; a few natural terms missing' anchor. It is not 5 because common variations users would say (e.g., 'protein', 'gene', 'pathway lookup', R-HSA/UniProt identifiers) are absent.

4 / 5

Distinctiveness Conflict Risk

"Reactome ContentService" carves out a clear niche with distinct triggers (Reactome, pathway, event, participant, diagram), making accidental triggering of unrelated skills very unlikely, which matches the 'clear niche with distinct triggers; minimal conflict risk' anchor.

5 / 5

Total

17

/

20

Passed

Validation

100%

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

openai/plugins

Path

plugins/life-science-research/skills/reactome-skill/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.