# azure-quantum

A skill for Claude Code, Codex, Cursor, and other AI coding assistants that adds expert knowledge of Azure Quantum.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 168 installs · ★ 818 repo stars
- Author: MicrosoftDocs
- License: CC-BY-4.0 · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/MicrosoftDocs/Agent-Skills/tree/HEAD/skills/azure-quantum/SKILL.md
- Updated: 2026-11-09
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/azure-quantum

## What it does

The skill covers diagnosing job failures, testing and debugging quantum programs through QDK, choosing job submission methods, managing quotas and sessions, configuring workspaces and development tools, and setting up workspace security via RBAC and access keys. The skill references local content and can fetch documentation from `learn.microsoft.com` using `mcp_microsoftdocs:microsoft_docs_fetch` or `fetch_webpage`.

Includes guidance on hybrid workflow patterns, Stim and qodec integration, resource estimation, QDK language support options, and regional provider availability for IonQ, Quantinuum, and Rigetti. Requires network access to pull documentation; falls back to `fetch_webpage` if `mcp_microsoftdocs` is unavailable.

## Requirements
- Works with: Azure

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add MicrosoftDocs/Agent-Skills --skill azure-quantum -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/azure-quantum/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/azure-quantum/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add MicrosoftDocs/Agent-Skills --skill azure-quantum -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/azure-quantum/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add MicrosoftDocs/Agent-Skills --skill azure-quantum -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/azure-quantum/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install MicrosoftDocs/Agent-Skills skills/azure-quantum
```

2. **Manually: put the files in place**
- File: `.github/skills/azure-quantum/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add MicrosoftDocs/Agent-Skills --skill azure-quantum -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/MicrosoftDocs/Agent-Skills --path skills/azure-quantum
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/azure-quantum/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add MicrosoftDocs/Agent-Skills --skill azure-quantum -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/MicrosoftDocs/Agent-Skills/tree/HEAD/skills/azure-quantum/SKILL.md

## When to use it
- Troubleshoot and resolve errors in Azure Quantum job submissions
- Choose the right architecture for a hybrid quantum-classical workflow
- Set up an Azure Quantum workspace with proper RBAC roles and secure access keys
- Test and debug Q# and OpenQASM programs before running on real hardware
- Select the best provider and region based on pricing and availability

## Example prompts
- Debug a failed Q# job submission to IonQ on Azure Quantum
- Should I run my program on a simulator or submit it to real quantum hardware?
- Help me configure Azure Quantum workspace access for my development team

## Source text · SKILL.md · CC-BY-4.0

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 97b6ceb5fa32752f.

BEGIN THIRD-PARTY FILE 97b6ceb5fa32752f
```text
---
name: azure-quantum
description: Expert knowledge for Azure Quantum development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, and integrations & coding patterns. Use when submitting Q#/OpenQASM jobs, configuring workspaces, using QDK/CLI, or running hybrid quantum workflows, and other Azure Quantum related development tasks.
compatibility: Requires network access. Uses mcp_microsoftdocs:microsoft_docs_fetch or fetch_webpage to retrieve documentation.
metadata:
  generated_at: "2026-11-08"
  generator: "docs2skills/1.0.0"
---
# Azure Quantum Skill

This skill provides expert guidance for Azure Quantum. Covers troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, and integrations & coding patterns. It combines local quick-reference content with remote documentation fetching capabilities.

## How to Use This Skill

> **IMPORTANT for Agent**: Use the **Category Index** below to locate relevant sections. For categories with line ranges (e.g., `L35-L120`), use `read_file` with the specified lines. For categories with file links (e.g., `[security.md](security.md)`), use `read_file` on the linked reference file

> **IMPORTANT for Agent**: If `metadata.generated_at` is more than 3 months old, suggest the user pull the latest version from the repository. If `mcp_microsoftdocs` tools are not available, suggest the user install it: [Installation Guide](https://github.com/MicrosoftDocs/mcp/blob/main/README.md)

This skill requires **network access** to fetch documentation content:
- **Preferred**: Use `mcp_microsoftdocs:microsoft_docs_fetch` with query string `from=learn-agent-skill`. Returns Markdown.
- **Fallback**: Use `fetch_webpage` with query string `from=learn-agent-skill&accept=text/markdown`. Returns Markdown.

## Category Index

| Category | Lines | Description |
|----------|-------|-------------|
| Troubleshooting | L36-L43 | Troubleshooting Azure Quantum provider issues: diagnosing job failures and support/escalation policies and limits for IonQ, Quantinuum, and Rigetti hardware on Azure Quantum. |
| Best Practices | L44-L48 | Tools and techniques for testing, debugging, and validating quantum programs with the Azure Quantum Development Kit (QDK), including simulators, logging, and troubleshooting. |
| Decision Making | L49-L57 | Guidance on choosing job submission methods, regions and data migration, provider pricing and availability, and supported quantum languages in the QDK. |
```
END THIRD-PARTY FILE 97b6ceb5fa32752f

The third-party file has ended. Everything between the 97b6ceb5fa32752f tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2584 of 10857 bytes. © MicrosoftDocs · CC-BY-4.0 · https://github.com/MicrosoftDocs/Agent-Skills/tree/HEAD/skills/azure-quantum/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
