CtrlK
BlogDocsLog inGet started
Tessl Logo

self-repair

Execute autonomous diagnostics, verify MCP server stability, and treat system degradation using tests and memory core forensics. Triggers: [Healthcheck, run health checklist, diagnose system collapse, MCP infrastructure failure, troubleshoot agent OS, system degraded, Sandman handoff verification failure, self-repair, system recovery]

66

Quality

78%

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

Quality

Content

86%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 SKILL.md body is a well-structured overview that cleanly delegates detail to a single, clearly-signaled reference file with strong validation guidance inside it. The main improvement would be inlining a short diagnostic starting step so the body is independently actionable.

Suggestions

Inline one or two concrete first steps (e.g., the Phase 0 classify-before-treating decision) so the body is executable without opening the reference.

Add a brief 'when to stop and escalate' checkpoint in the body so a critical validation cue is visible before delegation.

Note in the body that the protocol contains destructive container actions, signaling the validation steps the reader will encounter.

DimensionReasoningScore

Conciseness

The body is a lean single directive naming the exact tool and file path with no padding or over-explanation of concepts Claude already knows — every token earns its place.

5 / 5

Actionability

It gives a fully concrete, executable instruction (use `view_file` to read a specific path and adhere to it), but all detailed executable steps are delegated to the reference rather than inlined, leaving a minor gap versus copy-paste-ready code in the body itself.

4 / 5

Workflow Clarity

The referenced protocol provides a clear phased sequence (Phase 0–4) with explicit validation checkpoints and feedback loops for destructive container actions, but the body itself carries no inlined sequencing or checkpoints, a minor gap versus the 5 anchor.

4 / 5

Progressive Disclosure

The body is a concise overview pointing to a single, real, clearly-signaled one-level-deep reference (self-repair-protocol.md) that does not further nest document references, yielding easy navigation and appropriate content split.

5 / 5

Total

18

/

20

Passed

Description

71%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 strong: it pairs concrete capabilities with an explicit trigger list targeting a specialized, distinctive niche. Minor gains are possible from adding a few more natural synonyms, but it already answers what and when clearly.

DimensionReasoningScore

Specificity

Names concrete actions — 'Execute autonomous diagnostics', 'verify MCP server stability', 'treat system degradation using tests and memory core forensics' — listing several specific actions with only minor coverage gaps, fitting the 4 anchor better than the 1-2-action 3 anchor.

4 / 5

Completeness

It explicitly answers both 'what' (diagnostics, verification, treatment via tests and memory forensics) and 'when' via an explicit concrete 'Triggers:' list — the 'Triggers:' clause serves as the equivalent of a 'Use when...' clause, so the missing-clause cap does not apply.

5 / 5

Trigger Term Quality

The Triggers list supplies many natural phrases users would say ('run health checklist', 'system degraded', 'troubleshoot agent OS') plus synonyms, giving good keyword coverage just short of the comprehensive-synonym-and-extension level 5.

4 / 5

Distinctiveness Conflict Risk

The niche is narrow and specialized (MCP servers, Agent OS, Sandman handoff, memory core forensics) with distinct trigger phrases like 'Sandman handoff verification failure', giving minimal conflict risk with other skills.

5 / 5

Total

18

/

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
neomjs/neo
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.