Build a formal security architecture threat model for an LLM-Wiki system. Use when the user asks for STRIDE, LINDDUN, PASTA, data-flow diagrams, trust boundaries, attack-surface mapping, abuse cases, risk matrices, red-team scenarios, or control baselines; route existing-config safety reviews to…
Audit an LLM-Wiki system for anti-slop controls such as provenance, review gates, protected human synthesis, stale claims, and unsafe agent write permissions. Use when the user asks whether their wiki can be trusted; route setup/permission safety reviews to llm-wiki-security-review and proposal risk audits to…
Create a first useful LLM-Wiki from zero. Use when the user wants a zero-to-working-wiki walkthrough, first vault, first source ingest, first reusable query, first lint report, or a visible demo loop before a larger rollout; route full workflow installs to llm-wiki-setup.
Convert trusted raw sources into reviewable LLM-Wiki pages. Use when adding PDFs, articles, transcripts, notes, repository docs, web captures, or other source material into a raw/wiki/schema vault while preserving provenance, ambiguity, links, index updates, and log entries.
Run structural and trust health checks for an LLM-Wiki vault. Use for broken links, orphan pages, missing provenance, stale claims, contradiction reports, taxonomy drift, protected-section edits, and review queue generation.
Answer questions from an existing LLM-Wiki vault and save reusable answers back into the wiki. Use when the user asks for research, synthesis, comparison, decision support, or recall from a raw/wiki/schema knowledge base.
Sort messy captured material before full LLM-Wiki ingestion. Use for inbox folders, web clips, chat exports, voice transcripts, forwarded notes, duplicate source candidates, sensitive material review, and keep/defer/drop triage reports.
3 9d agoA51 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: