Files
chemenu/instructions/wiki-status/SKILL.md
T
torben 18ae28f918
CI / verify (push) Failing after 32s
Release / release (push) Successful in 38s
Chemenu 2.1.0 - deterministischer Wissenskompiler
Chemenu kompiliert Rohnotizen zu einem verlinkten, quellengebundenen Wiki:
raw/ -> types/ + tools/ -> kb/ -> reports/. Was mechanisch ist, macht
tools/wikitool; was Urteil braucht, macht ein Agent unter Contracts, deren
Grenzen in Code durchgesetzt sind statt im Prompt.

Dieser Commit ist der Startpunkt der oeffentlichen Historie. Die vorherige
Entwicklung fand in einer privaten Instanz statt und ist nicht Teil dieses
Repositorys; ihre Erzaehlung steht vollstaendig in CHANGES.md, das mit 44
Eintraegen von 0.1.0 bis 2.1.0 erhalten geblieben ist.

Der mitgelieferte Korpus ist ein Testbett und eine Demo: 170 Seiten ueber den
Stack selbst - Gates, Lint, Versionierung, Suche, das Wiki-Muster. Er
dokumentiert das Werkzeug mit den eigenen Mitteln des Werkzeugs.

Lizenz: AGPL-3.0 fuer den Stack (tools/, types/), CC-BY-4.0 fuer die Inhalte.
Die Grenze zwischen beiden ist der Dateiplan, den dist export berechnet -
siehe NOTICE.
2026-09-01 16:26:14 +02:00

54 lines
2.1 KiB
Markdown

---
name: wiki-status
description: Show a quick read-only snapshot of the LLM wiki - page counts, orphan pages, uncovered raw files, recent activity. Use when the user says "wiki status", "show wiki statistics", "what's new", or wants a quick health snapshot without running a full lint.
---
# Wiki Status
**Purpose:** Report a quick, read-only snapshot of the wiki's current state, without the
semantic review a lint pass does.
**Trigger:** User asks for wiki statistics, "what's new", or a quick health snapshot.
**Hard rule:** read-only. Never writes, scaffolds, or modifies any file. If something looks
wrong, point the user at `wiki-lint` or `wiki-manage` instead of fixing it here.
## Steps
1. **Counts.** Read `kb/index.md` - it is the catalog map: totals, one row per collection and
per area. Small enough to read in full; the page tables live in the shards it links to.
2. **Structural snapshot.**
```bash
tools/wikitool lint
```
No flags: prints the sections that found something - broken links, orphan pages, schema
issues, uncovered raw files - and writes the full report to `reports/Lint Report <date>.md`,
naming the path. One pass is enough; read that file for anything the summary left out
rather than running `lint` a second time.
3. **Most-connected pages.** The link-graph summary is a statistic, not a finding, so it is
not in the printed summary: read the "Most-Linked Pages" section of the report file step 2
named. Useful for telling hub pages from candidates for a page of their own.
4. **Recent activity.** Read the last few entries of `kb/log.md`.
5. **Summarize in chat.** Counts by type, N orphan pages, N uncovered raw files, most-connected
pages, and what changed recently. Do not write a report file - that is `wiki-lint`'s job.
## Decision points
- **Findings worth acting on?** Point at `wiki-lint` (repairs) or `wiki-manage` (content). Do
not fix anything here.
- **Never publishes** - nothing was written.
## wikitool commands used
`lint` (no flags), `lint --json` (optional, for the link-graph data).
## Output
A short chat summary, plus a pointer to `wiki-lint` if deeper investigation is warranted.