Foundry iq skill

Foundry IQ knowledge bases.

by microsoft·MIT license·★ 3,077 Stars on the repo·GitHub ↗

Use now

Files of Foundry iq

microsoft/main1 file shown
SKILL.md
Show the full text60 lines
foundry-iq/SKILL.md60 lines · 3.4 KB
RawView on GitHub

Foundry IQ

Read one procedure before questions/actions; invocation is not a read. Read the owning procedure before blocked/unsupported responses too. Before mutation plans/approval, successfully read its required pre-action references, selected branches only. Do not reload successful reads. On failure, try only permitted bounded exact-path reads with any supported reader; never bypass restrictions or search broadly. If still unavailable: blocked: reference-unavailable, name missing references and inability to plan. Never invent requirements/plans. Failures first.

Cleanup and receipt-backed execution go directly to their lifecycle/producer owner; do not reopen Search intake, provisioning or hardening.

Before expensive service discovery, reuse supplied resource/intent; otherwise ask one early USE EXISTING / FIND CANDIDATES / CREATE NEW choice. Only FIND enumerates; supplied identity uses exact/minimum scoped resolution. CREATE checks its proposed name, not existing-service inventories. Preserve these answers across source/KB/CU/model handoffs; selection is not write approval.

Searchable docs: KB + validated retrieval. Confirm intent once; KS-only must be explicit. Child success is not KB completion. Unclear/compound/mode/completion: read.

Route by requested operation, not existing KB source count. Connecting an existing KB with two or more sources, without changing the KB, uses Connect. Read-only operations use their owning procedure and actual helper constraints; this does not add retrieval modes or supported source kinds. Explicit unsupported provisioning or multi-source KB creation/reconfiguration uses Diagnose and stops before discovery, even when connecting an agent is also requested. Do not silently execute only the supported part of a compound request. If existing-KB connection versus KB creation/reconfiguration is unclear, read intent-routing and clarify that scope before Azure discovery. Never infer KB mutation.

Outcome Read
Cleanup Plan cleanup
Failure/drift Diagnose
Unsupported connector provisioning / multi-source KB creation or reconfiguration Diagnose
Connect Connect
Read KB Query
Search only Search
File KS only File
Blob/ADLS KS only Blob
Searchable/KB KB

Generic agents: microsoft-foundry. Reads: no approval; approve unchanged plans before writes. Hide hashes. No Search/Storage keys, scope widening, guessed identity/boundaries, drift repair or joint cleanup/creation approval. Acceptance != success.

1---
2name: foundry-iq
3description: "Foundry IQ knowledge bases. WHEN: make local or Blob documents searchable; create/diagnose KBs; triage unsupported connectors or multi-source KB creation/reconfiguration; connect existing KB to agents (including multi-source KBs); create/reuse a Search service; retrieve from an existing knowledge base with citations; no brand words needed. Read its procedure before query/target questions. NOT: other KB providers, repository-file search, classic Azure AI Search index/query/app work, generic agent creation."
4license: MIT
5compatibility: Azure
6metadata:
7 author: Microsoft
8 version: "0.1.4"
9---
10 
11# Foundry IQ
12Read one procedure before questions/actions; invocation is not a read.
13Read the owning procedure before blocked/unsupported responses too.
14Before mutation plans/approval, successfully read its required pre-action references, selected
15branches only. Do not reload successful reads. On failure, try only permitted
16bounded exact-path reads with any supported reader; never bypass restrictions
17or search broadly. If still unavailable: `blocked: reference-unavailable`, name
18missing references and inability to plan. Never invent requirements/plans.
19Failures first.
20 
21Cleanup and receipt-backed execution go directly to their lifecycle/producer owner;
22do not reopen Search intake, provisioning or hardening.
23 
24Before expensive service discovery, reuse supplied resource/intent; otherwise ask
25one early **USE EXISTING / FIND CANDIDATES / CREATE NEW** choice.
26Only FIND enumerates; supplied identity uses exact/minimum scoped resolution.
27CREATE checks its proposed name, not existing-service inventories. Preserve these
28answers across source/KB/CU/model handoffs; selection is not write approval.
29 
30Searchable docs: KB + validated retrieval. Confirm intent once; KS-only must be explicit.
31Child success is not KB completion.
32Unclear/compound/mode/completion: [read](references/intent-routing.md).
33 
34Route by requested operation, not existing KB source count.
35Connecting an existing KB with two or more sources, without changing the KB, uses Connect.
36Read-only operations use their owning procedure and actual helper constraints;
37this does not add retrieval modes or supported source kinds.
38Explicit unsupported provisioning or multi-source KB creation/reconfiguration uses Diagnose
39and stops before discovery, even when connecting an agent is also requested.
40Do not silently execute only the supported part of a compound request.
41If existing-KB connection versus KB creation/reconfiguration is unclear, read
42intent-routing and clarify that scope before Azure discovery. Never infer KB mutation.
43 
44|Outcome|Read|
45|---|---|
46|Cleanup|[Plan cleanup](lifecycle/cleanup.md)|
47| Failure/drift | [Diagnose](troubleshooting/diagnose.md) |
48| Unsupported connector provisioning / multi-source KB creation or reconfiguration | [Diagnose](troubleshooting/diagnose.md) |
49| Connect | [Connect](agents/connect.md) |
50| Read KB | [Query](knowledge-bases/retrieve.md) |
51| Search only | [Search](search-services/create.md) |
52| File KS only | [File](knowledge-sources/create-file.md) |
53| Blob/ADLS KS only | [Blob](knowledge-sources/create-azure-blob.md) |
54| Searchable/KB | [KB](knowledge-bases/create.md) |
55 
56Generic agents: `microsoft-foundry`.
57Reads: no approval; approve unchanged plans before writes.
58Hide hashes. No Search/Storage keys, scope widening, guessed identity/boundaries,
59drift repair or joint cleanup/creation approval. Acceptance != success.
60 

Discussion