CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

reflect

Reflect on previus response and output, based on Self-refinement framework for iterative improvement with complexity triage and verification

Quality

51%

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 ./plugins/reflexion/skills/reflect/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

51%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 content is a thorough, well-sequenced self-refinement framework with concrete checklists, a report template, and worked examples, but it is markedly verbose, re-explains general CS concepts Claude already knows, and ships as one monolithic file with no progressive disclosure or external reference structure.

Suggestions

Cut the explanatory material Claude already knows (Clean Architecture/DDD definitions, the SOLID/AAA primers, the long enumerations of npm/PyPI libraries and SaaS services) and keep only the skill-specific checklists and decision rules.

Move the report-format template and the bias-awareness table into a separate references/ file (e.g. REPORT_FORMAT.md) and link to it one level deep, so the main SKILL.md stays a lean overview.

Replace repeated rhetorical framing ('ruthless gatekeeper', 'You will be killed', 'Lenient judges get replaced') with a single concise directive; the repetition adds tokens without adding guidance.

DimensionReasoningScore

Conciseness

The ~645-line body is noticeably verbose: it re-explains concepts Claude already knows (Clean Architecture, DDD, SOLID, AAA test pattern, common library lists, date-fns/lodash usage) and repeats the same 'ruthless gatekeeper' framing multiple times; much of the CODE-SPECIFIC and BIAS sections restate general knowledge.

2 / 5

Actionability

It provides mostly executable guidance: concrete checklists, a copy-paste report-format template, named library/service examples, and a worked before/after refactoring snippet; minor gaps are that the process steps are phrased as self-reflection questions rather than commands, and the example code snippets are illustrative rather than runnable on the user's codebase.

4 / 5

Workflow Clarity

The triage (Quick/Standard/Deep path) followed by Step 1 Assessment -> Step 2 Decision -> Step 3 Refinement -> Final Verification is a clear, ordered sequence with explicit checkpoints (confidence thresholds >4.0 / >4.5, RE-EVALUATE loop), though validation is framed as self-checks rather than tool-verified gates.

4 / 5

Progressive Disclosure

It is a single monolithic SKILL.md with no bundle files (references/scripts/assets absent) and no one-level-deep links; large reference-style blocks (library lists, bias tables, the full report template) are inlined rather than split into separate files, so structure is section-based only with no external navigation.

2 / 5

Total

12

/

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 names the domain of self-refinement and iterative improvement but is vague about concrete actions, omits an explicit 'Use when...' trigger, and relies on framework jargon rather than natural user phrases. It also contains a typo ('previus') and uses no trigger synonyms or file-extension-style anchors.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user asks you to double-check, critique, or improve a response you just produced.'

Replace jargon ('complexity triage', 'self-refinement framework') with concrete actions and natural trigger phrases like 'review my answer', 'check my work', 'find issues in what you just wrote'.

Fix the 'previus' typo and add concrete capability verbs (e.g. 'Critiques, fact-checks, and refines a previous response; verifies claims and flags dependency risks') to lift specificity.

DimensionReasoningScore

Specificity

The description only states one generic action ('Reflect on previus response and output') plus the framework's mechanism names; it names the domain (self-refinement) but lists no concrete, distinguishable actions a user would invoke.

2 / 5

Completeness

It gives a vague 'what' ('Reflect on previous response') but no explicit 'Use when...' trigger clause; the trigger guidance appears only as an argument-hint, not in the description, which caps completeness at 3 and the weak 'when' pushes it to 2.

2 / 5

Trigger Term Quality

Phrases like 'reflect', 'self-refinement', 'iterative improvement', 'complexity triage', and 'verification' are framework jargon rather than the natural phrases a user would say when they need this skill; no everyday synonyms are present.

2 / 5

Distinctiveness Conflict Risk

The skill is somewhat specific (self-refinement / iterative improvement on prior output) but 'reflect on output' is broad enough to overlap with general code-review or quality-check skills; the framework framing helps but does not fully carve a distinct niche.

3 / 5

Total

9

/

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.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (651 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository

NeoLabHQ/context-engineering-kit

Path

plugins/reflexion/skills/reflect/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.