DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to find notes filed in the wrong folder and check wiki health with LLM Wiki V2

Use the audit and health commands to review where CROW would move notes and which folders keep growing.

  • Research
  • Intermediate
  • 60 minutes
  • From the README
  • Any agent

Who it is forA wiki maintainer running CROW mode who wants to review the folder layout before changing it.

The problemAs notes pile up, some end up in folders the classifier would not choose, and folders may need splitting.

The outcomeA list of notes the classifier would move and a summary of folders that need attention.

What you need first

  • Python 3.11 or later, or uv to install it
  • An API key for OpenRouter, OpenAI, Gemini or another OpenAI-compatible server, or Ollama installed for free local use
  • Documents as text, Markdown, PDF, Word, PowerPoint, Excel or OpenDocument files

Steps

  1. Confirm the wiki runs in CROW mode with a classifier configured in Settings.
  2. Run llmwiki2 audit to list notes the classifier would file in another branch.
  3. Run llmwiki2 health to see folders that keep needing new subfolders or the LLM fallback.
  4. Review the audit list, then run llmwiki2 audit --apply only for moves you accept. (inferred, check the README)

Prompt for your agent

In the llm-wiki-v2 wiki at <wiki path>, run llmwiki2 audit and llmwiki2 health and summarize the proposed moves and flagged folders. Expected output: a table of notes with proposed folders and a list of folders to review. Verify that no note moves until a human runs the apply step.

Caveat. The audit confidence threshold is compared with a probability scale the README says has not been recalibrated, so treat --min-confidence values with care.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page