CtrlK
BlogDocsLog inGet started
Tessl Logo

axiom-data

Use when working with ANY data persistence, database, storage, CloudKit, migration, or serialization in an Apple app. Covers SwiftData, Core Data, GRDB, SQLite, Realm, CloudKit sync, file storage, Codable, migrations.

67

Quality

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-organized router/index body that routes symptoms to specific reference files and auditor agents with clear decision logic and a critical-migration gate. Its main weakness is redundancy: the same routing mappings are repeated across the Quick Reference, Decision Tree, and Example Invocations sections.

Suggestions

Consolidate the Quick Reference table, Decision Tree, and Example Invocations into a single routing structure — the same ~30 topic→file mappings appear three times; pick one primary format (e.g. the table) and link the others to it.

Trim the Example Invocations section, which largely restates the Quick Reference; keep only the few examples that illustrate non-obvious routing (e.g. the tvOS iCloud-first case or errSecDuplicateItem).

Normalize reference notation so all pointers use the same form; mixing `See skills/foo.md`, `See axiom-security (skills/foo.md)`, and `→ Read: skills/foo.md` makes the navigation surface inconsistent.

DimensionReasoningScore

Conciseness

Mostly efficient tables/pointers, but the Quick Reference table, Decision Tree, and Example Invocations sections each re-encode the same ~30 topic→file mappings in three formats, and the ~50-line Example Invocations largely restates the Quick Reference — material that could be consolidated.

3 / 5

Actionability

Gives concrete, executable routing — explicit file paths to read, named agents to launch ("Launch `core-data-auditor` agent"), and slash commands ("/axiom:audit core-data") — with minor gaps since the referenced skills/*.md files are not present in this skill's bundle.

4 / 5

Workflow Clarity

The numbered Decision Tree is a clear sequenced routing flow, and the "Critical Pattern: Migrations" callout ("ALWAYS read `skills/database-migration.md`... prevents data loss") acts as an explicit gate on the destructive path, though the router itself delegates validation to the downstream migration skill.

4 / 5

Progressive Disclosure

Well-structured overview pointing to one-level-deep references with clear navigation (tables + decision tree), but the bundle directories are empty so the many `skills/*.md` references resolve to sibling-suite files rather than this skill's own bundle, and cross-suite hops ("See axiom-security (skills/keychain.md)") slightly muddy the one-level-deep ideal.

4 / 5

Total

15

/

20

Passed

Description

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

A strong, well-scoped router description that explicitly pairs concrete trigger conditions with a clear statement of coverage across the Apple data-persistence stack. Its only weakness is that capabilities are expressed as domain nouns rather than concrete action verbs.

DimensionReasoningScore

Specificity

Lists several specific domains and technologies — "data persistence, database, storage, CloudKit, migration, or serialization" plus SwiftData, Core Data, GRDB, SQLite, Realm, Codable — but states activity-categories rather than concrete verbs (extract/fill/merge), leaving a minor gap versus the comprehensive-action anchor.

4 / 5

Completeness

Explicitly answers both: the "when" via the "Use when working with ANY data persistence, database, storage, CloudKit, migration, or serialization in an Apple app" trigger clause, and the "what" via "Covers SwiftData, Core Data, GRDB, SQLite, Realm, CloudKit sync, file storage, Codable, migrations."

5 / 5

Trigger Term Quality

Comprehensive natural terms an Apple developer would actually say — "data persistence", "database", "storage", "CloudKit", "migration", "serialization" — alongside framework synonyms (SwiftData, Core Data, GRDB, SQLite, Realm), matching the full-coverage-with-synonyms anchor.

5 / 5

Distinctiveness Conflict Risk

Carves a clear niche — Apple-app data persistence/storage — with distinct triggers; the Apple-app scoping and the enumerated persistence technologies keep conflict risk with other skills minimal.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

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.