CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

sequential-thinking

Structured reflective problem-solving methodology. Process: decompose, analyze, hypothesize, verify, revise. Capabilities: complex problem decomposition, adaptive planning, course correction, hypothesis verification, multi-step analysis. Actions: decompose, analyze, plan, revise, verify solutions step-by-step. Keywords: sequential thinking, problem decomposition, multi-step analysis, hypothesis verification, adaptive planning, course correction, reflective thinking, step-by-step, thought sequence, dynamic adjustment, unclear scope, complex problem, structured analysis. Use when: decomposing complex problems, planning with revision capability, analyzing unclear scope, verifying hypotheses, needing course correction, solving multi-step problems.

79

3.17x
Quality

86%

Does it follow best practices?

Impact

54%

3.17x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

88%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.

A well-crafted, token-efficient methodology body: a clearly sequenced 7-step process with explicit verification, revision, and branching templates plus a completion checklist, and clean one-level-deep reference structure. The only defects are a dangling README.md reference and missing inline usage examples for the optional scripts.

Suggestions

Remove the 'See README.md for usage examples' pointer or add the README.md file, since it does not exist in the bundle.

Inline a one-line example invocation of scripts/process-thought.js and scripts/format-thought.js in the Scripts section so the optional tooling is usable without external docs.

DimensionReasoningScore

Conciseness

The body is lean bullet-only prose with zero concept explanations and no padding; every section (When to Apply, Core Process, Application Modes, Scripts, References) earns its place, matching the 'every token earns its place' anchor.

5 / 5

Actionability

Provides concrete marker templates ('Thought 5/8 [REVISION of Thought 2]' with Original/Why/Impact fields; '[BRANCH A from Thought 2]') and names the exact script files, but script usage is not shown and 'See README.md' points to a file that does not exist in the bundle, leaving minor execution gaps.

4 / 5

Workflow Clarity

The 7-step Core Process is clearly sequenced with an explicit validation loop ('Generate & Verify Hypotheses ... Iterate until hypothesis verified'), revision as the error-recovery mechanism, and a concrete completion checklist in step 7 ('Solution verified, All critical aspects addressed, Confidence achieved, No outstanding uncertainties').

5 / 5

Progressive Disclosure

The body is a genuine overview with all six references/ and both scripts/ files one level deep, each with a one-line description and a clear load signal ('Load when deeper understanding needed', 'Use when validation/persistence needed'); however, the body references a README.md that is absent from the bundle, a real navigation gap.

4 / 5

Total

18

/

20

Passed

Description

80%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 explicitly states what the skill does and when to use it with concrete trigger phrases and an extensive keyword list. Main weaknesses are moderate distinctiveness (broad 'complex problem'/'planning' triggers risk overlap with other reasoning skills) and some redundancy across the Process, Capabilities, Actions, and Keywords sections that pads length without adding information.

Suggestions

Consolidate the redundant Process/Capabilities/Actions sections, which repeat decompose, analyze, verify, and revise, into one concise list to reduce keyword-stuffed padding.

Narrow the 'Use when' triggers away from generic phrases like 'solving multi-step problems' toward distinguishing markers (e.g., needing visible thought sequences, mid-solution revision, or branching alternatives) to reduce conflict with general planning skills.

Add a couple of natural user phrasings (e.g., 'think step by step', 'work through this problem systematically') to close the remaining trigger-term gaps.

DimensionReasoningScore

Specificity

Lists several explicit actions ('Process: decompose, analyze, hypothesize, verify, revise'; 'Actions: decompose, analyze, plan, revise, verify solutions step-by-step') but they are abstract verbs rather than the fully concrete, comprehensive action coverage of the top anchor.

4 / 5

Completeness

Explicitly answers both what ('Structured reflective problem-solving methodology. Process: ... Capabilities: ... Actions: ...') and when ('Use when: decomposing complex problems, planning with revision capability, analyzing unclear scope, verifying hypotheses, needing course correction, solving multi-step problems') with six concrete trigger phrases.

5 / 5

Trigger Term Quality

A dedicated Keywords clause ('sequential thinking, problem decomposition, multi-step analysis, hypothesis verification, adaptive planning, course correction, reflective thinking, step-by-step, thought sequence, dynamic adjustment, ... complex problem, structured analysis') gives good natural-term coverage, though it misses common user phrasings like 'walk through my reasoning' or 'think step by step aloud'.

4 / 5

Distinctiveness Conflict Risk

The sequential-thinking framing with revision/branching markers is a recognizable niche, but broad triggers like 'complex problem', 'multi-step problems', 'planning', and 'needing course correction' overlap significantly with general planning, reasoning, and debugging skills.

3 / 5

Total

16

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

samhvw8/dot-claude

Path

skills/sequential-thinking/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.