SKILLEMALL.ai

AF myvibe-publish

Publish static HTML, ZIP archive, or directory to MyVibe. Use this skill when user wants to publish web content to MyVibe.

modbender/skill-library-mcp Agent Skills author: modbender MIT 13 files body ≈ 2 316 tokens Open the sourcegithub.com analyzed 2 d ago

Publish static HTML, ZIP archive, or directory to MyVibe.

As a process F 48/100 · Will not run — References files that are not bundled: scripts/node_modules

ProcedureAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
A
92/100
safety, quality, tests
Safety 60%
99
Quality 40%
81
Run on models
none yet
Process rating
F
48/100
Will not run
References files that are not bundled: scripts/node_modules
Tools and files w 18
0
Result and completion w 14
0
Consistency w 8
40
the three weakest of ten parameters · all ten

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 · 1

✓ No critical or high findings

Medium and low: 1
  • low Secrets in code secret-high-entropy-token scripts/utils/upload-image.mjs:13
    High-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: 13. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: scripts/node_modules

Process rating: all ten parameters 48/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
  • 60Steps. 32 steps, 5 vague phrases
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Failures and branches. 2 branches, has a failure section
  • 100Execution cost. Instruction body is 2316 tokens
  • 100Running it twice. Mutating operations check current state
  • 100Progress reporting. Reports progress
  • 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.