SKILLEMALL.ai
GitHub ↗ RU Sign in

CD build

Build the GenieX SDK, CLI, Python bindings, or release packages, and run Go test coverage. Use when the user asks to build, rebuild, package, or measure coverage.

The skillemall take

Promises to build GenieX SDK, CLI, Python bindings, and release packages, plus measure Go test coverage. Single file with no scripts—just command descriptions. Quality score 70, process 49. No critical findings, but broken_references_missing_files flag is on: the instructions reference files that don't exist or are invalid. Never run on models, not tested in sandbox. Supports many platforms, but will work only if your environment already has all the tools and paths match what's written. Install if you know the project structure and can fix paths manually.

NexaAI/nexa-sdk Claude Code author: NexaAI 1 file body ≈ 266 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Build the GenieX SDK, CLI, Python bindings, or release packages, and run Go test coverage.

As a process D 49/100 · Unfinished process — References files that are not bundled: ../../../notes/build.md

IntegrationSoftware 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
C
88/100
safety, quality, tests
Safety 60%
100
Quality 40%
70
Run on models
none yet
Process rating
D
49/100
Unfinished process
References files that are not bundled: ../../../notes/build.md
Tools and files w 18
0
Result and completion w 14
0
Failures and branches w 10
0
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 · 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-ref reference to a missing file: ../../../notes/build.md

Process rating: all ten parameters 49/100

Will not run. References files that are not bundled: ../../../notes/build.md
  • 0Tools and files. 1 referenced file(s) missing: ../../../notes/build.md
  • 0Result and completion. Does not say what the result is
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 70When it triggers. States when to use, but not when not to
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Steps. 6 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 266 tokens
  • 100Running it twice. No mutating operations

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)
  • +4Structure: 1 headings, hard to scan
  • +3Output format is not stated: the model decides each time
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions
  • +3Description length 162: enough signal without eating the budget
  • +3Step-by-step instructions: 6 items

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