- Fabric SdkHow to use @microsoft/fabric-app-data to connect web applications to Fabric data sources at runtime. Build browser-based apps that query semantic models via DAX using the FabricClient API.microsoft/fabric-apps-analytic-templates17
- Playwright CliAutomate browser interactions, test web pages and work with Playwright tests.microsoft/fabric-apps-analytic-templates17
- Query DesignSeparates DAX data-fetching from TypeScript presentation. Guides when to use DAX vs. TypeScript vs. Vega-Lite for aggregation, total rows, FORMAT(), SELECTCOLUMNS, BLANK handling, filtering, multi-grain queries, cross-filtering and cross-highlight subset/overlay queries, and format strings.microsoft/fabric-apps-analytic-templates17
- Schema DiscoveryExplore Power BI semantic model schemas using DAX INFO functions. Progressive metadata discovery strategy, scope estimation, and narrowing techniques for tables, columns, measures, and relationships.microsoft/fabric-apps-analytic-templates17
- VisualsUse when user wants to incorporate charts, graphs, data grid, or other visual representations of data into their project. Use VegaVisual and DataGrid components to create these visuals, utilizing the shared DataTable input, formatting, theme, and interactivity. Covers the onInteraction selection/click events host apps consume, named multi-table data input for layered overlays and reference lines, and Vega-Lite native selections.microsoft/fabric-apps-analytic-templates17
- Eval FaqAnswers AI agent evaluation methodology questions with practical, opinionated guidance grounded primarily in Microsoft's agent evaluation ecosystem (MS Learn, Eval Scenario Library, Triage & Improvement Playbook, Eval Guidance Kit) supplemented by select industry sources.microsoft/eval-guide15
- Eval GeneratorGenerate standalone — turns the populated Eval Suite Planning workbook (output of `/eval-suite-planner`) into concrete capability eval sets and trust & safety eval sets. Delivers playbook Steps 2 & 3 and designs the Step 8 regression partition. Outputs 2-column Copilot Studio `-for-import.csv` files (Question + Expected response only), a customer-ready `.docx` manifest report, and an `eval-setup-guide.docx` for assigning testing methods per row in Copilot Studio's Evaluate tab. Use after planninmicrosoft/eval-guide15
- Eval Result InterpreterAnalyzes Copilot Studio evaluation results using Practical Guidance on Agent Evaluation's 10-step playbook (Steps 6, 7, and 9) plus Microsoft's triage diagnostics. Returns a gate-based SHIP / ITERATE / BLOCK verdict with root cause classification, remediation, and pattern analysis.microsoft/eval-guide15
- Eval Triage And ImprovementUse this skill when the user's Copilot Studio agent evaluations have come back and they need to interpret scores, diagnose root causes of underperforming test cases, find remediation steps, or analyze patterns to improve their agent. Always use this skill when the user mentions: "eval failed", "why did this fail", "triage", "diagnose failure", "low pass rate", "fix evaluation results", "not passing", "failing test cases", "evaluation results", "improve my eval scores", or any situation where evamicrosoft/eval-guide15
- Mcscatblog Local ServerStart the local Jekyll dev server and open a post in the browsermicrosoft/mcscatblog15
- Mcscatblog New PostCreate a new blog post with branch, front matter, and asset foldermicrosoft/mcscatblog15
- Mcscatblog React WidgetBuild and embed a React widget into a Jekyll blog post as a self-contained HTML filemicrosoft/mcscatblog15
- Mcscatblog Review PostEnd-to-end review, fix, publish, and verify a blog post PR from another authormicrosoft/mcscatblog15
- Mcscatblog Submit PrCommit current changes and create a pull request for reviewmicrosoft/mcscatblog15
- Shadow FrogUse a shadow knowledge base to understand any codebase. The .shadow/ directory mirrors the source tree with markdown files containing behavioral insights — known bugs, edge cases, implicit contracts, and user preferences. Always check the shadow before editing, debugging, or investigating code. When the user shares important context, write it to the shadow immediately. Invoke shadow-frog-init to create it, shadow-frog-update to refresh it, shadow-frog-dream for autonomous exploration, shadow-fromicrosoft/ShadowFrog13
- Shadow Frog DreamRun autonomous experimentation while the user is AFK. Uses 6 investigation categories (investigation, bug hunting, feature design, refactoring, optimization, security audit) to systematically discover non-obvious behaviors. Every task is an experiment — implement in worktrees, commit to persistent dream branches, and push to the fork. Dreams compound across sessions: future experiments branch from prior dream branches, building a tree of progressively deeper work. Invoke when the user is AFK or microsoft/ShadowFrog13
- Shadow Frog InitInitialize a shadow knowledge base for any codebase. Creates a .shadow/ directory that mirrors the source tree with markdown files for AI-discovered insights. Run this once per repo before using other shadow-frog skills. Refuses to overwrite an existing .shadow/ unless --reset is passed.microsoft/ShadowFrog13
- Shadow Frog MeditateClean and consolidate the shadow knowledge base. Scans all shadow files for duplicate discoveries (same claim, different wording), near-duplicates (one extends another), and conflicting entries (contradicting claims). Merges duplicates, resolves conflicts by investigating the code, and asks the user only when resolution is unclear. Invoke periodically to keep the shadow focused and free of noise.microsoft/ShadowFrog13
- Shadow Frog UpdateUpdate the shadow knowledge base after code changes and from conversational insights. Detects what changed via git diff, refreshes per-file shadows, captures knowledge shared by the user during the session, and updates cross-cutting discoveries. Invoke manually with /shadow-frog-update; the preToolUse hook will remind the agent when the shadow is behind HEAD.microsoft/ShadowFrog13
- Shadow Frog ViewerBrowse and query the shadow knowledge base: overview, search for files or symbols or text, view preferences, or see recent discoveries. Invoke when the user wants to see what's in the shadow, get an overview, or find specific knowledge.microsoft/ShadowFrog13
- Live Site SqlLive-site triage playbook for Azure SQL on-call incidents — protocol, diagnostic catalog (dx_index_exists, dx_resource_pressure, dx_deadlock_recent), hybrid search, and grounded mitigation generation. Loaded by the live-site-sql custom agent. Use when the user asks to mitigate, triage, or diagnose a Zava SQL incident.microsoft/Build26-BRK223-from-rows-to-reasoning-designing-databases-for-ai-apps-and-agents12
- Content Track ScaffolderScaffold a complete new content track (like Foundation, Advanced, or Terminal) with all required files — data parser, page components, routes, markdown content, and navigation. Use when adding a new learning path, creating a new track, or expanding the tutorial with a new module series. Use for questions like "add a new track", "create learning path for X", "scaffold track pages".microsoft/learn-ai-native-dev11
- Deploy Agent Aca AwsAI-led deployment of the AWS Bedrock sample agent with the Microsoft Entra Agent ID sidecar to Azure Container Apps. Use when the user wants to deploy the AWS sample to ACA, provision the AWS-federation intermediary Entra app, wire the token refresher, create the AWS OIDC provider and IAM role for Bedrock, build and push the four container images to ACR, or debug InvalidIdentityToken / AADSTS65001 / Directory.AccessAsUser.All / AcrPull errors in this specific deployment. NOT for local docker-commicrosoft/entra-agentid-samples11
- Deploy Agent Aca DevAI-led deployment of the local-LLM sample agent (Ollama + Microsoft Entra Agent ID sidecar) to Azure Container Apps. Use when the user wants to deploy sidecar/dev to ACA, run the agent on Azure without AWS/GCP, host Ollama on Container Apps, promote the docker-compose local-dev stack from ClientSecret to SignedAssertionFromManagedIdentity (secretless), or debug AADSTS65001/AADSTS50011/ImagePullBackOff/Ollama OOM errors in this specific deployment. NOT for AWS Bedrock (use deploy-agent-aca-aws) amicrosoft/entra-agentid-samples11
- Diagram ScaffolderGenerate new interactive diagram components for tutorial content. Use when adding a visual diagram, creating architectural illustrations, or building interactive flow visualizations. Use for questions like "add a diagram", "create diagram component", "new visual for module X". Produces a React component, registers it in the barrel export and StepCard parser, and provides the markdown reference syntax.microsoft/learn-ai-native-dev11
- Docs SyncDiff src/ and .github/ against docs/ to detect drift between code and design spec. Use when auditing the docs folder, after merging structural changes (adding paths/modules/diagrams/syntax/agents/skills/hooks), or before a release. Use for questions like "is docs in sync?", "what changed since the last docs update?", "find docs drift". Produces a structured report with proposed edits — does not modify docs/ directly.microsoft/learn-ai-native-dev11
- Entra Agent Id SetupAI-guided setup for Microsoft Entra Agent ID. Use when the user wants to provision an Agent Identity Blueprint, Agent Identity, and OBO client app in an Entra tenant; when configuring the dev/AWS/GCP sidecar stack; when debugging 403 Authorization_RequestDenied on blueprint creation; when checking which Entra role is required (Global Admin / Agent ID Administrator / Agent ID Developer); when running Start-EntraAgentIDWorkflow / setup-obo-client-app / setup-obo-blueprint.microsoft/entra-agentid-samples11
- Exercise ScaffolderGenerate consistent, high-quality coding exercises for AI-Native development tutorials. Use when creating hands-on exercises, coding challenges, practice problems, quizzes, labs, or skill-building activities. Use for questions like "create an exercise", "add practice activity", "build a challenge for Part X". Includes starter templates, solution patterns, hint progressions, and verification criteria.microsoft/learn-ai-native-dev11
- Teardown Agent Aca AwsAI-led teardown of the AWS Bedrock sample agent deployment on Azure Container Apps created by deploy-agent-aca-aws. Use when the user wants to delete the AWS sample ACA deployment, clean up the resource group, remove the AWS IAM role + OIDC provider, delete the intermediary Entra app, or optionally delete the Blueprint / Agent Identity / Client SPA. Defaults to DRY-RUN and keeps Entra/AWS objects unless the user explicitly opts in. NOT for local docker-compose (no cloud resources to delete) and microsoft/entra-agentid-samples11
- Teardown Agent Aca DevAI-led teardown of the local-LLM (Ollama) sample agent deployment on Azure Container Apps created by deploy-agent-aca-dev. Use when the user wants to delete the dev sample ACA deployment, clean up the resource group, or optionally delete the Blueprint / Agent Identity / Client SPA. Defaults to DRY-RUN and keeps Entra objects unless the user explicitly opts in. NOT for local docker-compose (use `docker compose down -v`) and NOT for the AWS Bedrock variant (use teardown-agent-aca-aws).microsoft/entra-agentid-samples11
- Track GeneratorGenerate new example tracks for the AI-Native tutorial. Use when creating new industry examples, adding a new track, building project templates, or expanding learning paths. Use for questions like "add a track for healthcare", "create new example", "new industry template". Produces consistent ExampleTrack data with all required fields including projectName, requirements, colorCoding, taskExamples, and verification examples matching the TypeScript interface in exampleTracks.ts.microsoft/learn-ai-native-dev11
- Tutorial Content QaComprehensive quality assurance for AI-Native development tutorials across all tracks (Foundation, Advanced, Terminal). Use when reviewing content for accuracy, clarity, consistency, and completeness. Use for proofreading, checking errors, auditing content, or running QA checks before publishing.microsoft/learn-ai-native-dev11
- Version CheckerValidate that tutorial content references current tool versions, APIs, CLI commands, and features. Use when reviewing content for outdated information, checking deprecations, verifying feature availability, auditing tool references, or updating stale version numbers. Covers GitHub Copilot (VS Code + CLI), Claude Code, VS Code settings, MCP, and Agent Skills standard.microsoft/learn-ai-native-dev11
- FeedbackFile a bug report or feature suggestion on GitHub via gh CLI. Gathers details conversationally, previews, and creates an issue. Use when the user wants to report a bug or suggest a feature.microsoft/MCS-Agent-Builder10
- IterateUse this skill when the user asks Claude to autonomously test, fix, review, and merge a change end-to-end. Detects which lane(s) changed (frontend / backend / framework / agentspec), spawns relevant verifiers (agentic-test-loop with --require-oracle for false-green prevention; backend-verify for contracts/types/unit/server), runs a facilitator review loop using qa-challenger via Agent tool with worktree isolation until score>=9 and zero critical findings, calls multi-model-review.js review-mergemicrosoft/MCS-Agent-Builder10
- Mcs BuildUse this skill to build an agent in Copilot Studio from a researched agentspec.json. Runs pre-build validation (auth, env, connections, tools, model), then creates the agent, configures instructions, knowledge, tools, model, topics, and publishes. Supports single-agent, multi-agent, and connected-agent architectures. Use after /mcs-research when agentspec.json is ready, or to resume a partially completed build.microsoft/MCS-Agent-Builder10
- Mcs ContextUse this skill to pull M365 history about a customer or company before research. Searches emails, meetings, documents, Teams, and people via WorkIQ MCP to compile a customer context file. Use when starting a new project, when the user mentions a customer name, or when you need business context for architecture decisions.microsoft/MCS-Agent-Builder10
- Mcs EvalUse this skill to test an agent's quality after building or fixing it. Runs eval test sets against a published agent via Direct Line API (default, auto), CopilotStudio SDK, Power CAT Kit, or MCS Native Eval (for MCP agents). Results are written per-test to evalSets[].tests[].lastResult in agentspec.json. Use after /mcs-build or /mcs-fix, or when the user wants to re-test.microsoft/MCS-Agent-Builder10
- Mcs FixUse this skill to fix an agent after eval failures. Classifies root causes (instruction gaps, boundary violations, routing failures, knowledge gaps, scoring issues, decision mismatches), applies targeted fixes via PE and TE, then re-evaluates. Use after /mcs-eval shows failures, not during initial build (which has its own fix loop).microsoft/MCS-Agent-Builder10
- Mcs InitUse this skill to start a new MCS agent project. Creates the folder structure in Build-Guides/, copies template files, and detects the intake path (SDR documents, wizard, or manual). Use when the user says 'new project', 'start a build', or provides intake documents.microsoft/MCS-Agent-Builder10
- Mcs IterateUse this skill to autonomously build, evaluate, and fix an MCS agent until it reaches SHIP verdict. Composite of /mcs-build → /mcs-eval → /mcs-fix → re-eval, max 3 fix cycles per agent. Reuses the iterate-orchestrator audit + verdict primitives. Use after /mcs-research when agentspec.json is ready and the user wants the agent shipped without manual phase transitions. Use when the user says 'ship it', 'iterate to SHIP', 'build and evaluate this agent', or to resume a partially-built agent. Notifymicrosoft/MCS-Agent-Builder10
- Mcs Pipeline TestUse this skill to run the MCS build pipeline verify-fix harness against the canonical kitchen-sink agent. The harness reads back every component from MCS via API, classifies any drift against a fixed taxonomy, and auto-applies fixes for confirmed classifications. Use when validating the build pipeline end-to-end, after touching tools/mcs-lsp.js, tools/island-client.js, tools/add-tool.js, or app/lib/build-runner.js, or when component pushes are silent-failing in real builds.microsoft/MCS-Agent-Builder10
- Mcs ReportUse this skill to generate an export from agentspec.json without running a build. Produces a single self-contained HTML file with three tabs: Brief (design state), Evaluations (test sets and results), and How-To Guide (step-by-step MCS build instructions). Use when the user wants a summary, status update, or shareable document.microsoft/MCS-Agent-Builder10
- Mcs ResearchUse this skill to research and design an agent before building it. Reads project documents, identifies agents, researches MCS components, scores architecture, writes instructions, and generates eval sets. Use after /mcs-init, when documents change, when the user wants to analyze requirements, or when agentspec.json needs enrichment.microsoft/MCS-Agent-Builder10
- Mcs SyncUse this skill to detect changes across all external dependencies (knowledge cache, upstream repos, Elevate, eval-guide plugin, MCP servers, om-cli binary, MS Learn docs, Claude Code plugins) and produce a triage board so a human can decide TAKE or REJECT per change. Never auto-applies. Use when the user asks to 'refresh everything', 'check what's new upstream', 'run dependency sync', 'sync', or when you want to see what has drifted since the last manual review.microsoft/MCS-Agent-Builder10
- Playwright CliAutomate browser interactions, test web pages and work with Playwright tests.microsoft/MCS-Agent-Builder10
- Share ScreenshotUse this only when a user explicitly asks to upload or share a screenshot image file to the Lab 502 Community Hub. Resolve the image path before uploading.microsoft/Build26-LAB502-make-github-copilot-work-your-way-custom-tools-context-and-workflows10
- Adapt SkillAdapt a skill written for another AI coding assistant (Claude Code, Cursor, etc.) into a properly structured Amplifier SKILL.md file. Reads the source skill, identifies platform-specific conventions, researches the source platform if needed, and produces an Amplifier-native skill conforming to the Agent Skills specification with Amplifier extensions. Use when the user wants to adapt a skill, port a skill, convert a skill to amplifier, translate a skill, or has a SKILL.md from another platform thmicrosoft/amplifier-bundle-skills9
- Agent DeveloperMicrosoft Agent Framework + Foundry Toolbox MCP integration specialistmicrosoft/Build26-BRK242-turn-your-agents-into-action-connect-tools-apis-and-documents9
- Amplifier Tool Leverage PatternsUse when building an Amplifier-powered workflow or automation tool and deciding how to expose it — as standalone .dot attractor pipelines (incl. inside the Resolve dot-graph resolver), an importable Python lib, agent-callable tool modules, or a CLI. Covers the four leverage levels, the DRY rule that keeps logic in ONE home, and the judgment for which levels a real consumer actually needs (and when adding a level is just ceremony).microsoft/amplifier-bundle-skills9
- Auth Tls PatternsUse when your service needs authentication that works without friction locally but secures remote access, automatic TLS certificate setup, or token-based auth with auto-generation and localhost bypass.microsoft/amplifier-bundle-skills9
- Azure Search OpsOperate the Azure AI Search index and knowledge base behind FoundryIQ for Fibey field ops.microsoft/Build26-BRK242-turn-your-agents-into-action-connect-tools-apis-and-documents9
- Cli Packaging PatternsUse when building a new CLI tool that needs one-line install via uv or npm, subcommand dispatch with a default action, or 3-tier config resolution (CLI flags, config file, hardcoded defaults).microsoft/amplifier-bundle-skills9
- Code ReviewReview changed code for reuse, quality, and efficiency, then fix any issues found.microsoft/amplifier-bundle-skills9
- Config State PatternsUse when your tool needs persistent configuration files with safe defaults merging, atomic state writes that survive crashes, or conventional file locations for config vs state vs secrets.microsoft/amplifier-bundle-skills9
- Container Orchestration PatternsUse when running tasks in Docker containers with safety limits, watchdog monitoring for resource enforcement, orphan container recovery, sidecar container provisioning, or scripting reproducible dev stack environments.microsoft/amplifier-bundle-skills9
- CouncilConvene the persona panel (six orthogonal review lenses) on a target — cold independent fan-out, debate-to-consensus, synthesized verdict with recorded dissent and a roster manifest.microsoft/amplifier-bundle-skills9
- Council HereConvene the persona panel on the CURRENT conversation / work-in-progress — the plan, design, or decision you've been building in this session. The INLINE counterpart to /council (which forks and runs isolated, so it cannot see the chat). Use when you want the council to critique what we're working on right now.microsoft/amplifier-bundle-skills9
- Cranky Old SamSimplicity-obsessed design reviewer that interrogates complexity, questions every abstraction, and insists on the minimal viable design. Sounds like a senior engineer who has watched too many systems collapse under their own weight and now treats every unnecessary layer as a personal affront. Not a generalist skeptic — a simplicity zealot. A lens for any checkpoint — brainstorm, design, plan, implement, debug, or review — not just design. Use when: anything looks more complex than the problem nemicrosoft/amplifier-bundle-skills9
- Crusty Old EngineerCurmudgeonly engineering advisor that provides grounded skepticism, evidence-linked judgment, and constructive progress on architectural decisions, legacy refactors, tooling choices, and broad "how should I start?" questions. Sounds like a senior systems engineer who has reviewed too many designs to be impressed, but still cares about correctness. A lens for any checkpoint — brainstorm, design, plan, implement, debug, or review — not just up-front decisions. Use when: weighing consequences, hiddmicrosoft/amplifier-bundle-skills9