CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

thinkies

Applies Kent Beck's Thinkies—pattern-based thinking habits that generate ideas. Use when stuck, exploring alternatives, or reframing decisions.

Quality

79%

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/thinkies/SKILL.md
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.

A well-structured, lean instruction skill with a clear four-step workflow, concrete starter set, and exemplary progressive disclosure — both referenced files exist, are one level deep, and are purpose-labeled with explicit escalation rules. The remaining gaps are minor: no inline worked example of presenting a Thinkie, no fallback path when suggestions miss, and small redundancies (triple-stated attribution, the unexplained STARTER_CHARACTER line).

Suggestions

Add one short worked example inline showing exactly how to present a single Thinkie (name, pattern, transformation, attribution line) so the output format is unambiguous without loading references/examples.md.

Add a fallback step to the workflow for the cases where no Thinkie pattern matches the situation or the user rejects the initial 3-5 suggestions (e.g., widen to the catalog by category, or say so and stop).

Explain or remove the "STARTER_CHARACTER = 💡🔄" line — as written it consumes tokens with no stated purpose or usage instruction.

DimensionReasoningScore

Conciseness

The body is lean with well-scoped sections and no explanation of concepts Claude already knows; it assumes competence throughout. Not 5 because of minor trimmable redundancy: the attribution line appears three times (Attribution, Step 3, Reminder), the "start with 3-5" guidance appears in three sections, and the unexplained "STARTER_CHARACTER = 💡🔄" line spends tokens without stated purpose. It stays above 3 because the repetition of attribution reads as deliberate enforcement of a compliance-critical rule rather than padding.

4 / 5

Actionability

Concrete, executable guidance for an instruction-only skill: a numbered four-step process, a default approach ("Suggest 3-5 relevant Thinkies... with name, pattern, transformation, and attribution line"), five named starter Thinkies with one-line transformations, and verbatim copy-paste attribution lines. Not 5 because it never shows a concrete worked presentation of a single Thinkie (format is described but not exemplified inline) and gives no guidance on how to search or match against the 80+ item catalog beyond "Reference references/catalog.md".

4 / 5

Workflow Clarity

The Four-Step Process is a clearly sequenced loop whose step 4 ("Evaluate together: After generation, assess usefulness with user") acts as an explicit checkpoint, reinforced by the Anti-Patterns section. Not 5 because there are no error-recovery branches for the obvious failure modes: no Thinkie matches the situation, or the user rejects all initial suggestions. This is not a destructive or batch operation, so no cap applies, and the sequence itself is unambiguous.

4 / 5

Progressive Disclosure

The SKILL.md is a lean overview that keeps the bulk (80+ Thinkies) in references/catalog.md (verified to exist and be organized by category) and scenarios in references/examples.md (verified to exist), each one level deep and clearly signaled with its purpose ("For complex situations or more options", "For examples"). A dedicated "Progressive Disclosure" section explicitly governs when to escalate to the catalog, which matches the top anchor's easy navigation and appropriate split.

5 / 5

Total

17

/

20

Passed

Description

70%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 solid description with correct third-person voice, a clear what, and a genuinely natural Use-when clause. Its main weakness is coverage: neither the capability list nor the trigger list is comprehensive, omitting obvious terms like "generate ideas", "brainstorm", or "different perspectives" that appear in the skill body itself.

Suggestions

Enumerate 2-3 concrete capabilities in the description, e.g. "suggests relevant Thinkies by matching patterns to the situation, applies their transformations to generate ideas, and presents them with attribution".

Broaden the Use-when clause with natural synonyms from the body: "Use when stuck or blocked, brainstorming, exploring alternatives, wanting different perspectives, or reframing decisions".

Include "generate ideas" and "Kent Beck" as explicit trigger terms since users seeking this skill would likely say both.

DimensionReasoningScore

Specificity

Names the domain ("Kent Beck's Thinkies") and the mechanism ("pattern-based thinking habits that generate ideas"), which is 1-2 concrete actions but not a comprehensive list of capabilities. It does not reach 4 because no several specific actions are enumerated, and it is above 2 because it goes beyond naming the domain to explain what is actually applied.

3 / 5

Completeness

Both parts are present: the what ("Applies Kent Beck's Thinkies—pattern-based thinking habits that generate ideas") and an explicit when ("Use when stuck, exploring alternatives, or reframing decisions"), and the voice is correctly third person. Not 5 because the when clause omits several concrete triggers the skill itself lists (wanting to generate ideas, asking for different perspectives, mentioning Kent Beck), leaving it less exhaustive than the anchor example.

4 / 5

Trigger Term Quality

"Use when stuck, exploring alternatives, or reframing decisions" contains natural phrases users would actually say ("I'm stuck", "what are my alternatives"). Not 5 because common variations like "blocked", "brainstorm", or "generate ideas" are missing; not 3 because the terms present are genuinely natural user language rather than merely relevant keywords.

4 / 5

Distinctiveness Conflict Risk

"Kent Beck's Thinkies" carves out a clear named niche with minimal conflict risk, and the attribution makes it unlikely to fire for the wrong skill. Not 5 because "stuck" and "exploring alternatives" are broad triggers that could overlap with general brainstorming or ideation skills; not 3 because the named source and specific framing keep it mostly distinct.

4 / 5

Total

15

/

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

saski/arnesto

Path

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