CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

refit

Cross-session environment retrospective driven by OMC's own instrumentation — trace timelines, friction reports, logs, and plan notepads. Every finding lands on the surface that owns the fix (deterministic check, steering volume, tooling, or information access); nothing is written without user approval.

Quality

79%

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

Quality

Content

85%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 tight, well-structured instruction skill: the survey sources, fix-owner taxonomy, approval gate, and check-verification loop are all concrete and explicitly sequenced. The only improvements are cosmetic — dedupating one stated-twice rule and showing one example finding line.

Suggestions

State the 'invented findings are the same violation as skipping the survey' rule once (Evidence first) and reference it from the Headless section rather than repeating it verbatim.

Include one example finding line in the proposal format (e.g., 'ralph loop retried lint step 7× → deterministic check → add pre-commit rule') so the `finding → surface → intended change` shape is unambiguous.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence (no concept explanations), but contains minor trims: the rule "an invented finding is the same violation as skipping the survey" is stated twice (Evidence first and Headless refit sections), and rhetorical flourishes like "starts in a better yard" and "decoration, not protection" add tokens beyond the bare rule. This matches 'efficient; minor instances of over-explanation that could be trimmed' rather than the every-token-earns-its-place anchor at 5.

4 / 5

Actionability

Concrete artifacts are named throughout — `trace_timeline` / `trace_summary`, `omc session friction report`, `.omc/logs/`, `.omc/notepads/*/issues.md`, `.omc/refit/pending-proposals.md`, `docs/standards/`, `.mcp.json` — plus a concrete tool call (Skill tool with `agent-doc-discipline`). Minor gaps keep it below fully-executable: the trace instruments' invocation form is unstated, and 'pass its verification checklist' gestures at content it does not show; an example finding line would make the output format unambiguous.

4 / 5

Workflow Clarity

The process is explicitly sequenced with validation checkpoints: 'Read before asking the user anything' for the survey, 'Stop for user approval' as an explicit gate, and a full feedback loop for landed checks — 'run it clean once, then demonstrate it failing on a deliberately introduced violation, then revert the violation' with a bail-out rule ('A check that cannot be shown failing goes back to the proposal'). Headless mode re-states the same contract with its boundary. This matches the anchor 'clear sequence with explicit validation steps; feedback loops for error recovery'.

5 / 5

Progressive Disclosure

The skill has no references/, scripts/, or assets/ directories, and the body (~49 lines) is under 50 lines with no need for external files — the rubric's simple-skill exception applies. It is organized into five clearly-headed sections (Evidence first, Four fix-owner surfaces, Proposal and landing, Headless refit, Output), and the only external pointers (`agent-doc-discipline`, `configure-notifications`) are one level deep and clearly signaled.

5 / 5

Total

18

/

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.

A distinctive, fairly concrete description whose main weakness is the absence of any 'when to use' guidance: it says what the skill does but never when a user should reach for it. Adding an explicit invocation clause with natural phrasing would lift both completeness and trigger-term quality.

Suggestions

Add a 'Use when...' clause (e.g., 'Use when the user asks for a retrospective, a refit, or wants recurring friction from past sessions fixed') to satisfy the when-half of completeness.

Swap some project jargon for natural synonyms users would actually say — 'what kept breaking', 'repeated failures', 'environment cleanup' — to broaden trigger-term coverage.

Lead with the concrete actions ('reads trace timelines, friction reports, logs, and plan notepads; routes each finding to the check, steering, tooling, or information surface that owns the fix') before the approval-policy tail.

DimensionReasoningScore

Specificity

The description names several concrete capabilities and artifacts: 'trace timelines, friction reports, logs, and plan notepads' and the four fix surfaces '(deterministic check, steering volume, tooling, or information access)'. It sits between 'several specific actions; minor gaps' (4) and comprehensive coverage (5) — the verbs themselves ('retrospective', 'lands on the surface') stay somewhat abstract, so 4 fits.

4 / 5

Completeness

The 'what' is clear and concrete (cross-session environment retrospective over named instruments, findings routed to owning surfaces), but there is no 'Use when...' clause or equivalent explicit trigger guidance — 'when' is only weakly implied by 'cross-session'. Per the judging guidelines, a missing 'Use when...' clause caps completeness at 3.

3 / 5

Trigger Term Quality

Some relevant natural terms are present ('retrospective', 'friction', 'logs', 'trace'), but the description leans on project-local jargon ('OMC's own instrumentation', 'steering volume', 'sediment') and offers no common variations or synonyms a user would casually say ('what kept breaking', 'environment cleanup', 'post-run review'). This matches 'some relevant keywords but missing common variations or synonyms'.

3 / 5

Distinctiveness Conflict Risk

The niche is unmistakable — an environment/infrastructure retrospective driven by OMC's instrumentation with findings routed to four named surfaces — and the vocabulary (friction reports, plan notepads, refit) is shared with no generic skill category. It could not plausibly trigger for a coding, review, or document skill, matching 'clear niche with distinct triggers; minimal conflict risk'.

5 / 5

Total

15

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

Yeachan-Heo/oh-my-claudecode

Path

skills/refit/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.