CtrlK
BlogDocsLog inGet started
Tessl Logo

axiom-profile-performance

Use when the user wants automated performance profiling, headless Instruments analysis, or CLI-based trace collection.

64

Quality

75%

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-profile-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.

The body is a strong, highly actionable profiling workflow with explicit validation gates and error-recovery loops. Its only real weakness is progressive disclosure: it is a monolithic single file with no accompanying reference bundle despite referencing external skills.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence (no explanations of what profiling or Instruments are), with only minor repetition — the consent gate is restated across the workflow and the error-handling table.

4 / 5

Actionability

It gives fully executable, copy-paste-ready commands throughout — the intent-to-preset table maps user phrasing to exact `xcprof record` invocations, plus concrete `jq` discovery pipelines and analyze/compare commands covering the common cases.

5 / 5

Workflow Clarity

A clear four-step sequence (target → record → analyze → report) with explicit validation checkpoints (`doctor` prereq, the support-matrix honesty gate) and feedback loops for error recovery (re-scope a hang window, re-record with the right preset, add `--dsym`).

5 / 5

Progressive Disclosure

Well-organized sections with clearly signaled one-level-deep pointers to external skills in 'Related', but no bundle files exist and the single ~160-line file inlines detail (comparison workflow, error table, tips) that could be split into reference files.

4 / 5

Total

18

/

20

Passed

Description

62%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 a clear, explicit trigger clause and a distinct niche, but its capability phrasing is category-level rather than concrete and it omits common user synonyms. It sits just above midpoint overall.

Suggestions

Lead with a concrete capability statement ('Profiles running apps headlessly via xcprof and produces an honest, actionable report') before the 'Use when' clause so 'what' is stated, not just implied.

Add natural trigger synonyms users actually say — 'slow app', 'memory leak', 'high CPU', 'retain cycle', 'profile my app' — alongside the technical terms.

Replace category labels ('analysis', 'trace collection') with one or two concrete actions ('record bounded traces, attribute hot frames to user code').

DimensionReasoningScore

Specificity

Names the profiling domain and a few activities ('automated performance profiling, headless Instruments analysis, CLI-based trace collection') but these read as category labels rather than concrete actions like 'record traces, attribute hot frames, report regressions'.

3 / 5

Completeness

An explicit 'Use when the user wants...' clause answers 'when' clearly, and the listed activities imply the 'what', but there is no standalone capability statement of what the skill does.

4 / 5

Trigger Term Quality

'performance profiling' is a natural user phrase, but 'headless Instruments analysis' and 'CLI-based trace collection' lean technical; common variations users actually say ('slow app', 'memory leaks', 'CPU', 'profile my app') are missing.

3 / 5

Distinctiveness Conflict Risk

The headless-Instruments / CLI-trace niche is fairly distinct, with only minor overlap risk against the related axiom-performance skill family.

4 / 5

Total

14

/

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.