Agent Skills › microsoft/azure-skills › foundry-iq

foundry-iq

GitHub

管理Foundry IQ知识库，支持文档搜索、KB创建诊断、连接器排查、Agent连接及检索引用。

.github/plugins/foundry-iq-skills/skills/foundry-iq/SKILL.md microsoft/azure-skills

Trigger Scenarios

使本地或Blob文档可搜索创建或诊断知识库处理不支持的连接器或多源KB配置将现有KB连接至Agent 从知识库检索带引用的信息

Install

npx skills add microsoft/azure-skills --skill foundry-iq -g -y

More Options

Non-standard path

npx skills add https://github.com/microsoft/azure-skills/tree/main/.github/plugins/foundry-iq-skills/skills/foundry-iq -g -y

Use without installing

npx skills use microsoft/azure-skills@foundry-iq

指定 Agent (Claude Code)

npx skills add microsoft/azure-skills --skill foundry-iq -a claude-code -g -y

安装 repo 全部 skill

npx skills add microsoft/azure-skills --all -g -y

预览 repo 内 skill

npx skills add microsoft/azure-skills --list

SKILL.md

Frontmatter

{
    "name": "foundry-iq",
    "license": "MIT",
    "metadata": {
        "author": "Microsoft",
        "version": "0.1.1"
    },
    "description": "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.",
    "compatibility": "Azure"
}

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.