CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

4x4

Pull 16 fast decisions out of the user with 4 sets of 4 open questions, then present an implementation plan. Only for risky changes, large product decisions, or large refactors. Run when the user types /4x4. Agents may suggest it in one line but never start it on their own.

Quality

92%

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

92%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 lean, tightly organized instruction set with a clear sequenced workflow, explicit wait-for-answer checkpoints, and error-recovery rules for handling bad or vague responses. The single gap is that the message-format example is a skeleton with ellipses rather than one complete worked example.

Suggestions

Include one fully worked example set of four real open questions (e.g., for a large refactor) so the exact tone and level of concreteness is copy-paste demonstrable.

Clarify in the Workflow what to do if the user answers a set with questions instead of decisions (e.g., re-ask the set concisely) to close the last error-handling gap.

DimensionReasoningScore

Conciseness

Every line is instruction ("Show one set at a time. Never preview or list the other sets. Stop and wait.", "One short sentence per question."); there is no concept explanation, padding, or reiteration of what Claude already knows. Lean throughout, matching the top anchor.

5 / 5

Actionability

Concrete, executable guidance throughout: a literal message-format template, exact workflow steps, and specific rules ("Vague or skipped answer: move on and use your judgment"). Not a 5 because the format example uses "..." placeholders instead of one fully worked example set of four real questions, leaving a minor gap in covering the common case.

4 / 5

Workflow Clarity

The 6-step workflow is clearly sequenced with explicit stop-and-wait checkpoints ("Stop and wait. Show the next set only after the user answers") and error-recovery feedback loops in the Rules section (bad question → replace or drop; answer contradicts an ADR → point it out in the plan). Not a 4 because checkpoints are explicit rather than implicit; the destructive/batch validation cap does not apply to this interactive elicitation skill.

5 / 5

Progressive Disclosure

The body is under 50 lines with no external references needed, organized into well-labeled sections (The 4 sets, Workflow, Message format, Rules), which per the rubric's simple-skill guideline earns the top score. There are no buried or nested references.

5 / 5

Total

19

/

20

Passed

Description

87%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 concise and concrete, explicitly covering both what the skill does and when to run it, including a distinct slash-command trigger and an explicit agent-behavior boundary. Its only weakness is slightly thin coverage of natural trigger variations (e.g., synonyms for "large refactor"/"big decision").

DimensionReasoningScore

Specificity

"Pull 16 fast decisions out of the user with 4 sets of 4 open questions, then present an implementation plan" names concrete, quantified actions (elicit 16 decisions via 4 sets of open questions, present a plan). Not a 5 because coverage is limited to two core actions rather than several; not a 3 because the detail ("16", "4 sets of 4", "open questions", "implementation plan") is noticeably more concrete than the 1-2 generic-action anchor.

4 / 5

Completeness

The "what" is explicit ("Pull 16 fast decisions out of the user with 4 sets of 4 open questions, then present an implementation plan") and the "when" is explicit ("Only for risky changes, large product decisions, or large refactors. Run when the user types /4x4") — both answered with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Natural triggers include "/4x4", "risky changes", "large product decisions", "large refactors" — phrases a user would plausibly say. Not a 5 because common variations ("big decision", "major refactor", "big change") are missing; not a 3 because coverage goes beyond a bare minimum with multiple distinct natural terms.

4 / 5

Distinctiveness Conflict Risk

Clear niche (structured user-decision elicitation before planning) with a distinct trigger ("/4x4"), and the clause "Agents may suggest it in one line but never start it on their own" explicitly limits conflict with other skills. Only minor, sub-anchor-level overlap with general planning skills.

5 / 5

Total

18

/

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

davidondrej/skills

Path

skills/thinking-and-docs/4x4/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.