SKILLEMALL.ai
GitHub ↗ RU Sign in

AB wireframe-sketch

A hand-drawn wireframe exploration — graph-paper background, marker / pencil tone, multiple tab labels for variants, sticky-note annotations, scribbled chart placeholders, hatched fills. Reads like a designer's whiteboard before any pixels are committed. Use when the brief asks for "wireframe", "sketch wireframe", "hand-drawn", "lo-fi", "whiteboard", "草稿", or "手绘原型".

nexu-io/open-design Agent Skills author: nexu-io Apache-2.0 3 files body ≈ 743 tokens Open the sourcegithub.com↗ analyzed 6 d ago

A hand-drawn wireframe exploration — graph-paper background, marker / pencil tone, multiple tab labels for variants, sticky-note annotations, scribbled chart…

As a process B 65/100 · Nearly there — weak spots: when it triggers, inputs and preconditions, running it twice

ProcedureDesigntype 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
A
96/100
safety, quality, tests
Safety 60%
100
Quality 40%
90
Run on models
none yet
Process rating
B
65/100
Nearly there
Progress reporting w 2
0
When it triggers w 12
20
Inputs and preconditions w 11
30
the three weakest of ten parameters · all ten

How to improve

    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: 3. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • note frontmatter-key unknown frontmatter key "triggers"
    • note frontmatter-key unknown frontmatter key "od"

    Process rating: all ten parameters 65/100

    • 0Progress reporting. Says nothing while it works
    • 20When it triggers. No condition that starts the skill
    • 30Inputs and preconditions. Does not say what the process needs to start
    • 30Running it twice. 1 mutating operations with no state check
    • 50Failures and branches. 0 branches, has a failure section
    • 60Result and completion. Output format stated, no completion criterion
    • 85Steps. 21 steps, 1 vague phrases
    • 100Tools and files. No external tools needed
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 743 tokens

    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

    • +4Description does not say when NOT to use the skill (false activations)
    • +1No license
    • +2Single-language instructions
    • +5Description quotes 4 example trigger phrases
    • +3Description length 369: enough signal without eating the budget
    • +4Structure: 3 headings
    • +3Step-by-step instructions: 21 items
    • +3Output format is stated explicitly
    • +4Has examples (1 code blocks)

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