Sensei
Invoke Microsoft’s Azure-skills “sensei” pack entry when your agent needs Azure-oriented guidance and workflows from the official repo.
Overview
Sensei is an agent skill most often used in Build (also Ship, Operate) that provides Azure-focused procedural guidance from Microsoft’s azure-skills collection for agent-assisted cloud work.
Install
npx skills add https://github.com/microsoft/azure-skills --skill senseiWhat is this skill?
- Official skill from the microsoft/azure-skills GitHub collection
- Listed on skills.sh as “sensei” for Azure-focused agent assistance
- Fits agentic workflows that pair coding tools with cloud provisioning and operations tasks
- Installable via the azure-skills source URL referenced in catalog metadata
- Sparse public SKILL.md body—treat capabilities as Azure mentor/orchestration until docs expand
Adoption & trust: 951 installs on skills.sh; 1.2k GitHub stars.
What problem does it solve?
You are building or running on Azure and need a packaged agent skill identity instead of ad-hoc cloud prompts scattered across chat threads.
Who is it for?
Solo builders using Claude Code, Cursor, or Codex who already target Azure and want the official sensei skill slug in their skills path.
Skip if: Teams on other clouds only, or users who require fully documented step lists in SKILL.md before trusting automation.
When should I use this skill?
When implementing or operating workloads on Azure and you want the sensei skill from microsoft/azure-skills loaded for agent-guided cloud workflows.
What do I get? / Deliverables
Your agent loads the sensei skill from azure-skills so Azure tasks follow a consistent, repo-maintained procedure set you can repeat across sessions.
- Agent-executed Azure workflow steps per sensei SKILL.md in your installed copy
- Repeatable cloud task playbooks referenced from the azure-skills repo
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Build/integrations is the canonical first shelf because Azure skills most often wire services, APIs, and cloud resources while you are constructing the product. Integrations subphase matches connecting apps and agents to Azure APIs, identity, and managed services during implementation.
Where it fits
Hook your API to Azure App Service or Functions using sensei-guided steps from azure-skills.
Run pre-launch cloud checks with agent procedures before exposing production endpoints.
Iterate scaling or config changes with a consistent Azure mentor skill instead of fragmented chat advice.
How it compares
A cloud mentor skill package from Microsoft’s azure-skills repo—not a standalone MCP server or generic DevOps checklist.
Common Questions / FAQ
Who is sensei for?
Sensei is for indie developers and small teams that deploy on Azure and want an agent-loadable skill from Microsoft’s azure-skills project.
When should I use sensei?
Use it during Build/integrations when wiring Azure services, during Ship when validating cloud launch steps, and during Operate/infra when iterating deployments—whenever your agent should follow Azure-skills procedures instead of one-off prompts.
Is sensei safe to install?
Install from the official microsoft/azure-skills source linked on this page, then review the Security Audits panel here and inspect SKILL.md and scripts in your checkout before granting shell or network access.
SKILL.md
READMESKILL.md - Sensei
# sensei Installs: 951 Source: microsoft/azure-skills { "id": "microsoft/azure-skills/sensei", "url": "https://www.skills.sh/microsoft/azure-skills/sensei", "name": "sensei", "slug": "sensei", "source": "microsoft/azure-skills", "installs": 951, "installUrl": "https://github.com/microsoft/azure-skills", "sourceType": "github" }