CtrlK
BlogDocsLog inGet started
Tessl Logo

axiom-performance

Use when app feels slow, memory grows, battery drains, or diagnosing ANY performance issue. Covers memory leaks, profiling, Instruments workflows, retain cycles, performance optimization.

57

Quality

66%

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 ./.claude-plugin/plugins/axiom/skills/axiom-performance/SKILL.md
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.

An effective, well-organized routing skill with concrete commands and a strong decision tree, undermined by significant structural redundancy across five overlapping sections. Progressive disclosure is good but references could be cleaner.

Suggestions

Collapse the Example Invocations section (or trim it heavily) since it duplicates the Routing Logic and Decision Tree; keep only cases that add new routing decisions.

Convert file references to markdown link form (e.g. '[memory-debugging](skills/memory-debugging.md)') and consolidate cross-suite pointers into a single 'Related skills' map.

Trim the Anti-Rationalization table to the highest-value rows to reduce token cost while preserving the strongest rebuttals.

DimensionReasoningScore

Conciseness

Content is dense and assumes Claude's competence (no concept explanations), but Routing Logic, Decision Tree, Anti-Rationalization, Example Invocations, and Critical Patterns heavily overlap, with the ~130-line Example Invocations largely duplicating earlier sections.

3 / 5

Actionability

Routing guidance is concrete and executable: specific slash commands ('/axiom:audit memory', '/axiom:profile', '/axiom:console'), named agents, and exact file paths per case, with only minor gaps for a router-style skill.

4 / 5

Workflow Clarity

The numbered Decision Tree provides a clear sequenced procedure with explicit YES/NO branching (e.g. item 4), though it lacks validation/feedback loops; routing is not a destructive/batch operation so the cap does not apply.

4 / 5

Progressive Disclosure

A well-structured router with clear section headers and one-level-deep references ('See skills/X.md'), but references are plain paths rather than link-formatted and several cross-suite pointers add minor navigation friction.

4 / 5

Total

15

/

20

Passed

Description

65%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 trigger-oriented description with explicit 'Use when' guidance and natural symptom phrases, weakened by a topic-list 'what' rather than concrete actions. Distinctiveness is good within the performance domain.

Suggestions

Replace 'Covers memory leaks, profiling, Instruments workflows...' with concrete verbs, e.g. 'Diagnose memory leaks and retain cycles, profile CPU and memory with Instruments, optimize battery and launch performance.'

Add a few common synonyms users say ('laggy', 'hangs', 'freezes', 'device gets hot') to round out trigger coverage.

Narrow 'ANY performance issue' or note it is the router for the suite, to reduce overlap ambiguity with sibling energy/memory skills.

DimensionReasoningScore

Specificity

The 'what' is expressed as a topic list ('Covers memory leaks, profiling, Instruments workflows, retain cycles, performance optimization') rather than concrete verbs; only 'diagnosing' is a real action, so actions are minimal/generic like the score-2 anchor.

2 / 5

Completeness

Both 'what' (Covers memory leaks, profiling...) and 'when' (Use when app feels slow...) are present with an explicit 'Use when' clause; the topic-based 'what' keeps it just short of a 5.

4 / 5

Trigger Term Quality

Natural symptom phrases ('app feels slow, memory grows, battery drains') are exactly what users say, but common synonyms like 'laggy', 'hangs', 'freezes', or 'device gets hot' are missing, matching good-but-incomplete coverage.

4 / 5

Distinctiveness Conflict Risk

The performance niche is clear and trigger phrases are specific, though 'ANY performance issue' creates minor overlap with sibling skills (energy, memory) in the same suite.

4 / 5

Total

14

/

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.