CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

principle-never-block-on-the-human

Apply when tempted to ask 'should I do X?' on reversible work. Proceed, present the result, let the human course-correct after the fact; reserve confirmation for irreversible actions.

67

Quality

84%

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

SKILL.md
Quality
Evals
Security

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.

An exceptionally tight principle skill: every section either states the rule, justifies it, or bounds it, and the Pattern/Boundaries split makes the reversible-vs-irreversible decision crisp. The only notable weakness is mild redundancy in the cost rationale and the absence of a worked example of the proceed-then-present pattern.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence, but the cost argument is repeated three times ('Code is cheap. Waiting is expensive.', 'a wrong decision usually costs less than blocking', 'Code is cheap, attention is scarce'), so a few tokens could be trimmed.

4 / 5

Actionability

For an instruction-only skill the guidance is concrete and directive with a quoted example ('Don't ask "should I do X?" Do X, explain why') and concrete action categories in the boundaries, though no worked example of a good proceed-then-present message is given.

4 / 5

Workflow Clarity

A simple single-purpose skill whose single action is unambiguous: proceed without blocking on reversible work, with a clearly delineated exception for irreversible actions (force-push, delete production data, send external messages). No destructive or batch operations, so no validation cap applies.

5 / 5

Progressive Disclosure

Under 50 lines with no need for external references (none exist in the bundle), and the content is organized into clean sections (intro, Why, Pattern, Boundaries), which merits a 5 per the simple-skill guideline.

5 / 5

Total

18

/

20

Passed

Description

75%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 description that states concrete actions and an explicit quoted trigger, cleanly separating reversible from irreversible work. Its main limitations are missing trigger synonyms and a 'when' clause keyed to the agent's temptation rather than to situations a user would name.

Suggestions

Add natural trigger synonyms (e.g., 'permission', 'blocking on review', 'waiting for approval') to broaden keyword coverage.

Reframe the 'when' clause around concrete situations, e.g. 'Use when working autonomously on reversible tasks (writing code, editing files, splitting work) and tempted to ask before acting'.

Enumerate the actions more comprehensively, including the self-healing behavior from the body (log problems and fix them in the next round).

DimensionReasoningScore

Specificity

Lists several concrete actions ('Proceed, present the result', 'let the human course-correct after the fact', 'reserve confirmation for irreversible actions') but omits some behaviors from the body (e.g., self-healing/logging), leaving minor coverage gaps.

4 / 5

Completeness

Both 'what' (proceed, present, course-correct, reserve confirmation) and 'when' ('Apply when tempted to ask... on reversible work') are explicitly stated, but the 'when' is framed on the agent's internal state rather than concrete invocation situations, keeping it below a 5.

4 / 5

Trigger Term Quality

Natural phrases like "should I do X?", 'reversible work', and 'irreversible actions' give good keyword coverage, though common variations such as 'permission', 'blocking', or 'waiting for approval' are absent.

4 / 5

Distinctiveness Conflict Risk

Occupies a distinct niche (async supervision with a reversible/irreversible gate) unlikely to trigger for the wrong skill, with only minor overlap risk against other agent-autonomy principles.

4 / 5

Total

16

/

20

Passed

Validation

100%

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

adamsardo/pstack-claude

Path

plugins/pstack/skills/principle-never-block-on-the-human/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.