CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

rethink

Develop the strongest grounded vision of a system, API, or abstraction through dialectic, then work backward to make it real. Use when the user asks for greenfield thinking, radical options, a clean break, first-principles design, or questions the current organizing idea or boundaries.

Quality

77%

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 ./.agents/skills/rethink/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 presents a coherent, well-sequenced four-phase methodology with explicit feedback loops and a closing verification phase, and it cleanly delegates three sub-techniques to real, clearly-signaled reference files. Its weakness is actionability: guidance stays at the level of principle with no worked example or sample artifact to show what 'concrete expression' or 'closing against the vision' produces, and two cross-skill links cannot be verified. It is an instruction-only skill where absence of code is acceptable, but the guidance would be stronger with a concrete exemplar.

Suggestions

Add one compact worked example (e.g., a cramped existing API, the rethought surface with realistic caller code, and the derived dependency-ordered changes) to anchor the abstract directives in 'Give the vision concrete expression' and 'Work backward from the destination'.

Tighten the restatements of the dialectic loop across sections — the revision-through-user-reaction idea appears in both 'Form an account of the whole' and 'Give the vision concrete expression' and could be consolidated.

Make the two cross-skill references resolvable or inline their key guidance, since ../dialectic/SKILL.md and ../collapse-pass/references/concept-inventory.md do not resolve from this bundle.

DimensionReasoningScore

Conciseness

The body is dense guidance with no padding or explanation of concepts Claude already knows — every section carries method instruction, matching anchor 4 ('efficient; minor instances of over-explanation that could be trimmed'). Not 5 because the dialectic theme is restated several times (e.g., 'Use the user's reactions to develop the account of the whole' and 'bring the latter back into dialectic') and a few aphoristic lines ('An attractive entrypoint alone may conceal the decisions that matter') could be tightened; not 3 because there is no genuinely unnecessary explanation.

4 / 5

Actionability

The body gives directional, method-level guidance ('Show how someone would use the proposed system: realistic caller code, an interaction, or a data flow'; 'Derive what must be created, moved, replaced, or removed, in dependency order') but includes no worked example, template, or sample artifact to anchor what output should look like — matching anchor 3 ('some concrete guidance but incomplete; missing key details'). Not 4 because a before/after design example would make the guidance executable rather than interpretable; not 2 because there are several specific directives about what to produce, beyond high-level hints.

3 / 5

Workflow Clarity

The four sections form a clear sequence (form an account → give concrete expression → work backward → close against the vision) with an explicit closing verification section ('Exercise the concrete use and verify changed contracts') and explicit feedback loops ('bring the latter back into dialectic... then work backward from the revised understanding'), matching anchor 4. Not 5 because transitions between phases are left to judgment ('As the direction settles') and there are no checkpoints or checklists for when a phase is complete; not 3 because validation and feedback steps are explicitly present, not implicit.

4 / 5

Progressive Disclosure

The SKILL.md is a well-structured overview whose three sub-techniques live in real, one-level-deep reference files, each linked at a specific decision point with conditional guidance ('Use radical options when the apparent choices share an assumption worth reconsidering'), matching anchor 4. Not 5 because two links point outside the bundle (../dialectic/SKILL.md, ../collapse-pass/references/concept-inventory.md) and do not resolve in this workspace, creating a minor navigation gap; not 3 because the structure and signaling of the in-bundle references are clear and appropriately split.

4 / 5

Total

15

/

20

Passed

Description

78%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 clearly and explicitly states both what the skill does and when to use it, with a rich set of natural trigger phrases that form a distinctive niche. Its main limitation is that the 'what' is stated in abstract language ('develop the strongest grounded vision... through dialectic') rather than concrete, comprehensible capabilities, and a few common synonyms for the triggers are missing.

DimensionReasoningScore

Specificity

The description names the domain ("a system, API, or abstraction") and two actions ("Develop the strongest grounded vision... through dialectic", "work backward to make it real"), but the actions are abstract rather than concrete — matching anchor 3 ('names domain and 1-2 concrete actions'). Not 4 because it does not list several specific concrete actions, and not 2 because the actions and domain are clearly stated rather than minimal or generic.

3 / 5

Completeness

It explicitly answers both what ("Develop the strongest grounded vision... then work backward to make it real") and when ("Use when the user asks for greenfield thinking, radical options, a clean break, first-principles design, or questions the current organizing idea or boundaries") with concrete trigger phrases, matching the anchor-5 example structure. Not 4 because the 'when' clause is not merely explicit but enumerates five concrete trigger conditions.

5 / 5

Trigger Term Quality

The 'when' clause includes natural phrases users would actually say — "greenfield thinking", "radical options", "a clean break", "first-principles design" — giving good keyword coverage. Not 5 because common synonyms such as 'rethink', 'redesign', or 'start from scratch' are missing; not 3 because the coverage goes beyond 'some relevant keywords' with multiple distinct natural trigger phrases.

4 / 5

Distinctiveness Conflict Risk

The trigger set (greenfield thinking, radical options, clean break, first-principles design) carves out a distinct niche that is unlikely to fire for unrelated skills. Not 5 because 'first-principles design' and 'questions the current... boundaries' carry minor overlap risk with general planning/design skills; not 3 because the niche is clearly defined rather than merely 'somewhat specific'.

4 / 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

relative_links

Relative link issues: 2 suspicious

Warning

Total

15

/

16

Passed

Repository

EpicenterHQ/epicenter

Path

.agents/skills/rethink/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.