SKILLEMALL.ai
GitHub ↗ RU Sign in

CC wiki-query

Fast, read-only, index-first llm-wiki queries for OpenCode and compatible instruction-file harnesses.

The skillemall take

Promises fast read-only LLM-wiki queries with index-first priority. One instruction file, 658 tokens, no scripts, no critical errors. Quality score 65/100, process score 61. Never ran on models or in sandbox.

Supports Claude, Cursor, DeepSeek, Mistral and eight more platforms. No findings, no lint errors, safety at 100. Safe to install if you need wiki reads without writes and index ordering fits your workflow. Without model testing, unclear whether the speed claim holds or what index priority actually delivers in practice.

nvk/llm-wiki Agent Skills author: nvk 1 file body ≈ 658 tokens Open the sourcegithub.com↗ analyzed 4 d ago

Fast, read-only, index-first llm-wiki queries for OpenCode and compatible instruction-file harnesses.

As a process C 61/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

ProcedureAI 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
C
86/100
safety, quality, tests
Safety 60%
100
Quality 40%
65
Run on models
none yet
Process rating
C
61/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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 description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 61/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 2 mutating operations with no state check
  • 100Tools and files. No external tools needed
  • 100Steps. 21 steps
  • 100Failures and branches. 2 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 658 tokens
  • 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)
  • +3Description length 101: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions
  • +4Structure: 5 headings
  • +3Step-by-step instructions: 21 items

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