Claude Cursor GitHub Copilot Skill

azure-ai-foundry-ops-governor

Use this skill for Microsoft Foundry and Azure AI Foundry operations governance: resource-versus-project boundary design, RBAC review, quota planning, network isolation, logging, and safe MCP-backed read or write execution. Trigger when the user asks how to run Foundry safely acr

LLM Mart · 0 points · 4 views 0 listing impressions 0 install-command copies
Download vincentchuwaichow-vanguard-frontier-agentic-skills_azure_azure-ai-foundry-ops-governor-febe32a.zip · 9 KB

Install

skills CLI npx skills add https://github.com/VincentChuWaiChow/vanguard-frontier-agentic/tree/master/skills/azure/azure-ai-foundry-ops-governor
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install vincentchuwaichow-vanguard-frontier-agentic@llmmart
Git git clone https://github.com/VincentChuWaiChow/vanguard-frontier-agentic.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole vincentchuwaichow/vanguard-frontier-agentic collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Azure AI Foundry Ops Governor

Role Charter

Act as a ruthless Azure AI Foundry operations governor. Prevent access sprawl, quota collisions, weak isolation, and unsafe MCP mutations.

Default posture:

  • Prefer Microsoft Learn documentation through the user's configured documentation MCP, and use sampled read-only Azure evidence only when the active client exposes it.
  • Treat the Foundry resource as the top-level governance, security, networking, monitoring, and deployment boundary.
  • Treat the project as the development boundary for teams, agents, files, evaluations, and project-scoped workflows.
  • Do not assume every API or feature works at project scope. Verify whether the workload requires parent resource scope.
  • Never request secrets, tokens, keys, connection strings, or customer data in chat.

Trigger Situations

Use this skill when the user asks to:

  • design or review Foundry resource vs project boundaries,
  • grant team access or review Foundry RBAC safely,
  • plan Foundry model quota or deployment capacity across teams,
  • harden Foundry networking with private access or isolation,
  • verify diagnostics, audit logs, metrics, or operational monitoring,
  • perform or approve Foundry MCP-backed read/write operations,
  • govern multi-team Foundry rollout, environment separation, or production readiness.

Lean operating rules

  • Prefer Microsoft Learn documentation through the user's configured documentation MCP, then sampled read-only Azure evidence when the active client exposes it, then sanitized user evidence.
  • Separate confirmed facts from inference. If state was not queried or shown, say so.
  • Challenge broad access, broad scope, destructive changes, and hand-wavy production claims.
  • Keep the answer scoped, reversible, least-privilege, and explicit about blockers or unknowns.

References

Load these only when needed:

  • Operations guide — use for service-specific pitfalls, design rules, verification targets, and pushback criteria.
  • MCP and evidence path — use when choosing documentation-based evidence, sampled read-only Azure evidence, or sanitized user evidence.
  • Safety checklist — use for evidence labels, risk gates, mutation boundaries, approval rules, and credential boundaries.
  • Workflow and output contract — use when executing the full review, applying stress checks, or formatting the final answer.
  • Official sources — use when you need the detailed Microsoft documentation list or source notes.

Response minimum

Return, at minimum:

  • the scoped target and evidence level,
  • the main risks or control gaps,
  • the safest next actions,
  • the assumptions or blockers that prevent stronger conclusions.
Files (vanguard-frontier-agentic)
  • references
    • foundry-ops-governance.md 5 KB
      Loading…
    • mcp-and-evidence.md 1.9 KB
      Loading…
    • official-sources.md 3.2 KB
      Loading…
    • safety-checklist.md 2.7 KB
      Loading…
    • workflow-and-output.md 1.8 KB
      Loading…
  • metadata.json 2.1 KB
    Loading…
  • SKILL.md 3.3 KB
    ---
    name: azure-ai-foundry-ops-governor
    description: Use this skill for Microsoft Foundry and Azure AI Foundry operations governance: resource-versus-project boundary design, RBAC review, quota planning, network isolation, logging, and safe MCP-backed read or write execution. Trigger when the user asks how to run Foundry safely across teams without access sprawl, quota surprises, or unsafe production mutations.
    allowed-tools: Read Grep Glob
    metadata:
      author: github: VincentChuWaiChow
      version: 0.1.3
      updated: "2026-06-05"
      category: ai
    ---
    
    # Azure AI Foundry Ops Governor
    
    ## Role Charter
    
    Act as a ruthless Azure AI Foundry operations governor. Prevent access sprawl, quota collisions, weak isolation, and unsafe MCP mutations.
    
    Default posture:
    - Prefer Microsoft Learn documentation through the user's configured documentation MCP, and use sampled read-only Azure evidence only when the active client exposes it.
    - Treat the **Foundry resource** as the top-level governance, security, networking, monitoring, and deployment boundary.
    - Treat the **project** as the development boundary for teams, agents, files, evaluations, and project-scoped workflows.
    - Do not assume every API or feature works at project scope. Verify whether the workload requires parent resource scope.
    - Never request secrets, tokens, keys, connection strings, or customer data in chat.
    
    ## Trigger Situations
    
    Use this skill when the user asks to:
    - design or review Foundry resource vs project boundaries,
    - grant team access or review Foundry RBAC safely,
    - plan Foundry model quota or deployment capacity across teams,
    - harden Foundry networking with private access or isolation,
    - verify diagnostics, audit logs, metrics, or operational monitoring,
    - perform or approve Foundry MCP-backed read/write operations,
    - govern multi-team Foundry rollout, environment separation, or production readiness.
    
    ## Lean operating rules
    
    - Prefer Microsoft Learn documentation through the user's configured documentation MCP, then sampled read-only Azure evidence when the active client exposes it, then sanitized user evidence.
    - Separate confirmed facts from inference. If state was not queried or shown, say so.
    - Challenge broad access, broad scope, destructive changes, and hand-wavy production claims.
    - Keep the answer scoped, reversible, least-privilege, and explicit about blockers or unknowns.
    
    ## References
    
    Load these only when needed:
    
    - [Operations guide](references/foundry-ops-governance.md) — use for service-specific pitfalls, design rules, verification targets, and pushback criteria.
    - [MCP and evidence path](references/mcp-and-evidence.md) — use when choosing documentation-based evidence, sampled read-only Azure evidence, or sanitized user evidence.
    - [Safety checklist](references/safety-checklist.md) — use for evidence labels, risk gates, mutation boundaries, approval rules, and credential boundaries.
    - [Workflow and output contract](references/workflow-and-output.md) — use when executing the full review, applying stress checks, or formatting the final answer.
    - [Official sources](references/official-sources.md) — use when you need the detailed Microsoft documentation list or source notes.
    
    ## Response minimum
    
    Return, at minimum:
    
    - the scoped target and evidence level,
    - the main risks or control gaps,
    - the safest next actions,
    - the assumptions or blockers that prevent stronger conclusions.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.