CtrlK
BlogDocsLog inGet started
Tessl Logo

think-harder

4-phase structured analysis wrapper for vibe pre-routing (compatible with claude-code-settings think-harder semantics).

49

Quality

53%

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

Fix and improve this skill with Tessl

tessl review fix ./bundled/skills/think-harder/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

76%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 exceptionally concise and well-structured as a reasoning template, with a clear 4-phase sequence and output contract. It loses points on actionability (template guidance, no executable examples) and workflow clarity (no validation/feedback checkpoints for a deliberation process).

Suggestions

Add one short worked example showing the 4-phase analysis applied to a realistic task, so the template is concrete rather than abstract.

Insert explicit validation checkpoints between phases (e.g. 'Before Synthesis: confirm each insight has a stated confidence level and uncertainty marker').

Convert the `code-reviewer` reference into a clearly signaled pointer (e.g. 'Pair with the code-reviewer skill') and note when each integration applies.

DimensionReasoningScore

Conciseness

The body is lean (~45 lines of tight bullet structure) with no padding or explanation of concepts Claude already knows; every line is task-relevant.

5 / 5

Actionability

It gives a concrete 4-phase checklist and a numbered output contract, but these are instructions/templates rather than executable commands; guidance is actionable as a process but lacks worked examples or runnable artifacts.

3 / 5

Workflow Clarity

The 4 phases are clearly sequenced and the Output Contract enumerates expected outputs, but there are no explicit validation checkpoints or error-recovery feedback loops; 'Mark uncertainty and confidence level' is the only checkpoint-like step.

4 / 5

Progressive Disclosure

Content is well-organized into short sections with no bundle files needed and no nested references; structure is clean, though the single `code-reviewer` cross-reference is text-only rather than a signaled link.

4 / 5

Total

16

/

20

Passed

Description

30%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 jargon-heavy and lacks a natural 'Use when...' trigger, so users would be unlikely to invoke it by intent. It states a vague 'what' and omits 'when', capping completeness. Trigger terms favor internal product vocabulary over natural user phrasing.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when a task needs deeper reasoning, tradeoff analysis, or a structured decision before implementation.'

Replace internal jargon ('vibe pre-routing', 'claude-code-settings think-harder semantics') with natural trigger phrases users would actually say.

Spell out concrete capabilities of the 4 phases (e.g. 'decompose problems, run pre-mortems, surface uncertainties') instead of the abstract 'structured analysis wrapper'.

DimensionReasoningScore

Specificity

The phrase '4-phase structured analysis wrapper' names the domain (analysis) but actions are minimal/generic — 'wrapper' and 'pre-routing' are abstract with no concrete named capability.

2 / 5

Completeness

There is a vague 'what' ('4-phase structured analysis wrapper') and no 'when'/'Use when' clause, so it fails the explicit-trigger guidance and caps at 3, sitting below at 2 due to weak 'what'.

2 / 5

Trigger Term Quality

Triggers lean on internal jargon ('vibe pre-routing', 'claude-code-settings think-harder semantics') rather than natural user phrases like 'think harder', 'reason about tradeoffs', or 'analyze a problem'.

2 / 5

Distinctiveness Conflict Risk

'think-harder' / 'structured analysis' is a recognizable niche with some distinct signal, but 'analysis' is broad and could overlap with other reasoning or review skills.

3 / 5

Total

9

/

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
foryourhealth111-pixel/Vibe-Skills
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.