CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

78

3.17x
Quality

83%

Does it follow best practices?

Impact

54%

3.17x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is sequential-thinking in majiayu000/claude-skill-registry

SKILL.md
Quality
Evals
Security

Quality

Content

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

Concise and well-structured instructional skill with concrete thought-sequence templates and a clear process checklist. The main weakness is that the referenced reference/script bundle files are not present, so progressive disclosure navigation points to missing material.

Suggestions

Either ship the referenced files under references/ and scripts/ or remove the References and Scripts sections so the body is self-contained.

Add one short worked example inline (a 4-5 thought sequence) so the methodology is immediately demonstrable without loading a reference file.

Make intermediate checkpoints explicit in the Core Process steps (e.g., 'after Step 3, confirm scope is stable before continuing') to strengthen workflow clarity.

DimensionReasoningScore

Conciseness

Lean throughout with no padding or explanation of concepts Claude already knows; every section (Core Process, Application Modes, References) earns its place and assumes Claude's competence.

5 / 5

Actionability

Provides concrete, reusable thought-marker templates ('Thought 1/5: ...', '[REVISION of Thought 2]', '[BRANCH A from Thought 2]', '[HYPOTHESIS]') that are directly applicable, though as instructional templates rather than executable code they stop just short of copy-paste-ready commands.

4 / 5

Workflow Clarity

A clear 7-step Core Process with an explicit completion checklist ('Solution verified; All critical aspects addressed; Confidence achieved; No outstanding uncertainties'); not a destructive/batch operation so no validation cap applies, but intermediate checkpoints are mostly implicit.

4 / 5

Progressive Disclosure

The body is well-organized with a clearly signaled References and Scripts section, but the referenced bundle files (references/core-patterns.md, scripts/process-thought.js, etc.) do not exist on disk, so the one-level-deep navigation does not actually resolve to real supporting material.

3 / 5

Total

16

/

20

Passed

Description

88%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, well-structured description that clearly states capabilities and provides explicit trigger guidance with natural keywords. Main gap is mild overlap risk inherent to the broad problem-solving domain.

DimensionReasoningScore

Specificity

Lists multiple concrete actions across process, capabilities, and actions ('decompose, analyze, hypothesize, verify, revise'; 'complex problem decomposition, adaptive planning, course correction, hypothesis verification, multi-step analysis'), giving comprehensive coverage of what the skill does.

5 / 5

Completeness

Explicitly answers both 'what' (process, capabilities, actions) and 'when' via a dedicated 'Use when:' clause listing concrete trigger scenarios, matching the top anchor.

5 / 5

Trigger Term Quality

Strong natural keyword coverage with synonyms ('sequential thinking', 'problem decomposition', 'multi-step analysis', 'hypothesis verification', 'course correction', 'step-by-step'), though a few common user phrasings are absent; just short of fully comprehensive.

4 / 5

Distinctiveness Conflict Risk

The 'sequential thinking' framing carves a recognizable niche with distinct triggers, but the general problem-solving/analysis domain is broad and could overlap with related reasoning or planning skills.

4 / 5

Total

18

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

referenced_paths_exist

Referenced path issues: 8 missing

Warning

Total

14

/

16

Passed

Repository
majiayu000/claude-skill-registry-data
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.