agents: prefer onyx over direct CQL for internal-doc research
This commit is contained in:
parent
dd4698fca7
commit
774e5183e5
1 changed files with 6 additions and 0 deletions
|
|
@ -4,6 +4,12 @@
|
||||||
|
|
||||||
- For questions about internal processes, tools, or "wie machen wir X
|
- For questions about internal processes, tools, or "wie machen wir X
|
||||||
bei Seibert", check the company knowledge first (skill `onyx`).
|
bei Seibert", check the company knowledge first (skill `onyx`).
|
||||||
|
- **Default to onyx for any "find internal docs on topic X" research**
|
||||||
|
(products, services, systems, teams) — its semantic index regularly
|
||||||
|
surfaces Confluence pages that direct CQL/JQL text search misses
|
||||||
|
(unexpected spaces, differently worded titles). Use direct
|
||||||
|
Confluence CQL only for precise lookups where space or title is
|
||||||
|
already known.
|
||||||
- Pick the mode by use case (see the skill's mode table): `answer` for
|
- Pick the mode by use case (see the skill's mode table): `answer` for
|
||||||
simple factual questions (cheap on context), `search` when you need
|
simple factual questions (cheap on context), `search` when you need
|
||||||
the source text itself — always cite source links.
|
the source text itself — always cite source links.
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue