CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

claude-scientific-skills

Scientific research and analysis skills

Quality

44%

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 ./plugins/AI-Agents-Safe-Coding-Skills/skills/claude-scientific-skills/SKILL.md

The canonical home for this skill is claude-scientific-skills in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

30%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 body is a near-empty stub: it repeats the description three times, provides no actionable guidance, no workflow, and defers everything to an external GitHub link with no bundled references. Brevity is the only strength, and it comes from an absence of content rather than efficient writing.

Suggestions

Replace 'This skill provides guidance and patterns' with concrete, executable instructions or code examples for the actual scientific tasks the skill covers — this is the single largest gap (actionability 1).

If the skill has real content in the source repository, bring key material into bundled reference files (e.g., references/analysis.md) and link them from the body instead of relying on an external URL.

Remove the redundant repetition of 'scientific research and analysis skills' across the Overview, When to Use, and Instructions sections, and give each section distinct, useful content.

DimensionReasoningScore

Conciseness

The body is brief and doesn't explain concepts Claude already knows, but the identical phrase 'scientific research and analysis skills' is repeated three times across sections with no new information — 'Efficient; minor instances ... that could be trimmed'. It is not a 5 because several tokens (the repeated Overview/When-to-Use boilerplate) earn nothing.

4 / 5

Actionability

The Instructions section only says 'This skill provides guidance and patterns for scientific research and analysis skills' — no code, commands, examples, or specific steps; it merely points to an external GitHub URL. This matches 'Entirely vague or abstract; no concrete code or commands; only describes rather than instructs'.

1 / 5

Workflow Clarity

No process is described at all — no steps, sequence, or validation checkpoints of any kind, matching 'Steps missing or incoherent; no sequence'. The body is a stub with nothing to sequence.

1 / 5

Progressive Disclosure

Sections (Overview, When to Use, Instructions) are present and organized, and no bundle files exist to reference. However, all substantive content is deferred to an external repository URL rather than bundled reference files, making the SKILL.md a pointer stub — matching 'Some structure but could be better organized' rather than a well-split 5, since navigation to actual content depends on an external site.

3 / 5

Total

9

/

20

Passed

Description

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

The description is a bare domain label that restates the skill name without stating any concrete capability, trigger conditions, or usage context. It scores in the low range on nearly every dimension and closely resembles the rubric's bad examples ('Helps with documents'). It needs concrete actions (e.g., which scientific tasks it supports) and an explicit 'Use when...' clause.

Suggestions

State concrete capabilities instead of the domain label, e.g., 'Performs literature searches, statistical analysis, and visualization of experimental data' — this would raise specificity from 2 toward 4-5.

Add an explicit trigger clause such as 'Use when the user mentions scientific data, experiments, lab results, or research analysis tasks' to fix the missing 'when' that currently caps completeness at 2.

Include natural trigger synonyms and specifics (e.g., disciplines or file types covered) to distinguish this skill from generic data-analysis and research skills.

DimensionReasoningScore

Specificity

The description "Scientific research and analysis skills" names a domain but contains no concrete actions whatsoever — there is not a single verb describing a capability. It matches the anchor 'Names the domain but actions are minimal or generic' (e.g., 'Processes PDF files'), and does not reach level 3 because no concrete action is stated.

2 / 5

Completeness

The 'what' is only a vague label (restates the skill's name) and there is no 'when to use' clause at all, matching 'Has a vague what and no when'. It is above level 1 only because a domain is at least named.

2 / 5

Trigger Term Quality

It includes relevant keywords ('scientific', 'research', 'analysis') that a user might naturally say, matching 'Some relevant keywords but missing common variations or synonyms'. It falls short of 4 because coverage is thin and generic — no discipline-specific terms, file formats, or natural phrase variations.

3 / 5

Distinctiveness Conflict Risk

'Scientific research and analysis' is very broad and would overlap with any research, data-analysis, or statistics skill, matching 'Very broad; high overlap risk with many similar skills'. The qualifier 'scientific' keeps it just above entirely-generic level 1.

2 / 5

Total

9

/

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

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills/skills/claude-scientific-skills/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.