SKILLEMALL.ai
GitHub ↗ RU Sign in

AB coco-cli

Install, update, version-check, or uninstall the Coco open-core AI workflow framework via bin/coco.js. Use when setting up Coco on a machine, checking out the pinned release tag into an existing clone, checking the installed version, or removing it. npx cocosuperintelligence is the published path (clones the pin and installs). Triggers on "install coco", "update coco", "set up coco", "coco cli", "uninstall coco".

coco-research/coco Agent Skills author: coco-research 1 file body ≈ 695 tokens Open the sourcegithub.com↗ analyzed 6 h ago

Install, update, version-check, or uninstall the Coco open-core AI workflow framework via bin/coco.js. Use when setting up Coco on a machine, checking out the…

As a process B 71/100 · Nearly there — weak spots: running it twice, progress reporting

ProcedureGitHubSoftware developmentAI and agentstype and topics are labelled automatically from the skill text
Runs in: 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) OpenClaw Goose OpenCode
JSON
Technical rating
A
96/100
safety, quality, tests
Safety 60%
100
Quality 40%
91
Run on models
none yet
Process rating
B
71/100
Nearly there
Progress reporting w 2
0
Running it twice w 4
30
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: 1. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • note frontmatter-key unknown frontmatter key "domain"

    Process rating: all ten parameters 71/100

    • 0Progress reporting. Says nothing while it works
    • 30Running it twice. 5 mutating operations with no state check
    • 50Failures and branches. 0 branches, has a failure section
    • 60Tools and files. Uses tools (bash, web, node) that frontmatter does not declare
    • 60Result and completion. Output format stated, no completion criterion
    • 70When it triggers. States when to use, but not when not to
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Steps. 16 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 695 tokens

    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)
    • +1No license
    • +2Single-language instructions
    • +5Description quotes 5 example trigger phrases
    • +3Description length 416: enough signal without eating the budget
    • +4Structure: 7 headings
    • +3Step-by-step instructions: 16 items
    • +3Output format is stated explicitly
    • +4Has examples (0 code blocks)

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