BD publish-website
Publish sites with no signup, and deploy backend APIs with a free account. Use when asked to "publish this", "host this", "put this online", "share this as a webpage", "make a website", "give me a link", "get a public URL", "deploy this folder", "password protect this site", or "publish to chorus.host". Also use for backend work that static hosts can't do: "deploy an API", "add a backend to my site", "receive form submissions", "proxy an API with a secret key", "webhook endpoint", or "deploy this Hono / Workers app". Sites live at {slug}.chorus.host; workers run on Cloudflare at {slug}.worker.chorus.host. Anonymous sites last 24 hours and can be claimed with a free account.
Publish sites with no signup, and deploy backend APIs with a free account.
As a process D 43/100 · Unfinished process — References files that are not bundled: assets/app.js
How to improve
- The text references files that are not there: add them or drop the references.
- 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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: assets/app.js
Process rating: all ten parameters 43/100
- 0Tools and files. 1 referenced file(s) missing: assets/app.js
- 0Result and completion. Does not say what the result is
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 35 mutating operations with no state check
- 40Consistency. Frontmatter name (publish-website) differs from the folder (chorus-host)
- 50Failures and branches. 0 branches, has a failure section
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 13 steps
- 100Execution cost. Instruction body is 2566 tokens
- 100Progress reporting. Reports progress
- low 16 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (21 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
- +1No license
- +2Single-language instructions
- +5Description quotes 16 example trigger phrases
- +3Description length 682: enough signal without eating the budget
- +4Structure: 17 headings
- +3Step-by-step instructions: 13 items
- +4Has examples (9 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 83.