CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

skill-reflection

Generic post-workflow self-reflection that any skill can invoke at the end of its run. Analyzes friction encountered during execution and produces advisory recommendations for improving the calling skill's SKILL.md. Use when a skill finishes (success or failure) and wants to capture improvement opportunities.

Quality

75%

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 ./.github/skills/skill-reflection/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%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 highly concrete, actionable guidance with a clearly sequenced workflow and explicit fallback handling for every failure mode, plus worked examples and complete output templates. Its weaknesses are redundancy (the advisory-only rule and escalation rule are each stated multiple times) and a monolithic 430-line single file whose templates and optional obsidian integration belong in reference files.

Suggestions

State the advisory-only rule once (e.g. in Purpose) and remove the repetitions in Design Principles, the step-6 output template, and Anti-Patterns; likewise keep the two-consecutive-runs escalation rule in one place instead of both the template and its own section.

Move the verbose output template, the clean-run template, and the obsidian Agent Memory follow-up (with its PowerShell commands) into a references/ file (e.g. templates.md), keeping SKILL.md as a lean overview with one-level-deep, clearly signaled references.

Tighten section 2.5's five drift-sign bullets and the six reflect prompts by merging overlapping items, and fix the inconsistent indentation in the step-6 template (e.g. 'Evidence:' and 'Workaround used:' lines) so the format is unambiguous when copied.

DimensionReasoningScore

Conciseness

Quotes: 'This skill does not modify SKILL.md files automatically', 'Advisory — produces recommendations, never edits SKILL.md directly', 'No SKILL.md changes made — recommendations are advisory', '❌ Auto-editing the calling skill's SKILL.md — always advisory'. The advisory-only rule is stated four times, and the two-consecutive-runs escalation rule appears both inside the step-6 output template ('Self-improvement rule: If the same friction point appears in two consecutive runs, escalate to P0') and again as its own '## Escalation Rule' section. The content is otherwise directive rather than explanatory, so it is mostly efficient but could be tightened — the level-3 anchor — rather than noticeably padded.

3 / 5

Actionability

Quotes: the exact invocation shape ('Run skill-reflection for <skill-name>. SKILL.md path: ... Steps completed: ... Friction: ...'), two fully worked examples (azure-local-deploy, branch-wrapup), the structured input table, the seven-category friction taxonomy, complete output templates for both friction and clean runs, the priority definitions table, and the executable command 'python .github/skills/obsidian/scripts/obsidian.py search ... --format json'. Guidance is copy-paste ready and covers the common cases (missing path, missing step list, unavailable history, no friction), matching the fully-executable anchor; the only minor gap is that step 5's history search does not name the search mechanism, but step 7 supplies one.

5 / 5

Workflow Clarity

Quotes: 'When invoked, follow these steps in order' with numbered steps 1-8; explicit fallback loops such as 'If the caller provides the skill name but no step list, ask only for the missing steps and statuses', 'If SKILL.md path is missing ... continue with the rest of the reflection instead of blocking the run', 'If those history sources are unavailable, say so explicitly instead of assuming there is no repeat friction', and a dedicated clean-run branch ('When There's No Friction'). The sequence is clear with explicit validation/checkpoint behavior for each failure mode, and since the skill is advisory (non-destructive, non-batch) the validation cap does not apply.

5 / 5

Progressive Disclosure

The body is a single ~430-line file with no bundle files (no references/, scripts/, or assets/ exist) and no external references at all. Sections are well-organized with headers, but content that would fit better in separate reference files is inlined — the ~45-line verbose output template, the clean-run template, and the obsidian Agent Memory follow-up with its PowerShell commands — matching the anchor for content that should be separate being inline rather than the good-placement anchor.

3 / 5

Total

16

/

20

Passed

Description

62%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 states what the skill does and when to use it, with a distinctive composable niche. Its main weaknesses are limited action coverage and trigger phrasing that is compositional ('calling skill's SKILL.md') rather than natural user language, omitting common synonyms like retrospective or post-mortem.

Suggestions

Expand the capability list to 3-4 concrete actions, e.g. 'Analyzes friction encountered during execution, categorizes it (prerequisite gaps, command failures, environment issues), checks repeat-friction history, and produces prioritized P0/P1/P2 recommendations for improving the calling skill's SKILL.md.'

Add natural trigger phrases users would actually say: 'Use when the user says "reflect on that run", "what could be improved", or asks for a retrospective, post-mortem, or lessons learned after a skill run.'

Make the when-clause more concrete by naming the invoking context explicitly, e.g. 'Use at the end of any multi-step skill workflow, or mid-run when a step fails and a workaround is applied.'

DimensionReasoningScore

Specificity

Quotes: 'Analyzes friction encountered during execution and produces advisory recommendations for improving the calling skill's SKILL.md.' The description names the domain (post-workflow self-reflection) and two concrete actions, matching the anchor for domain plus 1-2 concrete actions. It does not list several specific actions with only minor gaps, so it falls below the level-4 anchor.

3 / 5

Completeness

Quotes: 'Analyzes friction encountered during execution and produces advisory recommendations...' (what) and 'Use when a skill finishes (success or failure) and wants to capture improvement opportunities' (when). Both what and when are explicitly present, but the trigger phrasing is compositional/abstract rather than concrete user phrasing, so it does not reach the level-5 anchor requiring concrete trigger phrases.

4 / 5

Trigger Term Quality

Quotes: 'self-reflection', 'friction', 'improvement opportunities'. Some relevant keywords are present, but common natural variations users would say — 'retrospective', 'post-mortem', 'lessons learned', 'what went wrong', 'reflect on this run' — are absent, matching the anchor for relevant keywords missing common synonyms rather than the good-coverage anchor.

3 / 5

Distinctiveness Conflict Risk

Quotes: 'Generic post-workflow self-reflection that any skill can invoke at the end of its run' and 'improving the calling skill's SKILL.md'. This carves a distinct composable niche (skill self-improvement invoked by other skills) with low conflict risk; minor overlap remains with general retrospective or lessons-learned skills, so it sits at the mostly-distinct anchor rather than the minimal-conflict one.

4 / 5

Total

14

/

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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

0xRabbidfly/Eric-Cartman

Path

.github/skills/skill-reflection/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.