CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

scientific-problem-selection

Evaluate and prioritize research questions by importance, novelty, tractability, evidence, resources, ethics, and falsifiability.

62

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./resources/bundled-skills/scientific-problem-selection/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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-organized instruction-only skill with a clear sequenced workflow and explicit verification gates. Its main gaps are minor: a redundant Purpose line duplicating the description, and missing scoring mechanics (scale, weights, worked example) that would make the evaluation step fully executable.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — terse workflow steps ('Define field, decision horizon, available methods, resources, and constraints'), a compact tool-routing table, and no concept explanations. It is not a 5 because the '## Purpose' section repeats the frontmatter description verbatim, a small redundancy that could be trimmed; it is well above the midpoint because nothing is padded or over-explained.

4 / 5

Actionability

Guidance is concrete and instruction-only appropriate ('Express each candidate as a falsifiable question with a measurable outcome', 'Score importance, novelty, tractability, risk, ethics, and learning value', 'Identify required sample size, data access, and ethical approvals'). It is not a 5 because key details are missing — no scoring scale or rubric for the scoring step, no worked example, and no output template; it is above a 3 because the steps and gates are specific enough to execute without invention.

4 / 5

Workflow Clarity

The five-step workflow is clearly sequenced and the separate '## Completion gates' section supplies explicit checkpoints ('Verify novelty claims against current literature', 'State what result would change the research direction'). It is not a 5 because the gates are not tied into the step sequence and there are no feedback/recovery loops; it is above a 3 because validation checkpoints are explicitly present, not merely implied.

4 / 5

Progressive Disclosure

The skill is under 50 lines with no external references needed; content is organized into clear, well-labeled sections (Purpose, Tool routing, Workflow, Completion gates, Boundaries, Delivery) with nothing that belongs in a separate file inlined. Per the rubric guideline for short skills with no need for external references, this scores 5 with just well-organized sections.

5 / 5

Total

17

/

20

Passed

Description

66%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 has a clear, specific 'what' with good domain keyword coverage and a distinctive niche, but it entirely lacks a 'Use when...' trigger clause, capping completeness at 3 and weakening its routing value.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user asks which research question or problem to pursue, wants to compare candidate thesis/dissertation topics, or needs to assess the novelty or tractability of a research idea.'

Add natural synonyms and variations users would say, such as 'research problem', 'topic selection', and 'dissertation/thesis topic', alongside 'research questions'.

State the concrete outcome or deliverable (e.g., 'produces a scored, ranked comparison of candidate problems') so the 'what' is fully concrete.

DimensionReasoningScore

Specificity

The description lists two concrete actions ('Evaluate and prioritize research questions') and enumerates seven specific criteria ('importance, novelty, tractability, evidence, resources, ethics, and falsifiability'). It is not a 5 because only two verbs are given and the concrete output/deliverable is not described; it is above a 3 because the criteria enumeration goes well beyond naming a domain with 1-2 actions.

4 / 5

Completeness

The 'what' is clear ('Evaluate and prioritize research questions by importance, novelty, tractability...'), but there is no 'Use when...' clause or equivalent trigger guidance — the 'when' is not even weakly implied. Per the judging guideline, a missing 'Use when...' clause caps completeness at 3, which this description matches exactly.

3 / 5

Trigger Term Quality

Phrases like 'research questions', 'evaluate', 'prioritize', 'novelty', 'tractability', and 'falsifiability' are natural terms users would say when needing this skill. It is not a 5 because common variations such as 'research problem', 'topic selection', or 'dissertation/thesis topic' are missing; it is above a 3 because coverage extends well beyond a single domain keyword.

4 / 5

Distinctiveness Conflict Risk

The niche is fairly clear — evaluating and prioritizing research questions with criteria like falsifiability and tractability is distinct from document, code, or data skills. It is not a 5 because 'evaluate' and 'prioritize' are broad verbs and there is minor overlap risk with closely related skills like literature-review or research-planning skills (the body itself references a 'scholarly-research' skill).

4 / 5

Total

15

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

KunAgent/Kun

Path

resources/bundled-skills/scientific-problem-selection/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.