CtrlK
BlogDocsLog inGet started
Tessl Logo

axiom-audit-core-data

Use when the user mentions Core Data review, schema migration, production crashes, or data safety checking.

59

Quality

68%

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-core-data/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

88%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 skill body is a strong, highly executable audit workflow with clear phased sequencing, mandatory tool-use verification, and concrete code fixes throughout. The only minor gap is progressive disclosure — the self-contained pattern catalog could be split into reference files for larger codebases.

DimensionReasoningScore

Conciseness

The body is dense but every section earns its place with concrete grep patterns, fix snippets, and severity tables, and it avoids explaining Core Data basics Claude already knows; only minor explanatory rows could be trimmed.

4 / 5

Actionability

It provides exact Glob/Grep patterns, specific Swift fix code examples, and copy-paste-ready search strings covering the common Core Data anti-pattern cases, matching the fully executable anchor.

5 / 5

Workflow Clarity

Phases 1-5 are clearly sequenced with explicit verification checkpoints ('use Read to verify the surrounding context before reporting', 'Require evidence from the Phase 1 map') and a false-positives checklist, giving feedback loops for the destructive/batch auditing context.

5 / 5

Progressive Disclosure

The body is well-organized into distinct phases with a clearly signaled 'Related' section pointing to sibling skills one level deep; with no bundle files present the content is appropriately self-contained, though some pattern detail could arguably live in a reference file.

4 / 5

Total

18

/

20

Passed

Description

47%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, natural trigger phrasing but is missing any statement of what the skill actually does, which caps both completeness and specificity. Adding a concrete action clause (e.g., 'Detects Core Data safety violations and anti-patterns') alongside the triggers would lift it substantially.

Suggestions

Add a concrete 'what' clause before the trigger clause, e.g. 'Detects Core Data safety violations — schema migration gaps, thread-confinement crashes, and data-loss risks. Use when...'

Include the skill's output/deliverable in the description so users know it produces an audit report with a health score, not just a review.

Consider adding 'NSPersistentContainer', 'managed objects', or 'persistent store' as natural synonyms to broaden trigger coverage without losing distinctiveness.

DimensionReasoningScore

Specificity

The description names the Core Data domain and several conditions ('schema migration, production crashes, data safety checking') but states no concrete actions the skill performs, fitting the 'names the domain but actions are minimal or generic' anchor.

2 / 5

Completeness

It has an explicit 'Use when...' trigger but no stated 'what' — the skill's actual action (auditing/detecting violations) is unstated, matching the 'only when is present without what' anchor rather than a clear-what case.

2 / 5

Trigger Term Quality

'Core Data review', 'schema migration', 'production crashes', and 'data safety checking' are natural phrases a user would say, giving good keyword coverage, though synonyms like 'persistent store' or 'managed objects' are absent.

4 / 5

Distinctiveness Conflict Risk

'Core Data review' is a clear niche with minimal conflict risk, though 'production crashes' and 'data safety checking' are broad enough to overlap slightly with adjacent skills, keeping it just below a 5.

4 / 5

Total

12

/

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.