CtrlK
BlogDocsLog inGet started
Tessl Logo

reflect

Post-session reflection skill for review session, retrospective, or session summary. Reads recent git history, artifacts, and context files to extract learnings and produce improvement proposals for skills, CLAUDE.md, hooks, and plan templates. Use after any substantive session to capture what did we learn and embed improvements back into codebase context.

70

Quality

85%

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

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, actionable skill body with clear sequencing and good progressive disclosure via real reference files. The main gap is a missing explicit verification loop after applying approved improvements to target files.

Suggestions

Add a verification checkpoint in Step 7 (e.g., re-read the edited file or run a syntax/structure check) before committing each applied improvement.

Tighten the repeated 'BEFORE Plan Mode' framing across Steps 1-3 into a single upfront callout to reduce redundancy.

DimensionReasoningScore

Conciseness

Mostly efficient prose with well-organized tables and bolded key constraints; minor padding such as restating the 'BEFORE Plan Mode' emphasis across several steps could be trimmed.

4 / 5

Actionability

Concrete guidance throughout (specific git commands, TaskOutput flags, commit message format, proposal fields), though agent prompts and template are delegated to references rather than inlined.

4 / 5

Workflow Clarity

Clear 8-step sequence with explicit checkpoints ('If an agent returns thin results, note the gap') and user review before applying changes; the destructive apply step lacks an explicit re-validation/verification loop after editing target files.

4 / 5

Progressive Disclosure

Lean overview body with three real one-level-deep references (agent-prompts.md, template.md, improvement-guide.md) all clearly signaled via inline links; no nested references.

5 / 5

Total

17

/

20

Passed

Description

92%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, specific description that uses third-person voice and explicitly covers what it does and when to use it. Trigger-term coverage is good but could add common synonyms like 'post-mortem' or 'debrief'.

Suggestions

Add natural trigger synonyms such as 'post-mortem', 'debrief', or 'lessons learned' alongside 'retrospective' and 'session summary' to broaden trigger_term_quality.

DimensionReasoningScore

Specificity

Lists multiple concrete actions in third person ('Reads recent git history, artifacts, and context files to extract learnings and produce improvement proposals'), covering mining, synthesis, and embedding improvements across named targets.

5 / 5

Completeness

Clearly answers both what ('extract learnings and produce improvement proposals for skills, CLAUDE.md, hooks, and plan templates') and when ('Use after any substantive session to capture what did we learn').

5 / 5

Trigger Term Quality

Good natural triggers ('review session', 'retrospective', 'session summary') and explicit 'Use after any substantive session', but lacks synonyms like 'post-mortem' or 'debrief' that a user might naturally say.

4 / 5

Distinctiveness Conflict Risk

Clear niche of post-session reflection with distinct triggers and named output targets; minimal overlap risk with other skills.

5 / 5

Total

19

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
ericjohnolson/tessl-test
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.