Design dashboard layout sketches for clinical trials showing enrollment progress and adverse event rates
71
57%
Does it follow best practices?
Impact
98%
4.26xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./scientific-skills/Data analysis/dashboard-design-for-trials/SKILL.mdQuality
Discovery
50%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 excels at specificity and carves out a clear, distinctive niche in clinical trial dashboard design. However, it critically lacks any 'Use when...' guidance, making it incomplete for Claude's skill selection process. The trigger terms are domain-appropriate but could benefit from common variations.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user asks for clinical trial dashboards, enrollment tracking visualizations, or adverse event monitoring layouts'
Include common term variations users might say: 'trial dashboard', 'AE rates', 'patient enrollment charts', 'safety dashboard', 'wireframe'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Design dashboard layout sketches', 'clinical trials', 'enrollment progress', and 'adverse event rates'. These are concrete, domain-specific capabilities. | 3 / 3 |
Completeness | Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance. Per rubric guidelines, missing explicit trigger guidance caps completeness at 2, and this has no 'when' component at all. | 1 / 3 |
Trigger Term Quality | Contains good domain terms like 'dashboard', 'clinical trials', 'enrollment', 'adverse event rates', but missing common variations users might say like 'trial dashboard', 'patient enrollment', 'AE rates', 'safety metrics', or 'wireframe'. | 2 / 3 |
Distinctiveness Conflict Risk | Highly specific niche combining clinical trials domain with dashboard design for specific metrics (enrollment, adverse events). Unlikely to conflict with general dashboard or general clinical skills. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides good actionable CLI documentation with clear parameters and examples, but is bloated with template boilerplate sections (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status) that don't help Claude execute the task. The core functionality is clear but lacks validation guidance for verifying output quality.
Suggestions
Remove or relocate boilerplate sections (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status) that don't provide actionable guidance for generating dashboards
Add a validation step showing how to verify the generated HTML renders correctly (e.g., open in browser, check for expected modules)
Include a brief example of what the output HTML structure looks like or link to a sample output file
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes substantial boilerplate sections (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status) that add little value for Claude's execution. The core usage information is reasonably concise, but the document is padded with template content. | 2 / 3 |
Actionability | Provides concrete, executable CLI commands with clear parameter documentation. The examples show exact command-line invocations with realistic values that are copy-paste ready. | 3 / 3 |
Workflow Clarity | The skill describes a single-step process (run the script), but lacks validation steps for the output. No guidance on verifying the generated HTML is correct or handling errors if generation fails. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but everything is in one file including boilerplate that could be elsewhere. No references to external documentation for advanced customization or the actual script implementation details. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
ca9aaa4
Table of Contents
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.