BC stitch-design
Official Google Stitch SDK wrapper for OpenClaw. Requires only STITCH_API_KEY. Generate UI screens from text, apply targeted edits, branch variants, export HTML/images, and track design lineage with screen aliases plus append-only event history. Stores local artifacts under the skill folder and talks only to Google Stitch endpoints needed for generation and screenshot delivery.
Official Google Stitch SDK wrapper for OpenClaw.
As a process C 54/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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 · 5
✓ No critical or high findings
Medium and low: 5
-
low Secrets in code
secret-high-entropy-tokenscripts/package-lock.json:17High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…J8m+ITxQ…9QW+NoyB…z4A==",
detector -
low Secrets in code
secret-high-entropy-tokenscripts/package-lock.json:82High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…GLi+2W/6ao+6Y7gu/RCwR…Kng==",
detector -
low Secrets in code
secret-high-entropy-tokenscripts/package-lock.json:261High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…GLw+xYSd…cqA==",
detector -
low Secrets in code
secret-high-entropy-tokenscripts/package-lock.json:316High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…FrF+LTRo…W3g==",
detector -
low Secrets in code
secret-high-entropy-tokenscripts/package-lock.json:325High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…A6j+hAmM…GbS+kf5c…csw==",
detector
Files scanned: 16. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
edit-residuethe text marks something as outdated (lines 455): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 54/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 15 mutating operations with no state check
- 60Tools and files. Uses tools (bash, web, node) that frontmatter does not declare
- 70Execution cost. Instruction body is 4697 tokens
- 100Steps. 81 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 21 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (14 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
- -35 of 6 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 380: enough signal without eating the budget
- +4Structure: 37 headings
- +3Step-by-step instructions: 81 items
- +4Has examples (15 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.