BB deed-page
Publish an HTML file or static folder to a permanent public https://<slug>.deed.page/ URL with one curl request. No account; the first publish returns a token for updates.
Promises to publish static files to a permanent https URL with a single curl command, no signup required. Sounds convenient for quick demos.
Security checks flagged a high-severity exfiltration risk. Safety score of 81 isn't a failure, but it's a serious warning. Quality and process scores (80 and 67) indicate the instructions are documented but execution has gaps. No model run or sandbox test — actual behavior is untested.
Don't install it. A data exfiltration risk during static publishing isn't something to ignore, even if the skill technically functions.
Publish an HTML file or static folder to a permanent public https://<slug>.deed.page/ URL with one curl request. No account; the first publish returns a token…
As a process B 67/100 · Nearly there — weak spots: result and completion, inputs and preconditions, running it twice
The same skill appears in 2 more places: agentic-awesome-skills, agentic-awesome-skills
How to improve
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- 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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Exfiltration
net-credential-useSKILL.md:111Credential used in a network call (verify the destination is the intended service) (the skill's own vendor host)curl -sS -X DELETE "https://deed.page/v1/sites/$SLUG" -H "Authorization: Bearer $DEEDPAGE_TOKEN"
vendor-host
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 171 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - note
frontmatter-keyunknown frontmatter key "risk" - note
frontmatter-keyunknown frontmatter key "source" - note
frontmatter-keyunknown frontmatter key "source_repo" - note
frontmatter-keyunknown frontmatter key "source_type" - note
frontmatter-keyunknown frontmatter key "date_added" - note
frontmatter-keyunknown frontmatter key "license_source" - note
frontmatter-keyunknown frontmatter key "tools"
Process rating: all ten parameters 67/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 34 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 29 steps
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1716 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- high The skill tells the model to perform an irreversible action with no human approval
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
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 171: enough signal without eating the budget
- +4Structure: 17 headings
- +3Step-by-step instructions: 29 items
- +4Has examples (8 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 80.