# Foundry Iq

Foundry IQ knowledge bases.

- Repository: https://github.com/microsoft/azure-skills (1609 stars)
- Category: AI and agents
- License: MIT
- Last updated: 2026-10-30
- Runs scripts: yes, review before use

## Install

Claude Code: `npx skills add microsoft/azure-skills --skill foundry-iq -g -a claude-code -y`
Codex: `npx skills add microsoft/azure-skills --skill foundry-iq -g -a codex -y`
Cursor: `npx skills add microsoft/azure-skills --skill foundry-iq -g -a cursor -y`
Gemini CLI: `npx skills add microsoft/azure-skills --skill foundry-iq -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add microsoft/azure-skills`

## Description

Foundry IQ knowledge bases. WHEN: make local or Blob documents searchable; create/diagnose KBs; triage unsupported connectors or multi-source KB creation/reconfiguration (even with classic-search terms); 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 with no Foundry IQ KB or connector request, generic agent creation.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# 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](references/intent-routing.md).

The rest: https://github.com/microsoft/azure-skills/blob/HEAD/.github/plugins/foundry-iq-skills/skills/foundry-iq/SKILL.md