Stats
Actions
Tags
From repo-visuals
Retrospective meta-skill for the `repo-visuals` skill. Reads accumulated evaluation logs from past runs, spots patterns (recurring low-score criteria, repeated iteration failures, unsatisfied requests), consults other expert skills (skill-creator, frontend-design, etc.) where relevant, and proposes concrete edits to `repo-visuals/SKILL.md` as a reviewable diff. Runs on-demand, not per run.
How this skill is triggered — by the user, by Claude, or both
Slash command
/repo-visuals:repo-visuals-retroThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The `repo-visuals` skill scores every run on five criteria (see `repo-visuals/SKILL.md` §6). This meta-skill turns that accumulated evidence into skill improvements.
The repo-visuals skill scores every run on five criteria (see repo-visuals/SKILL.md §6). This meta-skill turns that accumulated evidence into skill improvements.
./evaluations/runs/ in the user's working directory (before that, the sample is noise).repo-visuals is planned and you want the evidence base first.Do not run this every session. Retros are more valuable with accumulated samples.
repo-visuals skill's SKILL.md — the current skill definition (sibling skill in the same plugin)./evaluations/index.md in the user's working directory — curated aggregate from previous retros./evaluations/runs/*.md in the user's working directory — all per-run raw evaluations since the last retroRead all inputs. Build a small table:
Name each pattern concretely:
For each pattern, consult the relevant expert skill(s) if available in the environment. Examples:
frontend-design skill. Feed it the final HTML + screenshots from low-scoring runs; ask for specific design-rule violations.skill-creator skill. Ask whether the skill's Phase N language is ambiguous or missing a step.evaluate-plugins style skill. Ask whether the 5-criterion scorecard is well-calibrated.Detect which skills are actually available — don't reference non-existent ones.
Write a diff-style proposal: for each pattern, which section of the repo-visuals skill's SKILL.md changes and why. Example:
Pattern: Hero moment delivery weak on CLI tools (2.6/5 avg over 4 runs).
Hypothesis: §1.4a probes don't surface CLI-specific hero moments
(install speed, clear command output, shell ergonomics).
Proposed edit to §1.4a: add a CLI-tool branch to the probing list with
3 tool-specific prompts.
Show the proposed diff. Wait for user approval before applying.
On user approval:
repo-visuals skill's SKILL.md with the approved changes./evaluations/index.md (date, patterns identified, edits applied)./evaluations/runs/processed/ so the next retro only sees new samplesrepo-visuals skill SKILL.md./evaluations/index.md with retro summaryrepo-visuals itselfnpx claudepluginhub livlign/claude-skills --plugin repo-visualsAnalyzes skill evaluation benchmarks and suggests prioritized improvements to instructions, descriptions, examples, error handling, and structure. Use after running /evaluate:skill for actionable skill enhancements.
Retrospectively evaluates and improves skills, agents, commands, and hooks using skill logs, git history, knowledge base, and performance metrics. Use after slow, confusing, or fragile sessions.
Analyzes skill executions from conversation friction, file diffs, user feedback, diagnostics, and lessons to propose concrete improvements to SKILL.md files for efficiency.