AF myvibe-publish
Publish static HTML, ZIP archive, or directory to MyVibe. Use this skill when user wants to publish web content to MyVibe.
As a process F 52/100 · Will not run — References files that are not bundled: scripts/node_modules
How to improve
- 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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Secrets in code
secret-high-entropy-tokenscripts/utils/upload-image.mjs:13High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)const MEDIA_KIT_DID = "z8ia…Gp9";
quoted
Files scanned: 14. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: scripts/node_modules
Process rating: all ten parameters 52/100
Will not run. References files that are not bundled: scripts/node_modules
- 0Tools and files. 1 referenced file(s) missing: scripts/node_modules
- 0Result and completion. Does not say what the result is
- 40Consistency. Frontmatter name (myvibe-publish) differs from the folder (myvibe-skills)
- 50When it triggers. No condition that starts the skill
- 70Inputs and preconditions. Inputs and preconditions are listed
- 85Steps. 32 steps, 3 vague phrases
- 100Failures and branches. 4 branches, has a failure section
- 100Execution cost. Instruction body is 2255 tokens
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 12 top-level sections: this looks like several domains in one skill
- 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
- +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
- +1No license
- +2Single-language instructions
- +3Description length 122: enough signal without eating the budget
- +4Structure: 20 headings
- +3Step-by-step instructions: 32 items
- +4Has examples (7 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 81.
External checks
ClawHub: suspicious
This appears to be a real MyVibe publishing skill, but it needs review because it installs unpinned tools, stores authorization state, uploads local content and screenshots, and can delete a user-supplied config file.
LLM: suspicious (high) · VirusTotal: suspicious · 28 May 2026