CtrlK
BlogDocsLog inGet started
Tessl Logo

skill-refactor

Analyzes bounded skill evidence, classifies root causes, and recommends a lifecycle lane such as keep, observe, improve through Skill Factory hardening, merge with approval, or retire with approval. Use when a skill is not working, a skill is not triggering correctly, evals or Tessl disagree, repeated failures need debugging, or skill performance issues need evidence-backed repair handoff items.

67

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Failed to scan

The risk profile of this skill

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 well-structured, actionable body with a clear sequenced workflow, validation checkpoints, a concrete output template, and a worked example. Minor tightening of the repeated SDK proof-ladder language would push conciseness to the top anchor.

DimensionReasoningScore

Conciseness

Efficient, sectioned content that assumes competence and avoids explaining known concepts, with only minor verbosity from the SDK proof-ladder enumeration repeated across Workflow and Validation.

4 / 5

Actionability

Provides a concrete YAML output template, a worked input/expected-output example, and specific commands like './bin/ask sdk start <skill-path> --json --robot', though some gates are named without exact invocations.

4 / 5

Workflow Clarity

A 7-step sequenced workflow with explicit validation checkpoints, a 'fail fast at first failed gate' rule, blocked_by feedback loop, and approval-handoff routing for destructive moves.

5 / 5

Progressive Disclosure

SKILL.md acts as an overview with well-signaled, one-level-deep references to verified files (taxonomy, discovery-interview, evidence-routing, harness-evidence-mapping), and bulk detail is split into separate reference files.

5 / 5

Total

18

/

20

Passed

Description

78%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, complete description that clearly states capability and trigger conditions with concrete lifecycle lanes. Its main limitation is heavy reliance on product-internal jargon (Tessl, Skill Factory hardening) that some users would not naturally say.

DimensionReasoningScore

Specificity

Lists several concrete actions (analyze evidence, classify root causes, recommend lanes keep/observe/improve/merge/retire) with comprehensive coverage, but lane naming leans on internal terminology keeping it just below 5.

4 / 5

Completeness

Explicitly answers both 'what' (analyze evidence, classify root causes, recommend a lane) and 'when' via a 'Use when...' clause with concrete triggers, but the dense internal vocabulary keeps it below the clean 5 anchor.

4 / 5

Trigger Term Quality

Includes natural phrases like 'skill is not working', 'not triggering correctly', and 'repeated failures need debugging', though 'Tessl' and 'Skill Factory hardening' are product-internal jargon and a few synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (skill lifecycle routing/repair handoff) distinct from creation (skillify/skill-creator) with minimal overlap risk.

5 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

Total

15

/

16

Passed

Repository
jscraik/Agent-Skills
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.