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.

58

Quality

66%

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

71%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 content is a well-structured, actionable auditing workflow with explicit validation checkpoints and concrete grep/Swift guidance, scoring high on workflow clarity and actionability. Its main weakness is conciseness — the long tables and repeated pattern descriptions could be trimmed without losing clarity.

Suggestions

Tighten the Phase 2 pattern blocks by collapsing the repeated Issue/Search/Verify/Fix headings into a compact table, reducing token cost while preserving every action.

The Phase 3 and Phase 4 tables overlap heavily; merge or cross-link them to avoid restating the same tmp/UserDefaults/Keychain findings twice.

Move the long Storage Location Decision Tree and cross-auditor notes to a reference file and link one level deep, keeping the main SKILL.md as an overview.

DimensionReasoningScore

Conciseness

The body is mostly dense and information-bearing (grep patterns, fix snippets, tables) with little concept re-teaching, but it is long and several tables and pattern descriptions could be tightened; it sits at 'mostly efficient with some excess'.

3 / 5

Actionability

It gives concrete grep patterns, executable Swift fix snippets (e.g. isExcludedFromBackup and .completeFileProtection calls), and a decision tree; minor gaps where some fixes remain advisory rather than copy-paste ready.

4 / 5

Workflow Clarity

Five clearly sequenced phases with explicit validation checkpoints ('use Read to verify before reporting', 'present the map before proceeding'), severity bumping rules, and false-positive/error-recovery guidance — strong feedback loops for a batch auditing task.

5 / 5

Progressive Disclosure

Well-organized into phases with a clear overview, a decision tree, and a Related section pointing one level out to sibling skills/refs; no bundle files exist so references are to external skills, and structure is good with minor organization gaps in the long tables.

4 / 5

Total

16

/

20

Passed

Description

61%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.

The description has strong trigger-term coverage and an explicit 'Use when' clause, making it well-targeted and distinguishable. Its weakness is specificity: the action is reduced to 'audit storage usage' rather than enumerating the concrete detection actions the skill performs.

Suggestions

Replace the generic 'audit storage usage' with concrete actions, e.g. 'detect files at risk of data loss, backup bloat, sensitive-data exposure, and cross-process invisibility, then produce a storage health score.'

Add natural synonyms users might say, such as 'disk space', 'iCloud quota', or 'app container size', to broaden trigger coverage.

Keep the third-person voice and 'Use when...' clause — they are already correct and effective.

DimensionReasoningScore

Specificity

The description names the domain (storage issues) and a couple of conditions (data loss, backup bloat) but frames the action only as 'audit storage usage' — minimal and generic rather than a list of concrete actions.

2 / 5

Completeness

It pairs a clear 'what' (audit storage / detect storage mistakes) with an explicit 'Use when...' clause naming concrete triggers; the 'when' is explicit though the 'what' is somewhat thin.

4 / 5

Trigger Term Quality

'file storage issues, data loss, backup bloat, audit storage usage' are natural phrases a user would say; missing a few common synonyms (e.g. 'disk space', 'iCloud quota') but coverage is good.

4 / 5

Distinctiveness Conflict Risk

'file storage issues, data loss, backup bloat' carves a clear storage-audit niche with distinct triggers; minor overlap risk with general data/security skills but mostly distinct.

4 / 5

Total

14

/

20

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.