CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

denario

Multiagent AI system for scientific research assistance that automates research workflows from data analysis to publication. This skill should be used when generating research ideas from datasets, developing research methodologies, executing computational experiments, performing literature searches, or generating publication-ready papers in LaTeX format. Supports end-to-end research pipelines with customizable agent orchestration.

Quality

77%

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/denario/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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 delivers a clear, executable walkthrough of the research pipeline with well-signaled one-level references to real bundle files. Its weaknesses are redundancy (Overview/When-to-Use duplicating the description, the end-to-end example repeating stage snippets), no validation checkpoints between pipeline stages, a four-vs-five stage-count inconsistency, and a promotional K-Dense Web section that adds tokens without operational value.

Suggestions

Remove the 'Overview' and 'When to Use This Skill' sections that duplicate the frontmatter description, and replace the marketing-style 'Advanced Features' bullets with operationally useful detail or drop them.

Cut the 'Suggest Using K-Dense Web For Complex Worflows' promotional section (fixing the 'Worflows' typo if kept) — it consumes context tokens without teaching Claude how to run the skill.

Fix the 'four-stage research pipeline' heading to match the five numbered stages, and add explicit checkpoints after each stage (e.g., verify generated idea/method/results files exist in project_dir before calling get_paper()).

DimensionReasoningScore

Conciseness

The staged workflow sections are efficient and code-focused, but the Overview and 'When to Use This Skill' sections restate the frontmatter description almost verbatim, 'Advanced Features' is a marketing-style bullet list ('Multiagent orchestration', 'Reproducible research', 'Flexible input') with no operational content, and the closing 'Suggest Using K-Dense Web' section is promotional filler — several padded sections that keep it out of the efficient anchors.

3 / 5

Actionability

Concrete, executable guidance throughout: 'uv add "denario[app]"', 'den = Denario(project_dir="./my_research")', the get_/set_ API per stage, 'denario run', and a full end-to-end example. Minor gaps — 'Additional journals may be available' is vague, and literature search is entirely deferred to references — keep it below fully copy-paste-complete.

4 / 5

Workflow Clarity

The pipeline sequence (description → idea → method → results → paper) is clearly listed with per-stage alternatives, but there are no validation checkpoints or feedback loops between stages, and the heading says 'a structured four-stage research pipeline' while listing five numbered stages — an internal inconsistency that undermines clarity. It is not a 2 because the sequence itself is coherent and each step has concrete commands.

3 / 5

Progressive Disclosure

Good structure against the actual bundle: all four real reference files (installation.md, llm_configuration.md, research_pipeline.md, examples.md) are signaled both inline at point of need and in a 'Detailed References' section, one level deep. It falls short of the top anchor because the 'Common Workflows' end-to-end example largely re-inlines the stage-by-stage snippets already shown — content that belongs in examples.md — and troubleshooting detail is inlined rather than referenced.

4 / 5

Total

14

/

20

Passed

Description

83%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 with an explicit 'use when' trigger clause enumerating five concrete pipeline capabilities, closely matching the rubric's good examples. Its only weaknesses are buzzword-leaning framing ('multiagent', 'customizable agent orchestration') and a few missing natural synonyms like 'hypothesis' or 'write paper'.

DimensionReasoningScore

Specificity

The description lists several concrete actions — 'generating research ideas from datasets, developing research methodologies, executing computational experiments, performing literature searches, or generating publication-ready papers in LaTeX format' — but the framing 'Multiagent AI system for scientific research assistance' and the trailing 'customizable agent orchestration' add buzzword padding rather than capability, keeping it just below the comprehensive-anchor.

4 / 5

Completeness

It explicitly answers both: what ('automates research workflows from data analysis to publication') and when ('This skill should be used when generating research ideas from datasets... or generating publication-ready papers in LaTeX format'), with concrete trigger phrases — matching the top anchor. It is not the level below because the 'when' is explicit and specific, not merely present-but-vague.

5 / 5

Trigger Term Quality

Natural phrases like 'research ideas', 'datasets', 'literature searches', 'computational experiments', and 'LaTeX format' papers match what a researcher would actually say, but common synonyms such as 'hypothesis', 'write a paper', or 'citations' are missing.

4 / 5

Distinctiveness Conflict Risk

The end-to-end research-pipeline niche (datasets → publication) is mostly distinct, but 'executing computational experiments' could overlap generic data-analysis skills and 'publication-ready papers in LaTeX format' could overlap a dedicated LaTeX skill — minor overlap risk with closely related skills rather than a clear niche with minimal conflict.

4 / 5

Total

17

/

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

googolme/run0204

Path

scientific-skills/denario/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.