Agent skill · DevOps & Cloud

foundry-agent-sync

Create and synchronize prompt-based AI agents directly within Azure AI Foundry via REST API, from a local JSON manifest. Unlike scaffolding skills that only generate local code, this skill registers agents in the Foundry service itself — making them immediately available for invocation. Use when the user asks to create agents in Foundry, sync, deploy, register, or push agents to Foundry, update agent instructions, or scaffold the manifest and sync script for a new repository. Triggers: 'create agent in foundry', 'sync foundry agents', 'deploy agents to foundry', 'register agents in foundry', '

GitHub68,948★ · +463/wk · 2 repos on radarProfile →
copilotMIT
Install
npx skills add github/awesome-copilot --skill foundry-agent-sync --agent copilot

Same command for any agent — swap --agent for claude-code, codex, cursor.

Facts
Files in the skill folder: 1
SKILL.md size: 8 KB
Bundled scripts: none
Path: skills/foundry-agent-sync/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 37,432 · +281 this week
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Foundry Agent Sync ## Overview Create and synchronize prompt-based AI agents directly within Azure AI Foundry via the Agent Service REST API. This skill registers agents in the Foundry service itself — making them immediately available for invocation, evaluation, and management through the Foundry portal or API. Each agent is created or updated idempotently via a named POST call, using definitions from a local JSON manifest file. > **Key distinction:** This skill creates agents inside AI Foundry (server-side). It does not scaffold local agent code or container images — for that, use the `microsoft-foundry` skill's `create` sub-skill. ## Prerequisites The user must have: 1. An Azure AI Foundry project with a deployed model (e.g. `gpt-5-4`) 2. Azure CLI (`az`) authenticated with access to the Foundry project 3. The **Azure AI User** role (or higher) on the Foundry project resource Collect these values before proceeding: | Value | How to get it | |---|---| | **Foundry project endpoint** | Azure Portal → AI Foundry project → Overview → Endpoint, or `az resource show` | | **Subscription ID** | `az account show --query id -o tsv` | | **Model deployment name** | The model name deployed

What's inside
Steps it walks through
  1. Overview
  2. Prerequisites
  3. Manifest Format
  4. Field Reference
  5. Sync Script
  6. PowerShell (interactive / CI)
  7. Bash (Bicep deployment script / CI)
  8. Bicep Integration (optional)
  9. Workflow
  10. Step 1 — Locate or scaffold the manifest
  11. Step 2 — Locate or scaffold the sync script
  12. Step 3 — Collect parameters
  13. Step 4 — Run the sync
  14. Step 5 — Verify
More from awesome-copilot
All skills →
About this skill
What does the foundry-agent-sync skill do?

Create and synchronize prompt-based AI agents directly within Azure AI Foundry via REST API, from a local JSON manifest. Unlike scaffolding skills that only generate local code, this skill registers agents in the Foundry service itself — making them immediately available for invocation. Use when the user asks to create agents in Foundry, sync, deploy, register, or push agents to Foundry, update agent instructions, or scaffold the manifest and sync script for a new repository. Triggers: 'create agent in foundry', 'sync foundry agents', 'deploy agents to foundry', 'register agents in foundry', '

How do I install it?

Run `npx skills add github/awesome-copilot --skill foundry-agent-sync --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From github/awesome-copilot, a repository with 37,432 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going