microsoft foundry

DevOps Community

Skill notes

Pre-Execution Requirements

MANDATORY: Before executing ANY workflow, you MUST first call the Azure MCP foundry tool and inspect the available Foundry MCP tools and related parameters. Treat this initial foundry call as a discovery/help step. For this skill, Azure MCP foundry is the required entry point for Foundry-related MCP operations.

Sub-Skills

MANDATORY: Before executing ANY workflow-specific steps, you MUST read the corresponding sub-skill document. Do not call workflow-specific MCP tools for a workflow without reading its skill document. This applies even if you already know the MCP tool parameters — the skill document contains required workflow steps, pre-checks, and validation logic that must be followed. This rule applies on every new user message that triggers a different workflow, even if the skill is already loaded.

Infrastructure Lifecycle

Match user intent to the correct infrastructure workflow. User Intent · Workflow "Create Foundry" / "Set up Foundry" (ambiguous) · Use AskUserQuestion: (a) just an AI Services resource, (b) a project with public access, or (c) a project with network isolation? Route: (a) → resource/create, (b) → project/create, (c) → private-network Set up Foundry with VNet isolation · private-network Create a Foundry project (public) · project/create

Agent Development Lifecycle

Match user intent to the correct agent workflow. Read each sub-skill in order before executing. User Intent · Workflow (read in order) Create a new agent from scratch · create → deploy → invoke Optimize existing Python hosted agent · agent-optimizer → scaffold/review → eval.yaml → optimize → apply candidate → deploy → invoke Deploy an agent (code already exists) · deploy (includes eval-suite setup) → invoke → observe (evaluate/optimize)

Agent: .foundry Workspace Standard

Every agent source folder can keep Foundry-specific cache and overlay state under .foundry/: In azd projects, derive deployment context (project endpoint, agent name/version, ACR, App Insights) from azure.yaml plus azd env get-values; do not duplicate those values in metadata when azd already provides them. agent-metadata.yaml is the preferred local/dev overlay for non-azd values, remote Foundry suite references, local cache paths, result summaries, and explicit overrides. Optional sidecar files such as agent-metadata.prod.yaml can hold a single prod or CI-targeted overlay without mixing multiple environments in one file.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
DevOps
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
94 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@XOEEst · MIT
Token usage
Heavy
Setup complexity
Manual integration
External API key
Not required
Operating systems
Docker
Runtime requirements
Python · Docker
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
  • Env read
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1: Discover Agent Roots and azd Context

First check whether the workspace has `azure.yaml` with services using `host: azure.ai.agent`. One azd agent service -> use that service's `project` folder as the agent root. Multiple azd agent services -> require the user to choose the target service/folder. No azd agent service -> search the workspace for `.foundry/` folders that contain `agent-metadata.yaml` or `agent-metadata.<env>.yaml`. One match -> use that agent root.

02
Step 2: Resolve Environment and Deployment Context

If `azure.yaml` is present, resolve the azd environment first: Environment explicitly named by the user `AZURE_ENV_NAME` from `azd env get-values` azd default environment from `.azure/config.json` Environment already selected earlier in the session

03
Step 3: Select Metadata Overlay and Resolve Environment

Inside the selected agent root, choose the metadata file in this order: Metadata filename or path explicitly provided by the user or workflow If an explicit environment is already known and `.foundry/agent-metadata.<env>.yaml` exists, use that file `.foundry/agent-metadata.yaml` If multiple metadata files remain and no rule above selects one, prompt the user to choose

04
Step 4: Resolve eval.yaml Local Evaluation Intent

If `eval.yaml` exists in the selected agent root, parse it before generating new suites: `agent.name` -> target agent candidate; verify it matches the selected azd/metadata agent before using it. `dataset_file` -> local seed dataset candidate. `evaluators[]` -> candidate Foundry evaluator names; verify with `evaluator_catalog_get` before treating them as remote evaluators. `name` -> local eval/suite candidate; verify remotely before persisting as `suiteName`.

05
Step 5: Resolve Common Configuration

Layer sources in this order: Explicit user input and values already selected in the session azd environment values for deployment context `.foundry/agent-metadata*.yaml` overlay values and remote suite/cache references `agent.yaml` and `eval.yaml` local source configuration

06
Step 6: Write Metadata Overlay (Create/Deploy/Observe Only)

On any metadata write (deploy, auto-setup, dataset refresh, or trace-to-dataset update), persist only non-derivable overlay/cache state in the selected metadata file: azd binding (`azd.environmentName`, `azd.service`) when useful for future resolution `evaluationSuites[]` with remote suite/dataset/evaluator references and local cache paths `lastEval`, result files, comparison summaries, or explicit non-azd overrides

07
Step 7: Collect Missing Values

Use the `ask_user` or `askQuestions` tool only for values not resolved from the user's message, session context, metadata, or azd bootstrap. Common values skills may need: Agent root — Target azd service project folder or folder containing `.foundry/agent-metadata*.yaml` Metadata file — `agent-metadata.yaml` for local/dev, or an explicit sidecar such as `agent-metadata.prod.yaml` Environment — azd environment, `dev`, `prod`, or another environment key from metadata

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.