AF kuikly-app-builder-skill
Use this skill when the user asks to create, build, or preview a cross-platform mobile app. Powered by Kuikly — a Kotlin Multiplatform UI framework supporting Android, iOS, HarmonyOS, macOS, H5 and miniApp. Handles project scaffolding, building, on-device preview, screenshot capture, and publishing via a single CLI.
As a process F 63/100 · Will not run — References files that are not bundled: references/KuiklyUI
How to improve
- The text references files that are not there: add them or drop the references.
- 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: 57. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/KuiklyUI - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 63/100
- 0Tools and files. 1 referenced file(s) missing: references/KuiklyUI
- 0Result and completion. Does not say what the result is
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Execution cost. Instruction body is 4517 tokens
- 100Steps. 42 steps
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 5 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 13 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (3 tags): a typed call is more reliable
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)
- +3Output format is not stated: the model decides each time
- -254 emoji in the instructions: noise for the model
- +2Single-language instructions
- +3Description length 317: enough signal without eating the budget
- +4Structure: 37 headings
- +3Step-by-step instructions: 42 items
- +4Has examples (17 code blocks)
- +4Reference files are cited in the instructions (3 of 4)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 80.