CtrlK
BlogDocsLog inGet started
Tessl Logo

axiom-health-check

Use when the user wants a comprehensive project-wide audit, full health check, or scan across all domains.

56

Quality

63%

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-health-check/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 body is a well-structured, mostly lean orchestrator workflow with concrete, actionable guidance and clear phase sequencing. Its main weakness is mild redundancy in scope handling and a few implicit rather than formal validation checkpoints.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, skipping explanations of Swift, CoreData, etc.; only minor redundancy exists in re-stating the DIFF SCOPE handling across Phases 0, 1, and 2.

4 / 5

Actionability

Guidance is concrete and executable for an instruction-only skill: exact Glob patterns, grep signal tables, fixed output filenames, and verbatim scope blocks to forward to sub-agents, with only minor implicit details.

4 / 5

Workflow Clarity

Phases 0-4 are clearly sequenced with explicit checkpoints ('Wait for all agents to return before proceeding', dedup step, scope-as-hard-boundary drop rule); a few validation steps are implicit rather than formal checklists.

4 / 5

Progressive Disclosure

No bundle files are needed; the ~190-line single file is well-organized into clearly headed sections (Phase 0-4, Guidelines, Related) with one-level navigation via the Related section, so progressive disclosure is clean and easy to navigate.

5 / 5

Total

17

/

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 provides a clear trigger ('Use when...') and a recognizable niche, but it is vague about concrete capabilities and leans on generic verbs like audit and scan rather than naming what the skill actually inspects or produces.

Suggestions

Replace generic verbs with concrete capabilities the audit performs, e.g. 'Detects memory leaks, accessibility gaps, concurrency issues, and deprecated APIs across a Swift project'.

Briefly state the output artifact (e.g. 'produces a unified health report') so the 'what' is explicit, not just the 'when'.

Add common synonyms a user might say ('lint my project', 'review my codebase health') to broaden trigger coverage.

DimensionReasoningScore

Specificity

The description names the audit domain ('comprehensive project-wide audit, full health check, or scan across all domains') but lists only generic actions (audit/scan/check) with no concrete capabilities such as which domains or issues are inspected.

2 / 5

Completeness

A clear 'Use when' clause is present, but the 'what' is only weakly and vaguely stated (audit/scan across all domains) without concrete actions, leaving the what largely unspecified.

2 / 5

Trigger Term Quality

Phrases like 'comprehensive project-wide audit', 'full health check', and 'scan' are natural things a user would say, though common synonyms like 'lint' or 'review my codebase' are missing.

4 / 5

Distinctiveness Conflict Risk

The 'health check / meta-audit across all domains' framing carves a recognizable niche distinct from single-purpose review skills, with only minor overlap risk against broad code-review or linting skills.

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.