microsoft/build-cli/microsoft-events

Claude Code and agent skill by microsoft/build-cli

Trust tier 4
  • vendor
Source check pending

Checking that the SKILL.md file is still in the repository.

Your companion for Microsoft events, defaulting to Ignite 2026. Helps you find sessions relevant to your project, discover what's new for your tech stack, scaffold projects from sessions, and plan your event schedule. Activate when users mention sessions, schedule, what's new, Build, Ignite, Microsoft event, conference, or reference a session code (BRK, DEM, LAB, KEY, LTG, THR). Supports Ignite 2026 and Build 2026 catalogs. Uses the msevents CLI for fast local search and Learn MCP Server for do…

Install

npx vskill@latest install microsoft/build-cli/microsoft-events

SKILL.md

The same SKILL.md was published earlier as microsoft/build-cli/microsoft-events.

Microsoft Events CLI

This skill supports multiple Microsoft events. Ignite 2026 is the default. When the user asks about a different event, use the appropriate event ID and endpoint from the table below.

Event context

Default event
SettingValue
EventIgnite 2026
Event IDignite-2026
DatesNovember 17-20, 2026 (optional pre-day: November 16)
LocationSan Francisco, CA (Moscone Center)
TimezonePacific Time (America/Los_Angeles)
Catalog endpointhttps://aka.ms/ignite2026-session-info
News & AnnouncementsCheck Key resources; if missing, search news.microsoft.com
Default CLI flag--event ignite-2026
Supported events
EventEvent IDCatalog EndpointLocationTimezone
Ignite 2026ignite-2026https://aka.ms/ignite2026-session-infoSan Francisco, CA (Moscone Center)PT (America/Los_Angeles)
Build 2026build-2026https://aka.ms/build2026-session-infoSan Francisco, CAPDT (UTC-7)
Recognized event names (not yet configured)
Event nameStatusBehavior
Frontier TourRecognized, not configuredRecognize the event name, but do not search or return event facts.

For recognized-but-not-configured event names, never invent dates, locations, sessions, schedule, or availability.

Time display

Always present session times in the event's local timezone (e.g., "2:30 PM PDT" when the event timezone is PDT). If startDateTime is null for an upcoming event, note that day assignments aren't available yet and show time slots only.

When the user mentions a specific event by name, use its event ID for CLI commands (--event <id>) and its endpoint for direct fetch. If no event is specified, default to Ignite 2026.

Use these values throughout. CLI commands should include --event ignite-2026 by default unless the user specifies another event.

Event and content availability
  • A configured catalog can represent upcoming, current, or historical content. Do not infer lifecycle state from catalog presence alone.
  • Use catalog fields to distinguish scheduled, live, recorded, on-demand, self-paced, and unavailable content.
  • For upcoming sessions, describe them as scheduled and do not imply recordings, transcripts, or replay unless explicitly indicated.
  • Treat missing availability fields as unavailable or unknown. Do not upgrade availability based on assumptions.
Schedule authority
  • Treat startDateTime and endDateTime as UTC when present.
  • Treat TimeSlot as display text only, not timezone authority.
  • Convert times only when timezone authority is explicit (catalog-provided or user-provided IANA timezone/UTC offset).
  • If UTC boundaries conflict with TimeSlot, preserve both and flag the conflict; do not reconcile.

Helps developers and IT pros find event sessions relevant to their projects, discover what's new for their tech stack, scaffold projects from session content, and plan their event schedule — all based on what they're actually building.

The "what's new for me" workflow works year-round — Learn MCP Server always has current documentation, SDK updates, and what's-new pages. During active events, the session catalog adds session recommendations on top of the documentation layer.

Two live data sources, no static files:

  1. Learn MCP Server — current SDK docs, API references, what's-new pages, quickstarts, code samples (always available)
  2. Event session catalog — accessed via the msevents CLI for local search, caching, and multi-event support
Golden rule: session metadata comes from the live catalog (via CLI or endpoint); SDK docs, API references, and code samples come from Learn MCP Server. Never fabricate session IDs, speaker names, or schedule data.

Source boundary

  • Catalog facts: session IDs, titles, abstracts, speakers, schedules, locations, formats, availability, and links.
  • Learn facts: current product, SDK/API behavior, lifecycle, implementation, quickstart, and tutorial facts.
  • Authorized context: project files, architecture, policies, role, technologies, interests, and learning goals the user explicitly authorizes.
  • Agent judgment: relevance categories, comparisons, suggested learning order, and next-step recommendations.

For recommendations, clearly separate facts from judgment and cite the concrete signal behind each recommendation.

When to use this skill

Activate when the user:

  • Mentions sessions, schedule, or anything about Build or Ignite
  • Asks about a Microsoft flagship event or conference
  • Asks what's new for their project or tech stack
  • Asks what changed in their dependencies or what updates are relevant to their code
  • Wants to find sessions relevant to their work
  • Asks to scaffold or start a project based on a session
  • Asks for help planning their event schedule
  • Asks what to do after attending a session, or wants next steps
  • Wants to log notes or takeaways from a session
  • References a session code (BRK, DEM, LAB, KEY, LTG, THR, etc.)
  • Asks to create or export their schedule as a markdown file

Do not activate when the user:

  • Asks general Azure architecture questions unrelated to recent updates
  • Asks you to register for sessions or manage their event account

Session catalog access

Preferred: msevents CLI

The msevents CLI fetches, caches, indexes, and searches the session catalog locally. It handles multi-event support, fuzzy search, and returns structured results.

sh
# Search by keyword
npx -y @microsoft/events-cli sessions --query "Microsoft Foundry" --event ignite-2026 --json
# Search by technology (matches product, tags, topic, languages, title, description)
npx -y @microsoft/events-cli sessions --tech "Azure Cosmos DB" --event ignite-2026 --json
# Search by speaker
npx -y @microsoft/events-cli sessions --speaker "Scott Hanselman" --event ignite-2026 --json
# Combine filters
npx -y @microsoft/events-cli sessions --tech "Microsoft Foundry" --speaker "Yina Arenas" --event ignite-2026 --json
# Look up a specific session by code
npx -y @microsoft/events-cli session BRK155 --json
# Refresh the cache
npx -y @microsoft/events-cli refresh --event ignite-2026
# Check cache status
npx -y @microsoft/events-cli status

The CLI caches session data locally. On first use it fetches automatically — no explicit refresh needed. Use npx -y so agents do not get stuck on npm's first-run install prompt. Use --json for structured output the agent can parse directly.

CLI reference
CommandOptionsDescription
sessions--query <text>Keyword search across all fields (boosts title)
--tech <name>Search by technology (product, tags, topic, languages, title, description)
--speaker <name>Search by speaker name
--type <type>Filter by session type (breakout, lab, demo, keynote, etc.)
--event <id>Filter by event (e.g., ignite-2026, build-2026)
--limit <n>Max results, default 10
--jsonOutput as JSON
session <code>--event <id>Scope to a specific event (for disambiguation)
--jsonOutput as JSON
refresh--event <id>Refresh a specific event only
--forceBypass cache, re-fetch unconditionally
status--jsonOutput as JSON
Fallback: direct HTTP fetch

If the CLI is not available (not installed, npx fails), fall back to fetching the session catalog directly:

# Use the aka.ms links from the supported events table above
# Ignite 2026 (default):
GET https://aka.ms/ignite2026-session-info
# Build 2026:
GET https://aka.ms/build2026-session-info

The response is a JSON array of session objects. Key fields:

FieldDescription
sessionCodeSession ID (e.g., "BRK180")
titleSession title
descriptionFull session abstract
speakerNamesSpeaker name(s), comma-separated
TimeSlotDisplay time (e.g., "11:45 - 13:15")
startDateTime / endDateTimeUTC timestamps
locationRoom/venue
sessionLevelDifficulty level
sessionTypeSession format (breakout, lab, demo, etc.)
topicTopic area
solutionAreaSolution area
productRelated products (often empty — search title/description too)
programmingLanguagesLanguages used
tagsContent tags
relatedSessionCodesRelated session IDs
slideDeckSlide deck URL (when available)
onDemandOn-demand video URL (when available)
deliveryTypesHow the session is delivered (e.g., "In-person", "Online")
viewingOptionsRecording status (e.g., "Will be recorded", "Will not be recorded")
hasLiveStreamWhether the session has a live stream (boolean)
hasOnDemandWhether on-demand video will be available (boolean)
langLocaleSession locale used in Ignite session-page URL (e.g., en-US)
sessionInstanceIdOpaque Ignite session instance ID used to build session-page URL

When using direct fetch: fetch once per conversation, filter for all technologies in the inventory in the same step, carry forward only matched sessions.

Deterministic catalog access guardrails
  1. Prefer msevents for live catalog retrieval whenever available.
  2. For generic cross-event search or event-less session-code lookup, ensure coverage for every required active event before returning results.
  3. If required event coverage is missing, state the limitation, list missing events, and ask the user to narrow scope.
  4. Do not return partial cross-event results as if complete.
  5. Do not use page scraping, browser extraction, or unbounded catalog loading for authoritative session lookup.
Session page link rules

When listing sessions, always include a session page URL when deterministically available from catalog facts.

  1. Ignite sessions: build the URL from catalog fields:
  • https://ignite.microsoft.com/{langLocale}/sessions/{sessionInstanceId}?source=sessions
  • Use langLocale and sessionInstanceId from the catalog record.
  • If CLI output omits either field, fetch the corresponding raw catalog record by sessionCode from the configured endpoint before constructing the URL.
  • Never invent or guess opaque IDs.
  1. Build sessions: use:
  • https://build.microsoft.com/sessions/{sessionCode}
  1. If required URL fields are missing, state that a direct session-page link is unavailable for that result instead of fabricating one.
Learn MCP Server (live)

Use Learn MCP tools to retrieve current documentation:

ToolWhen to use
microsoft_docs_searchFind current docs for an SDK, service, or feature
microsoft_docs_fetchRead full documentation page for a specific topic
microsoft_code_sample_searchFind official code samples

CLI fallback — if Learn MCP tools are not available (e.g., MCP server not configured), use the mslearn CLI instead:

sh
npx @microsoft/learn-cli search "azure functions timeout"
npx @microsoft/learn-cli fetch "https://learn.microsoft.com/..." --section "Configuration" --max-chars 5000
npx @microsoft/learn-cli code-search "azure openai streaming"
MCP toolCLI equivalent
microsoft_docs_search(query: "...")mslearn search "..."
microsoft_docs_fetch(url: "...")mslearn fetch "..." [--section heading] [--max-chars N]
microsoft_code_sample_search(query: "...")mslearn code-search "..."

Core workflows

"What's new for me?"

The user wants to know what recent Microsoft updates are relevant to them. This workflow works year-round.

This is the start of the file. Read the full SKILL.md on GitHub.

Security

  • Security scanPassed, 100 of 100Pattern checks on the skill's files. Certified 14 Nov 2026.
  • Model reviewPassed

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

Repository stars
294
Repository forks
85
7-day trend score
0

Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill CERTIFIED badge
[![vskill CERTIFIED](https://verified-skill.com/api/v1/skills/microsoft/build-cli/microsoft-events/badge)](https://verified-skill.com/skills/microsoft/build-cli/microsoft-events)

Something wrong with this skill or its page? Tell us.