CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

66

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

62%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured body with clear sequencing and validation, but it loses points on mild cross-section redundancy, lack of executable script invocation examples, and broken/duplicated references in the disclosure layout.

Suggestions

De-duplicate the fail-fast rule and the no-invented-evidence rule so each appears once (e.g., keep them in Validation/Constraints and remove the near-verbatim repeats in Failure mode and Gotchas).

Add at least one concrete example invocation and expected output shape for scan_codex_sessions.py / correlate_multi_source_skill_failures.py to lift actionability.

Fix or remove the missing ./agents/assets/icon-small.png and icon-large.png references and consolidate the duplicated session-evidence-workflow.md link into a single clearly-labeled references section.

DimensionReasoningScore

Conciseness

Sectioned and free of concept-explaining fluff, but near-verbatim redundancy appears across sections — 'stop at first missing or unreadable evidence source and report the exact gap' in both Validation and Failure mode, and the no-inventing-evidence rule repeated across Constraints, Gotchas, and Anti-patterns — so it could be tightened.

2 / 3

Actionability

Names concrete artifacts (scan_codex_sessions.py, correlate_multi_source_skill_failures.py), root-cause categories, and a keep/improve/merge/retire output structure, but gives no example invocations, flags, or sample output artifacts, leaving the guidance partially incomplete.

2 / 3

Workflow Clarity

A clear six-step Procedure is backed by an explicit Validation checklist ('Verify each recommendation cites...', 'Verify severity ordering...') and feedback loops ('Fail fast: stop...', 'If scope is ambiguous, request clarification'), satisfying validation for the destructive retire/remove operations.

3 / 3

Progressive Disclosure

Good 'Read when:' signaling and one-level-deep real references (contract.yaml, session-evidence-workflow.md, the two scripts), but two referenced paths are missing (./agents/assets/icon-small.png, ./agents/assets/icon-large.png), the session-evidence-workflow.md link is duplicated, and the bottom reference list mixes scripts, a collector root, and icon assets in a jumbled way.

2 / 3

Total

9

/

12

Passed

Description

100%

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: third-person voice, concrete actions, explicit 'Use when' trigger covering both what and when, and a distinct niche that is unlikely to conflict with other skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Scan Codex session history for skill failures, usage patterns, and coverage gaps' plus 'recommendations about installing, improving, merging, or pruning skills' — matching the multiple-specific-actions anchor.

3 / 3

Completeness

Explicitly answers both what ('Scan Codex session history for...') and when ('Use when the user wants daily skill-health monitoring or evidence-backed recommendations...'), with an explicit 'Use when' trigger.

3 / 3

Trigger Term Quality

Covers natural user phrasings ('installing, improving, merging, or pruning skills', 'skill failures', 'coverage gaps'); 'Codex session history' and 'skill-health monitoring' are slightly coined but overall trigger coverage is strong.

3 / 3

Distinctiveness Conflict Risk

Clear niche — skill reliability analysis from Codex session evidence — with distinct maintenance triggers unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

relative_links

Relative link issues: 2 missing, 2 deeper-than-1-level

Warning

Total

14

/

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.