agentleFS
Sign inStart free
Microsoft AzureKnown publisherAzure/ai-infrastructure-on-azure/.github/copilot-instructions.md

ai-infrastructure-on-azure

Copilot instructions30 starsChanged 6 months agoMITView on GitHub

This repository is operated with a skill-first workflow for Azure CycleCloud Workspace for Slurm and AKS clusters with NVIDIA GPU nodes. For any cluster operations, validation, or troubleshooting request: If the user invokes the skill explicitly with /ai-infra <request>, treat that as an explicit invocation and follow the same workflow. Canonical source (symlink target) is skills/ai-infra/. For operational responses, follow this structure:

  • Where files are headingNew Copilot instructions files have more rules about branches and pull requests, and fewer about code style.

    Of the Copilot instructions files we read, the 2,336 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repository2 other files it gives its agents.

The file

We split this copilot-instructions.md into the rules it gives an agent

5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use the local skill at .copilot/skills/ai-infra/SKILL.md first.

    line 9
  2. Very specific:

    Read the index in that SKILL.md to identify which reference files in .copilot/skills/ai-infra/references/ to load.

    line 10
  3. Distinctive:

    Do not provide generic HPC advice when a reference exists for that task.

    line 12
  4. Distinctive:

    If required inputs are missing (SKU, nodelist, cluster name, orchestrator, failing job details), ask for them explicitly.

    line 13
  5. Very specific:

    If the user invokes the skill explicitly with /ai-infra <request>, treat that as an explicit invocation and follow the same workflow.

    line 15

≈ “Common” is an estimate: at least 1 in 5 of the 3,779 Copilot instructions files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
copilot-instructions.md

Azure HPC GPU Cluster Operations (Skill-First)

This repository is operated with a skill-first workflow for Azure CycleCloud Workspace for Slurm and AKS clusters with NVIDIA GPU nodes.

Mandatory Behavior

For any cluster operations, validation, or troubleshooting request:

  1. Use the local skill at .copilot/skills/ai-infra/SKILL.md first.
  2. Read the index in that SKILL.md to identify which reference files in .copilot/skills/ai-infra/references/ to load.
  3. Execute commands and thresholds from the selected reference files only.
  4. Do not provide generic HPC advice when a reference exists for that task.
  5. If required inputs are missing (SKU, nodelist, cluster name, orchestrator, failing job details), ask for them explicitly.

If the user invokes the skill explicitly with /ai-infra <request>, treat that as an explicit invocation and follow the same workflow.

Local Skill Layout

.copilot/skills/ai-infra/
  SKILL.md                              # router + index + cross-cutting rules
  references/
    sku_baselines.md
    rack_topology.md
    ib_validation.md
    nccl_test.md
    nccl_diagnosis.md
    gpu_validation.md
    thermal_test.md
    outlier_detection.md
    ghr.md                              # Azure Guest Health Reporting
    node_drain_and_replace.md

Canonical source (symlink target) is skills/ai-infra/.

Response Contract

For operational responses, follow this structure:

  1. Selected reference files
  2. Ordered run plan
  3. Exact commands
  4. Pass/fail thresholds
  5. Action decision (continue, isolate, drain, reboot, GHR with specific impact category)

Test Script Paths

  • infrastructure_validations/slurm/NCCL/ — NCCL all_reduce_perf launcher with per-SKU configs
  • infrastructure_validations/slurm/gpu_test/ — GPU GEMM benchmark (ubergemm)
  • infrastructure_validations/slurm/thermal_test/ — Thermal stress test (dcgmproftester)
  • infrastructure_validations/aks/NCCL/ — NCCL on AKS
  • infrastructure_validations/aks/NHC/ — Node Health Check on AKS
  • infrastructure_validations/aks/fio/ — Storage I/O test on AKS

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free