CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

skill-refactor

Scan Codex session history for skill failures, usage patterns, and coverage gaps. Use when the user wants daily skill-health monitoring or evidence-backed recommendations about installing, improving, merging, or pruning skills.

Quality

76%

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 ./Plugins/skill-factory/fixtures/budget-archive/2026-04-19/skills/data_fetch_analysis/skill-refactor/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

51%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 maximally lean and its single reference is cleanly signaled, but it instructs almost nothing actionable: the analysis workflow is unspecified and the bundle's scan/correlate scripts and three other reference files are never pointed to. The skill currently reads as a stub overview rather than an executable guide.

Suggestions

Add a quick-start line that names the actual tooling, e.g. "Run `python scripts/scan_codex_sessions.py <sessions-dir>` to collect failures, usage, and coverage data", so the existing scripts are discoverable and the analysis has a concrete entry point.

Spell out the sequence with a validation checkpoint: scan sessions → identify failures/coverage gaps → rank recommendations, and require each recommendation to cite session evidence per the output_contract in references/contract.yaml before returning it.

Either add navigation pointers for the remaining bundle files (references/evals.yaml, references/task-profile.json) or state when they apply, so the whole bundle is reachable from SKILL.md.

DimensionReasoningScore

Conciseness

The body is two sentences plus one conditional reference line ("Analyze skill reliability from session evidence and return prioritized recommendations.") with zero padding and no explanation of concepts Claude already knows. Every token earns its place, matching the lean-and-efficient anchor. Its brevity costs are charged to actionability, not here.

5 / 5

Actionability

"Analyze skill reliability from session evidence and return prioritized recommendations" describes a goal rather than instructing how to achieve it — no command, code, or step for scanning or analysis. The only concrete guidance is the pointer to contract.yaml ("Read when: evidence schema or audit criteria are needed"), which is a minimal hint; the bundle's scripts (scripts/scan_codex_sessions.py, scripts/correlate_multi_source_skill_failures.py) are never mentioned, so it sits at the minimal-concrete-guidance anchor rather than entirely-vague (1) or some-incomplete-guidance (3).

2 / 5

Workflow Clarity

The body implies at most a rough sequence (gather session evidence → analyze → return recommendations) but defines no steps, never sequences the two available scan/correlate scripts, and includes no validation checkpoint for what is a batch analysis over session history. It is above the incoherent/no-sequence anchor (1) only because a rough input-to-output flow is implied, and below anchor 3 because no checkpoints or explicit steps are written at all.

2 / 5

Progressive Disclosure

The one reference present is well signaled and one level deep ("Read when: evidence schema or audit criteria are needed: [contract](./references/contract.yaml)", a real file), but scored against the actual bundle the navigation is incomplete: scripts/, references/evals.yaml, references/task-profile.json, and references/prompt-injection-expected-context.json are all unreferenced from SKILL.md, leaving the core tooling undiscoverable. That is more than the minor organization gaps of anchor 4, though the body itself is not a monolith, so it lands at 3.

3 / 5

Total

12

/

20

Passed

Description

92%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 description: concrete, third-person, and it explicitly pairs what the skill does with when to use it, closely matching the rubric's good examples. The only weakness is trigger synonym coverage (no "audit"/"maintenance" variants or file extensions), keeping trigger quality at 4.

DimensionReasoningScore

Specificity

"Scan Codex session history for skill failures, usage patterns, and coverage gaps" plus "recommendations about installing, improving, merging, or pruning skills" lists multiple specific concrete actions spanning input (session history), analysis targets (failures, patterns, gaps), and outputs (recommendations), matching the comprehensive-coverage anchor. It is not a 4 because the action list covers the full scan-to-recommendation pipeline with no significant coverage gaps.

5 / 5

Completeness

The what is explicit ("Scan Codex session history for skill failures, usage patterns, and coverage gaps") and the when is explicit with concrete triggers ("Use when the user wants daily skill-health monitoring or evidence-backed recommendations about installing, improving, merging, or pruning skills"), matching the both-what-and-when anchor with trigger phrases. Voice is third person ("Scan..."), so no voice penalty applies.

5 / 5

Trigger Term Quality

Natural phrases like "skill failures", "skill-health monitoring", and "pruning skills" are terms a user managing skills would plausibly say. It falls short of the 5 anchor because it lacks synonyms and concrete artifacts (e.g., "session logs", "skill audit", file extensions such as .jsonl).

4 / 5

Distinctiveness Conflict Risk

"Codex session history" and "skill-health monitoring" carve out a clear niche with distinct trigger phrases unlikely to fire for unrelated skills. It is not a 4 because the trigger surface (pruning/merging/monitoring skills) has minimal overlap with neighboring session-analysis or code-review skills.

5 / 5

Total

19

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

jscraik/Agent-Skills

Path

Plugins/skill-factory/fixtures/budget-archive/2026-04-19/skills/data_fetch_analysis/skill-refactor/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.