CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

propose-hypotheses

Execute complete FPF cycle from hypothesis generation to decision

Quality

70%

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 ./plugins/fpf/skills/propose-hypotheses/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 well-structured, actionable orchestration workflow with strong sequencing and validation checkpoints; its main gaps are minor boilerplate repetition and the absence of explicit error-recovery loops for the parallel sub-agent stages.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence, providing concrete prompts and commands without explaining concepts Claude already knows; the repeated 'Launch fpf-agent with sonnet[1m] model' boilerplate across steps is minor padding that keeps it just below anchor 5.

4 / 5

Actionability

It gives copy-paste bash scaffolding and concrete sub-agent prompts with exact file paths and task-file references, but templated placeholders like '<summary from Step 1b>' and '<get from user>' require the main agent to fill them, fitting anchor 4 over 5.

4 / 5

Workflow Clarity

Nine steps are clearly sequenced with postconditions, conditional loops, 'Wait for all agents' barriers, file-move checks, and a completion checklist; it stays at anchor 4 rather than 5 because the parallel batch steps lack an explicit error-recovery feedback loop if an agent fails to move its file.

4 / 5

Progressive Disclosure

The SKILL.md acts as a clean orchestrator that delegates per-step detail to one-level-deep, well-signaled task files (${CLAUDE_PLUGIN_ROOT}/tasks/*.md); it is held at anchor 4 because those referenced files are not part of this skill's bundle and cannot be verified, and some inline prompt detail could live in references.

4 / 5

Total

16

/

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 conveys a clear niche and a recognizable what, but lacks an explicit 'when to use' trigger clause and leans on FPF jargon, which keeps most dimensions at the midpoint.

Suggestions

Add an explicit 'Use when ...' clause naming natural user triggers (e.g., 'Use when you need to generate and compare competing hypotheses and reach a defensible decision').

Spell out the intermediate cycle stages (verify, validate, audit) rather than relying on 'complete FPF cycle' to imply them.

Introduce a user-natural synonym for FPF (e.g., 'first-principles reasoning') to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

The phrase 'Execute complete FPF cycle from hypothesis generation to decision' names the domain and two endpoint actions (generation, decision), but the intermediate stages (verify, validate, audit) are only implied by 'complete FPF cycle' rather than explicitly listed, matching anchor 3 over anchor 4.

3 / 5

Completeness

A clear 'what' is stated (execute the FPF cycle from generation to decision) but there is no 'Use when...' clause or equivalent trigger guidance, so per the rubric cap completeness is held at anchor 3.

3 / 5

Trigger Term Quality

'hypothesis generation' and 'decision' are relevant domain keywords, but 'FPF cycle' is plugin jargon and no natural user-facing trigger phrases or synonyms are present, placing it at anchor 3 rather than 4.

3 / 5

Distinctiveness Conflict Risk

The FPF hypothesis-to-decision framing carves a clear niche that is unlikely to trigger for unrelated skills, with only minor overlap risk against other FPF sub-skills, fitting anchor 4 better than 5.

4 / 5

Total

13

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

NeoLabHQ/context-engineering-kit

Path

plugins/fpf/skills/propose-hypotheses/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.