CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

jaspar-api

Access JASPAR database for transcription factor binding profiles (matrices), collections, and species via REST API. Use when user wants to search for transcription factors, retrieve matrix details (PFM/PWM), infer profiles from protein sequences, or explore JASPAR collections.

Quality

77%

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/jaspar-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 '## Usage' section is genuinely good — concrete, executable commands covering the main API operations with verified script support — but it is buried in template boilerplate ('When to Use', 'Key Features', 'Implementation Details') that duplicates the description and adds no JASPAR-specific guidance. The run plan is generic and lacks real validation checkpoints. Trimming the filler would roughly halve the body while improving clarity.

Suggestions

Delete the template sections that add no skill-specific information: 'When to Use' bullets 2–4, all of 'Key Features' and 'Implementation Details', and the self-referential 'Example Usage: See `## Usage` above' line — keep only the concrete command examples.

Rewrite the 'Example run plan' to match the actual script: remove the non-existent 'in-file CONFIG block' step, use paths relative to the skill directory instead of `cd "20260316/scientific-skills/Evidence Insight/jaspar-api"`, and add a real checkpoint such as checking the API response for errors before returning results.

Move the duplicated parameter documentation to `references/api_docs.md` and document the missing subcommands (`collections_read`, `species_list`) in the Usage section so the inline list matches the script's full interface.

DimensionReasoningScore

Conciseness

Roughly half the body is generic template boilerplate: 'When to Use' bullets 2–4 ('a evidence insight task needs a packaged method instead of ad-hoc freeform output', 'expects a concrete deliverable, validation step, or file-based result'), the entire 'Key Features' section that restates the frontmatter description verbatim, the 'Implementation Details' section ('Execution model: validate the request, choose the packaged workflow, and produce a bounded deliverable'), and the non-instruction 'Example Usage: See `## Usage` above for related details' (which also points the wrong way — the Usage section appears below it). This is several padded sections, matching anchor 2 rather than anchor 3's 'some unnecessary explanation'.

2 / 5

Actionability

The '## Usage' section provides concrete, verified-executable commands for four subcommands (e.g., `python scripts/jaspar_client.py matrix_list --search "SMAD3" --tax_group "Vertebrates"`) with a documented parameter list, all confirmed against the actual script's subparsers. It falls short of anchor 5 due to the environment-specific `cd "20260316/scientific-skills/Evidence Insight/jaspar-api"` path and the undocumented `collections_read`/`species_list` subcommands.

4 / 5

Workflow Clarity

The 'Example run plan' lists a 4-step sequence but it is generic template language — step 2 ('Edit the in-file CONFIG block') refers to a CONFIG block the script does not have, and there are no checkpoints for API errors, empty results, or rate limits. Sequence present with implicit/missing checkpoints matches anchor 3 rather than anchor 4's 'most checkpoints present'. The operations are read-only REST calls, so the destructive/batch cap at 3 does not apply.

3 / 5

Progressive Disclosure

The body clearly signals a real, one-level-deep reference ('See `references/api_docs.md` for full parameter lists and endpoint details' — the file exists and covers the endpoints) and the implementation lives in the bundled `scripts/jaspar_client.py`. Minor gaps keep it at anchor 4 rather than 5: the inline parameter list duplicates content that belongs in the reference file, and the vague 'Reference material available in `references/`' line adds noise.

4 / 5

Total

13

/

20

Passed

Description

92%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: it states concrete capabilities in third person and pairs them with an explicit 'Use when...' clause covering the skill's four main scenarios, closely matching the rubric's good examples. The only weakness is synonym coverage — domain-common phrases like 'motif' and 'position weight matrix' are absent.

DimensionReasoningScore

Specificity

The description lists four concrete, distinct actions ('search for transcription factors, retrieve matrix details (PFM/PWM), infer profiles from protein sequences, or explore JASPAR collections') with named data objects, giving comprehensive coverage of the skill's capabilities. It matches the anchor-5 exemplar structure rather than anchor 4, which requires 'minor gaps in coverage'.

5 / 5

Completeness

It explicitly answers both 'what' (first sentence: 'Access JASPAR database for transcription factor binding profiles (matrices), collections, and species via REST API') and 'when' ('Use when user wants to search for transcription factors, retrieve matrix details (PFM/PWM), infer profiles from protein sequences, or explore JASPAR collections') with concrete trigger phrases, mirroring the anchor-5 exemplar. It clearly exceeds anchor 4, where the 'when' clause is less specific.

5 / 5

Trigger Term Quality

Natural domain terms are present ('transcription factors', 'binding profiles', 'matrices', 'PFM/PWM', 'protein sequences', 'JASPAR'), but common synonyms users would say are missing — notably 'motif' and 'position weight matrix', which are the most frequent phrasings in this domain. Good coverage with a few natural terms missing matches anchor 4 rather than anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

Named-database triggers ('JASPAR database', 'PFM/PWM', 'infer profiles from protein sequences') carve out a clear niche with minimal overlap with any other skill class. It is well above anchor 4, which still allows 'minor overlap risk with closely related skills'.

5 / 5

Total

19

/

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