CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

llm-wiki

Karpathy's LLM Wiki: build/query interlinked markdown KB.

51

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/research/llm-wiki/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body delivers strong, sequenced operational guidance with genuine validation checkpoints for batch and destructive paths, held back by its monolithic structure and a pseudocode lint implementation. Splitting the SCHEMA template and Obsidian headless setup into reference files would simultaneously improve conciseness and progressive disclosure.

Suggestions

Move the full SCHEMA.md template and the Obsidian headless/systemd setup into reference files (e.g. references/schema-template.md, references/obsidian-headless.md) with one-line pointers from SKILL.md — the main file drops well over 100 lines and gains real progressive disclosure.

Replace the pseudocode orphan-scan block with an executable Python snippet (walk the layer-2 directories, regex-extract [[wikilinks]], build an inbound-link defaultdict) so the lint workflow is fully runnable.

Deduplicate guidance repeated across sections — the sha256 re-ingest rule and page thresholds each appear in both the template and the operations/pitfalls text — by stating each once and cross-referencing.

DimensionReasoningScore

Conciseness

The body is dense and mostly earns its tokens, but the ~100-line inline SCHEMA.md template, the ~55-line Obsidian-headless/systemd section, and guidance stated twice (sha256 re-ingest logic, page thresholds restated in Pitfalls) fit "mostly efficient but includes some unnecessary explanation or could be tightened". Not 4 because the redundancy is more than minor trimming; not 2 because there is no padding explaining concepts Claude already knows.

3 / 5

Actionability

Concrete bash snippets, copy-paste-ready SCHEMA/index/log templates, and numbered step checklists give mostly executable guidance; gaps are the explicitly pseudocode lint orphan scan ("# Scan all .md files ... build inbound link map") and unresolved placeholders like "<WIKI_PATH>" and "<vault-id>". Not 5 because the lint snippet is not runnable as written and no worked end-to-end example is given.

4 / 5

Workflow Clarity

Ingest (①–⑥), query, and lint (①–⑬) are clearly sequenced, with real validation checkpoints: lint is itself a health pass, re-ingest compares sha256 with skip/flag outcomes, and "Ask before mass-updating" validates the destructive batch path, so the batch-operation cap does not apply. Not 5 because several checkpoints are advisory reporting steps rather than validate-fix-retry loops.

4 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, or assets/), so content that clearly belongs in separate files — the SCHEMA.md template and the Obsidian headless/systemd setup — is inlined in one ~490-line file. Internal sectioning is good, keeping it above the minimal-structure anchor at 2, but it matches anchor 3: content that should be separate is inline and there is no reference navigation at all.

3 / 5

Total

14

/

20

Passed

Description

53%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is appropriately terse and distinct, but it compresses a multi-operation skill into two verbs and omits any explicit trigger guidance. Adding a "Use when..." clause naming the natural activation phrases (wiki, knowledge base, ingest a source) would lift completeness and trigger quality substantially.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user asks to build or update a wiki / knowledge base, ingest sources into it, query existing notes, or lint the wiki" — this resolves the missing-when cap on completeness.

Spell out "knowledge base" instead of the "KB" abbreviation and add common user phrasings ("knowledge base", "notes", "ingest") so trigger matching works on the words users actually say.

Mention the full operation set (build, ingest, query, lint/maintain) rather than only "build/query" to raise specificity toward the skill's actual coverage.

DimensionReasoningScore

Specificity

"build/query interlinked markdown KB" names the domain plus exactly two terse actions; the ingest, lint, and maintain operations covered in the body are absent, matching the "1-2 concrete actions, not comprehensive" anchor. Not 4 because the action list is far from covering what the skill actually does.

3 / 5

Completeness

The description has a clear "what" but no "Use when..." clause or equivalent trigger guidance; the judging guidelines explicitly cap completeness at 3 in that case. It is not 2 because the "what" is concrete and unambiguous, and not 4 because no when-guidance is even weakly present.

3 / 5

Trigger Term Quality

"wiki" and "markdown" are natural user terms, but "KB" is an abbreviation and common variations ("knowledge base", "notes", "ingest") are missing, fitting "some relevant keywords but missing common variations or synonyms". Not 4 since several natural phrasings users would actually say are absent.

3 / 5

Distinctiveness Conflict Risk

"Karpathy's LLM Wiki" plus "interlinked markdown KB" carves a mostly distinct niche with only minor overlap risk against note-taking/Obsidian-adjacent skills. Not 5 because the description itself does not differentiate from generic wiki/notes skills.

4 / 5

Total

13

/

20

Passed

Validation

75%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (508 lines); consider splitting into references/ and linking

Warning

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

12

/

16

Passed

Repository

NousResearch/hermes-agent

Path

skills/research/llm-wiki/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.