CtrlK
BlogDocsLog inGet started
Tessl Logo

swiftui-performance-audit

Audit SwiftUI performance issues from code review and profiling evidence.

53

Quality

60%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/swiftui-performance-audit/SKILL.md

The canonical home for this skill is swiftui-performance-audit in administrakt0r/AI-Agents-Safe-Coding-Skills

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.

The skill body is well-structured, actionable, and uses progressive disclosure effectively with real reference files. The main weakness is redundancy between the Workflow summary and the detailed numbered sections, plus repeated re-citation of the same reference files. Consolidating these would improve conciseness without losing clarity.

DimensionReasoningScore

Conciseness

The body is lean and does not explain concepts Claude already knows, but the Workflow summary (steps 1-5) duplicates the detailed numbered sections (Intake through Verify), and the same reference files are re-pointed to multiple times, so it is mostly efficient with some tightening possible.

3 / 5

Actionability

Provides concrete, specific guidance — named smell categories, explicit remediation actions ('Move heavy work out of body into derived state', 'Downsample images before rendering', 'Stabilize identities for ForEach') — appropriate for an instruction-only audit skill with minor gaps; absence of code is not penalized here.

4 / 5

Workflow Clarity

A clear six-step sequence (Intake, Code-First, Profile, Analyze, Remediate, Verify) with an explicit Verify checkpoint comparing against baseline metrics, but lacks explicit error-recovery feedback loops, fitting 'clear sequence with most checkpoints' rather than the 5 anchor.

4 / 5

Progressive Disclosure

SKILL.md is an overview with one-level-deep references (code-smells.md, profiling-intake.md, report-template.md, plus WWDC/Apple docs) that all exist as real files and are signaled inline and in a References section; minor redundancy in re-citing the same files keeps it just below 5.

4 / 5

Total

15

/

20

Passed

Description

53%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 is specific and distinctive but stops short of an explicit trigger clause, omitting the 'when to use' guidance that the rubric rewards. It also lacks the common symptom vocabulary users would naturally say. Adding a 'Use when...' sentence with symptom triggers would lift completeness and trigger-term quality.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user reports slow rendering, janky scrolling, layout thrash, or high CPU in SwiftUI.'

Include common user-facing symptom terms (janky scrolling, dropped frames, laggy UI) alongside 'profiling' to improve trigger-term coverage.

Consider naming 1-2 more concrete actions (e.g. 'classify symptoms, review code smells, guide Instruments profiling') to push specificity toward 4-5.

DimensionReasoningScore

Specificity

Names the domain ('SwiftUI performance issues') and two evidence sources ('code review and profiling evidence'), but does not list several distinct concrete actions, matching the anchor for 1-2 concrete actions.

3 / 5

Completeness

The 'what' is clear ('Audit SwiftUI performance issues from code review and profiling evidence') but there is no 'Use when...' clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Includes relevant natural terms ('SwiftUI performance', 'profiling') but misses common symptom phrasing users actually say ('janky scrolling', 'slow rendering', 'laggy'), fitting the 'some relevant keywords but missing variations' anchor.

3 / 5

Distinctiveness Conflict Risk

'SwiftUI performance' is a clear, narrowly-scoped niche with distinct triggers and only minor overlap risk with general code-review skills, matching the 'mostly distinct' anchor rather than the fully distinct 5 due to generic 'code review' phrasing.

4 / 5

Total

13

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.