CtrlK
BlogDocsLog inGet started
Tessl Logo

axiom-audit-storage

Use when the user mentions file storage issues, data loss, backup bloat, or asks to audit storage usage.

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

Quality

Content

92%

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 high-quality, actionable audit playbook with strong sequencing, verification checkpoints, and concrete fix code. Its only structural weakness is that everything lives in a single long file with no progressive disclosure into reference files.

Suggestions

Move the Storage Location Decision Tree and the Phase 4 cross-auditor overlap notes into a reference file (e.g. references/decision-tree.md) and link to it from the body to shorten SKILL.md.

Extract the False Positives and Phase 3 completeness table into a reference doc so the main body stays a lean overview of the five phases.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence, jumping straight to grep patterns and verification steps without explaining what iOS storage directories are, and every table earns its place.

3 / 3

Actionability

It provides concrete grep patterns, explicit Read-verification instructions, and copy-paste-ready fix code such as 'try data.write(to: url, options: [.atomic, .completeFileProtection])' and the URLResourceValues snippet.

3 / 3

Workflow Clarity

Phases 1-5 are clearly sequenced with explicit checkpoints ('Present this map before proceeding', 'use Read to verify before reporting') and verify-to-fix feedback loops for the risky detection steps.

3 / 3

Progressive Disclosure

No bundle files exist and all content sits inline in one ~280-line SKILL.md; sections are well-organized but material like the decision tree, cross-auditor notes, and false-positives could be split into reference files rather than kept inline.

2 / 3

Total

11

/

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 is trigger-rich and uses natural user phrasing, but it leans on the 'when' while leaving the 'what' implicit, so it does not fully state the skill's concrete capabilities. It is reasonably distinct but shares storage territory with related skills.

Suggestions

Lead with a concrete capability statement before the trigger clause, e.g. 'Audits iOS file storage for data-loss risks, backup bloat, and misprotected secrets. Use when...'

Enumerate the core actions (detects storage anti-patterns, maps directory usage, scores storage health) so the 'what' is explicit, not just implied by 'audit'.

Sharpen distinctiveness by scoping to auditing/detection language ('detects', 'flags', 'scores') to separate it from the storage-diag and storage-management skills.

DimensionReasoningScore

Specificity

It names the storage domain and an implied action ('audit storage usage') but does not list concrete capabilities such as detecting anti-patterns, mapping storage locations, or scoring storage health.

2 / 3

Completeness

It has an explicit 'Use when...' trigger clause (the when), but only weakly implies what the skill does via 'audit storage usage' without a clear capability statement (the what).

2 / 3

Trigger Term Quality

Phrases like 'file storage issues', 'data loss', 'backup bloat', and 'audit storage usage' are natural terms a user would actually say when they need this skill.

3 / 3

Distinctiveness Conflict Risk

It targets a clear storage-audit niche, but 'file storage issues' could overlap with sibling storage skills the body itself references (storage-diag, storage-management).

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.