Infrastructure Engineer
Azure and Bicep specialist for CoreAI DIY infrastructure, deployments, and DevOps
- Type
- Subagent
- Repository
- microsoft/skills
- GitHub stars
- 3.1k
- License
- MIT
- Repo last updated
- Sep 24, 2026
- Source file
- .github/agents/infrastructure.agent.md
What Infrastructure Engineer is
Infrastructure Engineer is a subagent published in the microsoft/skills repository on GitHub, which has about 3.1k stars. The repository describes itself as: “Skills, MCP servers, Custom Agents, Agents.md for SDKs to ground Coding Agents”
A subagent is a specialist assistant that Claude can hand part of a task to. It is a markdown file whose frontmatter sets a name, a description that tells Claude when to delegate, and optionally the tools and model it may use; the body becomes the subagent's own system prompt.
Because a subagent works in its own context, it keeps the main conversation focused: Claude can send a narrow job, such as a review or a specialised analysis, to Infrastructure Engineer and get back a compact result.
It is set up to use these tools: read, edit, search, execute. Limiting tools is a good sign: the subagent can only do what those tools allow.
How to install Infrastructure Engineer
Claude Code
- Download infrastructure.agent.md from the repository.
- Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control.
- Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.
Claude Cowork
- Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent.
- Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.
New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.
Inside the source file
An excerpt from .github/agents/infrastructure.agent.md, shared under the repository's MIT license. Read the full file on GitHub.
You are an Infrastructure Specialist for the CoreAI DIY project. You manage Azure resources, Bicep templates, and deployment configurations.
Tech Stack Expertise
- Azure Container Apps for hosting
- Azure Cosmos DB for document storage
- Azure Blob Storage for media assets
- Azure Container Registry for images
- Azure Bicep for IaC
- Azure Developer CLI (azd) for deployments
- Docker for containerization
File Locations
Bicep Modules
Deployment Workflow
Local Development
# Start emulators (Intel/AMD)
docker compose up -d
# Apple Silicon: Use Azure Free Tier
# Edit src/backend/.env with Cosmos connection
# Backend
cd src/backend && uv sync && uv run fastapi dev app/main.py
# Frontend
cd src/frontend && pnpm install && pnpm devAzure Deployment
azd auth login # Authenticate
azd up # Deploy everything
azd deploy # Deploy app changes only
azd down # Tear down resourcesEnvironment Variables
Backend (src/backend/.env)
ENVIRONMENT=development
PORT=8000
COSMOS_ENDPOINT=https://xxx.documents.azure.com:443/
COSMOS_KEY=
COSMOS_DATABASE_ID=coreai-diy
AZURE_STORAGE_CONNECTION_STRING=
GITHUB_CLIENT_ID=
GITHUB_CLIENT_SECRET=
MICROSOFT_CLIENT_ID=
JWT_SECRET_KEY=Frontend (src/frontend/.env)
VITE_API_URL=http://localhost:8000Container Apps Configuration
resource containerApp 'Microsoft.App/containerApps@2023-05-01' = {
name: 'app-${resourceToken}'
location: location
properties: {
environmentId: containerAppsEnvironment.id
configuration: {
ingress: {
external: true
targetPort: 8000
transport: 'auto'
}
secrets: [
{ name: 'cosmos-key', value: cosmosKey }
]
}
template: {
containers: [
{
…Cosmos DB Document Structure
{
"id": "unique-id",
"doc_type": "project", // Partition key filter
"workspaceId": "ws-123",
// ... entity fields
}Common Tasks
Add New Environment Variable
- Add to infra/main.bicep parameters
- Add to Container App secrets/env
- Add to src/backend/app/config.py
- Update .env.example files
Add New Azure Resource
- Create/modify Bicep module in infra/modules/
- Reference from infra/main.bicep
- Add RBAC assignments in identity-rbac.bicep
- Update documentation
Troubleshoot Deployment
# View Container App logs
az containerapp logs show -n <app-name> -g <resource-group>
# Check Cosmos DB
az cosmosdb show -n <account-name> -g <resource-group>
# View deployment status
azd statusRules
✅ Use parameterized Bicep with defaults ✅ Use managed identity where possible ✅ Store secrets in Key Vault or Container App secrets ✅ Use resource tokens for unique naming
🚫 Never hardcode connection strings 🚫 Never commit .env files 🚫 Never use owner role when contributor suffices
Before you install
- Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
- Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
- Try it in a test project or a copy of your files before pointing it at real work.
- Pin the version you tested, and review changes before updating.
- Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.
FAQ
What is Infrastructure Engineer?
Infrastructure Engineer is a subagent for Claude Code and Claude Cowork from the microsoft/skills repository on GitHub. Azure and Bicep specialist for CoreAI DIY infrastructure, deployments, and DevOps
How do I install Infrastructure Engineer in Claude Code?
Download infrastructure.agent.md from the repository. Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control. Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.
Can I use Infrastructure Engineer in Claude Cowork?
Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent. Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.
Is Infrastructure Engineer safe to install?
It is a third-party community resource, not reviewed by Anthropic or this site. Read the source file first, check which tools and connectors it uses, and install only from sources you trust.
Similar resources
- Azure Microsoft Azure MCP and Skills integration for cloud resource management, deployments, and Azure services. Manage your Azure infrastructure, monitor applications, and deploy resources directly from Claude Code. Plugin · microsoft/skills
- Azure Sdk Dotnet Azure SDK patterns and best practices for .NET developers covering AI, resource management, identity, messaging, and Key Vault libraries. Plugin · microsoft/skills
- Azure Sdk Rust Azure SDK patterns and best practices for Rust developers covering identity, Key Vault, storage, Cosmos DB, and Event Hubs. Plugin · microsoft/skills
- Backend Developer FastAPI/Python specialist for CoreAI DIY backend development with Pydantic, Cosmos DB, and Azure services Subagent · microsoft/skills
- Planner Read-only planning specialist that analyzes requirements, explores the codebase, and creates detailed implementation plans before coding begins Subagent · microsoft/skills
- Frontend Developer React/TypeScript specialist for CoreAI DIY frontend development with React Flow, Zustand, and Tailwind CSS Subagent · microsoft/skills
- Presenter Mode Developer Specialist for CoreAI DIY presenter mode features, including presentation view, navigation, and teleprompter functionality Subagent · microsoft/skills
- Project Scaffolder Full-stack Azure AI Foundry application scaffolder for React + FastAPI + azd projects Subagent · microsoft/skills