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

77%

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

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 well-structured and efficient: a clear sequenced workflow, concrete actionable constraints, and a clean one-level progressive-disclosure split into a verified reference file. The only real improvement is tightening minor redundancy between the "What is covered" section and the later Workflow/Constraints sections.

Dimension	Reasoning	Score
Conciseness	The body is lean with bulleted constraints and a numbered workflow, but the "What is covered in this Skill?" section overlaps with the Workflow and Constraints sections, leaving minor redundancy that could be trimmed.	4 / 5
Actionability	Concrete, specific instruction-style guidance ("state each assumption as a falsifiable claim believed true but not yet verified", "rank by impact if wrong and by current confidence") with the detailed worked examples appropriately deferred to the reference file.	4 / 5
Workflow Clarity	A clear six-step sequence (read reference, surface assumptions, list unknowns, rank, validation plan, report) with a flag-open-items checkpoint in step 6; this is an analytical skill so the destructive/batch validation cap does not apply, but it lacks explicit validation feedback loops.	4 / 5
Progressive Disclosure	A concise overview body with one clearly signaled, one-level-deep reference ("see references/023-assumption-analysis.md") that is a real file, with detailed examples and constraints appropriately split into that reference.	5 / 5
	Total	17 / 20 Passed

Description

76%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 strong: it explicitly states both what the skill produces and when to trigger it, with concrete deliverables and mostly-distinct niche positioning. Its main weakness is trigger-term quality, where abstract jargon crowds out the natural phrases a user would actually say.

Suggestions

Replace jargon-heavy triggers ("Assumption Analysis point of view needs evaluation") with natural user phrases such as "Use when surfacing assumptions and unknowns before committing to a design".

Add common synonyms a user might say (e.g. "hidden assumptions", "what we're assuming", "what we don't know yet") to broaden natural keyword coverage.

Drop the toolkit self-label ("Part of Plinth Toolkit") from the description, or move it to metadata, so the trigger text stays focused on user intent.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete deliverables ("explicit Assumptions, Unknowns, and a Validation plan", "surface hidden assumptions and unknowns"), listing multiple specific actions with minor gaps in coverage.	4 / 5
Completeness	Clearly and explicitly answers both what ("explicit Assumptions, Unknowns, and a Validation plan") and when ("Use when a framed and root-caused problem..." / "This should trigger when...") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Some relevant keywords are present but the phrasing leans abstract and jargon-heavy ("Assumption Analysis point of view needs evaluation"), missing common natural variations a user would actually say.	3 / 5
Distinctiveness Conflict Risk	The Assumption Analysis niche within the Plinth Toolkit is mostly distinct with only minor overlap risk against general problem-analysis or planning skills.	4 / 5
	Total	16 / 20 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: f6dfc6f

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