BC flowstitch
Turn one sentence into a deployed website. FlowStitch is your AI design team: prompt engineering, design system generation, multi-page creation, quality evaluation, React/TypeScript export, and one-command deploy. Scrape any competitor's site and build something better. Import a logo and get a full brand system. Build websites, admin dashboards, or mobile apps. Powered by Google Stitch MCP tools. Free from the Flow team.
As a process C 57/100 · Has gaps — weak spots: result and completion, when it triggers, execution cost
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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: 20. 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") - warning
body-longSKILL.md body ≈ 8127 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 57/100
- 0Result and completion. Does not say what the result is
- 20When it triggers. No condition that starts the skill
- 40Execution cost. Instruction body is 8127 tokens: crowds the task out of the window
- 60Tools and files. Uses tools (bash, web, node) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Failures and branches. 5 branches
- 85Steps. 126 steps, 1 vague phrases
- 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 19 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (5 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
- -226 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 424: enough signal without eating the budget
- +4Structure: 75 headings
- +3Step-by-step instructions: 126 items
- +4Has examples (39 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 67.