SKILLEMALL.ai
GitHub ↗ RU Sign in

CC render-ios-keyboard

Render a static iOS QWERTY keyboard as inline HTML+CSS sized for the 750-wide 9:16 stage. Includes the 3-suggestion bar, alpha keys, shift/backspace, 123/emoji/space/return row, and the bottom globe+mic strip. No animation logic — slide up/down is the molecule's job (CSS transform on the .keyboard root).

gooseworks-ai/goose-skills Agent Skills author: gooseworks-ai 8 files · 2 scripts body ≈ 1 843 tokens Open the sourcegithub.com↗ analyzed 3 d ago

Render a static iOS QWERTY keyboard as inline HTML+CSS sized for the 750-wide 9:16 stage.

As a process C 54/100 · Has gaps — References files that are not bundled: templates/keyboard.css

GeneratorDesignSoftware developmentWriting and documentstype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
C
87/100
safety, quality, tests
Safety 60%
100
Quality 40%
67
Run on models
none yet
Process rating
C
54/100
Has gaps
References files that are not bundled: templates/keyboard.css
Tools and files w 18
0
Progress reporting w 2
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

The same skill appears in 1 more place: goose-skills

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. 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: 4. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning missing-ref reference to a missing file: templates/keyboard.css
  • note frontmatter-key unknown frontmatter key "status"
  • note frontmatter-key unknown frontmatter key "superseded_by"

Process rating: all ten parameters 54/100

Will not run. References files that are not bundled: templates/keyboard.css
  • 0Tools and files. 1 referenced file(s) missing: templates/keyboard.css
  • 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
  • 50Failures and branches. 0 branches, has a failure section
  • 60Result and completion. Output format stated, no completion criterion
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Steps. 30 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1843 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)
  • +1No license
  • +2Single-language instructions
  • +3Description length 305: enough signal without eating the budget
  • +4Structure: 11 headings
  • +3Step-by-step instructions: 30 items
  • +3Output format is stated explicitly
  • +4Has examples (2 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 67.