SKILLEMALL.ai

CD pro-launch

Build an app or product from 0 to 1, taste-first, with phase gates: references, naming, style frames, UI loop, launch video, GTM and shipping. Use for 做产品, 起名, 找参考, UI 太丑, launch plans.

sickn33/agentic-awesome-skills Hermes author: sickn33 20 files body ≈ 1 663 tokens Open the sourcegithub.com↗ analyzed 27 h ago

Build an app or product from 0 to 1, taste-first, with phase gates: references, naming, style frames, UI loop, launch video, GTM and shipping.

As a process D 42/100 · Unfinished process — References files that are not bundled: scripts/domain_check.py, scripts/cutout_vector.sh, scripts/cut.swift

GeneratorGitHubPersonal productivitytype and topics are labelled automatically from the skill text
JSON
Technical rating
C
87/100
safety, quality, tests
Safety 60%
100
Quality 40%
68
Run on models
none yet
Process rating
D
42/100
Unfinished process
References files that are not bundled: scripts/domain_check.py, scripts/cutout_vector.sh, scripts/cut.swift
Tools and files w 18
0
Result and completion w 14
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: pro-launch (sickn33/agentic-awesome-skills)

How to improve

  1. For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
  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: 20. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-long-hermes description is 185 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period)
  • warning missing-ref reference to a missing file: scripts/domain_check.py
  • warning missing-ref reference to a missing file: scripts/cutout_vector.sh
  • warning missing-ref reference to a missing file: scripts/cut.swift
  • warning missing-ref reference to a missing file: scripts/vectorize.js
  • note frontmatter-key unknown frontmatter key "risk"
  • note frontmatter-key unknown frontmatter key "source"
  • note frontmatter-key unknown frontmatter key "source_repo"
  • note frontmatter-key unknown frontmatter key "source_type"
  • note frontmatter-key unknown frontmatter key "date_added"
  • note frontmatter-key unknown frontmatter key "tools"
  • note frontmatter-key unknown frontmatter key "license_source"

Process rating: all ten parameters 42/100

Will not run. References files that are not bundled: scripts/domain_check.py, scripts/cutout_vector.sh, scripts/cut.swift
  • 0Tools and files. 4 referenced file(s) missing: scripts/domain_check.py, scripts/cutout_vector.sh, scripts/cut.swift
  • 0Result and completion. Does not say what the result is
  • 0Failures and branches. Linear process with no failure handling
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 2 mutating operations with no state check
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Steps. 36 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1663 tokens
  • 100Progress reporting. Reports progress
  • low 12 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)
  • +3Output format is not stated: the model decides each time
  • +2Single-language instructions
  • +3Description length 185: enough signal without eating the budget
  • +4Structure: 13 headings
  • +3Step-by-step instructions: 36 items
  • +4Has examples (0 code blocks)
  • +4Reference files are cited in the instructions (17 of 17)
  • +1License stated

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