CD geniex
Use the geniex CLI — pull, list, infer, serve, benchmark models on Snapdragon CPU/GPU/NPU — and debug what actually ran. Use when running geniex commands, reproducing a user report, or verifying a change end to end.
Wraps geniex CLI to pull, list, infer, serve, and benchmark models on Snapdragon hardware—CPU, GPU, NPU—plus debug what actually ran. Single file, broken references, no model runs on record. Quality score sits at 68, which points to gaps in instructions or examples—likely incomplete commands or missing setup steps. Safety clears, but process score of 42 means the logic limps along.
Install if you already know geniex and just need IDE access. Otherwise, verify the docs are current and commands work on your device first. On unfamiliar ground, this skill will create more friction than it saves.
Use the geniex CLI — pull, list, infer, serve, benchmark models on Snapdragon CPU/GPU/NPU — and debug what actually ran.
As a process D 42/100 · Unfinished process — References files that are not bundled: ../../../docs/en/run/cli/reference.mdx, ../../../notes/run.md, ../../../docs/en/tutorials/benchmarking.mdx
How to improve
- The text references files that are not there: add them or drop the references.
- 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
- warning
missing-refreference to a missing file: ../../../docs/en/run/cli/reference.mdx - warning
missing-refreference to a missing file: ../../../notes/run.md - warning
missing-refreference to a missing file: ../../../docs/en/tutorials/benchmarking.mdx - warning
missing-refreference to a missing file: ../../../notes/bench.md
Process rating: all ten parameters 42/100
- 0Tools and files. 4 referenced file(s) missing: ../../../docs/en/run/cli/reference.mdx, ../../../notes/run.md, ../../../docs/en/tutorials/benchmarking.mdx
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 100Steps. 8 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 601 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
- low The response is described with custom markup (4 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
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 215: enough signal without eating the budget
- +4Structure: 6 headings
- +3Step-by-step instructions: 8 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 68.