CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

open-source-license-check

Check if referenced bioinformatics software/code licenses allow commercial use (GPL vs MIT, etc.).

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Evidence Insight/open-source-license-check/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

56%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 actionable sections (Usage, Parameters, License Types, Error Handling) are solid and match the actual bundle, but they are buried in ~150 lines of generic template boilerplate and circular cross-references. Trimming to the task-specific content and consolidating duplicated audit commands into the reference file would substantially improve the skill.

Suggestions

Delete the filler sections ("Key Features", "Dependencies", "Example Usage", "Implementation Details") whose only content is a circular pointer like "See `## Usage` above", and consolidate the duplicated py_compile/--help commands that appear in three sections into one.

Remove or relocate generic template boilerplate — "Security Checklist", "Risk Assessment", "Evaluation Criteria", "Lifecycle Status", "Response Template" — that adds no license-checking-specific guidance, keeping only task-relevant material in SKILL.md.

Replace the hardcoded environment path in Example Usage ("cd \"20260318/scientific-skills/Evidence Insight/open-source-license-check\"") with a path relative to the skill bundle so the documented commands run as written.

DimensionReasoningScore

Conciseness

Roughly half the body is padded boilerplate: "Key Features", "Dependencies", "Example Usage", and "Implementation Details" are filler with circular pointers ("See `## Prerequisites` above", "See `## Usage` above"), the same two commands are repeated across "Quick Check" and "Audit-Ready Commands", and "Security Checklist", "Risk Assessment", "Evaluation Criteria", and "Lifecycle Status" are generic template content unrelated to license checking, matching the "several unnecessary explanations or padded sections" anchor.

2 / 5

Actionability

The Usage section gives fully executable commands ("python scripts/main.py --software \"samtools,bwa,bedtools\"", "--check-requirements requirements.txt") that match the actual packaged script, plus runnable verification commands and a concrete license table. The minor gap is the Example Usage section's hardcoded path ("cd \"20260318/scientific-skills/Evidence Insight/open-source-license-check\"") that does not exist in the bundle, which keeps it below fully copy-paste ready.

4 / 5

Workflow Clarity

The 5-step Workflow has a coherent sequence with most checkpoints explicit: scope validation with an early stop ("stop early if the task would require unsupported assumptions"), a pre-execution parse check ("python -m py_compile scripts/main.py"), an output review step ("Review the generated output and return the final artifact"), and an error-recovery feedback loop ("switch to the fallback path and state exactly what blocked full completion"). It falls short of 5 because steps 3-5 are generic template language rather than task-specific validation of license-check results.

4 / 5

Progressive Disclosure

The single reference ("references/audit-reference.md - Supported scope, audit commands, and fallback boundaries") is real, one level deep, and clearly signaled, and scripts/main.py is properly referenced. However, substantial content that belongs in separate files (or nowhere) is inlined — the audit commands are duplicated in three places, and checklists, risk tables, and response templates pad the main file — matching the "content that should be separate is inline" anchor.

3 / 5

Total

13

/

20

Passed

Description

65%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 clear, domain-specific description with good natural keywords, but it only states what the skill does without any "Use when..." trigger guidance. Adding an explicit trigger clause with a few more synonyms would lift both completeness and trigger coverage.

Suggestions

Add a "Use when..." clause with concrete triggers, e.g., "Use when a pipeline or manuscript references bioinformatics tools and the user asks whether licenses (GPL, MIT, AGPL) permit commercial use."

Broaden trigger coverage with synonyms such as "open source", "copyleft", "permissive", and "license compliance" so the description matches more natural user phrasings.

Consider naming one or two additional concrete outputs (e.g., "produces a license compatibility report with commercial-use warnings") to move specificity beyond a single action.

DimensionReasoningScore

Specificity

The description names the domain ("bioinformatics software/code licenses") and one concrete action ("Check if... licenses allow commercial use") with concrete license examples ("GPL vs MIT, etc."), but lists only a single action rather than several, matching the 1-2-actions anchor rather than the several-actions anchor above.

3 / 5

Completeness

The "what" is clear (check bioinformatics software licenses for commercial use), but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines; the "when" is at best weakly implied by "referenced".

3 / 5

Trigger Term Quality

Natural keywords like "bioinformatics software", "licenses", "commercial use", "GPL", and "MIT" are terms users would plausibly say, but common synonyms such as "open source", "copyleft", or "license compliance" are missing, so coverage is good rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

The combination of bioinformatics tooling, license checking, and commercial-use assessment is a clear niche with distinct triggers and minimal conflict risk against generic skills; the 4 anchor's "minor overlap risk with closely related skills" is not a better fit since no closely related trigger surface is described.

5 / 5

Total

15

/

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/open-source-license-check/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.