CtrlK
BlogDocsLog inGet started
Tessl Logo

axiom-audit-grdb-performance

Use when the user mentions GRDB performance review, slow GRDB queries, app-group database setup audit, a ValueObservation that stopped updating, or pre-release GRDB scan.

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-grdb-performance/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.

This is a high-quality, expert-level audit prompt: concrete grep/verify/fix guidance, a rigorously gated five-phase workflow with validation checkpoints, and clearly signaled external references. The main weaknesses are moderate cross-phase redundancy and a long monolithic single-file structure with no bundled reference files.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence (no 'what is SQLite' padding) and almost every token is non-obvious domain specifics, but there is redundancy — Phase 3 re-asks questions already covered by Patterns 2/3/7 and the Phase 5 health table restates pattern descriptions.

4 / 5

Actionability

It provides exact runnable grep patterns, step-by-step verify instructions, and copy-paste fixes (e.g. `PRAGMA optimize=0x10002`, `PRAGMA journal_mode = WAL`, `config.observesSuspensionNotifications = true`) covering the common cases.

5 / 5

Workflow Clarity

A clear five-phase sequence with explicit validation checkpoints — verify-via-Read before reporting, framework gating with a hard stop, a false-positive checklist, and 'Require evidence... don't speculate without reading the code' as a feedback gate.

5 / 5

Progressive Disclosure

Well-organized into clearly headed phases with one-level-deep, clearly signaled external references ('See axiom-data (skills/grdb-performance.md) §6'), but no bundle files exist and the ~340-line SKILL.md inlines material (Phase 3/4 tables, the version table) that could be split into 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 excels at trigger specificity for a narrow GRDB-performance niche but is structurally a "when" clause with no "what" — it never states what the skill does. Adding an explicit capability statement (e.g., "Audits shipped Swift code for GRDB/SQLite performance and correctness anti-patterns and produces a severity-ranked report") would lift completeness and specificity.

Suggestions

Lead with a 'what' clause before the 'when' clause, e.g. 'Audits shipped Swift code for GRDB and SQLite performance/correctness anti-patterns. Use when the user mentions...'

Name the concrete actions the skill performs (audit, detect, cross-reference, score, report) rather than relying on trigger nouns to imply them.

Add 'SQLite' and 'SQLiteData' as trigger synonyms so the skill surfaces for users who frame the problem in SQLite rather than GRDB terms.

DimensionReasoningScore

Specificity

The description names a specific domain ("GRDB performance review", "app-group database setup audit", "ValueObservation") but states no concrete actions the skill performs — the action words (review, audit, scan) appear only as trigger nouns, not as stated capabilities.

2 / 5

Completeness

It provides a strong, explicit "when" ("Use when the user mentions...") but no explicit "what" — a reader cannot tell whether the skill audits, fixes, explains, or generates a report, matching the anchor "only 'when' is present without 'what'".

2 / 5

Trigger Term Quality

Phrases like "slow GRDB queries" and "a ValueObservation that stopped updating" are natural things a user would say, but synonyms such as "SQLite" and file extensions are absent.

4 / 5

Distinctiveness Conflict Risk

Triggers target a clear GRDB-performance niche with minimal conflict risk, though sibling auditors (database-schema-auditor, swiftdata-auditor) referenced in the body create minor overlap risk.

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.