eSlider
63d3be0e19
- bin/db/psql-yq + bin/web/search + tools/{yamlout,websearch} vendored as real files
- bin/db/ssh-tunnel added (OnlyOffice VM pg on 5433)
- skills reference local bin/ paths; no agent-skills/abs links in git
- pyproject.toml + uv.lock; CI installs via uv sync --frozen
- release-please auto-tags semver from conventional commits when green
- LICENSE MIT, badges/mermaid README
1.9 KiB
name, description
| name | description |
|---|---|
| web-search | 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
bin/web/search "LadybugDB vector index"
bin/web/search "model2vec multilingual" --category it
bin/web/search "hypervisor" --site ops.io --json | jq -r '.results[].url'
bin/web/search "postgres partial index" --lang en --fresh year
Web or knowledge base
bin/kb/search holds our own facts: the ops stack, portfolio, ssh hosts, the
lexicon. Go there first. Reach for bin/web/search when the answer is outside
our repos: upstream library behaviour, vendor documentation, public standards.
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.