# microsoft-events

Connects your project to the Microsoft Build and Ignite session catalog: reads your dependencies, finds relevant talks, and helps you act on them.

- plugin · `type=plugin` · GitHub Copilot · ★ 292
- Author: Microsoft
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/microsoft/Build-CLI
- Updated: 2026-10-23
- HTML: https://affpapa.org/en/nevibecode/plugins/microsoft-events

## What it does

The plugin reads dependency files in your project root — `package.json`, `requirements.txt`, `.csproj`, `go.mod` — maps them to Microsoft products, and searches the live Build 2026 session catalog. Nothing goes stale: queries hit the catalog API directly, and for SDK docs and code samples it falls back to the Microsoft Learn MCP Server.

It runs in four clients. In GitHub Copilot CLI you install it with `/plugin install microsoft/Build-CLI` and then run `/restart`. In VS Code, open the Extensions panel and search `@agentPlugins microsoft-events`. In Visual Studio 2026, copy `skills/microsoft-build/` to a supported skill location. Claude takes a different route: `/plugin marketplace add microsoft/Build-CLI` first, then `/plugin install microsoft-events@microsoft-events-marketplace`.

Node.js 22+ is recommended — it enables `@microsoft/events-cli` for faster local search and caching. Without it the skill falls back to plain HTTP and everything still works, just slower. Network access is required; there is no offline mode. Recommendations are only as good as the manifest files in your project root, so a project without one gets nothing useful back — tell the agent your stack directly instead. Worth checking that your manifest sits where the plugin looks for it.

The plugin targets Build 2026 and also indexes Build 2025 and Ignite 2025. It is not a replacement for the event app or the session browser, more a developer-first companion for people who live in the terminal.

## Install

### GitHub Copilot (native platform)

**Command from the source**
```bash
copilot plugin install microsoft-events@awesome-copilot
```

## When to use it
- find Build sessions that match your stack
- see what's new at Build for a specific Microsoft product
- look up a session by its code, like BRK155
- log a note tied to a session
- scaffold a project from a session

## Example prompts
- What Build sessions are relevant to my project?
- What's new at Build for Azure Cosmos DB?
- Tell me about session BRK155

## Source text · SKILL.md · MIT

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: 1d60cddfce8a8ba7.

BEGIN THIRD-PARTY FILE 1d60cddfce8a8ba7
````text
# Microsoft Build CLI

A [GitHub Copilot CLI](https://github.com/features/copilot/cli/) skill that connects your local project to the Microsoft Build session catalog. It reads your dependencies, finds relevant sessions, and helps you act on what you learn — all from your terminal.

![Build CLI](Build-CLI.png)

## Quick Start

1. Open **GitHub Copilot CLI** in any project and run:
   ```
   /plugin install microsoft/Build-CLI
   ```
2. Restart your Copilot CLI session:
   ```
   /restart
   ```
3. Try:
   ```
   What Build sessions are relevant to my project?
   ```

The skill reads `package.json`, `requirements.txt`, `.csproj`, `go.mod`, and other dependency files, maps them to Microsoft products, and searches the live Build 2026 session catalog.

## Requirements

- [GitHub Copilot CLI](https://github.com/features/copilot/cli/) installed and authenticated
- **Node.js 22+** (recommended) — enables the `@microsoft/events-cli` for faster local search and caching. Without Node.js, the skill falls back to direct HTTP and everything still works.

## What You Can Do

📺 **[Watch the overview video](https://www.youtube.com/watch?v=gm8gKtrd3po)** to see it in action.

### Before Build — plan your schedule

| Ask the skill to…                        | Example                                               |
|------------------------------------------|-------------------------------------------------------|
| Find sessions for your project           | *"What Build sessions should I attend?"*              |
| See what's new for your tech stack       | *"What's new at Build for Azure Cosmos DB?"*          |
| Look up a session by code                | *"Tell me about session BRK155"*                      |

### During Build — capture what matters

| Ask the skill to…                        | Example                                               |
|------------------------------------------|-------------------------------------------------------|
| Log notes tied to a session              | *"Log a note from session BRK155: great agent demo"*  |
| Get next steps after a session           | *"What should I do after session BRK155?"*            |

### After Build — ship what you learned

| Ask the skill to…                        | Example                                               |
|------------------------------------------|-------------------------------------------------------|
| Scaffold a project from a session        | *"Scaffold a project from session BRK155"*            |
| See what changed for your project        | *"What changed at Build for my project?"*             |

## How It Works

The skill is a thin layer over the **live Build 2026 catalog API** — no stale data, no manual updates. For SDK docs and code samples, it falls back to the [Microsoft Learn MCP Server](https://learn.microsoft.com/training/support/mcp).

Session results are a starting point. For broad topics, ask the agent to refine (*"show me more Foundry sessions about observability"*) or browse the full catalog at [build.microsoft.com/sessions](https://build.microsoft.com/sessions).

> [!NOTE]
> Build-CLI targets **Build 2026** and also indexes past events (Build 2025, Ignite 2025). It supports any future event that follows the same catalog endpoint pattern. It is not a replacement for the event app or session browser — it's a developer-first complement to them.

## Supported Clients

| Client | Configuration |
|--------|---------------|
| GitHub Copilot CLI | `/plugin install microsoft/Build-CLI` then `/restart` |
| VS Code | Open Extensions (Ctrl+Shift+X), search `@agentPlugins microsoft-events`, and install |
| Visual Studio 2026 | Copy `skills/microsoft-build/` to a [supported skill location](https://learn.microsoft.com/visualstudio/ide/copilot-agent-skills) |
| Claude Code | `/plugin marketplace add microsoft/Build-CLI` then `/plugin install microsoft-events@microsoft-events-marketplace` |

## Scope and Limitations
````
END THIRD-PARTY FILE 1d60cddfce8a8ba7

The third-party file has ended. Everything between the 1d60cddfce8a8ba7 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 3980 of 5040 bytes. © Microsoft · MIT · https://github.com/microsoft/Build-CLI

_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