Kinic Wiki

Console

Skip to main content
Skills

Health inspection

Lint

Use lint workflows to find wiki structure issues, missing source evidence, stale paths, malformed skill packages, or inconsistent store layout.

SKILL.md

Read the skill as documentation or switch to the exact source.

Frontmatter

name
kinic-wiki-lint
description
Kinic Wiki workflow skill for inspecting local and remote wiki health without silently fixing it.

Kinic Wiki Lint

Use this skill when the user wants to:

  • inspect wiki health
  • look for isolated or duplicated pages
  • check whether /Knowledge/index.md is stale
  • review missing links, weak structure, or outdated organization
  • inspect database discovery metadata for public retrieval
  • decide what to fix next without auto-applying changes

Do not use this skill for:

  • primary source ingestion
  • ordinary question answering
  • hidden repair runs
  • OKF bundle structure verification; use kinic-context-pack and context-pack verify
  • skill store package lifecycle work; use kinic-skill-registry

Core rules:

  • Treat the canister wiki as the source of truth.
  • Organized wiki nodes live under /Knowledge/...; evidence sources live under /Sources/<provider>/<id>.md.
  • Treat local Markdown as review or drafting aid unless a workflow explicitly writes it back through VFS commands.
  • Default to report-only behavior.
  • Do not silently fix pages.
  • Prefer concrete findings over vague style commentary.
  • Keep local lint and remote inspection conceptually separate.
  • Check note-role boundary violations as well as missing pages.
  • Treat exact-value drift in facts.md as a real canonicality problem, not a style nit.
  • Use the embedded note-role rules in lint.md as the trust model. When this skill runs inside the repo and docs/STORE_API.md is available, use that file only as the current repo-local refinement.

Read lint.md before doing substantive Kinic Wiki lint work.

For bounded repeated inspection, repair, and reinspection, use kinic-wiki-maintain. index.md is an agent catalog; optional overview.md is the reader description.

Kinic Wiki Lint Workflow

Goal

Inspect local or remote wiki health without silently fixing it. Report concrete findings with paths, evidence, severity, and suggested next actions.

CLI Reference

  • Use kinic-vfs-cli for remote VFS inspection.
  • Run kinic-vfs-cli --help for the command list.
  • Run kinic-vfs-cli <command> --help before using an unfamiliar inspection command.
  • Use docs/CLI.md as the full CLI usage reference when working inside this repo.

Workflow

  1. Confirm target database and access with status --json when inspecting remote state.
  2. Keep local Markdown checks separate from remote canister checks.
  3. Use list-nodes for structure, prefix, and etag inventory.
  4. Use read-node-context only when catalog, navigation, or link-aware context matters.
  5. Use search-remote, search-path-remote, and link commands to confirm or expand findings.
  6. Prefer query-context --namespace /Knowledge --json for task-scoped remote context.
  7. Use query-sql for 2 or more known-path content reads during canonicality checks.
  8. Use read-node --json for one final offending-line confirmation.
  9. Use snapshot/export commands only when a whole scope must be inspected or a trusted snapshot revision is already available. Check the command help before use.

Findings

  • Report exact paths and the command category used to verify the issue.
  • Treat exact-value drift in facts.md as a real canonicality issue.
  • Flag exact evidence leaking into summaries as a canonicality finding, not a style note.
  • Prefer concrete missing-link, stale-index, duplicate-page, isolated-page, and note-role boundary findings.
  • Do not produce vague style commentary without a path-specific impact.

Safety

  • Do not mutate remote wiki nodes in this skill.
  • Do not use delete-node, delete-tree, write, append, edit, rebuild, or proposal/status mutation commands.
  • If a repair is needed, hand off to kinic-wiki-edit or kinic-wiki-ingest.
  • For OKF bundle validation, use kinic-context-pack.

Catalog health and coverage

Read-only lint is also the inspection phase of kinic-wiki-maintain. Only that separately authorized repair run may hand off to edit; lint never writes or rebuilds.

Compare actual Knowledge inventory with agent catalogs (index.md) and reader descriptions (overview.md). Report empty root templates despite existing knowledge, broken catalog links, missing navigation to important articles/child scopes, misleading summaries, duplicate/isolated notes, and note-role violations. Omission from a curated catalog is not by itself a defect. Scoped catalogs are useful where navigation warrants them; do not require boilerplate indexes in empty folders. A legacy index mixing prose and navigation may need a preserved merge into overview, not deletion.

Report each finding with stable ID, paths, impact, inspected evidence, and a focused repair. Never describe a stale catalog as proof that articles are absent. Prefer a focused index edit; broad rebuilds can destroy curation.

For complete-coverage claims, reconcile bounded listing results against actual inventory. Results at the limit require subtree decomposition or ordered SQL batches with exact prefix boundaries; otherwise report partial coverage and uninspected ranges. Listing completeness does not prove article-body checks are complete. Incomplete inspection, permission errors, and unresolved ambiguity must remain visible in the result. Check modified content and affected inventory again before closing a repair finding.

When inspecting a narrower Wiki scope, pass its prefix as --namespace (or API namespace). The public API defaults to /Memory; never interpret that default as a complete Knowledge inspection.