Official agent skill

Dev Setup

Set up the local development environment for APIView Copilot.

OfficialMITAuto-check: notesBackend & APIs

Install Dev Setup

skills CLI

$ npx skills add Azure/azure-sdk-tools --skill dev-setup -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install Azure/azure-sdk-tools dev-setup --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/Azure/azure-sdk-tools.git skills-src && mkdir -p .claude/skills && cp -r skills-src/packages/python-packages/apiview-copilot/.github/skills/dev-setup .claude/skills/dev-setup && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "dev-setup" agent skill from https://github.com/Azure/azure-sdk-tools/tree/main/packages/python-packages/apiview-copilot/.github/skills/dev-setup into .claude/skills/dev-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dev-setup", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/Azure/azure-sdk-tools/tree/main/packages/python-packages/apiview-copilot/.github/skills/dev-setup

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add Azure/azure-sdk-tools --skill dev-setup -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install Azure/azure-sdk-tools dev-setup --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Azure/azure-sdk-tools.git skills-src && mkdir -p .agents/skills && cp -r skills-src/packages/python-packages/apiview-copilot/.github/skills/dev-setup .agents/skills/dev-setup && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "dev-setup" agent skill from https://github.com/Azure/azure-sdk-tools/tree/main/packages/python-packages/apiview-copilot/.github/skills/dev-setup into .agents/skills/dev-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dev-setup", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Azure/azure-sdk-tools --skill dev-setup -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install Azure/azure-sdk-tools dev-setup --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Azure/azure-sdk-tools.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/packages/python-packages/apiview-copilot/.github/skills/dev-setup .cursor/skills/dev-setup && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "dev-setup" agent skill from https://github.com/Azure/azure-sdk-tools/tree/main/packages/python-packages/apiview-copilot/.github/skills/dev-setup into .cursor/skills/dev-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dev-setup", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/Azure/azure-sdk-tools.git --path packages/python-packages/apiview-copilot/.github/skills/dev-setup

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add Azure/azure-sdk-tools --skill dev-setup -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install Azure/azure-sdk-tools dev-setup --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Azure/azure-sdk-tools.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/packages/python-packages/apiview-copilot/.github/skills/dev-setup .gemini/skills/dev-setup && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "dev-setup" agent skill from https://github.com/Azure/azure-sdk-tools/tree/main/packages/python-packages/apiview-copilot/.github/skills/dev-setup into .gemini/skills/dev-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dev-setup", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install Azure/azure-sdk-tools dev-setup

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add Azure/azure-sdk-tools --skill dev-setup -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/Azure/azure-sdk-tools.git skills-src && mkdir -p .github/skills && cp -r skills-src/packages/python-packages/apiview-copilot/.github/skills/dev-setup .github/skills/dev-setup && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "dev-setup" agent skill from https://github.com/Azure/azure-sdk-tools/tree/main/packages/python-packages/apiview-copilot/.github/skills/dev-setup into .github/skills/dev-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dev-setup", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Azure/azure-sdk-tools --skill dev-setup -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install Azure/azure-sdk-tools dev-setup --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Azure/azure-sdk-tools.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/packages/python-packages/apiview-copilot/.github/skills/dev-setup .opencode/skills/dev-setup && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "dev-setup" agent skill from https://github.com/Azure/azure-sdk-tools/tree/main/packages/python-packages/apiview-copilot/.github/skills/dev-setup into .opencode/skills/dev-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dev-setup", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: dev-setup
GitHub stars: 134
Token cost: ~546 tokens
SKILL.md length: 183 words
Files: 1
Skills in repo: 35
Repo updated: Oct 6, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Set up the local development environment for APIView Copilot.

Works in 5 steps: Create and activate a virtual environment → Install dependencies → Create the .env file → …
Environment setup
SKILL.md covers Procedure and Gotchas
Calls python, pip and pytest

What it does

Dev Setup is an agent skill from Azure/azure-sdk-tools, published by the product's own GitHub organization. Set up the local development environment for APIView Copilot. Use for: dev setup, environment setup, install dependencies, create venv, configure env, permissions, get started, onboarding, new developer, RBAC setup, .env file.

Its SKILL.md is about 550 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Backend & APIs, covering Authorization and RBAC. It works with Microsoft Azure, Azure Cosmos DB and Azure AI Search. The repository describes itself as: Tools repository leveraged by the Azure SDK team. The licence is MIT.

When your agent uses it

Environment setup
Install dependencies

Example prompts

“/dev-setup”

Requirements

Python 3

Workflow steps

5 steps, taken from the step headings in SKILL.md.

Create and activate a virtual environment
Install dependencies
Create the .env file
Grant Azure RBAC permissions
Verify the setup

What it can do on your machine

Read from SKILL.md and the folder at commit 69f4006. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- python
- pip
- pytest
- az
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use pip and az, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Dev Setup loads about 546 tokens when it runs. Until then it costs about 59 tokens; SKILL.md has 183 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~59
When it runs · the whole SKILL.md, loaded when a task matches: ~546

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

NoteMentions a .env fileSKILL.md:3

, onboarding, new developer, RBAC setup, .env file."

NoteMentions a .env fileSKILL.md:32
```
### 3. Create the `.env` file
```

NoteMentions a .env fileSKILL.md:34

Create a `.env` file in the project root with:

NoteMentions a .env fileSKILL.md:76

- **Staging vs production** — The `.env` defaults to staging. To use production, swap to the production App Config endpo

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Azure/azure-sdk-tools at commit 69f4006, republished under its MIT licence (© Azure). 183 words, ~546 tokens.

Download SKILL.mdSave it as .claude/skills/dev-setup/SKILL.md (or your agent's skills folder).

name: dev-setup
description: Set up the local development environment for APIView Copilot. Use for: dev setup, environment setup, install dependencies, create venv, configure env, permissions, get started, onboarding, new developer, RBAC setup, .env file.

Development Environment Setup

Procedure

1. Create and activate a virtual environment

bash

# Windows
python -m venv .venv
.venv\Scripts\activate

# Linux/macOS
python -m venv .venv
source .venv/bin/activate

2. Install dependencies

bash

# Runtime + dev + eval dependencies
pip install -r dev_requirements.txt

# Runtime only
pip install -r requirements.txt

3. Create the `.env` file

Create a .env file in the project root with:

ENVIRONMENT_NAME="staging"

All other settings (Cosmos DB, Search, Key Vault, etc.) are resolved from App Configuration at runtime.

4. Grant Azure RBAC permissions

bash

avc ops grant

This grants your identity the required roles:

App Configuration Data Reader on avc-appconfig-staging
Search Index Data Reader on Azure AI Search
Cosmos DB Contributor on avc-cosmos-staging
Key Vault access on avc-vault-staging
Cognitive Services OpenAI User on azsdk-engsys-openai
Azure AI User on azsdk-engsys-ai

Pass --assignee-id <ID> to grant to a specific user instead of yourself.

5. Verify the setup

bash

# Run unit tests
pytest tests

# Generate a review (needs a test API view file in scratch/apiviews/<lang>/)
avc review generate -l python -t scratch/apiviews/python/test.txt

# Health check the deployed service
avc ops check

Gotchas

Always activate the venv before running any commands (avc, pytest, pylint, etc.)
avc not found? Use .\avc on Windows PowerShell, or ensure the project root is in your PATH
ModuleNotFoundError: prompty — You're running outside the venv. Activate it first.
Azure auth errors — Run az login first, then avc ops grant to set up RBAC
Staging vs production — The .env defaults to staging. To use production, swap to the production App Config endpoint and set ENVIRONMENT_NAME="production"

Files

Just SKILL.md in packages/python-packages/apiview-copilot/.github/skills/dev-setup of Azure/azure-sdk-tools.

Open the folder on GitHubat commit 69f4006

Compare with similar skills

Dev Setup next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Dev Setup compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Dev Setup this skillAzure/azure-sdk-tools	134	—	~546	Automated safety check: Notes	MIT	yesterday
Azure Resource Manager Cosmosdb Dotnetmicrosoft/skills	3.1k	5 repos	~2.1k	Automated safety check: Pass	MIT	yesterday
Azure Cache RedisMicrosoftDocs/Agent-Skills	775	—	~2.9k	Automated safety check: Pass	CC-BY-4.0	yesterday
API Security Designvinayaklatthe/microsoft-security-skills	175	—	~2.2k	Automated safety check: Pass	MIT	3 mo ago
Iam Auditbriiirussell/cybersecurity-skills	412	—	~3.1k	Automated safety check: Notes	MIT	4 mo ago
Apex Azure Rbacjonathan-vella/apex	217	—	~1.8k	Automated safety check: Pass	MIT	today

Similar skills

Azure Resource Manager Cosmosdb Dotnet
microsoft/skills
Official
Azure Resource Manager SDK for Cosmos DB in .NET. An agent skill from microsoft/skills.
3.1k GitHub starsUsed in 5 repos~2.1k tokens
Backend & APIsAuto-check passed
Azure Cache Redis
MicrosoftDocs/Agent-Skills
Official
Expert knowledge for Azure Cache for Redis development including troubleshooting, best practices, decision making, architecture & design patterns, security, configuration, and deployment.
775 GitHub stars~2.9k tokensUpdated yesterday
DatabasesAuto-check passed
API Security Design
vinayaklatthe/microsoft-security-skills
Guidance for designing secure APIs on Azure - authentication, authorization, gateway controls, input validation, rate limiting, secret management, and runtime threat detection - aligned to OWASP API…
175 GitHub stars~2.2k tokensUpdated 3 mo ago
Backend & APIsAuto-check passed
Iam Audit
briiirussell/cybersecurity-skills
Audit, design, and migrate Identity and Access Management — cloud provider IAM (AWS, GCP, Azure), identity providers (Okta, Entra ID / Azure AD, Auth0, Google Workspace), application authorization…
412 GitHub stars~3.1k tokensUpdated 4 mo ago
Backend & APIsAuto-check: notes
Apex Azure Rbac
jonathan-vella/apex
ANALYSIS SKILL — Find the right Azure RBAC role for an identity with least-privilege access; generate CLI, Bicep, and Terraform code to assign it.
217 GitHub stars~1.8k tokensUpdated today
Backend & APIsAuto-check passed
Writing Bicep Templates
microsoft-foundry/foundry-agent-webapp
Provides Bicep coding standards for Azure infrastructure in this repository.
127 GitHub stars~1.2k tokensUpdated 5 mo ago
Backend & APIsAuto-check passed

Questions about Dev Setup

What does Dev Setup do?

Set up the local development environment for APIView Copilot. Dev Setup is an agent skill from Azure/azure-sdk-tools, published by the product's own GitHub organization. Set up the local development environment for APIView Copilot.

When should I use Dev Setup?

Dev Setup fits situations like: environment setup; install dependencies.

How do I install Dev Setup in Claude Code?

Run `npx skills add Azure/azure-sdk-tools --skill dev-setup -a claude-code`. Or copy the skill folder (packages/python-packages/apiview-copilot/.github/skills/dev-setup in Azure/azure-sdk-tools) into .claude/skills/dev-setup in your project. Claude Code loads it when a task matches its description.

How do I install Dev Setup in Codex?

Run `npx skills add Azure/azure-sdk-tools --skill dev-setup -a codex`. Or copy the skill folder (packages/python-packages/apiview-copilot/.github/skills/dev-setup in Azure/azure-sdk-tools) into .agents/skills/dev-setup in your project. Codex loads it when a task matches its description.

Can I use Dev Setup in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Azure/azure-sdk-tools --skill dev-setup -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/dev-setup, .gemini/skills/dev-setup, .github/skills/dev-setup and .opencode/skills/dev-setup in your project.

What does Dev Setup need to run?

Going by SKILL.md and its folder, Dev Setup needs the command-line tools its instructions call (python, pip, pytest and az). Our summary lists: Python 3.

Does Dev Setup access the network?

SKILL.md contains no URLs. Its commands use pip, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Dev Setup safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Dev Setup use?

Dev Setup is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Dev Setup use?

About 546 tokens (SKILL.md is roughly 2.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Dev Setup?

Skills that share tags, products or a category with Dev Setup: Azure Resource Manager Cosmosdb Dotnet (microsoft/skills, 3.1k stars), Azure Cache Redis (MicrosoftDocs/Agent-Skills, 775 stars), API Security Design (vinayaklatthe/microsoft-security-skills, 175 stars) and Iam Audit (briiirussell/cybersecurity-skills, 412 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Dev Setup?

Azure (a GitHub organization, an official publisher) maintains it in Azure/azure-sdk-tools, which has 134 GitHub stars. The repository holds 35 skills in this directory. The repository was last updated on October 6, 2026.

Source: Azure/azure-sdk-tools on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Dev Setup

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Development Environment Setup

Procedure

1. Create and activate a virtual environment

2. Install dependencies

3. Create the .env file

4. Grant Azure RBAC permissions

5. Verify the setup

Gotchas

Files

Compare with similar skills

Similar skills

More from Azure/azure-sdk-tools

Related

Questions about Dev Setup

3. Create the `.env` file