Foundry Knowledge System
Foundry iq
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);…
--- name: foundry-iq 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." license: MIT compatibility: Azure metadata: author: Microsoft version: "0.1.4" --- # 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.
Overview
Cleanup and receipt-backed execution go directly to their lifecycle/producer owner; do not reopen Search intake, provisioning or hardening.
Manual install (npx, ZIP)
npx skills add microsoft/skills --skill foundry-iq -g -a claude-codenpx degit microsoft/skills/.github/plugins/foundry-iq-skills/skills/foundry-iq#main ~/.claude/skills/foundry-iqConnects with Agent Alley MCP · agentalley.io/mcp
Files included
SKILL.md3.4 KB
Read SKILL.md here
Show the full text60 lines
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 | |
| 2 | name foundry-iq |
| 3 | 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." |
| 4 | license MIT |
| 5 | compatibility Azure |
| 6 | metadata |
| 7 | author Microsoft |
| 8 | version "0.1.4" |
| 9 | |
| 10 | |
| 11 | # Foundry IQ |
| 12 | Read one procedure before questions/actions; invocation is not a read. |
| 13 | Read the owning procedure before blocked/unsupported responses too. |
| 14 | Before mutation plans/approval, successfully read its required pre-action references, selected |
| 15 | branches only. Do not reload successful reads. On failure, try only permitted |
| 16 | bounded exact-path reads with any supported reader; never bypass restrictions |
| 17 | or search broadly. If still unavailable: `blocked: reference-unavailable`, name |
| 18 | missing references and inability to plan. Never invent requirements/plans. |
| 19 | Failures first. |
| 20 | |
| 21 | Cleanup and receipt-backed execution go directly to their lifecycle/producer owner; |
| 22 | do not reopen Search intake, provisioning or hardening. |
| 23 | |
| 24 | Before expensive service discovery, reuse supplied resource/intent; otherwise ask |
| 25 | one early **USE EXISTING / FIND CANDIDATES / CREATE NEW** choice. |
| 26 | Only FIND enumerates; supplied identity uses exact/minimum scoped resolution. |
| 27 | CREATE checks its proposed name, not existing-service inventories. Preserve these |
| 28 | answers across source/KB/CU/model handoffs; selection is not write approval. |
| 29 | |
| 30 | Searchable docs: KB + validated retrieval. Confirm intent once; KS-only must be explicit. |
| 31 | Child success is not KB completion. |
| 32 | Unclear/compound/mode/completion: [read]. |
| 33 | |
| 34 | Route by requested operation, not existing KB source count. |
| 35 | Connecting an existing KB with two or more sources, without changing the KB, uses Connect. |
| 36 | Read-only operations use their owning procedure and actual helper constraints; |
| 37 | this does not add retrieval modes or supported source kinds. |
| 38 | Explicit unsupported provisioning or multi-source KB creation/reconfiguration uses Diagnose |
| 39 | and stops before discovery, even when connecting an agent is also requested. |
| 40 | Do not silently execute only the supported part of a compound request. |
| 41 | If existing-KB connection versus KB creation/reconfiguration is unclear, read |
| 42 | intent-routing and clarify that scope before Azure discovery. Never infer KB mutation. |
| 43 | |
| 44 | |Outcome|Read| |
| 45 | |---|---| |
| 46 | |Cleanup|[Plan cleanup]| |
| 47 | | Failure/drift | [Diagnose] | |
| 48 | | Unsupported connector provisioning / multi-source KB creation or reconfiguration | [Diagnose] | |
| 49 | | Connect | [Connect] | |
| 50 | | Read KB | [Query] | |
| 51 | | Search only | [Search] | |
| 52 | | File KS only | [File] | |
| 53 | | Blob/ADLS KS only | [Blob] | |
| 54 | | Searchable/KB | [KB] | |
| 55 | |
| 56 | Generic agents: `microsoft-foundry`. |
| 57 | Reads: no approval; approve unchanged plans before writes. |
| 58 | Hide hashes. No Search/Storage keys, scope widening, guessed identity/boundaries, |
| 59 | drift repair or joint cleanup/creation approval. Acceptance != success. |
| 60 |
Details
- License
- MIT
- Stars on the repo
- ★ 3,077
- Checked
- Source
- microsoft/skills ↗
- Creator
- microsoft · 31 listings
Similar skills
See all →
SkillCross-Platform Reverse Engineer
morluto/rea · by morlutoReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.★ 316k GitHub stars
SkillBrainstorm Ideas
obra/superpowers · by obraYou MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.★ 290k GitHub stars
SkillCode Review Feedback Analyzerobra/superpowers · by obraUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation★ 290k GitHub stars
SkillBug Diagnosis Framework
mattpocock/skills · by mattpocockDiagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.★ 267k GitHub stars
SkillImplement Specmattpocock/skills · by mattpocockImplement the result of /to-spec and /to-tickets in code.★ 267k GitHub stars
SkillPR Description Writermattpocock/skills · by mattpocockUse when writing a PR body.★ 267k GitHub starsMore from microsoft
AgentPlaywright Browser Automation MCP
microsoft/playwright-mcp · by microsoftMicrosoft's browser automation server: your AI opens pages, clicks, fills forms and reads the page through the accessibility tree.★ 37.5k GitHub stars
SkillUsage-Based Agent Trainermicrosoft/SkillOpt · by microsoftUse when the user wants their Claude agent to self-improve from past usage, asks about a nightly/offline 'sleep' or 'dream' cycle, memory/skill consolidation, or says things like 'make my agent better the more I use it', 'review my past sessions', 'learn my pr★ 17.3k GitHub stars
SkillAzure App Deployermicrosoft/skills · by microsoftEnd-to-end orchestrator: from a business idea, app idea, or existing app to running Azure deployment with cost estimates and pre-deploy approval. Analyzes your app, auto-detects the right Azure services, scaffolds infrastructure code, and deploys — tailored to your app, not a template. Handles moving existing apps to Azure without rewriting or with minimal changes. WHEN: bring your app to Azure, plan my app, cost to run, is my code ready to deploy, deploy my app to the cloud, deploy all my services, what Azure services do I need, plan my Azure deployment, deploy my new app to Azure, one-click deploy, I have an app and want it on Azure, migrate my app to Azure, help me get started, build an app, no code yet, starter project. DO NOT USE FOR: use azd for deployment(use azure-deploy), optimizing existing costs (use cost-optimization), code readiness checks only (use azure-app-onboard-prereq).★ 3.1k GitHub stars
SkillAzure Deployment Auditormicrosoft/skills · by microsoftAssess whether source code is ready to deploy to Azure — the check BEFORE infrastructure work. Evaluates build health, app completeness, dependencies and local services, stack compatibility, and deployment feasibility. Answers questions about what your app needs before it can be deployed — frameworks, dependencies, and configuration. Checks whether dependencies are compatible and identifies deployment blockers and unsupported frameworks. WHEN: "evaluate my repo", "is my app ready to deploy", "what does my app need to deploy", "what do I need before deploying", "does my app need", "can I ship this to Azure", "scan my repo for issues", "is this app deployable", "check if my app is ready for Azure", "do I need a Dockerfile", "what's blocking my deployment", "are there any blockers", "are my dependencies compatible", "does Azure support my framework", "what needs to change before deploying", "check my app configuration".★ 3.1k GitHub stars
SkillAzure Security Auditormicrosoft/skills · by microsoftRun Azure compliance and security audits with azqr plus Key Vault expiration checks. Covers best-practice assessment, resource review, policy/compliance validation, and security posture checks. WHEN: compliance scan, security audit, BEFORE running azqr (compliance cli tool), Azure best practices, Key Vault expiration check, expired certificates, expiring secrets, orphaned resources, compliance assessment.★ 3.1k GitHub stars
SkillAzure AI Gatewaymicrosoft/azure-skills · by microsoftConfigure Azure API Management as an AI Gateway for AI models, MCP tools, and agents. WHEN: semantic caching, token limit, content safety, load balancing, AI model governance, MCP rate limiting, jailbreak detection, add Azure OpenAI backend, add AI Foundry model, test AI gateway, LLM policies, configure AI backend, token metrics, AI cost control, convert API to MCP, import OpenAPI to gateway.★ 1.6k GitHub stars