feat(skills): integrate web-search, db-yaml, agent-cost, diataxis-docs, kb-search; retire searxng

2026-08-10 20:50:25 +01:00
parent 390784d406
commit d4a88eead7
8 changed files with 294 additions and 0 deletions
@@ -0,0 +1,51 @@
+---
+name: web-search
+description: >-
+  Search the public web through the self-hosted SearXNG at search.ops.io
+  using bin/web/search. Use for German care law, SGB paragraphs, vendor
+  documentation and any fact that is not in our own repos - and as the second
+  independent source the detective method requires.
+---
+
+# web-search
+
+```bash
+bin/web/search "Pflegegrad SGB XI Einstufung"
+bin/web/search "Toureffizienz" --site ticket.detective.de
+bin/web/search "sqlite-vec" --category it -n 3 --json | jq -r '.results[].url'
+bin/web/search "Pflegereform" --lang de --fresh year
+```
+
+## Web or knowledge base
+
+`bin/kb/search` holds our own facts: product docs, detective business logic, the
+lexicon. Go there first. Reach for `bin/web/search` when the answer is outside
+our repos: legislation, vendor documentation, upstream library behaviour.
+
+Keep the two apart. A finding is stronger when the reader can see that one
+source was ours and one was not.
+
+## PII: this query leaves the host
+
+The search goes to external engines. Never put a client or staff identifier in
+it. The tool refuses long digit runs, `Personalnummer`, `KV-Nr`, dates of birth
+and street-with-number, and exits 2. Rephrase rather than reaching for `--force`.
+
+## Read the status, not just the results
+
+The instance answers HTTP 200 with an empty list when it throttles, so an empty
+answer is ambiguous by construction. The tool resolves that for you:
+
+| status | exit | meaning |
+|--------|------|---------|
+| `ok` | 0 | engines answered |
+| `throttled` | 3 | nobody answered; say nothing about what exists |
+
+Never turn a `throttled` result into "there is no information about X".
+
+## Etiquette
+
+Calls are serialised host-wide and kept ten seconds apart, and answers are
+cached for seven days. Do not loop over queries, and do not use `--refresh`
+unless the cached answer is genuinely stale: a burst suspends the engines for
+several minutes for everyone.