SKILLEMALL.ai
GitHub ↗ RU Sign in

AB onyx-cli

Query the Onyx knowledge base using the onyx-cli command. Use when the user wants to search company documents, ask questions about internal knowledge, query connected data sources, or look up information stored in Onyx.

onyx-dot-app/onyx Agent Skills author: onyx-dot-app NOASSERTION 2 files body ≈ 2 584 tokens Open the sourcegithub.com↗ analyzed 6 d ago

Query the Onyx knowledge base using the onyx-cli command.

As a process B 77/100 · Nearly there — weak spots: consistency

IntegrationSlackAI and agentsSoftware developmenttype 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
77/100
Nearly there
Consistency w 8
40
Tools and files w 18
60
Result and completion w 14
60
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: 2. 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 77/100

    • 40Consistency. Frontmatter name (onyx-cli) differs from the folder (embedded)
    • 60Tools and files. Uses tools (bash, python) that frontmatter does not declare
    • 60Result and completion. Output format stated, no completion criterion
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 85Steps. 16 steps, 2 vague phrases
    • 100When it triggers. States when to use and when not to
    • 100Failures and branches. 1 branches, has a failure section
    • 100Execution cost. Instruction body is 2584 tokens
    • 100Running it twice. Mutating operations check current state
    • 100Progress reporting. Reports progress

    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
    • +1No license
    • +2Single-language instructions
    • +4Description says when NOT to use the skill
    • +3Description length 219: enough signal without eating the budget
    • +4Structure: 16 headings
    • +3Step-by-step instructions: 16 items
    • +3Output format is stated explicitly
    • +4Has examples (11 code blocks)

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