023-assumption-analysis

Use when a framed and root-caused problem needs its assumptions made explicit before design or planning begins — explicit Assumptions, Unknowns, and a Validation plan. This should trigger when an issue's Assumption Analysis point of view needs evaluation, or when a maintainer directly asks to surface hidden assumptions and unknowns before committing to an approach. Part of Plinth Toolkit

Quality

73%

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/023-assumption-analysis/SKILL.md

Quality

Content

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a lean, well-organized overview that uses progressive disclosure effectively via a real one-level reference, though its actionable guidance and inter-step validation checkpoints are more directive than concrete.

Suggestions

Add a compact concrete structure or worked mini-example for at least one step (e.g. a sample assumption-as-falsifiable-claim and its paired validation check) to raise actionability.

Insert an explicit verify-then-proceed checkpoint between ranking and validation planning (e.g. confirm high-impact/low-confidence items before drafting the validation plan).

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence, with no padding or explanation of concepts Claude already knows; every section earns its place.	3 / 3
Actionability	Guidance is concrete ("state each assumption as a falsifiable claim", "rank by impact and confidence", "name how and when") but stays directive rather than giving specific, copy-paste-ready structures or examples for each step.	2 / 3
Workflow Clarity	A clear 6-step numbered sequence is present, but checkpoints are limited to a final report-and-flag step rather than explicit validate/retry feedback loops between steps.	2 / 3
Progressive Disclosure	The body is an overview that points to a single, clearly signaled one-level-deep reference (references/023-assumption-analysis.md, verified to exist), with content appropriately split and easy navigation.	3 / 3
	Total	10 / 12 Passed

Description

75%

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 clearly answers both what and when with an explicit trigger and a well-scoped niche, though its trigger terms lean on toolkit jargon and its action list is artifact-level rather than enumerating multiple distinct operations.

Suggestions

Add concrete user-facing trigger phrasings (e.g. "what are we assuming", "what don't we know yet", "validate our assumptions") alongside the toolkit-internal terms.

Enumerate a couple more distinct actions (e.g. "rank risks", "define validation checks") to lift specificity toward the level-3 anchor.

Dimension	Reasoning	Score
Specificity	Names concrete deliverables ("explicit Assumptions, Unknowns, and a Validation plan") but stays at the artifact level rather than listing multiple distinct concrete actions like the level-3 anchor.	2 / 3
Completeness	Explicitly answers both what ("explicit Assumptions, Unknowns, and a Validation plan") and when ("Use when a framed and root-caused problem needs its assumptions made explicit before design or planning begins").	3 / 3
Trigger Term Quality	Includes relevant terms (assumptions, unknowns, validation plan, root-caused, design or planning) but leans on internal jargon ("Assumption Analysis point of view", "framed and root-caused problem") rather than a broad set of natural user phrasings.	2 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (pre-design assumption surfacing in a specification toolkit) with distinct triggers unlikely to fire for unrelated skills.	3 / 3
	Total	10 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: jabrena/plinth
Path: skills/023-assumption-analysis/SKILL.md
Commit: 26b0e71

Reviewed: about 21 hours 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.