CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

novelty-vs-feasibility-assessor

Assesses whether a medical research topic is worth starting now by separating true novelty from pseudo-novelty, auditing real feasibility under stated resource constraints, and forcing a concrete start / narrow / redesign / stop decision. Always require explicit assumptions and never fabricate references, datasets, resource availability, precedent studies, or publication claims.

Quality

73%

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 ./awesome-med-research-skills/Evidence Insight/novelty-vs-feasibility-assessor/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-structured, genuinely actionable instruction skill with a clear ordered workflow, decision bands, and self-audit. Its weaknesses are internal redundancy (steps vs. output sections vs. hard rules) and a bundle where a majority of reference files are orphaned or duplicated relative to what SKILL.md signals.

Suggestions

Remove or merge the 9 orphaned reference files (or link them explicitly), especially the near-duplicates like novelty-assessment-framework.md, decision-band-rules.md, and literature-integrity-rules.md, so every bundled file is reachable and unambiguous.

Consolidate the Mandatory Output Structure with the 8 execution steps (e.g., annotate each step with its output section) and trim Hard Rules / "What This Skill Should Not Do" overlap to a single list.

Add one short worked example (a compressed sample assessment ending in a decision band) to make the expected output concrete.

DimensionReasoningScore

Conciseness

Mostly efficient — the body teaches domain-specific judgment standards Claude does not already know — but it duplicates itself: the 11-section Mandatory Output Structure largely restates Steps 2–7, Hard Rules overlap "What This Skill Should Not Do" and the referenced frameworks (e.g., pseudo-novelty flags appear in Step 2 and again as Hard Rule 7), and the Reference Module Integration bullets restate in-step references. It is not 2 because there is no generic padding or explanation of concepts Claude already knows.

3 / 5

Actionability

Concrete, executable instruction-only guidance: 8 ordered steps each with explicit sub-items, five named decision bands, a copy-paste redirect message for out-of-scope requests, and 11 mandatory output sections. It is not 5 because there is no worked example showing what a high-quality assessment output looks like, and some judgments (e.g., "Flag pseudo-novelty aggressively") depend entirely on referenced frameworks without inline anchors.

4 / 5

Workflow Clarity

Clear fixed sequence ("8 Steps (always run in order)") with checkpoints: Step 1 forces restatement of vague proposals with explicit assumptions, Step 8 is a pre-finalization self-critical audit, and Step 7 requires justifying the chosen band against the nearest alternative. It is not 5 because there is no explicit feedback loop (e.g., "if the Step 8 audit invalidates the band, revisit Step 7") — the audit is a checkpoint, not a retry path.

4 / 5

Progressive Disclosure

The body's five referenced files all exist, are one level deep, and each carries explicit "Use for..." signals — good practice. However, the actual bundle contains 14 reference files and 9 are never linked from SKILL.md, including apparent near-duplicates (novelty-assessment-framework.md vs novelty-audit-framework.md, decision-band-rules.md vs start-decision-bands.md, literature-integrity-rules.md vs literature-and-resource-integrity-rules.md), leaving over half the bundle undiscoverable and ambiguous about which file is authoritative. It is not 4 because this goes beyond minor organization gaps.

3 / 5

Total

14

/

20

Passed

Description

71%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, specific, third-person description that concretely delimits the skill's capabilities and integrity constraints. Its main gap is the absence of an explicit "Use when..." trigger clause, which caps completeness and slightly weakens trigger guidance.

Suggestions

Add an explicit trigger clause, e.g., "Use when a user asks whether a medical research topic, hypothesis, or project idea is novel or feasible enough to start, or wants a start / narrow / redesign / stop recommendation."

Include a few more natural user phrasings as trigger synonyms, such as "research idea", "go/no-go decision", or "should I start this study".

Sharpen distinctiveness by differentiating from adjacent skills (e.g., literature-gap analysis or study-design review) in one short clause.

DimensionReasoningScore

Specificity

The description lists multiple concrete, differentiated actions — "separating true novelty from pseudo-novelty", "auditing real feasibility under stated resource constraints", and "forcing a concrete start / narrow / redesign / stop decision" — with comprehensive coverage of the skill's capability plus integrity guardrails, matching the top anchor. It is not 4 because no meaningful capability within its niche is left uncovered.

5 / 5

Completeness

The "what" is clear and multi-part, but there is no "Use when..." clause or equivalent explicit trigger guidance; the "when" is only weakly implied by "worth starting now", so completeness is capped at 3 per the judging guidelines. It is not 2 because the what-side is detailed, not vague.

3 / 5

Trigger Term Quality

Good keyword coverage including natural terms users would say: "medical research topic", "worth starting", "novelty", "feasibility", "start / narrow / redesign / stop". It misses a few natural variations such as "research idea", "project idea", or "go/no-go decision", so it falls short of the comprehensive-synonyms anchor at 5.

4 / 5

Distinctiveness Conflict Risk

A clear niche (research topic start-decision analysis) with distinct triggers like pseudo-novelty flagging and start-decision bands, giving minimal conflict with unrelated skills. It is not 5 because sibling medical-research skills (e.g., literature-gap or study-design skills from the same suite) could plausibly trigger on similar novelty/feasibility language.

4 / 5

Total

16

/

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

aipoch/medical-research-skills

Path

awesome-med-research-skills/Evidence Insight/novelty-vs-feasibility-assessor/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.