SKILLEMALL.ai

BD saas-landing

Single-page SaaS landing with hero, features, social proof, pricing, and CTA. Respects the active DESIGN.md color/typography/layout tokens. Trigger keywords: "saas landing", "marketing page", "product landing".

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

Single-page SaaS landing with hero, features, social proof, pricing, and CTA.

As a process D 38/100 · Unfinished process — References files that are not bundled: ../../docs/skills-protocol.md

GeneratorDesigntype and topics are labelled automatically from the skill text
JSON
Technical rating
B
90/100
safety, quality, tests
Safety 60%
100
Quality 40%
76
Run on models
none yet
Process rating
D
38/100
Unfinished process
References files that are not bundled: ../../docs/skills-protocol.md
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

The same skill appears in 1 more place: open-design

How to improve

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

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: ../../docs/skills-protocol.md
  • note frontmatter-key unknown frontmatter key "triggers"
  • note frontmatter-key unknown frontmatter key "od"

Process rating: all ten parameters 38/100

Will not run. References files that are not bundled: ../../docs/skills-protocol.md
  • 0Tools and files. 1 referenced file(s) missing: ../../docs/skills-protocol.md
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 50Failures and branches. 0 branches, has a failure section
  • 85Steps. 28 steps, 1 vague phrases
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 849 tokens
  • 100Running it twice. No mutating operations
  • low The response is described with custom markup (7 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

  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • -5TODO / placeholder text left in the skill
  • +1No license
  • +2Single-language instructions
  • +5Description quotes 3 example trigger phrases
  • +3Description length 210: enough signal without eating the budget
  • +4Structure: 8 headings
  • +3Step-by-step instructions: 28 items
  • +4Has examples (1 code blocks)

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