SKILLEMALL.ai
GitHub ↗ RU Sign in

AB kosmi-dj

This skill should be used when the user asks to "play a video in Kosmi", "queue a video", "DJ in Kosmi", "start the video DJ", "loop videos in Kosmi", "connect to Kosmi room", "play YouTube in Kosmi", "stop the DJ loop", "add a video to the queue", "be my video DJ", or needs guidance on controlling a Kosmi watch party room via agent-browser automation.

modbender/skill-library-mcp Agent Skills author: modbender MIT 7 files · 4 scripts body ≈ 1 471 tokens Open the sourcegithub.com↗ analyzed 2 d ago

This skill should be used when the user asks to "play a video in Kosmi", "queue a video", "DJ in Kosmi", "start the video DJ", "loop videos in Kosmi"…

As a process B 65/100 · Nearly there — weak spots: result and completion, progress reporting

ProcedureYouTubeMedia and videotype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
A
97/100
safety, quality, tests
Safety 60%
100
Quality 40%
92
Run on models
none yet
Process rating
B
65/100
Nearly there
Result and completion w 14
0
Progress reporting w 2
0
Failures and branches w 10
50
the three weakest of ten parameters · all ten

How to improve

    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: 7. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 65/100

    • 0Result and completion. Does not say what the result is
    • 0Progress reporting. Says nothing while it works
    • 50Failures and branches. 0 branches, has a failure section
    • 60Tools and files. Uses tools (bash, web, node) that frontmatter does not declare
    • 70When it triggers. States when to use, but not when not to
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Steps. 36 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1471 tokens
    • 100Running it twice. Mutating operations check current state
    • high The skill tells the model to perform an irreversible action with no human approval
    • low The response is described with custom markup (6 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
    • +4No input/output examples
    • +1No license
    • +2Single-language instructions
    • +5Description quotes 10 example trigger phrases
    • +3Description length 354: enough signal without eating the budget
    • +4Structure: 15 headings
    • +3Step-by-step instructions: 36 items
    • +4Reference files are cited in the instructions (2 of 2)
    • +3All 4 scripts are documented

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