CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

swiftui-performance-audit

Audit SwiftUI performance issues from code review and profiling evidence.

Quality

70%

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/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

75%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 content is a strong, lean instruction-only skill: a clearly sequenced six-phase audit workflow with concrete smell categories, remediation patterns, and a verification step, backed by an appropriate one-level-deep reference structure where every referenced file exists. It scores solidly across all dimensions with only minor tightening opportunities.

DimensionReasoningScore

Conciseness

The body is terse and assumes competence ("Invalidation storms from broad observation or environment reads" with no explanatory padding), with only minor trimmable redundancy: the Quick start restates the Workflow, and the profiling-intake pointer appears in three separate sections. This matches 'efficient; minor instances that could be trimmed' rather than the fully lean anchor 5.

4 / 5

Actionability

Guidance is concrete and specific throughout ("Stabilize identities for ForEach and lists", "Downsample images before rendering", "Move heavy work out of body into derived state"), with clear decision points for code-first vs. profiling paths. Per the scoring note, absence of code in an instruction-only skill is not penalized; it falls just short of anchor 5 because some steps (e.g. "guide the user through profiling") delegate specifics to reference files without inline minimal examples.

4 / 5

Workflow Clarity

A clear 6-phase sequence (Intake → Code-First Review → Profile → Analyze → Remediate → Verify) with explicit decision checkpoints ("If code review does not explain the issue, ask for runtime evidence") and a Verify step comparing against baseline metrics. Not anchor 5 because verification is conditional ("if provided") and there is no explicit validate→fix→retry feedback loop in the capture/compare cycle.

4 / 5

Progressive Disclosure

The body is a well-organized overview with one-level-deep references that all exist and are signposted inline at the point of use (code-smells.md, profiling-intake.md, report-template.md) plus a References index. Minor gaps keep it below anchor 5: the four Apple/WWDC references are listed only in the index with no pointers from the relevant sections, and one index line ("Add Apple documentation... as they are supplied by the user") is instructional noise.

4 / 5

Total

16

/

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 clearly names its domain and core action but is minimal: no use-when trigger guidance, no enumeration of the audit's concrete capabilities, and no natural symptom phrases users would say. It sits at the midpoint of the rubric — serviceable, but below the good examples' standard.

Suggestions

Add a 'Use when...' clause with concrete trigger phrases, e.g. "Use when the user reports slow rendering, janky scrolling, or high CPU in SwiftUI."

Enumerate the skill's concrete actions to raise specificity, e.g. "Diagnoses invalidation storms, identity churn, layout thrash, and main-thread work; remediates and verifies against baseline metrics."

Include natural user vocabulary and synonyms ("laggy", "dropped frames", "Instruments", "Time Profiler") so the skill triggers on how users actually describe these symptoms.

DimensionReasoningScore

Specificity

"Audit SwiftUI performance issues" names the domain and a single concrete action; it does not list the several specific capabilities the skill actually performs (diagnose causes, remediate, verify with baseline metrics), so it matches the '1-2 concrete actions' anchor rather than the 'several specific actions' anchor above.

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 explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

"SwiftUI performance issues" is a relevant keyword, but common natural phrases users would say ("slow rendering", "janky scrolling", "laggy", "high CPU", " Instruments") are missing, matching the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

"SwiftUI performance issues" carves out a clear niche with distinct triggers; the only overlap risk is with closely related general performance or code-review skills, matching the 'mostly distinct; minor overlap risk' anchor.

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.

Validation — 15 / 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

Path

plugins/AI-Agents-Safe-Coding-Skills/skills/swiftui-performance-audit/SKILL.md

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.