skill-pressure-test

Interrogate a plan, decision, or design one question at a time until it holds — use to stress-test your own thinking before committing to it

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 ./.claude/skills/skill-pressure-test/SKILL.md

Quality

Content

85%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, highly actionable instruction skill with explicit checkpoints, feedback loops, and a verification checklist — strong across every dimension. Its only soft spot is minor rhetorical padding and the lack of a full worked interview example.

Dimension	Reasoning	Score
Conciseness	The body is lean, assumes Claude's competence, and does not explain concepts Claude already knows; minor rhetorical justifications (e.g. 'A batch of questions is a questionnaire…') could be trimmed, keeping it just below a 5.	4 / 5
Actionability	It provides concrete directives, a copy-paste-ready question pattern (the token-expiry example), a 5-part Output Contract template, and a Verification checklist; the only gap is the absence of a full worked end-to-end interview example.	4 / 5
Workflow Clarity	It gives a clear sequenced workflow with explicit Stop/Checkpoint rules, feedback loops for error recovery (naming disagreement, reopening dependent work on new evidence), and a closing Verification checklist, matching the anchor for explicit validation and checklists.	5 / 5
Progressive Disclosure	Content is well-organized into clear sections with no nested references, no bundle files, and nothing that belongs in a separate file; it satisfies the 'no need for external references + well-organized' case for a top score.	5 / 5
	Total	18 / 20 Passed

Description

70%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 clear, third-person, and distinguishes the skill well, with explicit trigger guidance that answers both what and when. Its main limitation is specificity — it names one core action rather than several concrete capabilities, which is partly inherent to a meta-skill.

Suggestions

Add 1-2 more concrete actions to raise specificity, e.g. 'walk each branch of the decision tree and resolve dependencies one at a time' rather than a single 'interrogate' action.

Make the 'when' more trigger-phrase concrete by naming situations the user would say, e.g. 'use before committing to a hard-to-reverse change, or when scope feels slippery'.

Include a synonym like 'pressure-test' or 'red-team' alongside 'stress-test' to broaden natural trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (plan/decision/design) and one concrete mechanism ("interrogate one question at a time", "stress-test"), matching the 1-2 concrete actions anchor; it does not list several discrete actions, so it stops short of 4.	3 / 5
Completeness	It gives a clear "what" (interrogate one question at a time until it holds) and explicit trigger guidance ("use to stress-test your own thinking before committing to it"), but the "when" is a purpose/condition rather than concrete user-said trigger phrases, leaving it just below a 5.	4 / 5
Trigger Term Quality	"plan", "decision", "design", "stress-test", and "interrogate" are natural phrases a user would say; a few synonyms (e.g. "pressure test", "red-team") are absent, so it is good-but-not-comprehensive coverage.	4 / 5
Distinctiveness Conflict Risk	It carves a distinct niche (attacking an existing position before commitment) but overlaps with sibling thinking skills (thought-partner, decision-support) referenced in the body, giving minor rather than minimal conflict risk.	4 / 5
	Total	15 / 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: nyldn/claude-octopus
Path: .claude/skills/skill-pressure-test/SKILL.md
Commit: 0093dab

Reviewed: 5 days 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.