CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ctd-api

Accesses Comparative Toxicogenomics Database (CTD) for chemical, gene, disease, and pathway interaction data. Invoke when user needs to query CTD, retrieve toxicogenomics data, or investigate chemical-disease relationships.

Quality

75%

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 ./scientific-skills/Evidence Insight/ctd-api/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

53%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.

The core reference material is well structured — executable commands, real parameters, and a genuine one-level-deep reference split — but the body is heavily padded with generic template sections (When to Use, Key Features, Implementation Details, Output Contract, Validation and Safety Rules, Failure Handling) that restate platitudes instead of CTD-specific guidance. The duplicated and vague workflow sections lack a concrete validation feedback loop.

Suggestions

Delete the boilerplate sections (Key Features, When to Use, Implementation Details, Required Inputs, Output Contract, Validation and Safety Rules, Failure Handling) or replace them with CTD-specific content; keep only Capabilities, Examples, References, and one concrete workflow.

Merge the "Example run plan" and "Recommended Workflow" into a single sequence with an explicit validation checkpoint tied to a real command (e.g., run a one-term test query and check the result before running the full batch), including a fix-and-retry step for API or validation errors.

Fix the concrete errors: remove the non-portable `cd "20260316/..."` path in Example Usage, and replace the fabricated `--help` "Expected output format" block with the script's actual usage output.

DimensionReasoningScore

Conciseness

Roughly half the body is generic template padding that adds nothing Claude doesn't know: "Use this skill when the request matches its documented task boundary", a "Key Features" section that restates the frontmatter description verbatim, abstract "Implementation Details" bullets ("Execution model: validate the request, choose the packaged workflow"), and a fabricated "Expected output format" block for `--help` that does not describe real output. It is not a 1 because the Capabilities/Examples/References sections carry genuinely useful, specific content.

2 / 5

Actionability

The Capabilities section provides fully executable commands (e.g., `python scripts/query_ctd.py --inputType chem --inputTerms "Mercury" --report genes_curated --format json`), concrete parameter enumerations, and copy-pasteable direct-link URL patterns. Minor gaps keep it from 5: the Example Usage begins with a non-portable `cd "20260316/scientific-skills/Evidence Insight/ctd-api"` path, and the "Expected output format" shown for `--help` does not match what the script would actually print.

4 / 5

Workflow Clarity

Two overlapping four-step lists ("Example run plan" and "Recommended Workflow") are present but generic — "Run a final validation pass for completeness, consistency, and safety" names no concrete checkpoint, and there is no validate-then-retry feedback loop despite the script driving batch API queries. The sequence is stated but checkpoints are vague, matching anchor 3; the batch-operation guidance also caps this dimension at 3.

3 / 5

Progressive Disclosure

The detailed inputType/report matrix is correctly split into `references/ctd_api_docs.md` (which exists), clearly signaled as "See references/ctd_api_docs.md for a complete list of valid inputType and report combinations" and referenced again in Parameters — one level deep, no nesting. It is not a 5 because the SKILL.md overview itself is cluttered by ~10 boilerplate sections that obscure the navigation structure.

4 / 5

Total

13

/

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 in third-person voice that explicitly covers both what the skill does and when to invoke it, with specific data domains and natural trigger phrases. Minor gaps in enumerated capability coverage and synonym variety keep it just below perfect.

DimensionReasoningScore

Specificity

"Accesses Comparative Toxicogenomics Database (CTD) for chemical, gene, disease, and pathway interaction data" plus "query CTD, retrieve toxicogenomics data, or investigate chemical-disease relationships" names several concrete actions and data types. It is not a 5 because coverage has minor gaps (phenotypes, GO terms, references, exposure data are all supported by the skill but unmentioned).

4 / 5

Completeness

"Accesses CTD for chemical, gene, disease, and pathway interaction data" clearly answers what, and "Invoke when user needs to query CTD, retrieve toxicogenomics data, or investigate chemical-disease relationships" explicitly answers when with concrete trigger phrases — a direct match for the anchor-5 example.

5 / 5

Trigger Term Quality

"query CTD", "toxicogenomics data", "chemical-disease relationships", and the full database name give good natural keyword coverage. It falls short of 5 because common synonyms like "chemical-gene interactions" and "Comparative Toxicogenomics Database" spelled without the acronym in trigger position are missing.

4 / 5

Distinctiveness Conflict Risk

CTD is a distinct niche resource and the triggers ("toxicogenomics", "CTD", "chemical-disease") are unlikely to match any other skill, giving minimal conflict risk.

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Evidence Insight/ctd-api/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.