CtrlK
BlogDocsLog inGet started
Tessl Logo

1k-retrospective

Analyze accumulated bug fix cases and propose updates to the self-testing checklist. Use periodically (weekly/monthly) to evolve quality checks based on real issues.

60

Quality

72%

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 ./.skillshare/skills/1k-retrospective/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 is an exemplary lean workflow: numbered steps, quantified thresholds, a concrete output template, modification guardrails, and a worked example, with the heavy case data correctly offloaded to a real bundle reference. The main fixes are small operational gaps: specify the `self-testing.mdc` path, define first-run behavior when no retrospective marker exists, and add a post-change validation step.

Suggestions

Define first-run behavior when no `<!-- Retrospective completed -->` marker exists (the current case-studies.md contains zero markers) — e.g. 'If no marker exists, analyze the last 10 cases'.

Give the full path for `self-testing.mdc` and either create `references/patterns.md` or note it should be created on first use, since the bundle currently lacks it.

Add a post-application validation step: after Step 5, re-check that `self-testing.mdc` is still under 150 lines and retains the 9-section structure before appending the completion marker.

DimensionReasoningScore

Conciseness

The body is lean and instruction-only — no concept explanations, no padding; every section is a rule or a template (e.g. "Max 150 lines — if exceeded, consolidate similar items", the compact report block, and the 3-line worked example). This matches 'Lean and efficient; assumes Claude's competence; every token earns its place'.

5 / 5

Actionability

Guidance is largely executable: exact thresholds ("fewer than 3 new cases", "2+ times marked NEW", "3+ times already covered"), a fill-in report template, and four concrete modification rules. Minor gaps keep it below 5: no path for `self-testing.mdc`, and no specification of first-run behavior when no `<!-- Retrospective completed -->` marker exists (the shipped case file contains none).

4 / 5

Workflow Clarity

Six clearly sequenced steps with real checkpoints: an explicit stop gate ("If fewer than 3 new cases, report 'Not enough new cases' and stop") and a user-confirmation gate before modifying `self-testing.mdc`, so the destructive/batch cap does not apply. It falls short of anchor 5 because there is no feedback loop after applying changes (no re-validation that the 150-line limit or 9-section structure still holds) and the unhandled no-marker first run is a gap in the sequence.

4 / 5

Progressive Disclosure

The ~48-line body stays an overview and pushes the bulk (671-line case data) into `references/case-studies.md`, which exists in the bundle and is one level deep. Remaining gaps fit anchor 4: `references/patterns.md` is named as an overflow destination but does not exist in the bundle, and the reference is cited by the long path `.claude/skills/1k-retrospective/references/case-studies.md` rather than a clean relative link, slightly blurring navigation.

4 / 5

Total

17

/

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 is concise, in third person, and answers both what and when with an explicit periodic-use clause, avoiding fluff and over-claims. Its weaknesses are thin trigger-term coverage (the word 'retrospective' never appears in the description) and a what-clause limited to two actions.

Suggestions

Add natural trigger terms users would actually say — 'retrospective', 'postmortem', 'lessons learned' — since the skill's own name ('1k-retrospective') is absent from the description.

Broaden the what-clause from two actions to the full set the skill performs, e.g. 'Analyze accumulated bug fix cases, identify recurring root-cause patterns, and add or strengthen checks in the self-testing checklist.'

Make the when-clause more concrete, e.g. 'Use after a batch of bug fixes has accumulated, or when asked to run a retrospective or update the self-testing rules.'

DimensionReasoningScore

Specificity

"Analyze accumulated bug fix cases and propose updates to the self-testing checklist" names the domain (bug fix cases) and exactly two concrete actions (analyze, propose updates), matching the anchor 'Names domain and 1-2 concrete actions, but not comprehensive'. It does not list the fuller action set (aggregate patterns, strengthen weak checks, archive) that would reach level 4.

3 / 5

Completeness

The 'what' is clear ("Analyze accumulated bug fix cases and propose updates to the self-testing checklist") and an explicit when-clause is present ("Use periodically (weekly/monthly) to evolve quality checks based on real issues"), so it is not capped at 3. However the 'when' is time-based and generic rather than trigger-phrase driven, matching anchor 4 ('when' could be more explicit or specific) rather than anchor 5's concrete trigger phrases.

4 / 5

Trigger Term Quality

Terms like "bug fix cases", "self-testing checklist", and "quality checks" are relevant, but common natural variations users would say are missing — notably "retrospective" (only in the skill name, absent from the description), plus "postmortem" and "lessons learned". This fits 'Some relevant keywords but missing common variations or synonyms', not level 4's 'good keyword coverage'.

3 / 5

Distinctiveness Conflict Risk

The combination of accumulated bug fix case analysis and self-testing checklist evolution carves a fairly distinct niche with minimal conflict risk, but it could plausibly overlap with a general code-review or testing skill, matching 'Mostly distinct; minor overlap risk with closely related skills' rather than level 5's fully clear niche.

4 / 5

Total

14

/

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

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

14

/

16

Passed

Repository
OneKeyHQ/app-monorepo
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.