CtrlK
BlogDocsLog inGet started
Tessl Logo

axiom-audit-energy

Use when the user mentions battery drain, energy optimization, power consumption audit, or pre-release energy check.

61

Quality

72%

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-energy/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 tight, highly actionable audit playbook with concrete grep patterns, verification loops, and a clear phased workflow including validation checkpoints. It loses a little on conciseness to a few directive prose lines and on progressive disclosure because its cross-references point to sibling skills rather than a local reference bundle.

DimensionReasoningScore

Conciseness

The body is dense and mostly task-oriented with grep patterns, impact figures, and fix guidance rather than explaining what Swift or timers are; a few prose lines like 'Run every Glob, Grep, and Read this prompt lists' and the Phase 3 intro could be trimmed, but padding is minimal.

4 / 5

Actionability

Every pattern lists exact grep search strings, concrete verification checks, impact percentages, and actionable fixes; the output format and false-positive list give copy-paste-ready guidance covering common cases.

5 / 5

Workflow Clarity

Five sequenced phases with an explicit map-presented-before-proceeding checkpoint in Phase 1, per-match Read verification loops in Phase 2, cross-referencing in Phase 4, and a defined health-score rubric in Phase 5 form a clear workflow with feedback loops for the batch/destructive audit operation.

5 / 5

Progressive Disclosure

Content is well-organized into phases and tables with a clearly signaled Related section pointing one level out to sibling skills (energy.md, energy-ref.md, timer-patterns.md, xcsym-ref.md); however no local bundle files exist and several of these references point to other skills rather than local reference files, leaving minor organization gaps.

4 / 5

Total

18

/

20

Passed

Description

56%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 and a clear 'Use when' clause, but it lacks a concrete statement of what the skill actually does — it names triggers rather than capabilities. Adding an explicit capability clause would lift completeness and specificity.

Suggestions

Add a concrete capability clause before the trigger clause, e.g. 'Audits iOS code for energy anti-patterns (timer abuse, background location, polling) and reports battery-drain estimates. Use when...'

State the output the skill produces (e.g. 'produces an Energy Health Score and severity-ranked issue list') so the 'what' is explicit.

Include the file extension or artifact type the skill works on (e.g. '.swift codebases', or '.ips crash artifacts') to sharpen distinctiveness from sibling auditors.

DimensionReasoningScore

Specificity

The phrase 'battery drain, energy optimization, power consumption audit, or pre-release energy check' names the domain and a few activity types but lists no concrete detection actions like 'scans', 'reports', or 'detects anti-patterns'; it reads as a trigger list rather than a capability description.

2 / 5

Completeness

It explicitly answers 'when' via the 'Use when...' clause but the 'what' is only weakly implied — it never states that the skill detects anti-patterns and produces an energy audit report, so 'what' is missing as a concrete capability statement.

3 / 5

Trigger Term Quality

'battery drain', 'energy optimization', 'power consumption audit', and 'pre-release energy check' are natural phrases a user would say, with good synonym coverage, though it omits common variants like 'battery life' or 'power audit'.

4 / 5

Distinctiveness Conflict Risk

The energy/battery niche is fairly specific and distinct from general performance or memory auditors, with minimal overlap risk except against the closely related axiom-performance skill.

4 / 5

Total

13

/

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.