nanoresearch-planning

Produce an experiment blueprint from a research hypothesis

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/nanoresearch-planning/SKILL.md

Quality

Content

86%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 lean, well-structured instruction-only skill that assumes Claude's competence and sequences its process clearly. It could be strengthened with worked examples and a lightweight validation step that the blueprint is internally consistent before output.

Dimension	Reasoning	Score
Conciseness	The ~35-line body is lean and well-organized with no padding and no explanations of concepts Claude already knows; every section earns its place, matching the 'lean and efficient; assumes Claude's competence' anchor.	5 / 5
Actionability	The process gives concrete parameters (2-4 baselines, primary/secondary metrics, ablation groups isolating each component) and a specified output schema, which is mostly actionable guidance with minor gaps; it lacks worked examples of dataset/baseline selection that would make it fully copy-paste ready.	4 / 5
Workflow Clarity	A clear 7-step numbered sequence ends in an explicit compile step with a defined output, but there are no explicit validation or verification checkpoints; since this is a reasoning-only planning task (not destructive or batch), the cap-at-3 rule does not apply, so it earns a 4.	4 / 5
Progressive Disclosure	The skill is under 50 lines, requires no external references, and is organized into clearly labeled sections (Purpose, Tools Required, Input, Process, Output), satisfying the simple-skill exception for a 5.	5 / 5
	Total	18 / 20 Passed

Description

53%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 clear and concise about what the skill does but lacks any explicit 'when to use' trigger guidance, which limits its completeness and trigger-term quality. Adding a 'Use when...' clause with natural synonyms would raise it across multiple dimensions.

Suggestions

Append a 'Use when...' clause, e.g. 'Use when planning experiments from a research hypothesis, designing ablation studies, or selecting evaluation datasets and baselines.'

List the concrete actions the skill performs (e.g., 'identifies datasets, selects baselines, defines metrics, designs ablations') to lift specificity from 3 toward 4-5.

Include natural trigger synonyms users would actually say, such as 'experiment design', 'ablation study', or 'baseline selection', to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The phrase 'Produce an experiment blueprint from a research hypothesis' names the domain and a single concrete action (producing a blueprint), matching the 'names domain and 1-2 concrete actions' anchor; it does not list the several specific actions needed for a 4 or 5.	3 / 5
Completeness	It clearly states the 'what' (produce an experiment blueprint) but provides no 'when should Claude use it' guidance, which per the judging guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	Terms like 'experiment blueprint' and 'research hypothesis' are relevant domain keywords, but there are no 'Use when...' trigger phrases and no common synonyms or variations, so it sits at the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The research-experiment-planning niche is fairly distinct and unlikely to trigger for unrelated skills, but the absence of explicit distinct trigger phrases keeps it from a 5.	4 / 5
	Total	13 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: OpenRaiser/NanoResearch
Path: skills/nanoresearch-planning/SKILL.md
Commit: 9d3b440

Reviewed: 11 days ago

Table of Contents

Discovery Implementation Validation

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.