BF swiftui-ui-patterns
Apply proven SwiftUI UI patterns for navigation, sheets, async state, and reusable screens.
Apply proven SwiftUI UI patterns for navigation, sheets, async state, and reusable screens.
As a process F 51/100 · Will not run — References files that are not bundled: references/<component>.md
ProcedureSoftware developmentWriting and documentstype and topics are labelled automatically from the skill text
This is a copy of a skill from another catalog; the rating counts the canonical one: swiftui-ui-patterns (sickn33/agentic-awesome-skills)
How to improve
- The text references files that are not there: add them or drop the references.
For the model run — optional
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 32. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/<component>.md - note
frontmatter-keyunknown frontmatter key "risk" - note
frontmatter-keyunknown frontmatter key "source" - note
frontmatter-keyunknown frontmatter key "date_added" - note
edit-residuethe text marks something as outdated (lines 36, 52): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 51/100
Will not run. References files that are not bundled: references/<component>.md
- 0Tools and files. 1 referenced file(s) missing: references/<component>.md
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 3 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 50Failures and branches. 0 branches, has a failure section
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 50 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1867 tokens
- low 10 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 91: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +4Structure: 13 headings
- +3Step-by-step instructions: 50 items
- +4Reference files are cited in the instructions (9 of 30)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.