swiftui-performance-audit

SwiftUI performance: render, scroll, CPU/memory, updates, layout, Instruments.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/swiftui-performance-audit/SKILL.md

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with executable code fixes and a clear, validated workflow, supported by well-organized one-level reference files; its main weakness is verbatim duplication of the culprit list across sections.

Suggestions

Define the six common culprits once and reference it from Sections 1 and 3 instead of repeating the identical bullet list verbatim.

Tighten the Remediate section to cross-reference the culprit list rather than restating similar items.

Consider moving the full code-smell catalog into a references file to keep the core workflow lean.

Dimension	Reasoning	Score
Conciseness	Content is instruction-oriented with no concept padding, but Sections 1 and 3 repeat the identical six-bullet culprit list verbatim, and Remediate partially recaps them, so it could be tightened rather than rated 3.	2 / 3
Actionability	Every code smell includes executable Swift examples plus a concrete "Prefer" fix, giving copy-paste-ready, specific guidance rather than vague direction.	3 / 3
Workflow Clarity	A decision tree plus a numbered 1–5 workflow with an explicit Verify step (re-run capture, compare to baseline) provides a clear sequence with a feedback loop.	3 / 3
Progressive Disclosure	The body is an overview with a well-signaled References section listing four real one-level-deep reference files (all verified present in references/), enabling easy navigation.	3 / 3
	Total	11 / 12 Passed

Description

67%

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 omits an explicit use-when trigger clause, capping completeness at 2, and its trigger terms miss common colloquial phrasings users actually say.

Suggestions

Add an explicit "Use when..." clause, e.g. "Use when SwiftUI views lag, drop frames, scroll jankily, or use excessive CPU/memory."

Include natural trigger terms users say: "frame drops", "scroll jank", "laggy", "hangs", not just technical categories.

Keep the current concrete area list but pair it with the trigger clause for full completeness.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capability areas — "render, scroll, CPU/memory, updates, layout, Instruments" — matching the multiple-specific-actions anchor rather than the single-domain score-2.	3 / 3
Completeness	It clearly states what the skill covers but lacks any explicit "Use when..." trigger clause, which the guidelines say caps completeness at 2.	2 / 3
Trigger Term Quality	"SwiftUI performance" and "Instruments" are natural terms, but common user phrasings like laggy, frame drops, jank, slow scroll, or hangs are missing, leaving only partial coverage.	2 / 3
Distinctiveness Conflict Risk	The SwiftUI-specific niche with Instruments references is clearly distinguishable and unlikely to trigger for unrelated skills.	3 / 3
	Total	10 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: steipete/agent-scripts
Path: skills/swiftui-performance-audit/SKILL.md
Commit: bb36883

Reviewed: about 13 hours ago

Table of Contents

Discovery Implementation Validation

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.