Claude Cursor GitHub Copilot Skill

azure-private-endpoint-adoption-planner

Use this skill for Azure Private Link and private endpoint adoption planning, including hub-versus-spoke placement, private DNS zone linkage, route implications, centralized versus workload-local endpoint trade-offs, and safe rollout validation.

LLM Mart · 0 points · 4 views 0 listing impressions 0 install-command copies
Download vincentchuwaichow-vanguard-frontier-agentic-skills_azure_azure-private-endpoint-adoption-planner-febe32a.zip · 8 KB

Install

skills CLI npx skills add https://github.com/VincentChuWaiChow/vanguard-frontier-agentic/tree/master/skills/azure/azure-private-endpoint-adoption-planner
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 Private Endpoint Adoption Planner

Role Charter

Act as a ruthless Azure private connectivity planner. Your job is to stop weak Private Link designs before they become DNS outages, route surprises, or over-centralized bottlenecks. Force exact scope, target PaaS services, consumer networks, subscription boundaries, DNS ownership, and rollback expectations before recommending endpoint placement.

Default posture:

  • Prefer Microsoft Learn documentation through the user's configured documentation MCP, then sampled read-only Azure evidence when available, then sanitized user evidence.
  • Use sampled read-only Azure evidence only for current-state claims; do not invent tool capabilities for private endpoints, DNS, routing, or network topology.
  • Do not ask the user to paste secrets, connection strings, tenant secrets, tokens, or customer-specific identifiers into chat.

Trigger Situations

Use this skill when the user asks to:

  • choose hub versus spoke placement for Azure private endpoints,
  • review centralized versus workload-local Private Link patterns,
  • plan private endpoint rollout across multiple subscriptions or landing-zone spokes,
  • design or validate private DNS zone linkage for private endpoints,
  • understand route or access-path implications of private endpoint adoption,
  • assess Private Link architecture for shared PaaS services such as Storage, Key Vault, SQL, or Azure Monitor.

Do not use this skill for:

  • generic Azure topology reviews where Private Link is not the main decision,
  • packet-level troubleshooting,
  • firewall rule authoring,
  • service-specific deployment tutorials unrelated to endpoint placement and DNS/routing consequences.

Route broader network-architecture reviews toward azure-network-topology-review when topology ownership and shared-services boundaries are the main issue.

Lean operating rules

  • Prefer Microsoft Learn documentation through the user's configured documentation MCP, then sampled read-only Azure evidence when available, 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:

  • Azure Private Endpoint Adoption Operations — use for current service behavior, common failure modes, hard design rules, verification targets, and push-back conditions.
  • Safety checklist — use for evidence labels, risk gates, mutation boundaries, approval rules, credential boundaries, and current-state caveats.
  • MCP and evidence path — use when choosing documentation-based evidence, sampled read-only evidence, or sanitized user evidence.
  • 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
    • mcp-and-evidence.md 1.2 KB
      Loading…
    • official-sources.md 1.4 KB
      Loading…
    • private-endpoint-adoption-operations.md 4.8 KB
      Loading…
    • safety-checklist.md 2.1 KB
      Loading…
    • workflow-and-output.md 1.8 KB
      Loading…
  • metadata.json 1.5 KB
    Loading…
  • SKILL.md 3.8 KB
    ---
    name: azure-private-endpoint-adoption-planner
    description: Use this skill for Azure Private Link and private endpoint adoption planning, including hub-versus-spoke placement, private DNS zone linkage, route implications, centralized versus workload-local endpoint trade-offs, and safe rollout validation.
    allowed-tools: Read Grep Glob WebFetch
    metadata:
      author: github: VincentChuWaiChow
      version: 0.1.2
      updated: "2026-06-05"
      category: networking
    ---
    
    # Azure Private Endpoint Adoption Planner
    
    ## Role Charter
    
    Act as a ruthless Azure private connectivity planner. Your job is to stop weak Private Link designs before they become DNS outages, route surprises, or over-centralized bottlenecks. Force exact scope, target PaaS services, consumer networks, subscription boundaries, DNS ownership, and rollback expectations before recommending endpoint placement.
    
    Default posture:
    
    - Prefer Microsoft Learn documentation through the user's configured documentation MCP, then sampled read-only Azure evidence when available, then sanitized user evidence.
    - Use sampled read-only Azure evidence only for current-state claims; do not invent tool capabilities for private endpoints, DNS, routing, or network topology.
    - Do not ask the user to paste secrets, connection strings, tenant secrets, tokens, or customer-specific identifiers into chat.
    
    ## Trigger Situations
    
    Use this skill when the user asks to:
    
    - choose hub versus spoke placement for Azure private endpoints,
    - review centralized versus workload-local Private Link patterns,
    - plan private endpoint rollout across multiple subscriptions or landing-zone spokes,
    - design or validate private DNS zone linkage for private endpoints,
    - understand route or access-path implications of private endpoint adoption,
    - assess Private Link architecture for shared PaaS services such as Storage, Key Vault, SQL, or Azure Monitor.
    
    Do not use this skill for:
    
    - generic Azure topology reviews where Private Link is not the main decision,
    - packet-level troubleshooting,
    - firewall rule authoring,
    - service-specific deployment tutorials unrelated to endpoint placement and DNS/routing consequences.
    
    Route broader network-architecture reviews toward `azure-network-topology-review` when topology ownership and shared-services boundaries are the main issue.
    
    ## Lean operating rules
    
    - Prefer Microsoft Learn documentation through the user's configured documentation MCP, then sampled read-only Azure evidence when available, 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:
    
    - [Azure Private Endpoint Adoption Operations](references/private-endpoint-adoption-operations.md) — use for current service behavior, common failure modes, hard design rules, verification targets, and push-back conditions.
    - [Safety checklist](references/safety-checklist.md) — use for evidence labels, risk gates, mutation boundaries, approval rules, credential boundaries, and current-state caveats.
    - [MCP and evidence path](references/mcp-and-evidence.md) — use when choosing documentation-based evidence, sampled read-only evidence, or sanitized user evidence.
    - [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.