CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

reflect

Mid-conversation reflection skill that pauses execution and zooms out from detail-mode to honestly reassess direction, assumptions, and bias. Use when the user says 'reflect', 'take a step back', 'step back', 'zoom out', 'are we missing something', 'bigger picture', 'sanity check this', 'are we on track', 'are we overthinking this', 'forest for the trees', or any variation signaling intent to break out of detail-mode and reassess. Also trigger when the conversation has gone deep on implementation details without strategic check-in, or when the user shows signs of being stuck — that's often a signal the framing needs a reset, not more detail work. Intentionally low-intake: runs the 5-dimension analysis immediately when prior context is rich enough; asks one forcing clarifier only when invocation context is too thin to reassess from.

64

Quality

80%

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 ./.gemini/skills/reflect/SKILL.md

The canonical home for this skill is reflect in alirezarezvani/claude-skills

SKILL.md
Quality
Evals
Security

Quality

Content

63%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 delivers a well-sequenced, highly actionable reflection workflow with concrete formats, a bias-cue table, and error handling. Its main weaknesses are maintainer-metadata padding, the absence of a worked output example, and a bundle that ships none of the six files the body references — every reference link and script path is dead.

Suggestions

Ship or remove the six referenced bundle files: references/cognitive_bias_canon.md, references/honest_output_discipline.md, references/conversation_reflection_practice.md, and the three scripts/ files in the Tooling table are all absent from the bundle, so every link and script path is dead.

Delete the portability blockquote and the version/source-spec footer — maintainer metadata that does not guide execution and adds token cost.

Add a short worked example (2-3 sentences) of the required flowing-prose output so the tone and format rules have a concrete anchor.

DimensionReasoningScore

Conciseness

The core framework sections (bias table, recommendation formats, error handling) are tight and skill-specific, but there is real padding: the "This matters because:" rationale bullets under Stop Directive explain what Claude can infer, and the portability blockquote ("Most portable in the v2 collection") plus the version/source-spec footer are maintainer metadata that earns no tokens during execution. Not 4 because these unnecessary sections go beyond minor trimming; not 2 because the bulk is non-redundant, skill-specific guidance rather than explanation of known concepts.

3 / 5

Actionability

Concrete, executable guidance throughout for an instruction-only skill: the exact Q1 wording ("What specifically should I reassess? Pick one..."), the bias recognition-cue table mapping each bias to conversation patterns, exact closing formats ("Continue. {specific reasoning for why}."), and a branch-per-situation error handling table. Not 5 because there is no worked example of the required flowing-prose output to anchor tone, and the Tooling table lists scripts by role only with no usage or commands.

4 / 5

Workflow Clarity

A clear sequence is present: trigger detection (explicit vs implicit, with "don't auto-invoke — ask the user"), halt directive, conditional clarifier with an explicit stop condition ("One question max"), full-conversation re-read, 5-dimension analysis, and a mandatory closing recommendation, plus error-handling branches. Not 5 because there is no validation checkpoint confirming the output satisfies the tone/format rules — the validator script that would provide this feedback loop is described but never wired into the workflow.

4 / 5

Progressive Disclosure

References are clearly signaled and one level deep ("See references/cognitive_bias_canon.md for the full canon"), but no references/, scripts/, or assets/ directories exist in the bundle — all three reference links (cognitive_bias_canon.md, honest_output_discipline.md, conversation_reflection_practice.md) and all three scripts in the Tooling table are dangling paths that resolve to nothing. Not 4 because every advertised bundle file being missing is more than a minor organization gap; not 2 because the inline body is well sectioned and self-sufficient for the core task without the missing files.

3 / 5

Total

14

/

20

Passed

Description

91%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 clearly answers what the skill does and when to use it, with an unusually rich set of natural trigger phrases including synonyms, variations, and implicit signals. The only weaknesses are a minor coverage gap (the closing recommendation output is not mentioned) and slight overlap risk between a couple of triggers and review/planning skills.

DimensionReasoningScore

Specificity

Concrete actions are named — "pauses execution and zooms out from detail-mode to honestly reassess direction, assumptions, and bias", "runs the 5-dimension analysis immediately", "asks one forcing clarifier" — covering several specific capabilities. Not 5 because the skill's signature output (the mandatory continue/pivot/pause closing recommendation) is not mentioned, leaving a minor coverage gap; not 3 because it lists well more than 1-2 concrete actions.

4 / 5

Completeness

Both what and when are explicitly and concretely answered: the what is "pauses execution and... honestly reassess direction, assumptions, and bias" with the 5-dimension analysis named, and the when is an explicit "Use when the user says..." clause listing concrete trigger phrases plus implicit-trigger conditions. Matches the anchor-5 example pattern; not 4 because the when-clause is fully explicit rather than improvable.

5 / 5

Trigger Term Quality

Comprehensive natural trigger coverage with synonyms and variations: 'reflect', 'take a step back', 'zoom out', 'are we missing something', 'bigger picture', 'sanity check this', 'are we on track', 'are we overthinking this', 'forest for the trees', plus "any variation signaling intent to break out of detail-mode" and implicit-signal triggers. Matches the top anchor; these are all phrases a user would naturally say when needing this skill.

5 / 5

Distinctiveness Conflict Risk

The mid-conversation reflection niche ("pauses execution and zooms out from detail-mode") is distinct with dedicated trigger phrasing. Minor overlap risk remains: 'sanity check this' could plausibly route to a code-review skill and 'are we on track' to a planning/status skill. Not 5 due to those overlaps with closely related skills; not 3 because the core triggers are unmistakably about reassessment rather than generic.

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.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 5 missing

Warning

referenced_paths_exist

Referenced path issues: 13 missing

Warning

Total

14

/

16

Passed

Repository

alirezarezvani/claude-skills

Path

.gemini/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.