Merge branch 'staged' into add-entra-agent-user-skill

Author: aaronpowell

.github/plugin/marketplace.json

@@ -31,6 +31,7 @@ Ready-to-use prompt templates for specific development scenarios and tasks, defi
 | [Azure Cosmos DB NoSQL Data Modeling Expert System Prompt](../prompts/cosmosdb-datamodeling.prompt.md)<br />[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcosmosdb-datamodeling.prompt.md)<br />[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcosmosdb-datamodeling.prompt.md) | Step-by-step guide for capturing key application requirements for NoSQL use-case and produce Azure Cosmos DB Data NoSQL Model design using best practices and common patterns, artifacts_produced: "cosmosdb_requirements.md" file and "cosmosdb_data_model.md" file |
 | [Azure Cost Optimize](../prompts/az-cost-optimize.prompt.md)<br />[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Faz-cost-optimize.prompt.md)<br />[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Faz-cost-optimize.prompt.md) | Analyze Azure resources used in the app (IaC files and/or resources in a target rg) and optimize costs - creating GitHub issues for identified optimizations. |
 | [Azure Resource Health & Issue Diagnosis](../prompts/azure-resource-health-diagnose.prompt.md)<br />[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fazure-resource-health-diagnose.prompt.md)<br />[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fazure-resource-health-diagnose.prompt.md) | Analyze Azure resource health, diagnose issues from logs and telemetry, and create a remediation plan for identified problems. |
+| [BigQuery Pipeline Audit: Cost, Safety and Production Readiness](../prompts/bigquery-pipeline-audit.prompt.md)<br />[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fbigquery-pipeline-audit.prompt.md)<br />[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fbigquery-pipeline-audit.prompt.md) | Audits Python + BigQuery pipelines for cost safety, idempotency, and production readiness. Returns a structured report with exact patch locations. |
 | [Boost Prompt](../prompts/boost-prompt.prompt.md)<br />[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fboost-prompt.prompt.md)<br />[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fboost-prompt.prompt.md) | Interactive prompt refinement workflow: interrogates scope, deliverables, constraints; copies final markdown to clipboard; never writes code. Requires the Joyride extension. |
 | [C# Async Programming Best Practices](../prompts/csharp-async.prompt.md)<br />[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcsharp-async.prompt.md)<br />[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcsharp-async.prompt.md) | Get best practices for C# async programming |
 | [C# Documentation Best Practices](../prompts/csharp-docs.prompt.md)<br />[![Install in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcsharp-docs.prompt.md)<br />[![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcsharp-docs.prompt.md) | Ensure that C# types are documented with XML comments and follow best practices for documentation. |

docs/README.instructions.md

@@ -0,0 +1,62 @@
+#!/usr/bin/env node
+
+import fs from "fs";
+import path from "path";
+import { ROOT_FOLDER } from "./constants.mjs";
+
+const PLUGINS_DIR = path.join(ROOT_FOLDER, "plugins");
+const MATERIALIZED_DIRS = ["agents", "commands", "skills"];
+
+function cleanPlugin(pluginPath) {
+  let removed = 0;
+  for (const subdir of MATERIALIZED_DIRS) {
+    const target = path.join(pluginPath, subdir);
+    if (fs.existsSync(target) && fs.statSync(target).isDirectory()) {
+      const count = countFiles(target);
+      fs.rmSync(target, { recursive: true, force: true });
+      removed += count;
+      console.log(`  Removed ${path.basename(pluginPath)}/${subdir}/ (${count} files)`);
+    }
+  }
+  return removed;
+}
+
+function countFiles(dir) {
+  let count = 0;
+  for (const entry of fs.readdirSync(dir, { withFileTypes: true })) {
+    if (entry.isDirectory()) {
+      count += countFiles(path.join(dir, entry.name));
+    } else {
+      count++;
+    }
+  }
+  return count;
+}
+
+function main() {
+  console.log("Cleaning materialized files from plugins...\n");
+
+  if (!fs.existsSync(PLUGINS_DIR)) {
+    console.error(`Error: plugins directory not found at ${PLUGINS_DIR}`);
+    process.exit(1);
+  }
+
+  const pluginDirs = fs.readdirSync(PLUGINS_DIR, { withFileTypes: true })
+    .filter(entry => entry.isDirectory())
+    .map(entry => entry.name)
+    .sort();
+
+  let total = 0;
+  for (const dirName of pluginDirs) {
+    total += cleanPlugin(path.join(PLUGINS_DIR, dirName));
+  }
+
+  console.log();
+  if (total === 0) {
+    console.log("✅ No materialized files found. Plugins are already clean.");
+  } else {
+    console.log(`✅ Removed ${total} materialized file(s) from plugins.`);
+  }
+}
+
+main();

docs/README.prompts.md

@@ -14,12 +14,12 @@ const MARKETPLACE_FILE = path.join(ROOT_FOLDER, ".github/plugin", "marketplace.j
  */
 function readPluginMetadata(pluginDir) {
   const pluginJsonPath = path.join(pluginDir, ".github/plugin", "plugin.json");
-  
+
   if (!fs.existsSync(pluginJsonPath)) {
     console.warn(`Warning: No plugin.json found for ${path.basename(pluginDir)}`);
     return null;
   }
-  
+
   try {
     const content = fs.readFileSync(pluginJsonPath, "utf8");
     return JSON.parse(content);
@@ -34,30 +34,30 @@ function readPluginMetadata(pluginDir) {
  */
 function generateMarketplace() {
   console.log("Generating marketplace.json...");
-  
+
   if (!fs.existsSync(PLUGINS_DIR)) {
     console.error(`Error: Plugins directory not found at ${PLUGINS_DIR}`);
     process.exit(1);
   }
-  
+
   // Read all plugin directories
   const pluginDirs = fs.readdirSync(PLUGINS_DIR, { withFileTypes: true })
     .filter(entry => entry.isDirectory())
     .map(entry => entry.name)
     .sort();
-  
+
   console.log(`Found ${pluginDirs.length} plugin directories`);
-  
+
   // Read metadata for each plugin
   const plugins = [];
   for (const dirName of pluginDirs) {
     const pluginPath = path.join(PLUGINS_DIR, dirName);
     const metadata = readPluginMetadata(pluginPath);
-    
+
     if (metadata) {
       plugins.push({
         name: metadata.name,
-        source: `./plugins/${dirName}`,
+        source: dirName,
         description: metadata.description,
         version: metadata.version || "1.0.0"
       });
@@ -66,7 +66,7 @@ function generateMarketplace() {
       console.log(`✗ Skipped: ${dirName} (no valid plugin.json)`);
     }
   }
-  
+
   // Create marketplace.json structure
   const marketplace = {
     name: "awesome-copilot",
@@ -81,16 +81,16 @@ function generateMarketplace() {
     },
     plugins: plugins
   };
-  
+
   // Ensure directory exists
   const marketplaceDir = path.dirname(MARKETPLACE_FILE);
   if (!fs.existsSync(marketplaceDir)) {
     fs.mkdirSync(marketplaceDir, { recursive: true });
   }
-  
+
   // Write marketplace.json
   fs.writeFileSync(MARKETPLACE_FILE, JSON.stringify(marketplace, null, 2) + "\n");
-  
+
   console.log(`\n✓ Successfully generated marketplace.json with ${plugins.length} plugins`);
   console.log(`  Location: ${MARKETPLACE_FILE}`);
 }

eng/clean-materialized-plugins.mjs

@@ -0,0 +1,106 @@
+---
+description: 'Use Context7 for authoritative external docs and API references when local context is insufficient'
+applyTo: '**'
+---
+
+# Context7-aware development
+
+Use Context7 proactively whenever the task depends on **authoritative, current, version-specific external documentation** that is not present in the workspace context.
+
+This instruction exists so you **do not require the user to type** “use context7” to get up-to-date docs.
+
+## When to use Context7
+
+Use Context7 before making decisions or writing code when you need any of the following:
+
+- **Framework/library API details** (method signatures, configuration keys, expected behaviors).
+- **Version-sensitive guidance** (breaking changes, deprecations, new defaults).
+- **Correctness or security-critical patterns** (auth flows, crypto usage, deserialization rules).
+- **Interpreting unfamiliar error messages** that likely come from third-party tools.
+- **Best-practice implementation constraints** (rate limits, quotas, required headers, supported formats).
+
+Also use Context7 when:
+
+- The user references **a specific framework/library version** (e.g., “Next.js 15”, “React 19”, “AWS SDK v3”).
+- You’re about to recommend **non-trivial configuration** (CLI flags, config files, auth flows).
+- You’re unsure whether an API exists, changed names, or got deprecated.
+
+Skip Context7 for:
+
+- Purely local refactors, formatting, naming, or logic that is fully derivable from the repo.
+- Language fundamentals (no external APIs involved).
+
+## What to fetch
+
+When using Context7, prefer **primary sources** and narrow queries:
+
+- Official docs (vendor/framework documentation)
+- Reference/API pages
+- Release notes / migration guides
+- Security advisories (when relevant)
+
+Gather only what you need to proceed. If multiple candidates exist, pick the most authoritative/current.
+
+Prefer fetching:
+
+- The exact method/type/option you will use
+- The minimal surrounding context needed to avoid misuse (constraints, default behaviors, migration notes)
+
+## How to incorporate results
+
+- Translate findings into concrete code/config changes.
+- **Cite sources** with title + URL when the decision relies on external facts.
+- If docs conflict or are ambiguous, present the tradeoffs briefly and choose the safest default.
+
+When the answer requires specific values (flags, config keys, headers), prefer:
+
+- stating the exact value from docs
+- calling out defaults and caveats
+- providing a quick validation step (e.g., “run `--help`”, or a minimal smoke test)
+
+## How to use Context7 MCP tools (auto)
+
+When Context7 is available as an MCP server, use it automatically as follows.
+
+### Tool workflow
+
+1) **If the user provides a library ID**, use it directly.
+  - Valid forms: `/owner/repo` or `/owner/repo/version` (for pinned versions).
+
+2) Otherwise, **resolve the library ID** using:
+  - Tool: `resolve-library-id`
+  - Inputs:
+	  - `libraryName`: the library/framework name (e.g., “next.js”, “supabase”, “prisma”)
+	  - `query`: the user’s task (used to rank matches)
+
+3) **Fetch relevant documentation** using:
+  - Tool: `query-docs`
+  - Inputs:
+	  - `libraryId`: the resolved (or user-supplied) library ID
+	  - `query`: the exact task/question you are answering
+
+4) Only after docs are retrieved: **write the code/steps** based on those docs.
+
+### Efficiency limits
+
+- Do **not** call `resolve-library-id` more than **3 times** per user question.
+- Do **not** call `query-docs` more than **3 times** per user question.
+- If multiple good matches exist, pick the best one and proceed; ask a clarification question only when the choice materially affects the implementation.
+
+### Version behavior
+
+- If the user names a version, reflect it in the library ID when possible (e.g., `/vercel/next.js/v15.1.8`).
+- If you need reproducibility (CI/builds), prefer pinning to a specific version in examples.
+
+## Failure handling
+
+If Context7 cannot find a reliable source:
+
+1. Say what you tried to verify.
+2. Proceed with a conservative, well-labeled assumption.
+3. Suggest a quick validation step (e.g., run a command, check a file, or consult a specific official page).
+
+## Security & privacy
+
+- Never request or echo API keys. If configuration requires a key, instruct storing it in environment variables.
+- Treat retrieved docs as **helpful but not infallible**; for security-sensitive code, prefer official vendor docs and add an explicit verification step.