SKILLEMALL.ai

DC wiki-manager

Manage LLM-compiled wikis in OpenCode: ingest/import, shape/promote Ideas, review portfolios, track inventory/datasets, archive, compile/query/lint/audit, research/plan, manage sessions, private adapters, personal specialists, and outputs. Activates when the user mentions wiki workflows, knowledge-base management, ingestion, collection ingestion, import wiki, collect, catalog, curate, find all, idea, turn idea into project, portfolio, business ideas, projects, inventory, source queue, candidate list, watch list, backlog, dataset, large data, data registry, dataset manifest, compilation, querying, linting, audit, research, librarian, scan quality, article quality, content review, output drift, provenance, archive wiki, archive topic, restore wiki, private adapter, adapter registry, skill-factory, checkpoints, personal specialist, specialist skill, specialist reviewer, expert lens, adapter route, adapter doctor, adapter run, read, review, or edit a hosted external resource such as a document, session capture, capture context, rehydrate, resume from session, lessons learned, implementation plan, or uses wiki-related shorthand in a repo with .wiki/, ~/wiki/, or a configured hub path.

The skillemall take

Promises wiki management in OpenCode: import, cataloging, idea search, compilation, audit. Reality: 24 files with broken references scattered throughout. Content quality rated 37/100, process 63/100. No critical errors flagged, but the description is so bloated it's unclear what actually works versus what's wishlist. Never run on models. Install if you need a skeleton for your own wiki system and don't mind fixing broken links and rewriting half the logic yourself.

nvk/llm-wiki Agent Skills author: nvk 24 files body ≈ 7 128 tokens Open the sourcegithub.com↗ analyzed 4 d ago

Manage LLM-compiled wikis in OpenCode: ingest/import, shape/promote Ideas, review portfolios, track inventory/datasets, archive, compile/query/lint/audit…

As a process C 63/100 · Has gaps — References files that are not bundled: path, ../category/slug.md, url

ProcedureSoftware developmentData and analyticstype and topics are labelled automatically from the skill text
JSON
Technical rating
D
75/100
safety, quality, tests
Safety 60%
100
Quality 40%
37
Run on models
none yet
Process rating
C
63/100
Has gaps
References files that are not bundled: path, ../category/slug.md, url
Tools and files w 18
0
Inputs and preconditions w 11
0
When it triggers w 12
70
the three weakest of ten parameters · all ten

How to improve

  1. Shorten the description to 1024 characters.
  2. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
  3. 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: 24. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • error description-long description is 1199 chars, limit 1024
  • warning body-long SKILL.md body ≈ 7128 tokens (recommended < 5000); move details to references/
  • warning missing-ref reference to a missing file: path
  • warning missing-ref reference to a missing file: ../category/slug.md
  • warning missing-ref reference to a missing file: url
  • note edit-residue the text marks something as outdated (lines 16, 170, 202, 228, 347): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 63/100

Will not run. References files that are not bundled: path, ../category/slug.md, url
  • 0Tools and files. 3 referenced file(s) missing: path, ../category/slug.md, url
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 70When it triggers. States when to use, but not when not to
  • 70Execution cost. Instruction body is 7128 tokens
  • 85Steps. 62 steps, 1 vague phrases
  • 100Result and completion. Output format and completion criterion are stated
  • 100Failures and branches. 3 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Running it twice. Mutating operations check current state
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 14 top-level sections: this looks like several domains in one skill
  • low The response is described with custom markup (20 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 1198: 120–800 characters recommended
  • -4Absolute local paths (C:\Users, /home/…): not portable
  • +1No license
  • +2Single-language instructions
  • +4Structure: 42 headings
  • +3Step-by-step instructions: 62 items
  • +3Output format is stated explicitly
  • +4Has examples (2 code blocks)
  • +4Reference files are cited in the instructions (20 of 23)

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