Generated banner for Foundry Iq
Generated logo for Foundry Iq

Foundry Iq

MicrosoftOfficialCreated by Microsoft

  • Skill
  • Workflow
  • Data and AI
  • MIT
  • Medium risk
  • Has scripts

From the author

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.
— the description by Microsoft

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

Foundry IQ provides a structured framework for creating, diagnosing, and connecting knowledge bases to AI agents. It supports making local or Blob-based documents searchable, managing multi-source knowledge configurations, and retrieving information with citations. The skill emphasizes strict adherence to defined procedures for service discovery, resource creation, and troubleshooting to ensure reliable agent-knowledge integration.

What it does

  • Creates searchable knowledge bases from local or Azure Blob storage documents.
  • Connects existing knowledge bases to AI agents.
  • Diagnoses issues with knowledge base configurations or unsupported connectors.
  • Retrieves information from knowledge bases with source citations.
  • Manages the lifecycle of search services and knowledge sources.
  • Routes requests based on specific operational needs rather than source counts.

When to use it

  • When you need to make local or cloud-stored documents searchable by an AI agent.
  • When connecting an existing knowledge base to a new or current agent.
  • When troubleshooting or diagnosing a knowledge base configuration.
  • When you need to create a new search service or knowledge source.
  • When performing retrieval tasks that require citations from a knowledge base.

Advantages

  • Provides a clear, procedural approach to knowledge base management.
  • Ensures consistent handling of multi-source knowledge configurations.
  • Includes built-in diagnostic paths for troubleshooting.
  • Supports secure, citation-backed retrieval for agent responses.
  • Prevents unauthorized or unsupported configuration changes.

Usage examples

“Create a new knowledge base from my Azure Blob container.”
The agent will initiate the knowledge base creation procedure, validating the source and setting up the necessary search indexing.
“Connect my existing knowledge base to the current agent.”
The agent will follow the connection workflow to link the specified knowledge base to the agent's retrieval pipeline.
“Why is my multi-source knowledge base failing to index?”
The agent will trigger the diagnostic procedure to identify configuration drifts or unsupported connector issues.
“Retrieve information about project timelines from the knowledge base.”
The agent will query the knowledge base and provide an answer with citations from the source documents.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/microsoft/foundry-iq/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip foundry-iq.zip -d .agents/skills

Documentation by Microsoft

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. This routing takes precedence over classic-search terms (e.g. hybrid search) in compound requests. Never end in a plain refusal: Diagnose gives the boundary, docs pointer and agent handoff; writes still need an approved concrete plan. 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.

OutcomeRead
CleanupPlan cleanup
Failure/driftDiagnose
Unsupported connector provisioning / multi-source KB creation or reconfigurationDiagnose
ConnectConnect
Read KBQuery
Search onlySearch
File KS onlyFile
Blob/ADLS KS onlyBlob
Searchable/KBKB

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.

Files

knowledge-sources/create-file.md

Create a File knowledge source

When to use

Direct uploads; no customer Storage.

Do not use

Changing/scheduled corpora, lifecycle/DLP/permissions or overflow: Blob/ADLS. Unsupported content blocks. Never stage to Blob, split silently, alter files or upload outside the approved root.

Inputs and discovery order

Resolve prompt/session/workspace, then az account show for caller/tenant/default subscription. Explicit scope wins; never silently switch context. Missing CLI/sign-in blocks discovery, not proof of absence. Reads need no approval except content inspection: exact sample authorization. Silence is not approval. Recommend; after discovery batch compatible choices only for unresolved decisions. Reuse informed choices; separate sample-content consent from actual resource/permission/CU/source/KB approvals.

InputWhy neededRequired?Discovery orderSafe defaultIf missing or unansweredReconfirmation trigger
Scope/Search/accessTargetOutput before uploadExact Azure GETReuse/newChoicesScope/access
Root/inventoryDataPre-uploadSelection/listNever .Choose rootFiles
Owner/name/purpose/cleanupOwnerPre-writeCallerAzure userOverrideOwner
Processing/modelsSearchYesContent/choiceNo extraction defaultAssess/chooseContent/mode
API/cost/network/consentSecurityYesGETPreserveApprove planCost/access

Decisions

Opt-in title/content; no Q&A required. No auto-sample/query or filename defaults.

Search operation; bootstrap. Resume after readback, never call Create KB. No routine policy reads. File-only creates no KB/synthesis model. Minimal lexical extraction needs no model; standard independently selects CU.

Honor explicit processing choices only when informed and compatible. Unknown content or mode/goal conflicts: read content-fit. MUST assess/clarify before planning: bounded authorized samples or questions about text-only versus multimodal content and answer dependence. Reuse answers; honor informed reduced outcomes. Unavailable/declined/unreadable inspection means ask, not assume text-only. No filename/MIME inference, silent default/downgrade or model calls. Explain tradeoffs; obtain concrete-plan/CU/data approvals. Vectors are independent. New unresolved search: recommend Hybrid; confirm tradeoffs/opt-out. Keyword-only: no embedding discovery. Lexical skips vector references. If CU/models: discovery.

Reject absolute/traversing/unreadable paths or escaping links/reparse points. Freeze path/MIME/bytes/mtime/SHA-256 in byte order; recheck pre-upload.

Prove formats, at most 200 files, per-file maximum: 50 MB for Free/Basic, 100 MB otherwise. Unknown/overflow: Blob.

  • minimal: supported non-image content with contentExtractionMode: minimal.

  • standard: contentExtractionMode: standard, 2026-08-01-preview, CU and approved cost/security/data movement; source embeddings are optional. Detected images with minimal are invalid; never downgrade.

GET exact source; only FIND lists candidates. Read all file pages each run. Reuse exact definition/inventory/index/markers. Duplicates/inaccessible/drift block; no suffixing/upload repair.

Proposed plan

Read helper contracts before planning. For standard planning, read CU choices; minimal skips it. CU auth: verified Search MI or explicit ARM/ENV; never expose secrets.

python helpers/file_source.py --plan request.json --execution-output <new-private-plan.json>

UTF-8:

{"schema_version":"1.0","endpoint":"https://svc.search.windows.net","name":"manuals","owner":"team","local_root":"C:\\docs","paths":["guide.txt"],"service_tier":"basic","extraction_mode":"minimal","vectorization":"none","rbac":{"assignments":[{"id":"<role>","principalId":"<principal>"}]},"network":{"posture":"<posture>","evidence":"<readback>"}}

Tier: free/basic/dedicated/serverless. Require RBAC and network.posture/network.evidence. paths: 1–200 unique relative POSIX paths; no globs; MIME hint only. Types/API. Vectors: vectorization: azureOpenAI; choices.

Exit 0: planned, not ready. Private output: retain unapproved input privately; show reference/counts, not file hashes. Review actions/mode/access/cost/retention/cleanup. Verify known/security requirements before consent; unapproved input blocks. Exact reuse: execution_required: false and mutation_approval_required: false: no approval or executor. Reread definition/ETag after all pages; ingestion isn't retrieval. No writes/installs/identity changes/cached consent.

Confirmation

Retain immutable plan/plan_fingerprint/cleanup_approved: false; review choices, not hashes. Requirements/inventory/endpoint/API/model/identity/network/role/definition/ETag drift voids consent. Rerun --plan, replace the saved execution_input and discard old consent; approve only new actual mutations. Never edit nested plans or recompute hashes manually.

Mutation

After approval:

python helpers/file_source.py --input <approved.json> --cleanup-receipt-dir <private-receipts> --upload-receipt-dir <separate-empty-dir>

Require validated private receipts pre-write; no inferred paths/GET ownership. reconcile-and-ingest validates source/ingestion agreement before writes. Synchronous POST: 180s; final inventory. 429: one bounded retry; create once. Timeout/409/5xx: readback only. Exit 2: blocked; 3: partial. Never invoke children alone. Create absent sources only; reuse never uploads. fileParameters.ingestionParameters binds contentExtractionMode; lexical omits embeddingModel; vectors bind observed azureOpenAI endpoint/deployment/model. Standard binds aiServices.uri; no verbalization/chatCompletionModel.

Block rather than downgrade to minimal. Reject networkAccessMode: one index, no indexer/schedule; never patch children.

List /knowledgesources('<source-name>')/files; upload only absent exact inventory entries by multipart POST; read stable file IDs. Never modify/stage files, use Search/Storage keys/SAS, or rename an ambiguous retry.

Verification

Verify definition/mode/dependencies, count/path/type/size/hash-to-file-ID, zero ingestion failures, generated index/child ownership, keyless Search access, network and unchanged inventory. Rerun discovery: stable IDs/zero writes. Vectors: staged verification; deployment/lexical results aren't vector proof.

Failure and partial completion

Report first failure/proved counts and progress. Resume; never recreate, replay uncertain files or suggest cleanup.

Cleanup

Receipts: retain pre-create. Separate cleanup plan/approval: delete run-owned source/children. Never delete or alter local files, reused resources or shared roles. operation: delete: owned digest/ETag; unclear ownership blocks.

Return contract

Return status/fingerprint/IDs/API/boundary/inventory, auth/RBAC/network/ingestion/idempotency/ownership/warnings/cleanup. Pass assessment/uncertainty/answer needs/mode through prerequisites to the KB owner; resume KB plus validated retrieval. Never return content/credentials.

References

Authorities: failure/conflict/uncertainty only.

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Needs Python

The author says: Azure

Security

What our scanner noticed· Medium risk

  • References to credential files
  • Instructions that use the network
  • Scripts that your agent may run

This skill includes scripts that your agent may run. Read them before you use it.

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
Microsoft
Publisher
Microsoft (Official)
Source
microsoft/skills · .github/plugins/foundry-iq-skills/skills/foundry-iq · commit 0696600
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from .github/plugins/foundry-iq-skills/LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Microsoft or Microsoft.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download foundry-iq.zip