CtrlK
BlogDocsLog inGet started
Tessl Logo

axiom-audit-codable

Use when the user mentions Codable review, JSON encoding/decoding issues, data serialization audit, or modernizing legacy code.

61

Quality

71%

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 ./axiom-codex/skills/axiom-audit-codable/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%

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

The body is a highly actionable, well-sequenced audit procedure with explicit verification checkpoints and concrete code/grep examples. Its main weaknesses are verbosity in the coaching prose and a lack of progressive disclosure — everything lives in one large file with no reference split-out.

Suggestions

Tighten the Phase 3 table cells: collapse the repeated anti-rationalization warnings into a single concise rule so the table reads as a checklist rather than essays.

Move the 8 detection patterns (Phase 2) or the Phase 3 completeness table into a reference file (e.g. references/patterns.md) and link to it, enabling one-level-deep progressive disclosure and trimming the main SKILL.md.

Trim the cross-auditor overlap notes and output-limit rules to the essential one-liners to reduce token overhead without losing guidance.

DimensionReasoningScore

Conciseness

The body is dense and mostly procedural rather than explaining concepts Claude already knows, but the Phase 3 table cells are padded with long, repeated anti-rationalization prose ("Do NOT rationalize...", "The question is NOT...") that could be tightened without losing the instruction.

2 / 3

Actionability

It provides concrete grep patterns per anti-pattern, executable ❌/✅ Swift fix examples, and specific verification commands — copy-paste ready and fully actionable.

3 / 3

Workflow Clarity

A clear five-phase sequence is given with explicit validation checkpoints ("use Read to verify the surrounding context before reporting", "Require evidence from the Phase 1 map... don't speculate") and a severity-bumping cross-reference phase.

3 / 3

Progressive Disclosure

The skill is a single ~270-line monolithic SKILL.md with no bundle/reference files; sections are well-organized, but the 8 detection patterns and the Phase 3 reference table are inline content that could be split out for one-level-deep navigation.

2 / 3

Total

10

/

12

Passed

Description

65%

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 has strong, natural trigger terms and an explicit "Use when" clause, but it omits any statement of what the skill actually does and ends on a broad, overlapping trigger. It is clear on when to invoke but incomplete on capability.

Suggestions

Lead with a capability statement before the trigger clause, e.g. "Detects Codable safety violations and JSON serialization anti-patterns in Swift code. Use when the user mentions..." so the "what" is explicit.

Drop or narrow "modernizing legacy code" to a Codable-specific phrasing (e.g. "migrating JSONSerialization to Codable") to reduce overlap with general modernization skills.

Add at least one concrete action verb (audit, detect, review) up front so specificity reaches the multiple-concrete-actions anchor.

DimensionReasoningScore

Specificity

The description names the domain ("Codable review", "JSON encoding/decoding issues", "data serialization audit") but lists trigger conditions rather than concrete capabilities, so it does not enumerate the multiple specific actions the skill performs.

2 / 3

Completeness

The "when" is explicit and strong ("Use when the user mentions..."), but the "what" is entirely absent — the description never states that the skill audits/detects Codable safety violations, so it does not answer both halves.

2 / 3

Trigger Term Quality

Terms like "Codable review", "JSON encoding/decoding issues", and "data serialization audit" are natural phrases a Swift developer would actually say when they need this skill, giving good coverage.

3 / 3

Distinctiveness Conflict Risk

The Codable/serialization triggers are a clear niche, but the trailing "modernizing legacy code" is generic and could overlap with other codebase-modernization skills.

2 / 3

Total

9

/

12

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
CharlesWiltgen/Axiom
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.