CtrlK
BlogDocsLog inGet started
Tessl Logo

axiom-analyze-swift-performance

Use when the user mentions Swift performance audit, code optimization, or performance review.

70

Quality

86%

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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 tight, fully actionable audit playbook: runnable detection patterns, explicit validation loops, sequenced phases, and a concrete output template. It earns its tokens and assumes Claude's competence throughout.

DimensionReasoningScore

Conciseness

Lean and operational — concrete grep patterns, severity tables, and a false-positives list with no tutorial padding about ARC or COW basics; assumes Claude's Swift competence.

3 / 3

Actionability

Provides directly runnable Glob/Grep patterns and concrete fixes (borrowing, consuming, isKnownUniquelyReferenced, reserveCapacity, @_specialize) plus a fully specified output template.

3 / 3

Workflow Clarity

Clear five-phase sequence with explicit checkpoints (hotspot map presented before proceeding) and a Read-verify-before-reporting validation loop; output limits and false-positive guards add quality checks.

3 / 3

Progressive Disclosure

Self-contained with no bundle files and no nested references; well-labeled phase/section organization with clearly signaled one-level Related pointers and easy navigation.

3 / 3

Total

12

/

12

Passed

Description

72%

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 terms and a clear niche, but it only implies what the skill does rather than stating concrete capabilities. Adding an explicit action clause would lift specificity and completeness.

Suggestions

Add a concrete action clause before the trigger, e.g., 'Detects Swift performance anti-patterns (ARC traffic, unnecessary copies, unspecialized generics, actor overhead) and produces a health score.'

State what the skill does (audits/reports) explicitly so completeness answers both 'what' and 'when'.

DimensionReasoningScore

Specificity

Names the Swift performance domain and several trigger contexts but lists no concrete actions (e.g., detect anti-patterns, score health); it is a trigger clause rather than a capability list.

2 / 3

Completeness

The 'when' is explicit and strong ('Use when the user mentions...') but the 'what' is only implied — the description never states what the skill does.

2 / 3

Trigger Term Quality

'Swift performance audit', 'code optimization', and 'performance review' are natural phrases users would plausibly say, with good variation coverage.

3 / 3

Distinctiveness Conflict Risk

Scoped specifically to Swift performance, a clear niche with distinct triggers unlikely to conflict with other skills.

3 / 3

Total

10

/

12

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.