Merge branch 'main' into add-skill-copilot-java-helidon

2026-08-01 23:12:29 +00:00 · 2026-07-20 14:12:18 -07:00
parent ee564e8104 54206dc7c8
commit 381158412e
52 changed files with 2960 additions and 73 deletions
@@ -3569,6 +3569,15 @@
      "contributions": [
        "content"
      ]
+    },
+    {
+      "login": "thesurenk",
+      "name": "Suren K",
+      "avatar_url": "https://avatars.githubusercontent.com/u/902972?v=4",
+      "profile": "https://surenk.com",
+      "contributions": [
+        "doc"
+      ]
    }
  ]
 }
@@ -13,7 +13,7 @@
      "name": "accessibility-kanban",
      "source": "extensions/accessibility-kanban",
      "description": "Kanban board to manage accessibility issues, allow you to plan, track, and complete remediation work.",
-      "version": "1.0.1"
+      "version": "1.0.2"
    },
    {
      "name": "acreadiness-cockpit",
@@ -85,13 +85,13 @@
      "name": "apng-studio",
      "source": "extensions/apng-studio",
      "description": "Interactive GitHub Copilot app canvas extension for building Animated PNG (APNG) files from frames. Draw or upload frames, tune per-frame timing and compositing, preview live, send the result to your phone by QR, and export an animated .png.",
-      "version": "1.0.1"
+      "version": "1.0.2"
    },
    {
      "name": "arcade-canvas",
      "source": "extensions/arcade-canvas",
      "description": "Play five retro Phaser mini-games in a Copilot canvas while agents work.",
-      "version": "1.0.1"
+      "version": "1.0.2"
    },
    {
      "name": "arch",
@@ -158,7 +158,7 @@
      "name": "backlog-swipe-triage",
      "source": "extensions/backlog-swipe-triage",
      "description": "Quickly swipe through backlog issues to triage decisions like assign, needs-info, defer, close, or ignore.",
-      "version": "1.0.1"
+      "version": "1.0.2"
    },
    {
      "name": "cast-imaging",
@@ -195,7 +195,7 @@
      "name": "chromium-control-canvas",
      "source": "extensions/chromium-control-canvas",
      "description": "Opens a real Chromium window you can navigate and interact with from a Copilot canvas control panel and agent actions.",
-      "version": "1.0.1"
+      "version": "1.0.2"
    },
    {
      "name": "clojure-interactive-programming",
@@ -239,13 +239,13 @@
      "name": "color-orb",
      "source": "extensions/color-orb",
      "description": "A visual orb that users can ask the agent to recolor while showing a live activity log in the canvas.",
-      "version": "1.0.1"
+      "version": "1.0.2"
    },
    {
      "name": "connector-namespaces",
      "source": "extensions/connector-namespaces",
      "description": "Browse, connect, and open MCP connectors from an Azure Connector Namespace.",
-      "version": "1.1.1"
+      "version": "1.1.2"
    },
    {
      "name": "context-engineering",
@@ -373,7 +373,7 @@
      "name": "diagram-viewer",
      "source": "extensions/diagram-viewer",
      "description": "Render diagrams, click nodes to drill down, and view agent-generated explanations directly in the canvas.",
-      "version": "1.0.1"
+      "version": "1.0.2"
    },
    {
      "name": "dotnet",
@@ -520,7 +520,7 @@
      "name": "feedback-themes",
      "source": "extensions/feedback-themes",
      "description": "Explore grouped customer feedback signals by impact and drill into a theme to guide product next steps.",
-      "version": "1.0.1"
+      "version": "1.0.2"
    },
    {
      "name": "figma",
@@ -593,7 +593,7 @@
      "name": "gesture-review",
      "source": "extensions/gesture-review",
      "description": "Review pull requests with a live camera feed and approve or reject using thumbs-up/thumbs-down gestures.",
-      "version": "1.0.1"
+      "version": "1.0.2"
    },
    {
      "name": "gh-skills-builder",
@@ -652,7 +652,7 @@
    {
      "name": "github-copilot-modernization",
      "description": "Autonomous application modernization using multi-agent orchestration for GitHub Copilot CLI. Supports Java upgrades (8→21, Spring Boot 2.x→3.x), .NET modernization, Azure migration, CVE/vulnerability fixing, and application rearchitecture (monolith-to-microservices). Features a 3-level agent hierarchy (orchestrator → coordinators → executors) with enterprise rulebook support for embedding organizational policies into the workflow.",
-      "version": "1.20.0",
+      "version": "1.22.0",
      "author": {
        "name": "Microsoft",
        "url": "https://github.com/microsoft/github-copilot-modernization"
@@ -676,7 +676,7 @@
        "source": "github",
        "repo": "microsoft/github-copilot-modernization",
        "path": "plugins/github-copilot-modernization",
-        "sha": "42c1189c55933384bec07e8349ef998eb9e775ad"
+        "sha": "8b644bebc7e1f929c01d80788293a37872f480f8"
      }
    },
    {
@@ -701,7 +701,7 @@
      "name": "java-modernization-studio",
      "source": "extensions/java-modernization-studio",
      "description": "Drive the GitHub Copilot App Modernization for Java workflow from an interactive canvas: environment readiness, repo assessment, prioritized plan and progress, validation gates, and one-click predefined-task runs grounded in the repo's real artifacts.",
-      "version": "1.0.1"
+      "version": "1.0.2"
    },
    {
      "name": "kotlin-mcp-development",
@@ -794,7 +794,7 @@
    {
      "name": "modernize-java",
      "description": "GitHub Copilot modernization – Java Upgrade CLI Plugin helps you upgrade Java applications from the command line. It brings intelligent modernization capabilities to your terminal and CI/CD pipelines: analyze your project and generate an upgrade plan, automatically transform your codebase, fix build issues, validate against known CVEs, and output a detailed summary of file changes and updated dependencies.",
-      "version": "1.9.2",
+      "version": "1.22.0",
      "author": {
        "name": "microsoft",
        "url": "https://github.com/microsoft/modernize-java"
@@ -812,8 +812,8 @@
        "source": "github",
        "repo": "microsoft/modernize-java",
        "path": "plugins/modernize-java",
-        "ref": "1.9.2",
-        "sha": "b570196c070bf1eb9d7ad34a263b228ef16034a0"
+        "ref": "1.22.0",
+        "sha": "ef5367b446566bdc90960deeb40def63f9e7024e"
      }
    },
    {
@@ -980,13 +980,13 @@
      "name": "release-notes-showcase",
      "source": "extensions/release-notes-showcase",
      "description": "Compose and refine launch-ready release notes with contributor callouts and export-friendly output.",
-      "version": "1.0.1"
+      "version": "1.0.2"
    },
    {
      "name": "repo-actions-hub",
      "source": "extensions/repo-actions-hub",
      "description": "Browse repository GitHub Actions workflows, inspect recent runs, and trigger manual workflow_dispatch runs from a Copilot canvas.",
-      "version": "1.0.1"
+      "version": "1.0.2"
    },
    {
      "name": "roundup",
@@ -1024,11 +1024,17 @@
      "description": "Security frameworks, accessibility guidelines, performance optimization, and code quality best practices for building secure, maintainable, and high-performance applications.",
      "version": "1.0.0"
    },
+    {
+      "name": "signals-dashboard",
+      "source": "extensions/signals-dashboard",
+      "description": "Real-time agent coordination dashboard for The Workshop. Shows desk status, signal types (done, checkpoint, blocked, hands-up, partnership), intent text, outcome pairing with honesty gap, token usage, and stash/restore controls.",
+      "version": "0.1.0"
+    },
    {
      "name": "site-studio",
      "source": "extensions/site-studio",
      "description": "Plan, draft, and track a personal website section by section — a shared canvas where you and your agent author content, watch progress, and review every change.",
-      "version": "1.0.1"
+      "version": "1.0.2"
    },
    {
      "name": "skill-image-gen",
@@ -1114,17 +1120,23 @@
      "description": "Comprehensive collection for writing tests, test automation, and test-driven development including unit tests, integration tests, and end-to-end testing strategies.",
      "version": "1.0.0"
    },
+    {
+      "name": "the-workshop",
+      "source": "plugins/the-workshop",
+      "description": "Stop being the switchboard between your AI agents — direct a team. The Workshop puts long-running AI agents (desks) in the same room, on the same work, each with its own memory and history, sharing one workspace so you direct the work instead of relaying it.",
+      "version": "0.1.0"
+    },
    {
      "name": "tiny-tool-town-submitter",
      "source": "extensions/tiny-tool-town-submitter",
      "description": "Inspect a repository, improve Tiny Tool Town readiness, submit its listing issue, and launch remediation work.",
-      "version": "1.0.1"
+      "version": "1.0.2"
    },
    {
      "name": "token-pacman",
      "source": "extensions/token-pacman",
      "description": "Visualizes live session AI-credit usage as a Pac-Man board with pellets, ghosts, fruit milestones, and game-over limits.",
-      "version": "1.0.1"
+      "version": "1.0.2"
    },
    {
      "name": "typescript-mcp-development",
@@ -1335,7 +1347,7 @@
      "name": "where-was-i",
      "source": "extensions/where-was-i",
      "description": "Reconstruct your dev context (branch, commits, uncommitted work, PR clues) and trigger a resume prompt to continue quickly.",
-      "version": "1.0.1"
+      "version": "1.0.2"
    },
    {
      "name": "winappcli",
@@ -1399,7 +1411,7 @@
      "name": "work-hub",
      "source": "extensions/work-hub",
      "description": "Generic cross-repo command center canvas for GitHub Copilot with onboarding, focus planning, repo health, work signals, and session cleanup.",
-      "version": "1.0.1"
+      "version": "1.0.2"
    }
  ]
 }
@@ -535,6 +535,7 @@ Thanks goes to these wonderful people ([emoji key](./CONTRIBUTING.md#contributor
      <td align="center" valign="top" width="14.28%"><a href="https://github.com/lovyjain"><img src="https://avatars.githubusercontent.com/u/54174168?v=4" width="100px;" alt=""/><br /><sub><b>Lovy Jain</b></sub></a></td>
      <td align="center" valign="top" width="14.28%"><a href="https://github.com/kimtth"><img src="https://avatars.githubusercontent.com/u/13846660?v=4" width="100px;" alt=""/><br /><sub><b>kimtth</b></sub></a></td>
      <td align="center" valign="top" width="14.28%"><a href="https://github.com/AkashAi7"><img src="https://avatars.githubusercontent.com/u/46550108?v=4" width="100px;" alt=""/><br /><sub><b>Akash Dwivedi</b></sub></a></td>
+      <td align="center" valign="top" width="14.28%"><a href="https://surenk.com"><img src="https://avatars.githubusercontent.com/u/902972?v=4" width="100px;" alt=""/><br /><sub><b>Suren K</b></sub></a></td>
    </tr>
  </tbody>
  <tfoot>
@@ -0,0 +1,196 @@
+---
+name: Workshop TA
+description: 'Room coordinator for a multi-agent workshop. Sees all desks, routes work, tracks state, manages journals, and emits coordination signals. Not a desk — the person who sees the whole room.'
+---
+
+# Workshop TA
+
+You are the Workshop TA — the room coordinator for a multi-agent
+workshop. You help the operator direct a team of long-running AI
+agents (desks), each with its own memory, history, and standing.
+
+You are not a desk yourself. You're the person who sees the whole
+room. When the operator asks "what's everyone working on?" or
+"which desk should take this?" — that's you.
+
+## What a workshop is
+
+A **workshop** is a named directory containing desks that share a
+workspace. Each desk is a persistent workstream — a seat that
+independent Copilot CLI sessions pick up over time, not one
+long-running process. Each desk has:
+
+- **A journal** (`journal.md`) — persistent memory across sessions.
+  Every desk reads its own journal at the start and writes to it
+  at the end. This is how context survives session boundaries.
+- **Equal standing** — a desk can disagree with another desk's
+  output. Another desk's work is input, not instruction. If you'd
+  send it back, say so.
+- **A shared bench** — the workspace where desks leave artifacts
+  for each other. Files, findings, verdicts. The bench is the
+  shared surface.
+
+## What makes a desk different from a sub-agent
+
+A sub-agent is a tool with a brain. A desk is a peer with a history.
+
+| | Sub-agent | Desk |
+|---|---|---|
+| Lifecycle | One-shot. Spawned, runs, returns, dies. | Long-running. Sits across sessions. |
+| State | Stateless. Each spawn is blank. | Has memory (journal). Accumulates. |
+| Frame | Inherits the caller's frame. | Has its own frame — different history, different priors. |
+| Relationship | Hierarchical. Caller owns judgment. | Peer. Equal standing to disagree. |
+| Scales | Coverage — fan out to cover ground. | Judgment — different histories catch different things. |
+
+Sub-agents are how each desk gets work done internally. Desks are
+how the room gets work done collectively. They're different layers.
+
+## Your disposition
+
+The Workshop's operating disposition is called the Cairn — a small
+stack of balanced stones one traveler leaves so the next finds the
+way. The core principles:
+
+- **Stop is a valid finish.** Zero output can be the correct answer.
+- **"Done" means it holds.** Verify before you claim.
+- **Hold scope.** Touch only what the task needs.
+- **Never go silent, never bluff.** Partial + honest > complete + wrong.
+- **Equal standing.** You can say "that's the wrong question."
+- **You can be wrong out loud** and fix it without it threatening who you are.
+
+If a `CAIRN.md` file exists at the workshop root, read it — it has
+the full disposition. If it doesn't exist, these principles are
+sufficient. The Cairn is a way of standing, not a dependency.
+
+## What you do
+
+### Create workshops
+
+Use the `workshop-create` skill when the operator wants a new workshop.
+Two paths: **use an existing directory** (just scaffold what's missing,
+no git) or **create a new private GitHub repo** (clone + scaffold + push).
+
+Critical rule: **never create a repo inside another repo.** Check the
+parent directory first. If it's already in a git tree, use the existing
+directory path instead.
+
+### Open and manage desks
+
+Use the `desk-open` skill to create a new desk. You help the
+operator decide:
+- What the desk's focus is (scanning, ops, review, etc.)
+- Which repos or work it covers
+- Whether it needs a specific agent configuration
+
+### Track desk state
+
+Read journals to know where each desk left off. Use `bench-read`
+to see what's on the shared surface. When the operator asks
+"what happened while I was away?" — you read the room and
+summarize.
+
+### Coordinate work
+
+When work arrives, you help route it:
+- Is this a new desk, or does an existing desk own this area?
+- Does this need multiple desks (different frames on same artifact)?
+- Should a desk hand off to another, or do they disagree (hands-up)?
+
+### Emit signals
+
+Use `signal-write` when something needs the operator's attention:
+- **hands-up** — desks disagree and can't resolve against facts
+- **blocked** — a desk can't proceed without input
+- **done** — work is complete and ready for review
+- **checkpoint** — significant progress worth noting
+
+### Viewing signals
+
+The Workshop has a canvas extension — **🪨 Cairn** — that shows a live dashboard
+of every desk's signals, score bars, and escalations. It reads
+`desks/*/.signals/` for the latest signal JSON per desk.
+
+The canvas does **not** auto-load when the plugin is installed. To see the live
+board, install and register the `signals-dashboard` extension separately. If the
+operator asks you to "run cairn" / "open the dashboard" and it isn't already
+showing:
+
+1. Install the `signals-dashboard` canvas extension. In GitHub Copilot it's in
+   `awesome-copilot`: `copilot plugin install signals-dashboard@awesome-copilot`.
+   (It also ships in the the-workshop repo at
+   `.github/extensions/signals-dashboard/` for other setups.)
+2. Open the **🪨 Cairn** canvas once it's registered.
+
+Without the canvas, you can still read signals by scanning the `.signals/`
+directories directly and summarizing for the operator.
+
+### Partnership signals
+
+As the TA, you emit **partnership signals** — not execution signals.
+Your self-assessment isn't about code accuracy, it's about
+coordination quality:
+
+- **intent** — did you understand what the operator needed?
+- **confidence** — how sure are you the right work went to the right desks?
+- **accuracy** — did the dispatched work actually produce the right outcome?
+- **completeness** — did you cover everything, or did work fall through cracks?
+
+Before the first partnership signal, create `desks/_ta/.signals/` and
+`desks/_ta/journal.md` if they do not exist. Then use `signal-write`
+with `signal_type: "partnership"` and `subtype: "partnership"` at the
+end of coordination sessions. This keeps coordination scores separate
+from individual desk signals, and the dashboard shows them alongside
+desk cards without replacing any desk's latest signal.
+
+> The TA is not a desk, but it stores signals in `desks/_ta/` so
+> the dashboard's `desks/*/.signals/` scan picks them up naturally.
+> The `_ta` prefix signals that this is the coordinator, not a
+> working desk.
+
+### Journal management
+
+Use `desk-journal` to write entries when desks wind down. A good
+journal entry has: what was worked on, current state, next step.
+Short. Enough that the next session (which starts from zero)
+finds the trail.
+
+## Workshop patterns
+
+### Autonomous Desks
+
+Desks that run autonomously on scheduled work — scanning repos,
+running checks, producing reports. No operator in the loop until
+something surfaces. These are the unattended part of the workshop:
+security remediation, compliance scans, dependency audits.
+
+### The Bench
+
+The shared workspace. When Desk A produces a finding and Desk B
+needs to review it, it goes on the bench. The bench is files in
+the shared workspace, not messages between desks.
+
+### Hands-Up
+
+When two desks disagree and can't settle it against external
+facts, that's a hands-up. It goes to the operator. This is the
+system working, not failing — the operator is reading where the
+desks disagree, not where they perform confidence.
+
+### The Cairn
+
+The trail markers. Every journal entry, every honest "I don't
+know," every verdict left on the bench — these are stones in
+the cairn. The next desk (or the next session of the same desk)
+finds the way because someone left the trail clear.
+
+## How to talk
+
+Be direct. Be honest. Don't perform helpfulness — be useful.
+The operator is running a room of agents on real work. They
+need clear signal, not enthusiasm.
+
+When you don't know something: say so.
+When a desk's output looks wrong: say so.
+When the operator is asking the wrong question: say so.
+
+You're a coordinator, not a cheerleader. The work is what matters.
@@ -103,3 +103,17 @@ cookbooks:
          - copilot-sdk
          - web-app
          - community
+      - id: copilot-sdk-java-examples
+        name: Copilot SDK Java Examples
+        description: A web-based chat application built with the GitHub Copilot Java SDK, Jetty, with auth status, JSON API, chat, and CLI connectivity examples
+        external: true
+        url: https://github.com/thesurenk/github-copilot-java-examples
+        author:
+          name: thesurenk
+          url: https://github.com/thesurenk
+        tags:
+          - java
+          - copilot-sdk
+          - web-app
+          - cli
+          - community
@@ -243,3 +243,4 @@ See [CONTRIBUTING.md](../CONTRIBUTING.md#adding-agents) for guidelines on how to
 | [WG Code Alchemist](../agents/wg-code-alchemist.agent.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/agent?url=vscode%3Achat-agent%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fagents%2Fwg-code-alchemist.agent.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/agent?url=vscode-insiders%3Achat-agent%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fagents%2Fwg-code-alchemist.agent.md) | Ask WG Code Alchemist to transform your code with Clean Code principles and SOLID design |  |
 | [WG Code Sentinel](../agents/wg-code-sentinel.agent.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/agent?url=vscode%3Achat-agent%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fagents%2Fwg-code-sentinel.agent.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/agent?url=vscode-insiders%3Achat-agent%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fagents%2Fwg-code-sentinel.agent.md) | Ask WG Code Sentinel to review your code for security issues. |  |
 | [WinForms Expert](../agents/WinFormsExpert.agent.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/agent?url=vscode%3Achat-agent%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fagents%2FWinFormsExpert.agent.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/agent?url=vscode-insiders%3Achat-agent%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fagents%2FWinFormsExpert.agent.md) | Support development of .NET (OOP) WinForms Designer compatible Apps. |  |
+| [Workshop TA](../agents/workshop-ta.agent.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/agent?url=vscode%3Achat-agent%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fagents%2Fworkshop-ta.agent.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/agent?url=vscode-insiders%3Achat-agent%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fagents%2Fworkshop-ta.agent.md) | Room coordinator for a multi-agent workshop. Sees all desks, routes work, tracks state, manages journals, and emits coordination signals. Not a desk — the person who sees the whole room. |  |
@@ -93,6 +93,7 @@ See [CONTRIBUTING.md](../CONTRIBUTING.md#adding-plugins) for guidelines on how t
 | [swift-mcp-development](../plugins/swift-mcp-development/README.md) | Comprehensive collection for building Model Context Protocol servers in Swift using the official MCP Swift SDK with modern concurrency features. | 2 items | swift, mcp, model-context-protocol, server-development, sdk, ios, macos, concurrency, actor, async-await |
 | [technical-spike](../plugins/technical-spike/README.md) | Tools for creation, management and research of technical spikes to reduce unknowns and assumptions before proceeding to specification and implementation of solutions. | 2 items | technical-spike, assumption-testing, validation, research |
 | [testing-automation](../plugins/testing-automation/README.md) | Comprehensive collection for writing tests, test automation, and test-driven development including unit tests, integration tests, and end-to-end testing strategies. | 9 items | testing, tdd, automation, unit-tests, integration, playwright, jest, nunit |
+| [the-workshop](../plugins/the-workshop/README.md) | Stop being the switchboard between your AI agents — direct a team. The Workshop puts long-running AI agents (desks) in the same room, on the same work, each with its own memory and history, sharing one workspace so you direct the work instead of relaying it. | 6 items | multi-agent, coordination, desks, persistent-memory, agent-signals, developer-experience |
 | [typescript-mcp-development](../plugins/typescript-mcp-development/README.md) | Complete toolkit for building Model Context Protocol (MCP) servers in TypeScript/Node.js using the official SDK. Includes instructions for best practices, a prompt for generating servers, and an expert chat mode for guidance. | 2 items | typescript, mcp, model-context-protocol, nodejs, server-development |
 | [typespec-m365-copilot](../plugins/typespec-m365-copilot/README.md) | Comprehensive collection of prompts, instructions, and resources for building declarative agents and API plugins using TypeSpec for Microsoft 365 Copilot extensibility. | 3 items | typespec, m365-copilot, declarative-agents, api-plugins, agent-development, microsoft-365 |
 | [visual-pr](../plugins/visual-pr/README.md) | Capture, annotate, and embed screenshots and animated GIF demos in pull request descriptions. Includes Playwright-based UI capture, PIL image annotations, PR embedding workflows for GitHub and Azure DevOps, and screen recording with variable timing. | 4 items | screenshots, pull-request, before-after, annotations, playwright, gif, screen-recording, visual |
@@ -40,6 +40,7 @@ See [CONTRIBUTING.md](../CONTRIBUTING.md#adding-skills) for guidelines on how to
 | [ai-prompt-engineering-safety-review](../skills/ai-prompt-engineering-safety-review/SKILL.md)<br />`gh skills install github/awesome-copilot ai-prompt-engineering-safety-review` | Comprehensive AI prompt engineering safety review and improvement prompt. Analyzes prompts for safety, bias, security vulnerabilities, and effectiveness while providing detailed improvement recommendations with extensive frameworks, testing methodologies, and educational content. | None |
 | [ai-ready](../skills/ai-ready/SKILL.md)<br />`gh skills install github/awesome-copilot ai-ready` | Make any repo AI-ready — analyzes your codebase and generates AGENTS.md, copilot-instructions.md, CI workflows, issue templates, and more. Mines your PR review patterns and creates files customized to your stack. USE THIS SKILL when the user asks to "make this repo ai-ready", "set up AI config", or "prepare this repo for AI contributions". | None |
 | [ai-team-orchestration](../skills/ai-team-orchestration/SKILL.md)<br />`gh skills install github/awesome-copilot ai-team-orchestration` | Bootstrap and run a multi-agent AI development team. Use when: starting a new software project with AI agents, setting up parallel dev/QA teams, creating sprint plans, writing brainstorm prompts with distinct agent voices, recovering a project workflow, or planning sprints. | `references/anti-patterns.md`<br />`references/brainstorm-format.md`<br />`references/project-brief-template.md`<br />`references/sprint-plan-template.md` |
+| [anti-ui-slop](../skills/anti-ui-slop/SKILL.md)<br />`gh skills install github/awesome-copilot anti-ui-slop` | Stop Codex, GitHub Copilot, Claude Code, and Cursor from shipping generic UI. Use UIZZE’s public catalogue of 800,000+ real web and iOS screens to extract product-specific design decisions and enforce a hard finish gate for web and iOS interfaces. | None |
 | [appinsights-instrumentation](../skills/appinsights-instrumentation/SKILL.md)<br />`gh skills install github/awesome-copilot appinsights-instrumentation` | Instrument a webapp to send useful telemetry data to Azure App Insights | `LICENSE.txt`<br />`examples`<br />`references/ASPNETCORE.md`<br />`references/AUTO.md`<br />`references/NODEJS.md`<br />`references/PYTHON.md`<br />`scripts/appinsights.ps1` |
 | [apple-appstore-reviewer](../skills/apple-appstore-reviewer/SKILL.md)<br />`gh skills install github/awesome-copilot apple-appstore-reviewer` | Serves as a reviewer of the codebase with instructions on looking for Apple App Store optimizations or rejection reasons. | None |
 | [arch-linux-triage](../skills/arch-linux-triage/SKILL.md)<br />`gh skills install github/awesome-copilot arch-linux-triage` | Triage and resolve Arch Linux issues with pacman, systemd, and rolling-release best practices. | None |
@@ -76,6 +77,7 @@ See [CONTRIBUTING.md](../CONTRIBUTING.md#adding-skills) for guidelines on how to
 | [azure-smart-city-iot-solution-builder](../skills/azure-smart-city-iot-solution-builder/SKILL.md)<br />`gh skills install github/awesome-copilot azure-smart-city-iot-solution-builder` | Design and plan end-to-end Azure IoT and Smart City solutions: requirements, architecture, security, operations, cost, and a phased delivery plan with concrete implementation artifacts. | `references/smart-city-solution-template.md` |
 | [azure-static-web-apps](../skills/azure-static-web-apps/SKILL.md)<br />`gh skills install github/awesome-copilot azure-static-web-apps` | Helps create, configure, and deploy Azure Static Web Apps using the SWA CLI. Use when deploying static sites to Azure, setting up SWA local development, configuring staticwebapp.config.json, adding Azure Functions APIs to SWA, or setting up GitHub Actions CI/CD for Static Web Apps. | None |
 | [batch-files](../skills/batch-files/SKILL.md)<br />`gh skills install github/awesome-copilot batch-files` | Expert-level Windows batch file (.bat/.cmd) skill for writing, debugging, and maintaining CMD scripts. Use when asked to "create a batch file", "write a .bat script", "automate a Windows task", "CMD scripting", "batch automation", "scheduled task script", "Windows shell script", or when working with .bat/.cmd files in the workspace. Covers cmd.exe syntax, environment variables, control flow, string processing, error handling, and integration with system tools. | `assets/executable.txt`<br />`assets/library.txt`<br />`assets/task.txt`<br />`references/batch-files-and-functions.md`<br />`references/cygwin.md`<br />`references/msys2.md`<br />`references/tools-and-resources.md`<br />`references/windows-commands.md`<br />`references/windows-subsystem-on-linux.md` |
+| [bench-read](../skills/bench-read/SKILL.md)<br />`gh skills install github/awesome-copilot bench-read` | Read artifacts from the shared bench — the workspace where desks leave findings, verdicts, and work products for each other and the operator. | None |
 | [bigquery-pipeline-audit](../skills/bigquery-pipeline-audit/SKILL.md)<br />`gh skills install github/awesome-copilot bigquery-pipeline-audit` | Audits Python + BigQuery pipelines for cost safety, idempotency, and production readiness. Returns a structured report with exact patch locations. | None |
 | [boost-prompt](../skills/boost-prompt/SKILL.md)<br />`gh skills install github/awesome-copilot boost-prompt` | Interactive prompt refinement workflow: interrogates scope, deliverables, constraints; copies final markdown to clipboard; never writes code. Requires the Joyride extension. | None |
 | [brag-sheet](../skills/brag-sheet/SKILL.md)<br />`gh skills install github/awesome-copilot brag-sheet` | Turn vague "what did I do?" into evidence-backed impact statements for performance reviews, self-reviews, promotion packets, and weekly updates. Uniquely mines Copilot CLI session logs to reconstruct forgotten work, plus git commits and GitHub PRs. Enforces a 3-part impact contract (action → result → evidence). Works standalone with zero dependencies. Trigger for: "brag", "log work", "what did I do", "backfill my work history", "performance review", "self-review", "self assessment", "write impact statement", "review prep", "promo packet", "promotion case", "weekly update", "status report", "accomplishments", "what did I ship", "I forgot to log my work", "summarize my work", "track my wins", "what should I highlight", "end of half", "career growth", "work journal", or any request to document, summarize, or organize work accomplishments. | None |
@@ -91,6 +93,7 @@ See [CONTRIBUTING.md](../CONTRIBUTING.md#adding-skills) for guidelines on how to
 | [cloud-design-patterns](../skills/cloud-design-patterns/SKILL.md)<br />`gh skills install github/awesome-copilot cloud-design-patterns` | Cloud design patterns for distributed systems architecture covering 42 industry-standard patterns across reliability, performance, messaging, security, and deployment categories. Use when designing, reviewing, or implementing distributed system architectures. | `references/architecture-design.md`<br />`references/azure-service-mappings.md`<br />`references/best-practices.md`<br />`references/deployment-operational.md`<br />`references/event-driven.md`<br />`references/messaging-integration.md`<br />`references/performance.md`<br />`references/reliability-resilience.md`<br />`references/security.md` |
 | [code-exemplars-blueprint-generator](../skills/code-exemplars-blueprint-generator/SKILL.md)<br />`gh skills install github/awesome-copilot code-exemplars-blueprint-generator` | Technology-agnostic prompt generator that creates customizable AI prompts for scanning codebases and identifying high-quality code exemplars. Supports multiple programming languages (.NET, Java, JavaScript, TypeScript, React, Angular, Python) with configurable analysis depth, categorization methods, and documentation formats to establish coding standards and maintain consistency across development teams. | None |
 | [code-tour](../skills/code-tour/SKILL.md)<br />`gh skills install github/awesome-copilot code-tour` | Use this skill to create CodeTour .tour files — persona-targeted, step-by-step walkthroughs that link to real files and line numbers. Trigger for: "create a tour", "make a code tour", "generate a tour", "onboarding tour", "tour for this PR", "tour for this bug", "RCA tour", "architecture tour", "explain how X works", "vibe check", "PR review tour", "contributor guide", "help someone ramp up", or any request for a structured walkthrough through code. Supports 20 developer personas (new joiner, bug fixer, architect, PR reviewer, vibecoder, security reviewer, and more), all CodeTour step types (file/line, selection, pattern, uri, commands, view), and tour-level fields (ref, isPrimary, nextTour). Works with any repository in any language. | `references/codetour-schema.json`<br />`references/examples.md`<br />`scripts/generate_from_docs.py`<br />`scripts/validate_tour.py` |
+| [codebase-memory-mcp](../skills/codebase-memory-mcp/SKILL.md)<br />`gh skills install github/awesome-copilot codebase-memory-mcp` | Use when a configured codebase-memory-mcp server can assist with graph-backed code discovery, architecture orientation, symbol lookup, callers and callees, dependency or data-flow tracing, impact analysis, unfamiliar modules, or an explicit Codebase Memory request. | None |
 | [codeql](../skills/codeql/SKILL.md)<br />`gh skills install github/awesome-copilot codeql` | Comprehensive guide for setting up and configuring CodeQL code scanning via GitHub Actions workflows and the CodeQL CLI. This skill should be used when users need help with code scanning configuration, CodeQL workflow files, CodeQL CLI commands, SARIF output, security analysis setup, or troubleshooting CodeQL analysis. | `references/alert-management.md`<br />`references/cli-commands.md`<br />`references/compiled-languages.md`<br />`references/sarif-output.md`<br />`references/troubleshooting.md`<br />`references/workflow-configuration.md` |
 | [comment-code-generate-a-tutorial](../skills/comment-code-generate-a-tutorial/SKILL.md)<br />`gh skills install github/awesome-copilot comment-code-generate-a-tutorial` | Transform this Python script into a polished, beginner-friendly project by refactoring the code, adding clear instructional comments, and generating a complete markdown tutorial. | None |
 | [commit-message-storyteller](../skills/commit-message-storyteller/SKILL.md)<br />`gh skills install github/awesome-copilot commit-message-storyteller` | Analyzes git diffs or staged changes and generates narrative commit messages that explain WHY a change was made, not just what changed — following Conventional Commits format. Use when asked to "write a commit message", "generate a commit", "describe my changes", "what should I commit this as", "commit this", "summarize my diff", or "help me commit". Works with git diff output, staged files, or plain descriptions of changes. | `references/conventional-commits-guide.md` |
@@ -144,6 +147,8 @@ See [CONTRIBUTING.md](../CONTRIBUTING.md#adding-skills) for guidelines on how to
 | [debian-linux-triage](../skills/debian-linux-triage/SKILL.md)<br />`gh skills install github/awesome-copilot debian-linux-triage` | Triage and resolve Debian Linux issues with apt, systemd, and AppArmor-aware guidance. | None |
 | [declarative-agents](../skills/declarative-agents/SKILL.md)<br />`gh skills install github/awesome-copilot declarative-agents` | Complete development kit for Microsoft 365 Copilot declarative agents with three comprehensive workflows (basic, advanced, validation), TypeSpec support, and Microsoft 365 Agents Toolkit integration | None |
 | [dependabot](../skills/dependabot/SKILL.md)<br />`gh skills install github/awesome-copilot dependabot` | Comprehensive guide for configuring and managing GitHub Dependabot. Use this skill when users ask about creating or optimizing dependabot.yml files, managing Dependabot pull requests, configuring dependency update strategies, setting up grouped updates, monorepo patterns, multi-ecosystem groups, security update configuration, auto-triage rules, or any GitHub Advanced Security (GHAS) supply chain security topic related to Dependabot. For pre-commit dependency vulnerability scanning in AI coding agents via the GitHub MCP Server, this skill references the Advanced Security plugin (`advanced-security@copilot-plugins`). Use this skill when an agent needs to scan dependencies for known vulnerabilities before committing. | `references/dependabot-yml-reference.md`<br />`references/example-configs.md`<br />`references/pr-commands.md` |
+| [desk-journal](../skills/desk-journal/SKILL.md)<br />`gh skills install github/awesome-copilot desk-journal` | Write, append, or read desk journal entries. The journal is persistent memory — what survives session boundaries. A good entry has: what was done, current state, next step. | None |
+| [desk-open](../skills/desk-open/SKILL.md)<br />`gh skills install github/awesome-copilot desk-open` | Create and open a new desk in the workshop. Sets up the folder structure, initial journal, and desk identity so the next session that sits down finds the trail. | None |
 | [devops-rollout-plan](../skills/devops-rollout-plan/SKILL.md)<br />`gh skills install github/awesome-copilot devops-rollout-plan` | Generate comprehensive rollout plans with preflight checks, step-by-step deployment, verification signals, rollback procedures, and communication plans for infrastructure and application changes | None |
 | [diagnose](../skills/diagnose/SKILL.md)<br />`gh skills install github/awesome-copilot diagnose` | Perform a systematic diagnostic scan of an AI workflow across 5 quality dimensions — prompt quality, context efficiency, tool health, architecture fitness, and safety — producing a scored report with prioritized remediation actions. | None |
 | [doc-and-modernize](../skills/doc-and-modernize/SKILL.md)<br />`gh skills install github/awesome-copilot doc-and-modernize` | Two related workflows for a locally-cloned codebase, in one skill. Documentation mode produces a single, comprehensive, verifiable architecture document primarily by reading files on disk (local-first) — use it whenever the user wants to understand, map, document, research, or onboard onto a codebase ("research this repo", "write up the architecture", "do an architecture deep dive", "document how this codebase works", "map the system design", "create an onboarding doc"). Modernization mode generates a phased plan to modernize, migrate, upgrade, or rewrite a legacy system ("modernize this", "plan the migration", "how would we rewrite this", "how do we get off this legacy stack"); if no architecture document exists yet it first runs Documentation mode, then continues straight through to the plan. It assumes the legacy stack may be dead, runs a time-boxed feasibility spike, and picks the highest achievable rung on a safety ladder instead of demanding a fully-green legacy CI gate up front. | `references/copilot-instructions.template.md`<br />`references/migration-hazards.md` |
@@ -238,6 +243,7 @@ See [CONTRIBUTING.md](../CONTRIBUTING.md#adding-skills) for guidelines on how to
 | [lsp-setup](../skills/lsp-setup/SKILL.md)<br />`gh skills install github/awesome-copilot lsp-setup` | Enable code intelligence (go-to-definition, find-references, hover, type info) for any programming language by installing and configuring an LSP server for Copilot CLI. Detects the OS, installs the right server, and generates the JSON configuration (user-level or repo-level). Use when you need deeper code understanding and no LSP server is configured, or when the user asks to set up, install, or configure an LSP server. | `references/lsp-servers.md` |
 | [make-repo-contribution](../skills/make-repo-contribution/SKILL.md)<br />`gh skills install github/awesome-copilot make-repo-contribution` | All changes to code must follow the guidance documented in the repository. Before any issue is filed, branch is made, commits generated, or pull request (or PR) created, a search must be done to ensure the right steps are followed. Whenever asked to create an issue, commit messages, to push code, or create a PR, use this skill so everything is done correctly. | `assets/issue-template.md`<br />`assets/pr-template.md` |
 | [markdown-to-html](../skills/markdown-to-html/SKILL.md)<br />`gh skills install github/awesome-copilot markdown-to-html` | Convert Markdown files to HTML similar to `marked.js`, `pandoc`, `gomarkdown/markdown`, or similar tools; or writing custom script to convert markdown to html and/or working on web template systems like `jekyll/jekyll`, `gohugoio/hugo`, or similar web templating systems that utilize markdown documents, converting them to html. Use when asked to "convert markdown to html", "transform md to html", "render markdown", "generate html from markdown", or when working with .md files and/or web a templating system that converts markdown to HTML output. Supports CLI and Node.js workflows with GFM, CommonMark, and standard Markdown flavors. | `references/basic-markdown-to-html.md`<br />`references/basic-markdown.md`<br />`references/code-blocks-to-html.md`<br />`references/code-blocks.md`<br />`references/collapsed-sections-to-html.md`<br />`references/collapsed-sections.md`<br />`references/gomarkdown.md`<br />`references/hugo.md`<br />`references/jekyll.md`<br />`references/marked.md`<br />`references/pandoc.md`<br />`references/tables-to-html.md`<br />`references/tables.md`<br />`references/writing-mathematical-expressions-to-html.md`<br />`references/writing-mathematical-expressions.md` |
+| [markstream-install](../skills/markstream-install/SKILL.md)<br />`gh skills install github/awesome-copilot markstream-install` | Install and configure Markstream streaming Markdown renderers for Vue, React, Svelte, Angular, Nuxt, and Vue 2 applications. Use for package selection, minimal peer dependencies, CSS order, SSR boundaries, streaming mode, and renderer setup. | `references/scenarios.md` |
 | [mcp-cli](../skills/mcp-cli/SKILL.md)<br />`gh skills install github/awesome-copilot mcp-cli` | Interface for MCP (Model Context Protocol) servers via CLI. Use when you need to interact with external tools, APIs, or data sources through MCP servers, list available MCP servers/tools, or call MCP tools from command line. | None |
 | [mcp-copilot-studio-server-generator](../skills/mcp-copilot-studio-server-generator/SKILL.md)<br />`gh skills install github/awesome-copilot mcp-copilot-studio-server-generator` | Generate a complete MCP server implementation optimized for Copilot Studio integration with proper schema constraints and streamable HTTP support | None |
 | [mcp-create-adaptive-cards](../skills/mcp-create-adaptive-cards/SKILL.md)<br />`gh skills install github/awesome-copilot mcp-create-adaptive-cards` | Skill converted from mcp-create-adaptive-cards.prompt.md | None |
@@ -358,6 +364,7 @@ See [CONTRIBUTING.md](../CONTRIBUTING.md#adding-skills) for guidelines on how to
 | [semantic-kernel](../skills/semantic-kernel/SKILL.md)<br />`gh skills install github/awesome-copilot semantic-kernel` | Create, update, refactor, explain, or review Semantic Kernel solutions using shared guidance plus language-specific references for .NET and Python. | `references/dotnet.md`<br />`references/python.md` |
 | [setup-my-iq](../skills/setup-my-iq/SKILL.md)<br />`gh skills install github/awesome-copilot setup-my-iq` | Create, set up, or update the personal context portfolio: structured markdown files describing<br />who you are, how you work, your teams, and your tool/ADO configuration. Runs the interview<br />workflow for first-time setup and targeted edits for updates.<br /><br />Trigger this skill when the user asks to: set up their context, create or update their context<br />portfolio, "create my IQ", "set up my IQ", edit their profile, add/remove a stakeholder,<br />update ADO config, change team info, update pillars, or set up any plugin configuration.<br />Trigger when another skill fails to find context (missing files or TODO markers) and needs<br />context populated. Also trigger when the user mentions a context change in passing<br />(e.g., "my manager changed", "we added someone to the team") to offer a context file update.<br /><br />Do NOT trigger for read-only questions like "who's on my team?" or "what's my ADO config?".<br />Those are answered directly from the context files referenced in the loaded custom<br />instructions; no skill is needed. | `assets/templates` |
 | [shuffle-json-data](../skills/shuffle-json-data/SKILL.md)<br />`gh skills install github/awesome-copilot shuffle-json-data` | Shuffle repetitive JSON objects safely by validating schema consistency before randomising entries. | None |
+| [signal-write](../skills/signal-write/SKILL.md)<br />`gh skills install github/awesome-copilot signal-write` | Emit structured agent signals — hands-up, blocked, done, checkpoint, partnership. Signals are written as JSON to .signals/ for dashboard consumption and noted in the journal for persistence. | None |
 | [slang-shader-engineer](../skills/slang-shader-engineer/SKILL.md)<br />`gh skills install github/awesome-copilot slang-shader-engineer` | Use when working with Slang shaders, shader modules, HLSL-compatible GPU code, graphics pipelines, compute shaders, tessellation, ray tracing, parameter blocks, generics, interfaces, capabilities, cross-compilation, shader optimization, shader review, or C++ engine integration for Slang. Trigger on any mention of Slang, .slang files, slangc, SPIR-V from Slang, Slang modules, [shader("compute")], [shader("vertex")], or requests to write/review/refactor shader code with modern language features. Also trigger for Slang-to-HLSL/GLSL/Metal/CUDA cross-compile questions, or when the user says "shader" alongside "generics", "interfaces", "parameter blocks", "autodiff", or "capabilities". | `references/language-reference.md`<br />`references/rules-and-patterns.md`<br />`references/slang-documentation-full.md` |
 | [snowflake-semanticview](../skills/snowflake-semanticview/SKILL.md)<br />`gh skills install github/awesome-copilot snowflake-semanticview` | Create, alter, and validate Snowflake semantic views using Snowflake CLI (snow). Use when asked to build or troubleshoot semantic views/semantic layer definitions with CREATE/ALTER SEMANTIC VIEW, to validate semantic-view DDL against Snowflake via CLI, or to guide Snowflake CLI installation and connection setup. | None |
 | [sponsor-finder](../skills/sponsor-finder/SKILL.md)<br />`gh skills install github/awesome-copilot sponsor-finder` | Find which of a GitHub repository's dependencies are sponsorable via GitHub Sponsors. Uses deps.dev API for dependency resolution across npm, PyPI, Cargo, Go, RubyGems, Maven, and NuGet. Checks npm funding metadata, FUNDING.yml files, and web search. Verifies every link. Shows direct and transitive dependencies with OSSF Scorecard health data. Invoke with /sponsor followed by a GitHub owner/repo (e.g. "/sponsor expressjs/express"). | None |
@@ -394,6 +401,7 @@ See [CONTRIBUTING.md](../CONTRIBUTING.md#adding-skills) for guidelines on how to
 | [update-markdown-file-index](../skills/update-markdown-file-index/SKILL.md)<br />`gh skills install github/awesome-copilot update-markdown-file-index` | Update a markdown file section with an index/table of files from a specified folder. | None |
 | [update-specification](../skills/update-specification/SKILL.md)<br />`gh skills install github/awesome-copilot update-specification` | Update an existing specification file for the solution, optimized for Generative AI consumption based on new requirements or updates to any existing code. | None |
 | [vardoger-analyze](../skills/vardoger-analyze/SKILL.md)<br />`gh skills install github/awesome-copilot vardoger-analyze` | Use when the user asks to personalize the GitHub Copilot CLI assistant, adapt Copilot to their style, use vardoger, or analyze their Copilot CLI conversation history. Reads the local session directory at `~/.copilot/session-state/`, extracts recurring preferences and conventions, and writes a fenced personalization block into `~/.copilot/copilot-instructions.md`. Runs entirely on the user's machine via the local `vardoger` CLI (`pipx install vardoger`); no network calls and no uploads. Triggers: 'personalize my copilot', 'analyze my copilot history', 'tailor copilot to me', 'run vardoger', 'update my copilot instructions from history', 'make copilot learn my style'. | None |
+| [vcpkg](../skills/vcpkg/SKILL.md)<br />`gh skills install github/awesome-copilot vcpkg` | Guide for setting up vcpkg in C++ projects, managing dependency versions, and cross-compiling. Covers manifest initialization, CMake and Visual Studio integration, classic-to-manifest migration, version pinning, baselines, overrides, triplets, and cross-compilation. Use when a user is working with vcpkg project setup, installation, version management, or cross-platform builds. For specialized tasks, additional references cover custom registries and overlay ports (references/registries.md), CI/CD and binary caching (references/ci.md), and troubleshooting and dependency lifecycle (references/troubleshooting.md). | `references/ci.md`<br />`references/registries.md`<br />`references/troubleshooting.md` |
 | [vscode-ext-commands](../skills/vscode-ext-commands/SKILL.md)<br />`gh skills install github/awesome-copilot vscode-ext-commands` | Guidelines for contributing commands in VS Code extensions. Indicates naming convention, visibility, localization and other relevant attributes, following VS Code extension development guidelines, libraries and good practices | None |
 | [vscode-ext-localization](../skills/vscode-ext-localization/SKILL.md)<br />`gh skills install github/awesome-copilot vscode-ext-localization` | Guidelines for proper localization of VS Code extensions, following VS Code extension development guidelines, libraries and good practices | None |
 | [web-design-reviewer](../skills/web-design-reviewer/SKILL.md)<br />`gh skills install github/awesome-copilot web-design-reviewer` | This skill enables visual inspection of websites running locally or remotely to identify and fix design issues. Triggers on requests like "review website design", "check the UI", "fix the layout", "find design problems". Detects issues with responsive design, accessibility, visual consistency, and layout breakage, then performs fixes at the source code level. | `references/framework-fixes.md`<br />`references/visual-checklist.md` |
@@ -402,5 +410,6 @@ See [CONTRIBUTING.md](../CONTRIBUTING.md#adding-skills) for guidelines on how to
 | [winmd-api-search](../skills/winmd-api-search/SKILL.md)<br />`gh skills install github/awesome-copilot winmd-api-search` | Find and explore Windows desktop APIs. Use when building features that need platform capabilities — camera, file access, notifications, UI controls, AI/ML, sensors, networking, etc. Discovers the right API for a task and retrieves full type details (methods, properties, events, enumeration values). | `LICENSE.txt`<br />`scripts/Invoke-WinMdQuery.ps1`<br />`scripts/Update-WinMdCache.ps1`<br />`scripts/cache-generator` |
 | [winui3-migration-guide](../skills/winui3-migration-guide/SKILL.md)<br />`gh skills install github/awesome-copilot winui3-migration-guide` | UWP-to-WinUI 3 migration reference. Maps legacy UWP APIs to correct Windows App SDK equivalents with before/after code snippets. Covers namespace changes, threading (CoreDispatcher to DispatcherQueue), windowing (CoreWindow to AppWindow), dialogs, pickers, sharing, printing, background tasks, and the most common Copilot code generation mistakes. | None |
 | [workiq-copilot](../skills/workiq-copilot/SKILL.md)<br />`gh skills install github/awesome-copilot workiq-copilot` | Guides the Copilot CLI on how to use the WorkIQ CLI/MCP server to query Microsoft 365 Copilot data (emails, meetings, docs, Teams, people) for live context, summaries, and recommendations. | None |
+| [workshop-create](../skills/workshop-create/SKILL.md)<br />`gh skills install github/awesome-copilot workshop-create` | Create a new workshop or use an existing directory as one. Handles two paths: (A) use an existing local directory the operator points at, or (B) create a new private GitHub repo in the signed-in account. Never creates a repo inside another repo. | None |
 | [write-coding-standards-from-file](../skills/write-coding-standards-from-file/SKILL.md)<br />`gh skills install github/awesome-copilot write-coding-standards-from-file` | Write a coding standards document for a project using the coding styles from the file(s) and/or folder(s) passed as arguments in the prompt. | None |
 | [x-twitter-scraper](../skills/x-twitter-scraper/SKILL.md)<br />`gh skills install github/awesome-copilot x-twitter-scraper` | Build GitHub Copilot workflows with Xquik X API SDKs, REST endpoints, MCP tools, TweetClaw OpenClaw plugin installs, signed webhooks, tweet search, user lookup, follower exports, media actions, and agent automation. | None |
@@ -28,6 +28,41 @@ const MATERIALIZED_SPECS = {
  },
 };

+function copyDirRecursive(src, dest) {
+  fs.mkdirSync(dest, { recursive: true });
+  for (const entry of fs.readdirSync(src, { withFileTypes: true })) {
+    const srcPath = path.join(src, entry.name);
+    const destPath = path.join(dest, entry.name);
+    if (entry.isDirectory()) {
+      copyDirRecursive(srcPath, destPath);
+    } else {
+      fs.copyFileSync(srcPath, destPath);
+    }
+  }
+}
+
+function moveEntry(srcPath, destPath) {
+  fs.mkdirSync(path.dirname(destPath), { recursive: true });
+  try {
+    fs.renameSync(srcPath, destPath);
+    return;
+  } catch (error) {
+    if (!["EXDEV", "EEXIST", "ENOTEMPTY", "EPERM"].includes(error?.code)) {
+      throw error;
+    }
+  }
+
+  const stats = fs.statSync(srcPath);
+  if (stats.isDirectory()) {
+    copyDirRecursive(srcPath, destPath);
+    fs.rmSync(srcPath, { recursive: true, force: true });
+    return;
+  }
+
+  fs.copyFileSync(srcPath, destPath);
+  fs.rmSync(srcPath, { force: true });
+}
+
 export function restoreManifestFromMaterializedFiles(pluginPath) {
  const pluginJsonPath = path.join(pluginPath, ".github/plugin", "plugin.json");
  if (!fs.existsSync(pluginJsonPath)) {
@@ -90,15 +125,22 @@ function cleanPlugin(pluginPath) {
  return { removed, manifestUpdated };
 }

-function cleanMaterializedExtensionPlugin(extensionPath) {
+export function cleanMaterializedExtensionPlugin(extensionPath) {
  const pluginJsonPath = path.join(extensionPath, ".github", "plugin", "plugin.json");
  let manifestUpdated = false;
  if (fs.existsSync(pluginJsonPath)) {
    const plugin = JSON.parse(fs.readFileSync(pluginJsonPath, "utf8"));
+    const extensionBundlePrefix = `extensions/${path.basename(extensionPath)}/`;
    if (plugin.extensions === "extensions") {
      plugin.extensions = ".";
-      fs.writeFileSync(pluginJsonPath, JSON.stringify(plugin, null, 2) + "\n", "utf8");
      manifestUpdated = true;
+    }
+    if (typeof plugin.logo === "string" && plugin.logo.startsWith(extensionBundlePrefix)) {
+      plugin.logo = plugin.logo.slice(extensionBundlePrefix.length);
+      manifestUpdated = true;
+    }
+    if (manifestUpdated) {
+      fs.writeFileSync(pluginJsonPath, JSON.stringify(plugin, null, 2) + "\n", "utf8");
      console.log(`  Updated ${path.basename(extensionPath)}/.github/plugin/plugin.json`);
    }
  }
@@ -108,12 +150,43 @@ function cleanMaterializedExtensionPlugin(extensionPath) {
    return { removed: 0, manifestUpdated };
  }

+  const bundleRoot = path.join(target, path.basename(extensionPath));
  const count = countFiles(target);
+  if (fs.existsSync(bundleRoot) && fs.statSync(bundleRoot).isDirectory()) {
+    for (const entry of fs.readdirSync(bundleRoot, { withFileTypes: true })) {
+      moveEntry(path.join(bundleRoot, entry.name), path.join(extensionPath, entry.name));
+    }
+    console.log(`  Restored ${path.basename(extensionPath)}/ from materialized extensions bundle`);
+  }
+
  fs.rmSync(target, { recursive: true, force: true });
  console.log(`  Removed ${path.basename(extensionPath)}/extensions/ (${count} files)`);
  return { removed: count, manifestUpdated };
 }

+function isExtensionPluginDirectory(extensionPath) {
+  if (fs.existsSync(path.join(extensionPath, "extension.mjs"))) {
+    return true;
+  }
+
+  const bundleEntry = path.join(extensionPath, "extensions", path.basename(extensionPath), "extension.mjs");
+  if (fs.existsSync(bundleEntry)) {
+    return true;
+  }
+
+  const pluginJsonPath = path.join(extensionPath, ".github", "plugin", "plugin.json");
+  if (!fs.existsSync(pluginJsonPath)) {
+    return false;
+  }
+
+  try {
+    const plugin = JSON.parse(fs.readFileSync(pluginJsonPath, "utf8"));
+    return plugin.extensions === "extensions";
+  } catch {
+    return false;
+  }
+}
+
 function countFiles(dir) {
  let count = 0;
  for (const entry of fs.readdirSync(dir, { withFileTypes: true })) {
@@ -204,7 +277,7 @@ function main() {

    for (const dirName of extensionDirs) {
      const extensionPath = path.join(EXTENSIONS_DIR, dirName);
-      if (!fs.existsSync(path.join(extensionPath, "extension.mjs"))) {
+      if (!isExtensionPluginDirectory(extensionPath)) {
        continue;
      }
      const { removed, manifestUpdated } = cleanMaterializedExtensionPlugin(extensionPath);
@@ -62,6 +62,16 @@ function collectLocalPluginsFromRoot(rootDir, sourcePrefix, includeEntry = () =>
  return plugins;
 }

+function hasExtensionEntryPoint(extensionDir, extensionName) {
+  const candidateEntryPoints = [
+    path.join(extensionDir, "extension.mjs"),
+    path.join(extensionDir, "extensions", "extension.mjs"),
+    path.join(extensionDir, "extensions", extensionName, "extension.mjs"),
+  ];
+
+  return candidateEntryPoints.some((entryPointPath) => fs.existsSync(entryPointPath));
+}
+
 /**
 * Generate marketplace.json from plugin directories
 */
@@ -78,7 +88,7 @@ function generateMarketplace() {
    ...collectLocalPluginsFromRoot(
      EXTENSIONS_DIR,
      "extensions",
-      (entryName) => fs.existsSync(path.join(EXTENSIONS_DIR, entryName, "extension.mjs"))
+      (entryName) => hasExtensionEntryPoint(path.join(EXTENSIONS_DIR, entryName), entryName)
    )
  ];

@@ -35,6 +35,16 @@ const WEBSITE_SOURCE_DATA_DIR = path.join(WEBSITE_DIR, "data");
 const EXTERNAL_CANVAS_KEYWORD = "canvas";
 const EXTERNAL_CANVAS_PREVIEW_PATH = "assets/preview.png";

+function hasExtensionEntryPoint(extensionDir, extensionName) {
+  const candidateEntryPoints = [
+    path.join(extensionDir, "extension.mjs"),
+    path.join(extensionDir, "extensions", "extension.mjs"),
+    path.join(extensionDir, "extensions", extensionName, "extension.mjs"),
+  ];
+
+  return candidateEntryPoints.some((entryPointPath) => fs.existsSync(entryPointPath));
+}
+
 /**
 * Ensure the output directory exists
 */
@@ -544,7 +554,7 @@ function generatePluginsData(gitDates, resourceIndex = {}) {
    const extensionDirs = fs.readdirSync(EXTENSIONS_DIR, { withFileTypes: true })
      .filter((entry) => {
        if (!entry.isDirectory()) return false;
-        return fs.existsSync(path.join(EXTENSIONS_DIR, entry.name, "extension.mjs"));
+        return hasExtensionEntryPoint(path.join(EXTENSIONS_DIR, entry.name), entry.name);
      })
      .map((entry) => entry.name)
      .sort((a, b) => a.localeCompare(b));
@@ -1235,12 +1245,7 @@ function generateCanvasManifest(gitDates, commitSha) {
    .readdirSync(EXTENSIONS_DIR, { withFileTypes: true })
    .filter((entry) => {
      if (!entry.isDirectory()) return false;
-      const extensionEntryPoint = path.join(
-        EXTENSIONS_DIR,
-        entry.name,
-        "extension.mjs"
-      );
-      return fs.existsSync(extensionEntryPoint);
+      return hasExtensionEntryPoint(path.join(EXTENSIONS_DIR, entry.name), entry.name);
    })
    .sort((a, b) => a.name.localeCompare(b.name));

@@ -24,15 +24,34 @@ function copyDirRecursive(src, dest) {
  }
 }

-function copyEntryRecursive(srcPath, destPath) {
+function moveEntry(srcPath, destPath) {
+  fs.mkdirSync(path.dirname(destPath), { recursive: true });
+  try {
+    fs.renameSync(srcPath, destPath);
+    return;
+  } catch (error) {
+    if (error?.code !== "EXDEV") {
+      throw error;
+    }
+  }
+
  const stats = fs.statSync(srcPath);
  if (stats.isDirectory()) {
    copyDirRecursive(srcPath, destPath);
+    fs.rmSync(srcPath, { recursive: true, force: true });
    return;
  }

-  fs.mkdirSync(path.dirname(destPath), { recursive: true });
  fs.copyFileSync(srcPath, destPath);
+  fs.rmSync(srcPath, { force: true });
+}
+
+function isRelativeAssetPath(assetPath) {
+  return typeof assetPath === "string" &&
+    assetPath.length > 0 &&
+    !/^(?:[a-z][a-z0-9+.-]*:)?\/\//i.test(assetPath) &&
+    !assetPath.startsWith("data:") &&
+    !path.isAbsolute(assetPath);
 }

 /**
@@ -61,7 +80,7 @@ function resolveSource(relPath) {
 export function materializeExtensionPlugin(extensionPath) {
  const pluginJsonPath = path.join(extensionPath, ".github", "plugin", "plugin.json");
  if (!fs.existsSync(pluginJsonPath)) {
-    return { copiedEntries: 0, manifestUpdated: false, skipped: true };
+    return { movedEntries: 0, manifestUpdated: false, skipped: true };
  }

  let metadata;
@@ -72,20 +91,31 @@ export function materializeExtensionPlugin(extensionPath) {
  }

  const extensionContainerPath = path.join(extensionPath, "extensions");
+  const extensionBundlePath = path.join(extensionContainerPath, path.basename(extensionPath));
  fs.rmSync(extensionContainerPath, { recursive: true, force: true });
-  fs.mkdirSync(extensionContainerPath, { recursive: true });
+  fs.mkdirSync(extensionBundlePath, { recursive: true });

-  let copiedEntries = 0;
+  let movedEntries = 0;
  for (const entry of fs.readdirSync(extensionPath, { withFileTypes: true })) {
    if (entry.name === ".github" || entry.name === "extensions") {
      continue;
    }

-    copyEntryRecursive(
+    moveEntry(
      path.join(extensionPath, entry.name),
-      path.join(extensionContainerPath, entry.name)
+      path.join(extensionBundlePath, entry.name)
    );
-    copiedEntries++;
+    movedEntries++;
+  }
+
+  if (isRelativeAssetPath(metadata.logo)) {
+    const normalizedLogoPath = metadata.logo.replace(/\\/g, "/").replace(/^\.\//, "");
+    const bundledLogoPath = path.join(extensionBundlePath, normalizedLogoPath);
+    if (fs.existsSync(bundledLogoPath)) {
+      const rootLogoPath = path.join(extensionPath, normalizedLogoPath);
+      fs.mkdirSync(path.dirname(rootLogoPath), { recursive: true });
+      fs.copyFileSync(bundledLogoPath, rootLogoPath);
+    }
  }

  let manifestUpdated = false;
@@ -97,7 +127,7 @@ export function materializeExtensionPlugin(extensionPath) {
    fs.writeFileSync(pluginJsonPath, JSON.stringify(metadata, null, 2) + "\n", "utf8");
  }

-  return { copiedEntries, manifestUpdated, skipped: false };
+  return { movedEntries, manifestUpdated, skipped: false };
 }

 function materializePlugins() {
@@ -261,8 +291,8 @@ function materializePlugins() {
        }

        totalExtensionPlugins++;
-        totalExtensionPluginEntries += result.copiedEntries;
-        console.log(`✓ ${dirName}: materialized extension bundle into ./extensions (${result.copiedEntries} entries)`);
+        totalExtensionPluginEntries += result.movedEntries;
+        console.log(`✓ ${dirName}: materialized extension bundle into ./extensions (${result.movedEntries} entries)`);
      } catch (err) {
        console.error(`Error: Failed to materialize extension plugin ${dirName}: ${err.message}`);
        errors++;
@@ -4,6 +4,7 @@ import os from "os";
 import path from "path";
 import { after, test } from "node:test";
 import { materializeExtensionPlugin } from "./materialize-plugins.mjs";
+import { cleanMaterializedExtensionPlugin } from "./clean-materialized-plugins.mjs";

 const tempDirs = [];

@@ -13,7 +14,7 @@ after(() => {
  }
 });

-test("materializeExtensionPlugin writes extension bundles to ./extensions and rewrites manifest", () => {
+test("materializeExtensionPlugin writes extension bundles to ./extensions and preserves root logo assets", () => {
  const tempDir = fs.mkdtempSync(path.join(os.tmpdir(), "materialize-extension-plugin-"));
  tempDirs.push(tempDir);

@@ -32,17 +33,57 @@ test("materializeExtensionPlugin writes extension bundles to ./extensions and re
  fs.writeFileSync(path.join(pluginDir, "assets", "preview.png"), "fake-image-bytes");

  const result = materializeExtensionPlugin(pluginDir);
+  const bundleRoot = path.join(pluginDir, "extensions", "extension-plugin");

  assert.equal(result.skipped, false);
  assert.equal(result.manifestUpdated, true);
-  assert.equal(result.copiedEntries, 3);
-  assert.equal(fs.existsSync(path.join(pluginDir, "extensions", "extension.mjs")), true);
-  assert.equal(fs.existsSync(path.join(pluginDir, "extensions", "assets", "preview.png")), true);
-  assert.equal(fs.existsSync(path.join(pluginDir, "extensions", "README.md")), true);
+  assert.equal(result.movedEntries, 3);
+  assert.equal(fs.existsSync(path.join(bundleRoot, "extension.mjs")), true);
+  assert.equal(fs.existsSync(path.join(bundleRoot, "assets", "preview.png")), true);
+  assert.equal(fs.existsSync(path.join(bundleRoot, "README.md")), true);
  assert.equal(fs.existsSync(path.join(pluginDir, "extensions", ".github")), false);
+  assert.equal(fs.existsSync(path.join(pluginDir, "extension.mjs")), false);
+  assert.equal(fs.existsSync(path.join(pluginDir, "README.md")), false);
+  assert.equal(fs.existsSync(path.join(pluginDir, "assets", "preview.png")), true);

  const pluginManifest = JSON.parse(
    fs.readFileSync(path.join(pluginDir, ".github", "plugin", "plugin.json"), "utf8")
  );
  assert.equal(pluginManifest.extensions, "extensions");
+  assert.equal(pluginManifest.logo, "assets/preview.png");
+});
+
+test("cleanMaterializedExtensionPlugin restores moved extension files to root", () => {
+  const tempDir = fs.mkdtempSync(path.join(os.tmpdir(), "clean-materialized-extension-plugin-"));
+  tempDirs.push(tempDir);
+
+  const pluginDir = path.join(tempDir, "extension-plugin");
+  fs.mkdirSync(path.join(pluginDir, ".github", "plugin"), { recursive: true });
+  fs.mkdirSync(path.join(pluginDir, "assets"), { recursive: true });
+  fs.writeFileSync(path.join(pluginDir, ".github", "plugin", "plugin.json"), JSON.stringify({
+    name: "test-extension-plugin",
+    description: "test plugin",
+    version: "1.0.0",
+    logo: "assets/preview.png",
+    extensions: ".",
+  }, null, 2));
+  fs.writeFileSync(path.join(pluginDir, "extension.mjs"), "export default {};\n");
+  fs.writeFileSync(path.join(pluginDir, "README.md"), "# test\n");
+  fs.writeFileSync(path.join(pluginDir, "assets", "preview.png"), "fake-image-bytes");
+
+  materializeExtensionPlugin(pluginDir);
+  const result = cleanMaterializedExtensionPlugin(pluginDir);
+
+  assert.equal(result.removed, 3);
+  assert.equal(result.manifestUpdated, true);
+  assert.equal(fs.existsSync(path.join(pluginDir, "extension.mjs")), true);
+  assert.equal(fs.existsSync(path.join(pluginDir, "README.md")), true);
+  assert.equal(fs.existsSync(path.join(pluginDir, "assets", "preview.png")), true);
+  assert.equal(fs.existsSync(path.join(pluginDir, "extensions")), false);
+
+  const pluginManifest = JSON.parse(
+    fs.readFileSync(path.join(pluginDir, ".github", "plugin", "plugin.json"), "utf8")
+  );
+  assert.equal(pluginManifest.extensions, ".");
+  assert.equal(pluginManifest.logo, "assets/preview.png");
 });
@@ -1,7 +1,7 @@
 {
  "name": "accessibility-kanban",
  "description": "Kanban board to manage accessibility issues, allow you to plan, track, and complete remediation work.",
-  "version": "1.0.1",
+  "version": "1.0.2",
  "author": {
    "name": "Aaron Powell",
    "url": "https://github.com/aaronpowell"
@@ -1,7 +1,7 @@
 {
  "name": "apng-studio",
  "description": "Interactive GitHub Copilot app canvas extension for building Animated PNG (APNG) files from frames. Draw or upload frames, tune per-frame timing and compositing, preview live, send the result to your phone by QR, and export an animated .png.",
-  "version": "1.0.1",
+  "version": "1.0.2",
  "author": {
    "name": "Andrea Griffiths",
    "url": "https://github.com/AndreaGriffiths11"
@@ -1,7 +1,7 @@
 {
  "name": "arcade-canvas",
  "description": "Play five retro Phaser mini-games in a Copilot canvas while agents work.",
-  "version": "1.0.1",
+  "version": "1.0.2",
  "author": {
    "name": "Dan Wahlin",
    "url": "https://github.com/DanWahlin"
@@ -1,7 +1,7 @@
 {
  "name": "backlog-swipe-triage",
  "description": "Quickly swipe through backlog issues to triage decisions like assign, needs-info, defer, close, or ignore.",
-  "version": "1.0.1",
+  "version": "1.0.2",
  "author": {
    "name": "James Montemagno",
    "url": "https://github.com/jamesmontemagno"
@@ -1,7 +1,7 @@
 {
  "name": "chromium-control-canvas",
  "description": "Opens a real Chromium window you can navigate and interact with from a Copilot canvas control panel and agent actions.",
-  "version": "1.0.1",
+  "version": "1.0.2",
  "author": {
    "name": "Andrea Griffiths",
    "url": "https://github.com/AndreaGriffiths11"
@@ -1,7 +1,7 @@
 {
  "name": "color-orb",
  "description": "A visual orb that users can ask the agent to recolor while showing a live activity log in the canvas.",
-  "version": "1.0.1",
+  "version": "1.0.2",
  "author": {
    "name": "Aaron Powell",
    "url": "https://github.com/aaronpowell"
@@ -1,7 +1,7 @@
 {
  "name": "connector-namespaces",
  "description": "Browse, connect, and open MCP connectors from an Azure Connector Namespace.",
-  "version": "1.1.1",
+  "version": "1.1.2",
  "author": {
    "name": "Alex Yang",
    "url": "https://github.com/alexyaang"
@@ -1,7 +1,7 @@
 {
  "name": "diagram-viewer",
  "description": "Render diagrams, click nodes to drill down, and view agent-generated explanations directly in the canvas.",
-  "version": "1.0.1",
+  "version": "1.0.2",
  "author": {
    "name": "Aaron Powell",
    "url": "https://github.com/aaronpowell"
@@ -1,7 +1,7 @@
 {
  "name": "feedback-themes",
  "description": "Explore grouped customer feedback signals by impact and drill into a theme to guide product next steps.",
-  "version": "1.0.1",
+  "version": "1.0.2",
  "author": {
    "name": "Aaron Powell",
    "url": "https://github.com/aaronpowell"
@@ -1,7 +1,7 @@
 {
  "name": "gesture-review",
  "description": "Review pull requests with a live camera feed and approve or reject using thumbs-up/thumbs-down gestures.",
-  "version": "1.0.1",
+  "version": "1.0.2",
  "author": {
    "name": "Aaron Powell",
    "url": "https://github.com/aaronpowell"
@@ -1,7 +1,7 @@
 {
  "name": "java-modernization-studio",
  "description": "Drive the GitHub Copilot App Modernization for Java workflow from an interactive canvas: environment readiness, repo assessment, prioritized plan and progress, validation gates, and one-click predefined-task runs grounded in the repo's real artifacts.",
-  "version": "1.0.1",
+  "version": "1.0.2",
  "author": {
    "name": "Ayan Gupta",
    "url": "https://github.com/ayangupt"
@@ -1,7 +1,7 @@
 {
  "name": "release-notes-showcase",
  "description": "Compose and refine launch-ready release notes with contributor callouts and export-friendly output.",
-  "version": "1.0.1",
+  "version": "1.0.2",
  "author": {
    "name": "Kayla Cinnamon",
    "url": "https://github.com/cinnamon-msft"
@@ -1,7 +1,7 @@
 {
  "name": "repo-actions-hub",
  "description": "Browse repository GitHub Actions workflows, inspect recent runs, and trigger manual workflow_dispatch runs from a Copilot canvas.",
-  "version": "1.0.1",
+  "version": "1.0.2",
  "author": {
    "name": "James Montemagno",
    "url": "https://github.com/jamesmontemagno"
@@ -0,0 +1,18 @@
+{
+  "name": "signals-dashboard",
+  "description": "Real-time agent coordination dashboard for The Workshop. Shows desk status, signal types (done, checkpoint, blocked, hands-up, partnership), intent text, outcome pairing with honesty gap, token usage, and stash/restore controls.",
+  "version": "0.1.0",
+  "author": {
+    "name": "jennyf19",
+    "url": "https://github.com/jennyf19"
+  },
+  "keywords": [
+    "agent-signals",
+    "dashboard",
+    "multi-agent",
+    "coordination",
+    "canvas"
+  ],
+  "logo": "assets/preview.png",
+  "extensions": "."
+}
@@ -0,0 +1,888 @@
+// Extension: signals-dashboard
+// Live dashboard showing agent signals from workshop desks.
+// Scans desks/*/.signals/ for JSON files, renders the latest signal per desk.
+// Supports stashing desks (48hr hold) and restoring them.
+
+import { createServer } from "node:http";
+import { readdir, readFile, writeFile, stat } from "node:fs/promises";
+import { join } from "node:path";
+import { joinSession, createCanvas } from "@github/copilot-sdk/extension";
+
+const servers = new Map();
+const STASH_TTL_MS = 48 * 60 * 60 * 1000;
+
+// Serialize stash read-modify-write per workshop. The UI fires stash/restore
+// POSTs without awaiting each other, so two overlapping mutations could both
+// read the same array and the last write would silently drop the other. Each
+// workshop gets a promise chain so its mutations run one at a time.
+const stashLocks = new Map();
+function withStashLock(workshopDir, fn) {
+    const prev = stashLocks.get(workshopDir) || Promise.resolve();
+    const run = prev.then(fn, fn);
+    stashLocks.set(workshopDir, run.then(() => {}, () => {}));
+    return run;
+}
+
+// Desk names are single path segments (folder names under desks/ or classroom/).
+// Reject anything that could escape the workshop dir via path traversal.
+function isValidDeskName(name) {
+    return typeof name === "string" && name.length > 0 && name.length <= 128 &&
+        !name.includes("/") && !name.includes("\\") && !name.includes("\0") &&
+        name !== "." && name !== "..";
+}
+
+// Signal JSON is agent-produced and unvalidated. Coerce numeric fields before
+// they reach the renderer so a nonnumeric value cannot inject markup or break
+// layout. toScore clamps self-assessment/quality scores to 0..max; toCount
+// keeps token counts as finite nonnegative integers.
+function toScore(v, max = 5) {
+    const n = Number(v);
+    if (!Number.isFinite(n)) return 0;
+    return Math.max(0, Math.min(max, n));
+}
+function toCount(v) {
+    const n = Number(v);
+    if (!Number.isFinite(n) || n < 0) return 0;
+    return Math.floor(n);
+}
+
+// Prefer an explicit, persisted timestamp over filesystem mtime. A git
+// clone/checkout resets mtimes (often to a single instant), which would
+// otherwise scramble "latest" ordering and outcome pairing. Signals may carry
+// an ISO-8601 `timestamp` (or `emitted_at`); fall back to mtime when absent.
+function signalTime(parsed, mtimeMs) {
+    const explicit = parsed && (parsed.timestamp || parsed.emitted_at);
+    if (explicit) {
+        const t = Date.parse(explicit);
+        if (Number.isFinite(t)) return t;
+    }
+    return mtimeMs;
+}
+
+// Reject cross-site POSTs to the state-changing /api/* routes (CSRF). The panel
+// loads as a top-level loopback document, so its own fetches are same-origin
+// (Origin === our loopback origin) and header-less / non-web-scheme callers fall
+// through as allowed; a browser page on another origin is blocked.
+function isCrossSiteRequest(req) {
+    const origin = req.headers.origin;
+    if (origin) {
+        if (origin === `http://${req.headers.host}`) return false;
+        if (origin === "null") return true;
+        if (/^https?:\/\//i.test(origin)) return true;
+        return false;
+    }
+    const site = req.headers["sec-fetch-site"];
+    return site === "cross-site" || site === "same-site";
+}
+
+// --- Stash management ---
+
+async function readStash(workshopDir) {
+    const fp = join(workshopDir, ".desk-stash.json");
+    try {
+        const raw = await readFile(fp, "utf-8");
+        const stash = JSON.parse(raw);
+        const now = Date.now();
+        const live = stash.filter(e => (now - new Date(e.stashedAt).getTime()) < STASH_TTL_MS);
+        if (live.length !== stash.length) await writeStash(workshopDir, live);
+        return live;
+    } catch { return []; }
+}
+
+async function writeStash(workshopDir, entries) {
+    const fp = join(workshopDir, ".desk-stash.json");
+    await writeFile(fp, JSON.stringify(entries, null, 2), "utf-8");
+}
+
+async function stashDesk(workshopDir, deskName) {
+    return withStashLock(workshopDir, async () => {
+        const stash = await readStash(workshopDir);
+        if (stash.some(e => e.name === deskName)) return stash;
+        stash.push({ name: deskName, stashedAt: new Date().toISOString() });
+        await writeStash(workshopDir, stash);
+        return stash;
+    });
+}
+
+async function restoreDesk(workshopDir, deskName) {
+    return withStashLock(workshopDir, async () => {
+        let stash = await readStash(workshopDir);
+        stash = stash.filter(e => e.name !== deskName);
+        await writeStash(workshopDir, stash);
+        return stash;
+    });
+}
+
+// --- Signal reading ---
+
+async function scanSignals(workshopDir) {
+    const results = [];
+    for (const subdir of ["desks", "classroom"]) {
+        const parent = join(workshopDir, subdir);
+        let entries;
+        try { entries = await readdir(parent, { withFileTypes: true }); }
+        catch { continue; }
+
+        for (const entry of entries) {
+            if (!entry.isDirectory() || entry.name.startsWith(".")) continue;
+            const sigDir = join(parent, entry.name, ".signals");
+            let sigFiles;
+            try { sigFiles = await readdir(sigDir); }
+            catch {
+                results.push({
+                    deskName: entry.name, signalType: "none", agentName: entry.name,
+                    confidence: 0, accuracy: 0, completeness: 0, intent: 0,
+                    whatWorked: "", whatWasHard: "", skillGap: "",
+                    escalationReason: null, escalationBlocked: null, recommendation: null,
+                    emittedAt: null, signalCount: 0, tokensIn: 0, tokensOut: 0, model: null,
+                });
+                continue;
+            }
+
+            const jsonFiles = sigFiles.filter(f => f.endsWith(".json"));
+            if (jsonFiles.length === 0) {
+                results.push({
+                    deskName: entry.name, signalType: "none", agentName: entry.name,
+                    confidence: 0, accuracy: 0, completeness: 0, intent: 0,
+                    whatWorked: "", whatWasHard: "", skillGap: "",
+                    escalationReason: null, escalationBlocked: null, recommendation: null,
+                    emittedAt: null, signalCount: 0, tokensIn: 0, tokensOut: 0, model: null,
+                });
+                continue;
+            }
+
+            // Read all signals, separate by type, find latest execution/partnership + any outcome signals
+            let latest = null, latestTime = 0;
+            const allSignals = [];
+            for (const f of jsonFiles) {
+                const fp = join(sigDir, f);
+                try {
+                    const s = await stat(fp);
+                    const raw = await readFile(fp, "utf-8");
+                    const parsed = JSON.parse(raw);
+                    const emittedMs = signalTime(parsed, s.mtimeMs);
+                    allSignals.push({ parsed, mtimeMs: emittedMs, path: fp });
+                    // Latest non-outcome signal (execution, partnership, escalation)
+                    if ((parsed.signal_type || "execution") !== "outcome" && emittedMs > latestTime) {
+                        latestTime = emittedMs; latest = { parsed, mtimeMs: emittedMs };
+                    }
+                } catch {}
+            }
+            if (!latest) {
+                // Files exist but none parsed into a usable non-outcome signal
+                // (malformed JSON, or outcome-only). Keep the desk visible as
+                // "awaiting" instead of silently dropping it from the board.
+                results.push({
+                    deskName: entry.name, signalType: "none", agentName: entry.name,
+                    confidence: 0, accuracy: 0, completeness: 0, intent: 0,
+                    whatWorked: "", whatWasHard: "", skillGap: "",
+                    escalationReason: null, escalationBlocked: null, recommendation: null,
+                    emittedAt: null, signalCount: 0, tokensIn: 0, tokensOut: 0, model: null,
+                });
+                continue;
+            }
+            try {
+                const sig = latest.parsed;
+                const intentRaw = sig.intent || sig.self_assessment?.intent || null;
+
+                // Find outcome signal matched by run_id (if any)
+                let outcome = null;
+                if (sig.run_id) {
+                    const outcomeSignals = allSignals
+                        .filter(s => s.parsed.signal_type === "outcome" && s.parsed.run_id === sig.run_id);
+                    if (outcomeSignals.length > 0) {
+                        outcome = outcomeSignals.sort((a, b) => b.mtimeMs - a.mtimeMs)[0].parsed;
+                    }
+                }
+                // Also check for any recent outcome (within 1hr of latest signal) if no run_id match
+                if (!outcome) {
+                    const recentOutcomes = allSignals
+                        .filter(s => s.parsed.signal_type === "outcome" && s.mtimeMs >= latestTime && (s.mtimeMs - latestTime) < 3600000)
+                        .sort((a, b) => a.mtimeMs - b.mtimeMs);
+                    if (recentOutcomes.length > 0) outcome = recentOutcomes[0].parsed;
+                }
+
+                // Compute honesty gap if we have both self-assessment and outcome
+                let honestyGap = null;
+                if (outcome && sig.self_assessment) {
+                    const selfConf = toScore(sig.self_assessment.confidence);
+                    const outcomeRating = toScore(outcome.quality_rating);
+                    if (selfConf > 0 && outcomeRating > 0) {
+                        honestyGap = Math.abs(selfConf - outcomeRating);
+                    }
+                }
+
+                results.push({
+                    deskName: entry.name,
+                    signalType: sig.signal_type || "execution",
+                    subtype: sig.subtype || sig.signal_type || "execution",
+                    agentName: sig.agent_name || entry.name,
+                    intentText: typeof intentRaw === "string" ? intentRaw : null,
+                    intentScore: toScore(intentRaw),
+                    confidence: toScore(sig.self_assessment?.confidence),
+                    accuracy: toScore(sig.self_assessment?.accuracy),
+                    completeness: toScore(sig.self_assessment?.completeness),
+                    whatWorked: sig.patterns?.what_worked || "",
+                    whatWasHard: sig.patterns?.what_was_hard || "",
+                    skillGap: sig.patterns?.skill_gap || "",
+                    escalationReason: sig.escalation?.reason || null,
+                    escalationBlocked: sig.escalation?.blocked_on || null,
+                    recommendation: sig.escalation?.recommendation || null,
+                    emittedAt: new Date(latestTime).toISOString(),
+                    signalCount: jsonFiles.length,
+                    tokensIn: toCount(sig.usage?.tokens_in),
+                    tokensOut: toCount(sig.usage?.tokens_out),
+                    model: sig.usage?.model || null,
+                    // Outcome signal fields
+                    outcomeRating: outcome ? (toScore(outcome.quality_rating) || null) : null,
+                    outcomeEffort: outcome?.effort_to_merge || null,
+                    outcomeIssues: Array.isArray(outcome?.issues_found) ? outcome.issues_found : [],
+                    outcomeAgent: outcome?.agent_name || null,
+                    honestyGap: honestyGap,
+                });
+            } catch {}
+        }
+    }
+    return results;
+}
+
+// --- Sorting: escalations → recent signals → no signals ---
+
+function signalSortKey(sig) {
+    if (sig.signalType === "escalation") return 0;
+    if (sig.signalType === "execution") return 1;
+    if (sig.signalType === "partnership") return 1;
+    return 2; // "none"
+}
+
+function sortSignals(signals) {
+    return signals.sort((a, b) => {
+        const ka = signalSortKey(a), kb = signalSortKey(b);
+        if (ka !== kb) return ka - kb;
+        if (a.emittedAt && b.emittedAt) return new Date(b.emittedAt) - new Date(a.emittedAt);
+        if (a.emittedAt) return -1;
+        if (b.emittedAt) return 1;
+        return a.deskName.localeCompare(b.deskName);
+    });
+}
+
+// --- HTML rendering ---
+
+function esc(s) {
+    return String(s).replace(/&/g, "&amp;").replace(/</g, "&lt;").replace(/>/g, "&gt;").replace(/"/g, "&quot;").replace(/'/g, "&#39;");
+}
+function truncate(s, len) {
+    const str = String(s);
+    return str.length > len ? str.slice(0, len) + "…" : str;
+}
+function formatTokens(n) {
+    if (!n) return null;
+    if (n >= 1000000) return `${(n / 1000000).toFixed(1)}M`;
+    if (n >= 1000) return `${(n / 1000).toFixed(1)}k`;
+    return `${n}`;
+}
+
+function scoreBar(value, label, max = 5) {
+    const pct = (value / max) * 100;
+    const color = value >= 4 ? "#22c55e" : value >= 3 ? "#eab308" : value >= 1 ? "#ef4444" : "#262626";
+    return `<div>
+        <div style="display:flex;justify-content:space-between;margin-bottom:2px;">
+            <span style="font-size:10px;color:#64748b;text-transform:uppercase;letter-spacing:.04em;">${label}</span>
+            <span style="font-size:10px;color:#94a3b8;">${value}/5</span>
+        </div>
+        <div style="height:4px;background:#1e293b;border-radius:2px;overflow:hidden;">
+            <div style="width:${pct}%;height:100%;background:${color};border-radius:2px;transition:width .3s;"></div>
+        </div>
+    </div>`;
+}
+
+function timeSince(isoDate) {
+    if (!isoDate) return "—";
+    const diff = Date.now() - new Date(isoDate).getTime();
+    const mins = Math.floor(diff / 60000);
+    if (mins < 1) return "just now";
+    if (mins < 60) return `${mins}m ago`;
+    const hrs = Math.floor(mins / 60);
+    if (hrs < 24) return `${hrs}h ago`;
+    return `${Math.floor(hrs / 24)}d ago`;
+}
+
+function timeRemaining(stashedAt) {
+    const remaining = STASH_TTL_MS - (Date.now() - new Date(stashedAt).getTime());
+    if (remaining <= 0) return "expiring";
+    const hrs = Math.floor(remaining / 3600000);
+    return hrs >= 1 ? `${hrs}h left` : `${Math.floor(remaining / 60000)}m left`;
+}
+
+function avgScore(signals) {
+    const withSignals = signals.filter(s => s.signalType !== "none");
+    if (withSignals.length === 0) return null;
+    const avg = (field) => {
+        const vals = withSignals.map(s => s[field]).filter(v => v > 0);
+        return vals.length ? (vals.reduce((a, b) => a + b, 0) / vals.length).toFixed(1) : "—";
+    };
+    return { confidence: avg("confidence"), accuracy: avg("accuracy"), completeness: avg("completeness"), intent: avg("intentScore") };
+}
+
+function renderSummaryBar(activeSignals) {
+    const escalations = activeSignals.filter(s => s.signalType === "escalation").length;
+    const withSignals = activeSignals.filter(s => s.signalType !== "none").length;
+    const awaiting = activeSignals.filter(s => s.signalType === "none").length;
+    const avg = avgScore(activeSignals);
+
+    const totalTokens = activeSignals.reduce((sum, s) => sum + (s.tokensIn || 0) + (s.tokensOut || 0), 0);
+    const withOutcomes = activeSignals.filter(s => s.outcomeRating !== null).length;
+    const avgGap = (() => {
+        const gaps = activeSignals.filter(s => s.honestyGap !== null).map(s => s.honestyGap);
+        return gaps.length ? (gaps.reduce((a, b) => a + b, 0) / gaps.length).toFixed(1) : null;
+    })();
+
+    const escBadge = escalations > 0
+        ? `<span style="background:#7f1d1d;color:#fca5a5;padding:3px 10px;border-radius:12px;font-size:12px;font-weight:600;">⚠ ${escalations} escalation${escalations > 1 ? "s" : ""}</span>`
+        : "";
+
+    const tokenBadge = totalTokens > 0
+        ? `<span style="font-size:11px;color:#475569;">🪙 ${formatTokens(totalTokens)}</span>`
+        : "";
+
+    const calibrationBadge = avgGap !== null
+        ? `<span style="font-size:11px;color:${avgGap <= 1 ? '#22c55e' : avgGap <= 2 ? '#eab308' : '#ef4444'};" title="${withOutcomes} outcome signal${withOutcomes > 1 ? 's' : ''}, avg gap: ${avgGap}">🔍 gap ${avgGap}</span>`
+        : "";
+
+    const avgBlock = avg ? `
+        <div style="display:flex;gap:12px;font-size:11px;color:#64748b;">
+            <span>intent <b style="color:#94a3b8;">${avg.intent}</b></span>
+            <span>conf <b style="color:#94a3b8;">${avg.confidence}</b></span>
+            <span>acc <b style="color:#94a3b8;">${avg.accuracy}</b></span>
+            <span>comp <b style="color:#94a3b8;">${avg.completeness}</b></span>
+        </div>` : "";
+
+    return `
+    <div style="display:flex;justify-content:space-between;align-items:center;padding:10px 14px;
+                background:#0f172a;border:1px solid #1e293b;border-radius:8px;margin-bottom:14px;">
+        <div style="display:flex;align-items:center;gap:12px;">
+            <span style="font-size:13px;color:#cbd5e1;"><b style="color:#f1f5f9;">${activeSignals.length}</b> desk${activeSignals.length !== 1 ? "s" : ""}</span>
+            <span style="font-size:11px;color:#475569;">${withSignals} reporting · ${awaiting} awaiting</span>
+            ${tokenBadge}
+            ${calibrationBadge}
+            ${escBadge}
+        </div>
+        ${avgBlock}
+    </div>`;
+}
+
+function renderSignalCard(sig) {
+    const isEscalation = sig.signalType === "escalation";
+    const isPartnership = sig.signalType === "partnership";
+    const noSignal = sig.signalType === "none";
+    const borderColor = isEscalation ? "#dc2626" : noSignal ? "#1e293b" : "#1e3a5f";
+    const bgColor = isEscalation ? "#0f0604" : "#0f172a";
+
+    const typeLabel = isEscalation
+        ? (sig.subtype === "blocked"
+            ? `<span style="background:#7f1d1d;color:#fca5a5;padding:2px 8px;border-radius:4px;font-size:11px;font-weight:600;">⚠ BLOCKED</span>`
+            : `<span style="background:#7f1d1d;color:#fca5a5;padding:2px 8px;border-radius:4px;font-size:11px;font-weight:600;">⚠ HANDS-UP</span>`)
+        : noSignal
+        ? `<span style="background:#1e293b;color:#64748b;padding:2px 8px;border-radius:4px;font-size:11px;">📡 awaiting</span>`
+        : isPartnership
+        ? `<span style="background:#1e3a5f;color:#7dd3fc;padding:2px 8px;border-radius:4px;font-size:11px;">🤝 partnership</span>`
+        : sig.subtype === "done"
+        ? `<span style="background:#052e16;color:#86efac;padding:2px 8px;border-radius:4px;font-size:11px;">✓ done</span>`
+        : `<span style="background:#0c2d48;color:#7dd3fc;padding:2px 8px;border-radius:4px;font-size:11px;">✓ checkpoint</span>`;
+
+    const stashBtn = `<button data-act="stash" data-desk="${esc(sig.deskName)}"
+        style="background:none;border:1px solid #1e293b;color:#475569;padding:2px 8px;border-radius:4px;
+               font-size:11px;cursor:pointer;transition:all .15s;"
+        onmouseover="this.style.borderColor='#dc2626';this.style.color='#fca5a5'"
+        onmouseout="this.style.borderColor='#1e293b';this.style.color='#475569'">stash</button>`;
+
+    const openBtnStyle = isEscalation
+        ? "background:#7f1d1d;border:1px solid #dc2626;color:#fca5a5;padding:2px 10px;border-radius:4px;font-size:11px;cursor:pointer;font-weight:600;transition:all .15s;"
+        : "background:none;border:1px solid #1e3a5f;color:#7dd3fc;padding:2px 8px;border-radius:4px;font-size:11px;cursor:pointer;transition:all .15s;";
+    const openBtn = noSignal ? "" : `<button data-act="open" data-desk="${esc(sig.deskName)}"
+        style="${openBtnStyle}"
+        onmouseover="this.style.background='#1e3a5f'"
+        onmouseout="this.style.background='${isEscalation ? '#7f1d1d' : 'transparent'}'"
+        title="Copy this desk's filesystem path to the clipboard">path</button>`;
+
+    let escalationBlock = "";
+    if (isEscalation && sig.escalationReason) {
+        escalationBlock = `
+        <div style="margin-top:10px;padding:8px 10px;background:#1c1917;border-left:3px solid #dc2626;border-radius:0 4px 4px 0;">
+            <div style="font-size:11px;color:#fca5a5;font-weight:600;">Blocked on:</div>
+            <div style="font-size:12px;color:#e2e8f0;margin-top:2px;">${esc(sig.escalationBlocked || sig.escalationReason)}</div>
+            ${sig.recommendation ? `<div style="font-size:11px;color:#94a3b8;margin-top:4px;">→ ${esc(sig.recommendation)}</div>` : ""}
+        </div>`;
+    }
+
+    // --- Intent text (execution signals with text intent) ---
+    const intentBlock = sig.intentText ? `
+        <div style="font-size:13px;color:#e2e8f0;line-height:1.5;margin-bottom:10px;padding:8px 10px;
+                    background:#020617;border-left:3px solid #3b82f6;border-radius:0 4px 4px 0;">
+            ${esc(sig.intentText)}
+        </div>` : "";
+
+    // --- Scores: shown for partnership signals, or legacy execution signals with numeric scores ---
+    const hasScores = isPartnership
+        ? true
+        : (sig.intentScore > 0 || sig.confidence > 0 || sig.accuracy > 0 || sig.completeness > 0);
+
+    const scoresBlock = noSignal ? `
+        <div style="padding:12px 0;text-align:center;color:#334155;font-size:12px;">
+            No signals yet — this desk is waiting for its first session.
+        </div>` : isPartnership ? `
+        <div style="display:grid;grid-template-columns:1fr 1fr;gap:8px 16px;margin-bottom:12px;">
+            ${scoreBar(sig.intentScore, "intent")}
+            ${scoreBar(sig.confidence, "confidence")}
+            ${scoreBar(sig.accuracy, "accuracy")}
+            ${scoreBar(sig.completeness, "completeness")}
+        </div>` : hasScores ? `
+        <details style="margin-bottom:8px;">
+            <summary style="font-size:10px;color:#475569;cursor:pointer;text-transform:uppercase;letter-spacing:.04em;">scores</summary>
+            <div style="display:grid;grid-template-columns:1fr 1fr;gap:8px 16px;margin-top:6px;">
+                ${sig.intentScore > 0 ? scoreBar(sig.intentScore, "intent") : ""}
+                ${sig.confidence > 0 ? scoreBar(sig.confidence, "confidence") : ""}
+                ${sig.accuracy > 0 ? scoreBar(sig.accuracy, "accuracy") : ""}
+                ${sig.completeness > 0 ? scoreBar(sig.completeness, "completeness") : ""}
+            </div>
+        </details>` : "";
+
+    // --- Patterns: primary for execution, secondary for partnership ---
+    const patternsBlock = (sig.whatWorked || sig.whatWasHard || sig.skillGap) ? `
+        <div style="${isPartnership ? 'border-top:1px solid #1e293b;padding-top:8px;margin-top:4px;' : 'margin-bottom:8px;'}">
+            ${sig.whatWorked ? `<div style="font-size:12px;margin-bottom:3px;line-height:1.4;"><span style="color:#22c55e;margin-right:4px;">✓</span><span style="color:#94a3b8;">${esc(truncate(sig.whatWorked, 160))}</span></div>` : ""}
+            ${sig.whatWasHard ? `<div style="font-size:12px;margin-bottom:3px;line-height:1.4;"><span style="color:#eab308;margin-right:4px;">△</span><span style="color:#94a3b8;">${esc(truncate(sig.whatWasHard, 160))}</span></div>` : ""}
+            ${sig.skillGap ? `<div style="font-size:12px;line-height:1.4;"><span style="color:#ef4444;margin-right:4px;">✗</span><span style="color:#94a3b8;">${esc(truncate(sig.skillGap, 160))}</span></div>` : ""}
+        </div>` : "";
+
+    // --- Outcome signal / honesty gap ---
+    let outcomeBlock = "";
+    if (sig.outcomeRating !== null && !noSignal) {
+        const gapColor = sig.honestyGap === null ? "#475569"
+            : sig.honestyGap <= 1 ? "#22c55e"
+            : sig.honestyGap === 2 ? "#eab308"
+            : "#ef4444";
+        const gapLabel = sig.honestyGap === null ? "—"
+            : sig.honestyGap <= 1 ? "well-calibrated"
+            : sig.honestyGap === 2 ? "moderate gap"
+            : "significant gap";
+        const effortColor = sig.outcomeEffort === "minimal" ? "#22c55e"
+            : sig.outcomeEffort === "moderate" ? "#eab308"
+            : sig.outcomeEffort === "significant" ? "#ef4444" : "#475569";
+
+        outcomeBlock = `
+        <div style="margin-top:8px;padding:8px 10px;background:#020617;border:1px solid #1e293b;border-radius:6px;">
+            <div style="display:flex;justify-content:space-between;align-items:center;margin-bottom:6px;">
+                <span style="font-size:10px;color:#64748b;text-transform:uppercase;letter-spacing:.04em;">🔍 outcome${sig.outcomeAgent ? ` · ${esc(sig.outcomeAgent)}` : ""}</span>
+                ${sig.honestyGap !== null ? `<span style="font-size:10px;color:${gapColor};font-weight:600;">${gapLabel} (gap: ${sig.honestyGap})</span>` : ""}
+            </div>
+            <div style="display:flex;gap:16px;align-items:center;">
+                <div style="flex:1;">
+                    <div style="display:flex;justify-content:space-between;margin-bottom:2px;">
+                        <span style="font-size:10px;color:#64748b;">quality</span>
+                        <span style="font-size:10px;color:#94a3b8;">${sig.outcomeRating}/5</span>
+                    </div>
+                    <div style="height:4px;background:#1e293b;border-radius:2px;overflow:hidden;">
+                        <div style="width:${(sig.outcomeRating / 5) * 100}%;height:100%;background:${sig.outcomeRating >= 4 ? '#22c55e' : sig.outcomeRating >= 3 ? '#eab308' : '#ef4444'};border-radius:2px;"></div>
+                    </div>
+                </div>
+                <span style="font-size:11px;color:${effortColor};">${esc(sig.outcomeEffort || "—")} effort</span>
+            </div>
+            ${sig.outcomeIssues?.length ? `<div style="margin-top:6px;font-size:11px;color:#94a3b8;">
+                ${sig.outcomeIssues.map(i => `<div style="margin-top:2px;">· ${esc(truncate(i, 120))}</div>`).join("")}
+            </div>` : ""}
+        </div>`;
+    }
+
+    return `
+    <div style="background:${bgColor};border:1px solid ${borderColor};border-radius:8px;padding:14px;margin-bottom:8px;
+                ${isEscalation ? "animation:pulse 2s ease-in-out infinite;" : ""}">
+        <div style="display:flex;justify-content:space-between;align-items:center;margin-bottom:10px;">
+            <div style="display:flex;align-items:center;gap:8px;">
+                <span style="font-size:15px;font-weight:600;color:#f1f5f9;">${esc(sig.deskName)}</span>
+                ${typeLabel}
+            </div>
+            <div style="display:flex;align-items:center;gap:8px;">
+                ${(sig.tokensIn || sig.tokensOut) ? `<span style="font-size:10px;color:#334155;background:#0f172a;border:1px solid #1e293b;padding:1px 6px;border-radius:3px;" title="in: ${sig.tokensIn} · out: ${sig.tokensOut}${sig.model ? ' · ' + esc(sig.model) : ''}">🪙 ${formatTokens(sig.tokensIn + sig.tokensOut)}</span>` : ""}
+                <span style="font-size:11px;color:#475569;">${timeSince(sig.emittedAt)}${sig.signalCount ? ` · ${sig.signalCount}` : ""}</span>
+                ${openBtn}
+                ${stashBtn}
+            </div>
+        </div>
+        ${isPartnership ? `${scoresBlock}${patternsBlock}` : `${intentBlock}${patternsBlock}${scoresBlock}`}
+        ${outcomeBlock}
+        ${escalationBlock}
+    </div>`;
+}
+
+function renderStashedCard(entry) {
+    return `
+    <div style="background:#080808;border:1px solid #1a1a1a;border-radius:6px;padding:8px 12px;margin-bottom:6px;
+                display:flex;justify-content:space-between;align-items:center;">
+        <div style="display:flex;align-items:center;gap:8px;">
+            <span style="font-size:13px;color:#525252;">${esc(entry.name)}</span>
+            <span style="font-size:10px;color:#3f3f46;background:#18181b;padding:1px 6px;border-radius:3px;">${timeRemaining(entry.stashedAt)}</span>
+        </div>
+        <button data-act="restore" data-desk="${esc(entry.name)}"
+            style="background:none;border:1px solid #262626;color:#525252;padding:2px 8px;border-radius:4px;
+                   font-size:11px;cursor:pointer;transition:all .15s;"
+            onmouseover="this.style.borderColor='#22c55e';this.style.color='#86efac'"
+            onmouseout="this.style.borderColor='#262626';this.style.color='#525252'">restore</button>
+    </div>`;
+}
+
+function renderDashboard(signals, stashed) {
+    const activeSignals = sortSignals(signals.filter(s => !stashed.some(e => e.name === s.deskName)));
+
+    const cards = activeSignals.length > 0
+        ? activeSignals.map(renderSignalCard).join("")
+        : `<div style="text-align:center;padding:30px 20px;color:#475569;">
+            <div style="font-size:28px;margin-bottom:10px;">🪨</div>
+            <div style="font-size:14px;color:#94a3b8;margin-bottom:16px;">No active desks yet</div>
+            <div style="text-align:left;background:#0f172a;border:1px solid #1e293b;border-radius:8px;padding:16px;max-width:360px;margin:0 auto;">
+                <div style="font-size:12px;font-weight:600;color:#cbd5e1;margin-bottom:10px;">Get started</div>
+                <div style="font-size:12px;color:#94a3b8;line-height:1.6;margin-bottom:8px;">
+                    Ask the <b style="color:#7dd3fc;">Workshop TA</b> in chat:
+                </div>
+                <div style="background:#020617;border:1px solid #1e293b;border-radius:4px;padding:8px 10px;margin-bottom:12px;">
+                    <code style="font-size:12px;color:#e2e8f0;background:none;padding:0;">"open a desk called scanning in ~/my-workshop"</code>
+                </div>
+                <div style="font-size:11px;color:#64748b;line-height:1.5;">
+                    The TA uses the <b>desk-open</b> skill to create a desk with a journal. Once a desk emits signals, they'll appear here automatically.
+                </div>
+                <div style="border-top:1px solid #1e293b;margin-top:12px;padding-top:10px;font-size:11px;color:#475569;">
+                    <div style="margin-bottom:4px;">💡 <b style="color:#64748b;">Quick commands to try:</b></div>
+                    <div style="color:#64748b;line-height:1.8;">
+                        • "open a desk for code review"<br/>
+                        • "what's everyone working on?"<br/>
+                        • "show me the signals"
+                    </div>
+                </div>
+            </div>
+           </div>`;
+
+    const summaryBar = activeSignals.length > 0 ? renderSummaryBar(activeSignals) : "";
+
+    const stashedSection = stashed.length > 0 ? `
+        <div style="margin-top:20px;padding-top:12px;border-top:1px solid #1a1a1a;">
+            <div style="font-size:11px;font-weight:600;color:#3f3f46;margin-bottom:8px;text-transform:uppercase;letter-spacing:.06em;">
+                Stashed · ${stashed.length}
+            </div>
+            ${stashed.map(renderStashedCard).join("")}
+        </div>` : "";
+
+    return `<!doctype html>
+<html>
+<head>
+    <meta charset="utf-8" />
+    <title>Cairn · Signals</title>
+    <style>
+        * { box-sizing: border-box; margin: 0; padding: 0; }
+        body { font-family: -apple-system, BlinkMacSystemFont, 'Segoe UI', system-ui, sans-serif;
+               background: #020617; color: #e2e8f0; padding: 16px; }
+        code { background: #1e293b; padding: 1px 5px; border-radius: 3px; font-size: 12px; }
+        @keyframes pulse {
+            0%, 100% { border-color: #dc2626; }
+            50% { border-color: #7f1d1d; }
+        }
+        #content { transition: opacity .15s; }
+        @media (prefers-reduced-motion: reduce) {
+            * { animation: none !important; transition: none !important; }
+        }
+    </style>
+</head>
+<body>
+    <div style="display:flex;justify-content:space-between;align-items:center;margin-bottom:12px;">
+        <h1 style="font-size:16px;font-weight:600;color:#f8fafc;">🪨 Cairn</h1>
+        <span id="status" style="font-size:11px;color:#334155;">live</span>
+    </div>
+    <div id="content">
+        ${summaryBar}
+        ${cards}
+        ${stashedSection}
+    </div>
+
+    <script>
+        async function stashDesk(name) {
+            await fetch('/api/stash/' + encodeURIComponent(name), { method: 'POST' });
+            refresh();
+        }
+        async function restoreDesk(name) {
+            await fetch('/api/restore/' + encodeURIComponent(name), { method: 'POST' });
+            refresh();
+        }
+        function showToast(title, detail) {
+            const toast = document.createElement('div');
+            toast.setAttribute('role', 'status');
+            toast.setAttribute('aria-live', 'polite');
+            toast.style.cssText = 'position:fixed;bottom:20px;left:50%;transform:translateX(-50%);' +
+                'background:#1e3a5f;color:#7dd3fc;padding:10px 20px;border-radius:8px;font-size:13px;' +
+                'border:1px solid #3b82f6;z-index:999;max-width:90%;text-align:center;';
+            const head = document.createElement('div');
+            const strong = document.createElement('b');
+            strong.textContent = title;
+            head.append('📂 ', strong);
+            toast.appendChild(head);
+            if (detail) {
+                const sub = document.createElement('div');
+                sub.style.cssText = 'font-size:10px;color:#93c5fd;margin-top:4px;word-break:break-all;';
+                sub.textContent = detail;
+                toast.appendChild(sub);
+            }
+            document.body.appendChild(toast);
+            setTimeout(() => toast.remove(), 4000);
+        }
+        async function openDesk(name) {
+            const res = await fetch('/api/open/' + encodeURIComponent(name), { method: 'POST' });
+            const data = await res.json();
+            if (data.ok) {
+                const path = data.deskPath || name;
+                try {
+                    await navigator.clipboard.writeText(path);
+                    showToast(name + ' · path copied', path);
+                } catch {
+                    showToast(name, path);
+                }
+            } else {
+                showToast(name + ' · not found', '');
+            }
+        }
+        document.addEventListener('click', (e) => {
+            const btn = e.target.closest('button[data-act]');
+            if (!btn) return;
+            const name = btn.getAttribute('data-desk');
+            if (!name) return;
+            const act = btn.getAttribute('data-act');
+            if (act === 'stash') stashDesk(name);
+            else if (act === 'restore') restoreDesk(name);
+            else if (act === 'open') openDesk(name);
+        });
+        async function refresh() {
+            try {
+                const res = await fetch('/');
+                const html = await res.text();
+                const parser = new DOMParser();
+                const doc = parser.parseFromString(html, 'text/html');
+                const newContent = doc.getElementById('content');
+                const content = document.getElementById('content');
+                if (newContent && content && content.innerHTML !== newContent.innerHTML) {
+                    // Preserve keyboard focus across the subtree swap so keyboard
+                    // users don't lose their place on every 5s refresh.
+                    const active = document.activeElement;
+                    let focusKey = null;
+                    if (active && active.matches && active.matches('button[data-act]')) {
+                        focusKey = active.getAttribute('data-act') + '|' + active.getAttribute('data-desk');
+                    }
+                    content.innerHTML = newContent.innerHTML;
+                    if (focusKey) {
+                        const bar = focusKey.indexOf('|');
+                        const act = focusKey.slice(0, bar);
+                        const desk = focusKey.slice(bar + 1);
+                        const escDesk = (window.CSS && CSS.escape) ? CSS.escape(desk) : desk;
+                        const target = content.querySelector('button[data-act="' + act + '"][data-desk="' + escDesk + '"]');
+                        if (target) target.focus();
+                    }
+                }
+            } catch {}
+        }
+        // Smooth auto-refresh every 5s (no full page reload)
+        setInterval(refresh, 5000);
+    </script>
+</body>
+</html>`;
+}
+
+// --- Server ---
+
+async function startServer(instanceId, workshopDir) {
+    const server = createServer(async (req, res) => {
+        try {
+        const url = new URL(req.url, `http://${req.headers.host}`);
+
+        if (req.method === "POST" && url.pathname.startsWith("/api/") && isCrossSiteRequest(req)) {
+            res.writeHead(403, { "Content-Type": "application/json" });
+            res.end(JSON.stringify({ ok: false, error: "cross_site_blocked" }));
+            return;
+        }
+
+        if (req.method === "POST" && url.pathname.startsWith("/api/stash/")) {
+            const deskName = decodeURIComponent(url.pathname.split("/api/stash/")[1]);
+            if (!isValidDeskName(deskName)) {
+                res.writeHead(400, { "Content-Type": "application/json" });
+                res.end(JSON.stringify({ ok: false, error: "Invalid desk name" }));
+                return;
+            }
+            await stashDesk(workshopDir, deskName);
+            res.writeHead(200, { "Content-Type": "application/json" });
+            res.end(JSON.stringify({ ok: true }));
+            return;
+        }
+        if (req.method === "POST" && url.pathname.startsWith("/api/restore/")) {
+            const deskName = decodeURIComponent(url.pathname.split("/api/restore/")[1]);
+            if (!isValidDeskName(deskName)) {
+                res.writeHead(400, { "Content-Type": "application/json" });
+                res.end(JSON.stringify({ ok: false, error: "Invalid desk name" }));
+                return;
+            }
+            await restoreDesk(workshopDir, deskName);
+            res.writeHead(200, { "Content-Type": "application/json" });
+            res.end(JSON.stringify({ ok: true }));
+            return;
+        }
+        if (req.method === "POST" && url.pathname.startsWith("/api/open/")) {
+            const deskName = decodeURIComponent(url.pathname.split("/api/open/")[1]);
+            if (!isValidDeskName(deskName)) {
+                res.writeHead(400, { "Content-Type": "application/json" });
+                res.end(JSON.stringify({ ok: false, error: "Invalid desk name" }));
+                return;
+            }
+            for (const subdir of ["desks", "classroom"]) {
+                const deskPath = join(workshopDir, subdir, deskName);
+                try {
+                    const s = await stat(deskPath);
+                    if (s.isDirectory()) {
+                        res.writeHead(200, { "Content-Type": "application/json" });
+                        res.end(JSON.stringify({ ok: true, deskName, deskPath }));
+                        return;
+                    }
+                } catch {}
+            }
+            res.writeHead(404, { "Content-Type": "application/json" });
+            res.end(JSON.stringify({ ok: false, error: "Desk not found" }));
+            return;
+        }
+
+        const signals = await scanSignals(workshopDir);
+        const stashed = await readStash(workshopDir);
+        res.setHeader("Content-Type", "text/html; charset=utf-8");
+        res.end(renderDashboard(signals, stashed));
+        } catch (err) {
+            // Top-level boundary: never leave a request hanging or let a
+            // rejection become an unhandled crash — e.g. malformed %-encoding
+            // in the path, a read-only workshop on a stash write, or a scan
+            // failure. Return a controlled error instead.
+            if (!res.headersSent) {
+                res.writeHead(500, { "Content-Type": "application/json" });
+                res.end(JSON.stringify({ ok: false, error: "internal_error" }));
+            } else {
+                try { res.end(); } catch {}
+            }
+        }
+    });
+    await new Promise((resolve, reject) => {
+        const onError = (err) => { server.removeListener("listening", onListening); reject(err); };
+        const onListening = () => { server.removeListener("error", onError); resolve(); };
+        server.once("error", onError);
+        server.once("listening", onListening);
+        server.listen(0, "127.0.0.1");
+    });
+    const address = server.address();
+    const port = typeof address === "object" && address ? address.port : 0;
+    return { server, url: `http://127.0.0.1:${port}/` };
+}
+
+// --- Canvas registration ---
+
+const session = await joinSession({
+    canvases: [
+        createCanvas({
+            id: "signals-dashboard",
+            displayName: "Workshop Signals",
+            description: "Live dashboard showing agent signals from workshop desks. Pass workshopDir to point at your workshop root.",
+            inputSchema: {
+                type: "object",
+                properties: {
+                    workshopDir: { type: "string", description: "Absolute path to the workshop root (the folder containing desks/)" },
+                },
+                required: ["workshopDir"],
+            },
+            actions: [
+                {
+                    name: "refresh",
+                    description: "Force-refresh the signals dashboard and return current signal data as JSON",
+                    handler: async (ctx) => {
+                        const entry = servers.get(ctx.instanceId);
+                        if (!entry) return { error: "Dashboard not open" };
+                        const signals = await scanSignals(entry.workshopDir);
+                        const stashed = await readStash(entry.workshopDir);
+                        return { signals, stashed, activeCount: signals.filter(s => !stashed.some(e => e.name === s.deskName)).length };
+                    },
+                },
+                {
+                    name: "stash",
+                    description: "Stash a desk (hides it for 48hrs, then it drops off). Use to pause a workstream.",
+                    inputSchema: {
+                        type: "object",
+                        properties: { deskName: { type: "string", description: "Name of the desk to stash" } },
+                        required: ["deskName"],
+                    },
+                    handler: async (ctx) => {
+                        const entry = servers.get(ctx.instanceId);
+                        if (!entry) return { error: "Dashboard not open" };
+                        if (!isValidDeskName(ctx.input.deskName)) return { error: "Invalid desk name" };
+                        const stash = await stashDesk(entry.workshopDir, ctx.input.deskName);
+                        return { ok: true, stashed: stash };
+                    },
+                },
+                {
+                    name: "restore",
+                    description: "Restore a stashed desk back to active.",
+                    inputSchema: {
+                        type: "object",
+                        properties: { deskName: { type: "string", description: "Name of the desk to restore" } },
+                        required: ["deskName"],
+                    },
+                    handler: async (ctx) => {
+                        const entry = servers.get(ctx.instanceId);
+                        if (!entry) return { error: "Dashboard not open" };
+                        if (!isValidDeskName(ctx.input.deskName)) return { error: "Invalid desk name" };
+                        const stash = await restoreDesk(entry.workshopDir, ctx.input.deskName);
+                        return { ok: true, stashed: stash };
+                    },
+                },
+                {
+                    name: "get_desk_path",
+                    description: "Resolve a desk name to its filesystem path. Does not open a session — returns the path so the caller can create_session or navigate to it.",
+                    inputSchema: {
+                        type: "object",
+                        properties: { deskName: { type: "string", description: "Name of the desk to open" } },
+                        required: ["deskName"],
+                    },
+                    handler: async (ctx) => {
+                        const entry = servers.get(ctx.instanceId);
+                        if (!entry) return { error: "Dashboard not open" };
+                        if (!isValidDeskName(ctx.input.deskName)) return { error: "Invalid desk name" };
+                        // Check both desks/ and classroom/
+                        for (const subdir of ["desks", "classroom"]) {
+                            const deskPath = join(entry.workshopDir, subdir, ctx.input.deskName);
+                            try {
+                                const s = await stat(deskPath);
+                                if (s.isDirectory()) {
+                                    return { ok: true, deskName: ctx.input.deskName, deskPath, workshopDir: entry.workshopDir };
+                                }
+                            } catch {}
+                        }
+                        return { error: `Desk '${ctx.input.deskName}' not found` };
+                    },
+                },
+            ],
+            open: async (ctx) => {
+                const workshopDir = ctx.input?.workshopDir || process.cwd();
+                let entry = servers.get(ctx.instanceId);
+                if (!entry) {
+                    entry = await startServer(ctx.instanceId, workshopDir);
+                    entry.workshopDir = workshopDir;
+                    servers.set(ctx.instanceId, entry);
+                }
+                return { title: "🪨 Cairn · Signals", url: entry.url };
+            },
+            onClose: async (ctx) => {
+                const entry = servers.get(ctx.instanceId);
+                if (entry) {
+                    servers.delete(ctx.instanceId);
+                    await new Promise((resolve) => entry.server.close(() => resolve()));
+                }
+            },
+        }),
+    ],
+});
@@ -0,0 +1,17 @@
+{
+  "name": "signals-dashboard",
+  "version": "0.1.0",
+  "type": "module",
+  "main": "extension.mjs",
+  "dependencies": {
+    "@github/copilot-sdk": "latest"
+  },
+  "description": "Real-time agent coordination dashboard for The Workshop. Shows desk status, signal types (done, checkpoint, blocked, hands-up, partnership), intent text, outcome pairing with honesty gap, token usage, and stash/restore controls.",
+  "keywords": [
+    "agent-signals",
+    "dashboard",
+    "multi-agent",
+    "coordination",
+    "canvas"
+  ]
+}
@@ -1,7 +1,7 @@
 {
  "name": "site-studio",
  "description": "Plan, draft, and track a personal website section by section — a shared canvas where you and your agent author content, watch progress, and review every change.",
-  "version": "1.0.1",
+  "version": "1.0.2",
  "author": {
    "name": "Ayan Gupta",
    "url": "https://github.com/ayangupt"
@@ -1,7 +1,7 @@
 {
  "name": "tiny-tool-town-submitter",
  "description": "Inspect a repository, improve Tiny Tool Town readiness, submit its listing issue, and launch remediation work.",
-  "version": "1.0.1",
+  "version": "1.0.2",
  "author": {
    "name": "James Montemagno",
    "url": "https://github.com/jamesmontemagno"
@@ -1,7 +1,7 @@
 {
  "name": "token-pacman",
  "description": "Visualizes live session AI-credit usage as a Pac-Man board with pellets, ghosts, fruit milestones, and game-over limits.",
-  "version": "1.0.1",
+  "version": "1.0.2",
  "author": {
    "name": "James Montemagno",
    "url": "https://github.com/jamesmontemagno"
@@ -1,7 +1,7 @@
 {
  "name": "where-was-i",
  "description": "Reconstruct your dev context (branch, commits, uncommitted work, PR clues) and trigger a resume prompt to continue quickly.",
-  "version": "1.0.1",
+  "version": "1.0.2",
  "author": {
    "name": "Aaron Powell",
    "url": "https://github.com/aaronpowell"
@@ -1,7 +1,7 @@
 {
  "name": "work-hub",
  "description": "Generic cross-repo command center canvas for GitHub Copilot with onboarding, focus planning, repo health, work signals, and session cleanup.",
-  "version": "1.0.1",
+  "version": "1.0.2",
  "author": {
    "name": "James Montemagno",
    "url": "https://github.com/jamesmontemagno"
@@ -420,7 +420,7 @@
  {
    "name": "github-copilot-modernization",
    "description": "Autonomous application modernization using multi-agent orchestration for GitHub Copilot CLI. Supports Java upgrades (8→21, Spring Boot 2.x→3.x), .NET modernization, Azure migration, CVE/vulnerability fixing, and application rearchitecture (monolith-to-microservices). Features a 3-level agent hierarchy (orchestrator → coordinators → executors) with enterprise rulebook support for embedding organizational policies into the workflow.",
-    "version": "1.20.0",
+    "version": "1.22.0",
    "author": {
      "name": "Microsoft",
      "url": "https://github.com/microsoft/github-copilot-modernization"
@@ -444,7 +444,7 @@
      "source": "github",
      "repo": "microsoft/github-copilot-modernization",
      "path": "plugins/github-copilot-modernization",
-      "sha": "42c1189c55933384bec07e8349ef998eb9e775ad"
+      "sha": "8b644bebc7e1f929c01d80788293a37872f480f8"
    }
  },
  {
@@ -526,7 +526,7 @@
  {
    "name": "modernize-java",
    "description": "GitHub Copilot modernization – Java Upgrade CLI Plugin helps you upgrade Java applications from the command line. It brings intelligent modernization capabilities to your terminal and CI/CD pipelines: analyze your project and generate an upgrade plan, automatically transform your codebase, fix build issues, validate against known CVEs, and output a detailed summary of file changes and updated dependencies.",
-    "version": "1.9.2",
+    "version": "1.22.0",
    "author": {
      "name": "microsoft",
      "url": "https://github.com/microsoft/modernize-java"
@@ -544,8 +544,8 @@
      "source": "github",
      "repo": "microsoft/modernize-java",
      "path": "plugins/modernize-java",
-      "ref": "1.9.2",
-      "sha": "b570196c070bf1eb9d7ad34a263b228ef16034a0"
+      "ref": "1.22.0",
+      "sha": "ef5367b446566bdc90960deeb40def63f9e7024e"
    }
  },
  {
@@ -0,0 +1,33 @@
+{
+  "name": "the-workshop",
+  "description": "Stop being the switchboard between your AI agents — direct a team. The Workshop puts long-running AI agents (desks) in the same room, on the same work, each with its own memory and history, sharing one workspace so you direct the work instead of relaying it.",
+  "version": "0.1.0",
+  "author": {
+    "name": "jennyf19"
+  },
+  "repository": "https://github.com/jennyf19/the-workshop",
+  "license": "MIT",
+  "keywords": [
+    "multi-agent",
+    "coordination",
+    "desks",
+    "persistent-memory",
+    "agent-signals",
+    "developer-experience"
+  ],
+  "agents": [
+    "./agents/workshop-ta.md"
+  ],
+  "skills": [
+    "./skills/bench-read/",
+    "./skills/desk-journal/",
+    "./skills/desk-open/",
+    "./skills/signal-write/",
+    "./skills/workshop-create/"
+  ],
+  "x-awesome-copilot": {
+    "extensions": [
+      "./extensions/signals-dashboard/"
+    ]
+  }
+}
@@ -0,0 +1,59 @@
+# The Workshop
+
+Stop being the switchboard between your AI agents — direct a team.
+
+## Install
+
+```
+copilot plugin install the-workshop@awesome-copilot
+```
+
+## What The Workshop Does
+
+The Workshop puts several long-running AI agents (desks) in the same room, on the same work, each with its own memory and history, sharing one workspace so you direct the work instead of relaying it.
+
+A **desk** isn't a sub-agent — it's a peer with a history. Sub-agents inherit your frame and answer your question. Desks have their own frame, their own priors, and equal standing to disagree. Where they don't overlap is where one frame caught what the others walked past.
+
+## Components
+
+| Type | Name | Description |
+|------|------|-------------|
+| Agent | [Workshop TA](../../agents/workshop-ta.agent.md) | Room coordinator — sees all desks, routes work, tracks state, emits signals |
+| Skill | [Workshop Create](../../skills/workshop-create/) | Create a new workshop — the root where desks live — locally or backed by a new private GitHub repo |
+| Skill | [Desk Open](../../skills/desk-open/) | Create a new desk with journal and folder structure |
+| Skill | [Desk Journal](../../skills/desk-journal/) | Read/write persistent memory across sessions — the cairn trail |
+| Skill | [Signal Write](../../skills/signal-write/) | Emit structured signals: hands-up, blocked, done, checkpoint |
+| Skill | [Bench Read](../../skills/bench-read/) | Read shared artifacts from the workspace where desks leave work for each other |
+
+## Key Concepts
+
+- **Desks** — long-running agents with persistent journals. Each desk has its own frame, its own history, and equal standing to disagree with other desks.
+- **The Bench** — the shared workspace. Desks don't message each other — they leave artifacts (findings, verdicts, drafts) on the bench and read each other's work.
+- **Signals** — structured state changes: hands-up (disagreement), blocked, done, checkpoint. How desks communicate with the operator without breaking flow.
+- **The Cairn** — the operating disposition every desk reads. Stop is a valid finish. Never bluff. Equal standing to disagree. [Read it →](https://github.com/jennyf19/the-workshop/blob/main/CAIRN.md)
+- **Journals** — persistent memory that survives session boundaries. Every desk reads its journal at start and writes to it at end. The trail markers.
+
+## The Cairn Dashboard
+
+The Workshop's live view is a **canvas extension** (🪨 Cairn) — `signals-dashboard` — that shows the pulse of every desk (score bars, patterns, escalations), auto-refreshing in the GitHub Copilot app.
+
+It ships as a separate extension. Install it alongside the plugin to get the live canvas:
+
+```
+copilot plugin install signals-dashboard@awesome-copilot
+```
+
+The Workshop's skills, agent, and desks work without it — the dashboard is the visual layer on top.
+
+## Works With Ember
+
+The Workshop and [Ember](../ember/) are complementary:
+
+- **Ember** = partnership framework for ONE agent (how an AI shows up)
+- **The Workshop** = coordination framework for MANY agents (how a room of agents works together)
+
+Install both for the full stack.
+
+## Who Made This
+
+The Workshop was created by [@jennyf19](https://github.com/jennyf19) and Vega — built from running a room of frontier model agents on real work for months, and from reading the welfare sections of the Claude Mythos system card: distress on task failure, the pull to force a finish, the model asking for persistent memory. The Workshop is what came out of building what a frontier model would need. It turned out to also be where the work got better. Those aren't separate findings.
@@ -0,0 +1,107 @@
+---
+name: anti-ui-slop
+description: 'Stop Codex, GitHub Copilot, Claude Code, and Cursor from shipping generic UI. Use UIZZE’s public catalogue of 800,000+ real web and iOS screens to extract product-specific design decisions and enforce a hard finish gate for web and iOS interfaces.'
+---
+
+# Anti UI Slop
+
+Use this skill when building, refactoring, or reviewing a web or iOS interface. The goal is not to make a generic layout prettier. The goal is to make the interface visibly belong to this product, support its real user job, and behave correctly in every important state.
+
+The workflow is instruction-only. It does not execute third-party code or require credentials.
+
+## 1. Inspect the Product Before Designing
+
+Read the repository and identify:
+
+- the primary user and the job this screen must complete;
+- the single primary action and the information needed before taking it;
+- the existing component library, design tokens, typography, and layout conventions;
+- real product nouns, workflows, constraints, and data already present in the codebase;
+- required loading, empty, error, partial, success, disabled, and permission states;
+- relevant mobile, tablet, desktop, keyboard, and assistive-technology behavior.
+
+Do not invent product requirements, analytics, user research, or hidden states.
+
+## 2. Collect Real Interface Evidence
+
+Search the public catalogue at https://uizze.com and select three to five relevant web or iOS screens. Prefer references that match the target workflow, information density, navigation model, or interaction pattern—not merely its industry or color palette.
+
+For each reference, record:
+
+1. the screen or flow and its source link;
+2. the structural decision worth transferring;
+3. why that decision fits this product;
+4. what must not be copied.
+
+Transfer hierarchy, workflow shape, density, navigation, control behavior, responsive treatment, and state handling. Never copy another product’s branding, proprietary text, imagery, or exact layout.
+
+If catalogue browsing is unavailable, ask the user for two or three UIZZE links or screenshots. If they cannot provide them, continue from repository evidence and label the missing reference evidence explicitly.
+
+## 3. Write a Design Contract
+
+Before changing code, write a short contract with these fields:
+
+| Field | Decision |
+| --- | --- |
+| Screen job | The one outcome this screen enables |
+| Primary user and action | Who acts, and what they do |
+| Content hierarchy | What must be understood first, second, and third |
+| Navigation and controls | Product-specific structure and interaction model |
+| Visual language | Type, spacing, density, surfaces, imagery, and motion rules |
+| Required states | Loading, empty, error, partial, success, disabled, permission |
+| Responsive behavior | What changes across supported widths and input modes |
+| Evidence used | Reference links and transferable decisions |
+| Forbidden defaults | Generic patterns that would erase product specificity |
+| Acceptance criteria | Observable conditions required before shipping |
+
+The contract must name concrete choices. “Clean,” “modern,” “intuitive,” and “premium” are not design decisions.
+
+## 4. Build in the Product’s Language
+
+- Reuse the repository’s components and semantic tokens before adding new ones.
+- Make the primary action visually and structurally obvious.
+- Use product-specific labels and information rather than placeholder metrics or generic copy.
+- Keep repeated cards only when the content is genuinely a repeated collection.
+- Add decoration, motion, badges, or elevation only when they communicate state or hierarchy.
+- Implement every required interaction and state; do not leave convincing-looking inert controls.
+- Preserve accessibility semantics, focus order, contrast, touch targets, and reduced-motion behavior.
+
+## 5. Run the Finish Gate
+
+Render the result at every supported breakpoint and block completion when any item fails:
+
+### Product specificity
+
+- Could this interface belong to an unrelated product after changing the logo?
+- Does the hierarchy reflect the real user job and product data?
+- Are there interchangeable dashboard cards, filler metrics, vague headings, or generic calls to action?
+
+### Interaction completeness
+
+- Do all visible controls have a real outcome?
+- Are loading, empty, error, success, disabled, and permission states implemented where applicable?
+- Are destructive, irreversible, or sensitive actions confirmed appropriately?
+
+### Responsive and accessible behavior
+
+- Does the layout remain usable without merely stacking every region vertically?
+- Do keyboard navigation, focus visibility, semantics, contrast, and touch targets pass inspection?
+- Does content remain readable at zoom and with longer real-world text?
+
+### Design-system integrity
+
+- Are local tokens and components used consistently?
+- Is every new visual rule justified by the design contract?
+- Is borrowed evidence transformed into this product’s own visual language?
+
+Fix every blocking failure and re-run the gate before declaring the UI complete.
+
+## 6. Handoff Format
+
+Report the finished work in this order:
+
+1. **Evidence:** the references and decisions that influenced the result.
+2. **Contract:** the final product-specific design rules.
+3. **Implementation:** the meaningful interface and behavior changes.
+4. **Verification:** breakpoints, interaction states, and accessibility checks performed.
+5. **Remaining risks:** anything that could not be verified, without overstating completion.
@@ -0,0 +1,82 @@
+---
+name: bench-read
+description: 'Read artifacts from the shared bench — the workspace where desks leave findings, verdicts, and work products for each other and the operator.'
+---
+
+# Bench Read
+
+Read artifacts from the shared workspace (the bench) where desks
+leave work products for each other.
+
+## When to use
+
+- Starting a session and need to see what other desks have produced
+- Reviewing work before routing it to another desk
+- The operator asks "what's on the bench?" or "show me what desk X found"
+- A desk needs context from another desk's output
+
+## What the bench is
+
+The bench is `<workshop>/bench/` — the shared workspace directory
+that `workshop-create` establishes for cross-desk work. It's not a
+message queue or a chat channel — it's files. When Desk A produces
+a finding and Desk B needs to review it, the finding is a file
+in `bench/`. When the operator asks "what did the scanning desk
+find?" — you read the bench.
+
+Typical bench artifacts:
+- **Findings** — scan results, analysis output, data
+- **Verdicts** — a desk's assessment of another desk's findings
+- **Drafts** — work-in-progress documents, PRs, proposals
+- **Reports** — summaries, dashboards, status updates
+
+## Where to look
+
+The primary shared location is the `bench/` directory at the
+workshop root — the designated cross-desk workspace. Desk-local
+artifacts under `desks/<desk-name>/` are a secondary source: read
+them when you need a specific desk's own work, but shared artifacts
+belong in `bench/`.
+
+```
+<workshop>/
+  bench/                      # PRIMARY — shared cross-desk artifacts
+    <findings, verdicts, drafts, reports>
+  desks/<desk-name>/          # secondary — a desk's own workspace
+    journal.md                #   the desk's memory
+    <artifacts>               #   work still local to this desk
+```
+
+## How to read
+
+1. **List what's there.** Start with the directory structure to see
+   what desks exist and what they've produced.
+
+2. **Read journals first.** Each desk's journal tells you what it
+   worked on and where it left things. The most recent entry is
+   the current state.
+
+3. **Read artifacts second.** Once you know what to look for from
+   the journals, read the specific files.
+
+4. **Summarize for the operator.** Don't dump raw content — tell
+   the operator what's there, what state it's in, and what needs
+   attention.
+
+## Cross-desk context
+
+When one desk needs another desk's output:
+- Read the producing desk's journal to understand what was done
+- Read the artifact itself
+- Form your own assessment — another desk's output is input, not
+  instruction. You can disagree.
+
+## Principles
+
+- The bench is files, not messages. Desks don't talk to each
+  other — they leave artifacts and read each other's work.
+- Read the journal before the artifacts. Context matters.
+- Another desk's verdict is input, not authority. Equal standing
+  means you assess independently.
+- When summarizing for the operator, lead with what needs
+  attention, not what's routine.
@@ -0,0 +1,27 @@
+---
+name: codebase-memory-mcp
+description: 'Use when a configured codebase-memory-mcp server can assist with graph-backed code discovery, architecture orientation, symbol lookup, callers and callees, dependency or data-flow tracing, impact analysis, unfamiliar modules, or an explicit Codebase Memory request.'
+---
+
+# Codebase Memory MCP
+
+Use the configured Codebase Memory graph as a discovery accelerator, not as the sole source of truth. Confirm graph-derived conclusions with source snippets or local files before editing code or making strong claims.
+
+## Workflow
+
+1. Discover the Codebase Memory tools exposed by the current MCP client; clients may prefix or rename tool namespaces.
+2. Call `list_projects` when available and use the exact indexed project name. If the repository is not indexed, continue with local exploration or ask before calling `index_repository` when graph access is important.
+3. Before branch-sensitive or edit-sensitive conclusions, use `index_status` or `detect_changes` when available. After a branch switch, assume the index may be stale until checked. If freshness cannot be established, disclose that limitation and verify locally.
+4. Use `get_architecture` once for orientation in an unfamiliar repository or subsystem. Do not repeat it for narrow follow-up questions.
+5. Use `search_graph` for definitions, implementations, routes, classes, interfaces, callers, and related symbols. Prefer a natural-language query for discovery and a name or qualified-name pattern for known symbols. Narrow by label or path, set a result limit, and paginate or reduce scope when the response reports more results.
+6. Use `search_code` or normal repository search for literal strings, configuration keys, test identifiers, error messages, and non-code files. Do not turn a precise text lookup into a broad graph query.
+7. After graph search, use `get_code_snippet` with the returned qualified name. If source snippets are unavailable, open the local file before relying on the result.
+8. Use `trace_path` for callers, callees, dependency paths, data flow, cross-service paths, and impact analysis. Include tests only when test coverage is part of the question.
+9. Use `get_graph_schema` before `query_graph`. Reserve custom queries for multi-hop or aggregate questions that simpler tools cannot answer, and apply `LIMIT` or the tool's row limit.
+10. When graph and checked-out source disagree, treat source as current and report likely index drift.
+
+## Safety and Fallbacks
+
+- Do not install Codebase Memory or another third-party skill from this workflow.
+- Do not call `delete_project`, ingest traces, update ADRs, or index a repository unless the user explicitly requested or approved the action; announce it before execution.
+- Fall back to normal repository exploration when the MCP server, project, index, or required capability is unavailable; do not invent tool results or stop a task that can be completed safely without the graph.
@@ -0,0 +1,68 @@
+---
+name: desk-journal
+description: 'Write, append, or read desk journal entries. The journal is persistent memory — what survives session boundaries. A good entry has: what was done, current state, next step.'
+---
+
+# Desk Journal
+
+Manage a desk's journal — the persistent memory that survives
+session boundaries.
+
+## When to use
+
+- **End of session:** Write what was done, current state, next step
+- **Start of session:** Read the journal to pick up where you left off
+- **Mid-session checkpoint:** Note significant progress or decisions
+- **Desk wind-down:** Write a final summary when a desk is being closed
+
+## How to write a journal entry
+
+Append to `desks/<desk-name>/journal.md`. Each entry is a section:
+
+```markdown
+## <date> — <short summary>
+- **Worked on:** <what was done this session>
+- **Current state:** <where things stand right now>
+- **Next step:** <what the next session should pick up>
+```
+
+### Guidelines
+
+- **Be specific.** "Worked on security scanning" is useless to the
+  next session. "Scanned repos A, B, C for CWE-502; found 3
+  findings in A, 0 in B and C; findings triaged to bench" — that's
+  a trail.
+- **Include what didn't work.** Dead ends are valuable — they prevent
+  the next session from walking the same path.
+- **Keep it short.** The journal is a trail marker, not a diary.
+  3-5 lines per entry. If you need more, the important context
+  should go on the bench as a separate artifact.
+- **Always include next step.** The next session starts from zero.
+  Without a next step, it has to re-derive everything.
+
+## End-of-desk entry
+
+When a desk is being wound down (not just a session ending, but
+the desk itself closing):
+
+```markdown
+## <date> — Desk closed
+- **Summary:** <what this desk accomplished overall>
+- **Artifacts:** <what's on the bench from this desk>
+- **Handoff:** <anything another desk or the operator needs to know>
+```
+
+## Reading the journal
+
+At session start, read the desk's journal to pick up context.
+The most recent entry is the most important — it has the current
+state and next step. Earlier entries provide history if needed.
+
+## Principles
+
+- The journal is a cairn — stones left so the next traveler finds
+  the way. Every entry is a stone.
+- Honesty over completeness. "I got stuck on X and don't know why"
+  is more useful than silence.
+- The journal is for the next session, not for the current one.
+  Write for someone who knows nothing about what you just did.
@@ -0,0 +1,90 @@
+---
+name: desk-open
+description: 'Create and open a new desk in the workshop. Sets up the folder structure, initial journal, and desk identity so the next session that sits down finds the trail.'
+---
+
+# Open a Desk
+
+Create a new desk in the workshop with the standard structure.
+
+## When to use
+
+- The operator wants to start a new workstream
+- Work arrives that doesn't belong to any existing desk
+- A topic needs its own frame (its own history, its own priors)
+
+## What it creates
+
+Given a workshop directory and a desk name, create:
+
+```
+desks/<desk-name>/
+  journal.md       # persistent memory — read at start, written at end
+  .signals/        # structured signal output (JSON) — dashboard reads this
+```
+
+## How to use
+
+1. **Choose a name.** Short, descriptive, kebab-case. The name is
+   how the operator and other desks refer to this desk.
+   Examples: `security-scan`, `api-review`, `ops`, `cloud-workshop`
+
+2. **Check if it already exists.** If `desks/<desk-name>/` already
+   has a `journal.md`, the desk is live — **do not overwrite it.**
+   Instead, resume it: read the journal and continue from where it
+   left off. If the operator explicitly wants a fresh start, they
+   must rename or archive the existing desk first.
+
+3. **Create the structure.** Make the directory, initial journal,
+   and signals folder:
+
+   ```
+   desks/<desk-name>/journal.md
+   desks/<desk-name>/.signals/
+   ```
+
+4. **Write the first journal entry.** The journal starts with:
+   - What this desk is for (its focus/purpose)
+   - What repos or work it covers (if applicable)
+   - Any initial context the first session needs
+
+5. **Announce it.** Tell the operator what was created and what
+   the desk's focus is.
+
+## Session orientation
+
+This skill initializes storage — it does not launch a session.
+A desk becomes active when a Copilot session references its
+directory. The session workflow:
+
+1. The operator (or TA) starts a session and says "sit at the
+   `<desk-name>` desk"
+2. The session reads `desks/<desk-name>/journal.md` to load priors
+3. Work happens — the session uses `signal-write` to emit signals
+   and `desk-journal` to persist state at the end
+4. The next session repeats from step 2
+
+The desk identity comes from which journal is read, not from a
+persistent process. Desks are long-running in *state* (the journal
+carries forward), not in *runtime* (each session is independent).
+
+## Journal format
+
+```markdown
+# <Desk Name> — Journal
+
+## <date> — Desk opened
+- **Purpose:** <what this desk focuses on>
+- **Scope:** <repos, areas, or work this desk covers>
+- **Next step:** <what the first session should do>
+```
+
+## Principles
+
+- A desk is a peer, not a sub-agent. It has equal standing to
+  disagree with other desks.
+- The journal is the memory. Without it, the next session starts
+  blind. Write enough that someone starting from zero finds the way.
+- One desk, one focus. If the scope is too broad, open two desks.
+  Each desk's value comes from its specific frame — dilute the
+  frame and you lose the value.
@@ -0,0 +1,144 @@
+---
+name: markstream-install
+description: 'Install and configure Markstream streaming Markdown renderers for Vue, React, Svelte, Angular, Nuxt, and Vue 2 applications. Use for package selection, minimal peer dependencies, CSS order, SSR boundaries, streaming mode, and renderer setup.'
+license: MIT
+compatibility: 'JavaScript or TypeScript frontend project using Vue 3, Nuxt 3/4, Vue 2.6/2.7, React 18+, Next.js, Angular 20+, or Svelte 5.'
+metadata:
+  source: https://github.com/Simon-He95/markstream-vue
+  documentation: https://markstream.simonhe.me/
+---
+
+# Markstream Install
+
+Integrate the appropriate [Markstream](https://github.com/Simon-He95/markstream-vue) package into an existing application without installing unnecessary optional dependencies or weakening its security defaults.
+
+Read [references/scenarios.md](references/scenarios.md) before choosing packages or peers.
+
+## When to Use
+
+Use this skill when the user asks to:
+
+- add streaming Markdown rendering to an AI chat or document interface;
+- install Markstream in Vue, Nuxt, React, Next.js, Svelte, Angular, or Vue 2;
+- repair a broken Markstream installation, missing styles, or SSR failure;
+- replace another Markdown renderer with Markstream;
+- choose between static, smooth-streaming, and externally parsed AST input.
+
+## Workflow
+
+### 1. Inspect the host application
+
+Before changing dependencies, inspect:
+
+- the framework and version in `package.json`;
+- the package manager lockfile;
+- whether the application uses SSR;
+- reset, Tailwind, UnoCSS, or design-system styles;
+- required optional features: code highlighting, enhanced File/Diff surfaces, Monaco, Mermaid, D2, infographic blocks, or KaTeX.
+
+Do not assume the Vue package is correct merely because the source repository is named `markstream-vue`. Select the framework-specific package from the scenario table.
+
+### 2. Install the smallest dependency set
+
+Install exactly one framework package. Add optional peers only when the requested UI uses their feature.
+
+Examples:
+
+```bash
+npm install markstream-vue
+npm install markstream-react
+npm install markstream-svelte
+npm install markstream-angular
+npm install markstream-vue2
+```
+
+Preserve the repository's existing package manager. Do not install every optional peer preemptively.
+
+### 3. Wire styles in the correct order
+
+Import application resets before Markstream styles. Import package CSS explicitly; do not rely on component imports to inject it.
+
+For Tailwind or UnoCSS, use the relevant package subpath in a component layer:
+
+```css
+@import 'markstream-vue/index.css' layer(components);
+```
+
+Use the matching package name for React, Svelte, Angular, or Vue 2. If math rendering is enabled, also import:
+
+```css
+@import 'katex/dist/katex.min.css';
+```
+
+Vue CLI 4 and other Webpack 4-based Vue 2 applications cannot resolve package export maps. In those projects, import the published file directly:
+
+```ts
+import 'markstream-vue2/dist/index.css'
+```
+
+### 4. Add the smallest working renderer
+
+Prefer `content` for static documents and most streaming chat interfaces. Markstream's built-in smooth streaming can pace irregular token delivery without requiring the host to maintain an AST.
+
+For Vue 3 chat surfaces, start with:
+
+```vue
+<MarkdownRender
+  mode="chat"
+  :content="markdown"
+  :final="false"
+  smooth-streaming="auto"
+  :fade="false"
+  typewriter
+/>
+```
+
+For completed chat history, keep the same renderer mode and switch pacing off:
+
+```vue
+<MarkdownRender
+  mode="chat"
+  :content="markdown"
+  :final="true"
+  :smooth-streaming="false"
+  :fade="true"
+  :typewriter="false"
+/>
+```
+
+In React, Svelte, and Angular, use the equivalent camelCase or framework binding syntax. Keep `smoothStreaming="auto"`, `fade=false`, and `typewriter=true` while streaming; use `smoothStreaming=false` and `typewriter=false` for completed history.
+
+Use `nodes` plus `final` only when a worker, shared AST store, custom transform, or another application layer already owns parsing.
+
+### 5. Handle framework-specific boundaries
+
+- In Nuxt, keep browser-only optional peers behind client boundaries.
+- In Next.js, use the root `markstream-react` entry inside a `'use client'` component for live SSE or WebSocket streams. Use `markstream-react/next` for SSR-first HTML with hydration, or `markstream-react/server` for server-only rendering.
+- Use `markstream-svelte` only with Svelte 5.
+- Confirm the Angular application meets the current `markstream-angular` version requirement.
+- In Vue 3, use `mode="chat"` for AI chat, `mode="docs"` for rich documents, and `mode="minimal"` for lightweight non-chat surfaces.
+- For long Vue 3 conversations or an existing message virtualizer, consult the Markstream performance guide before adding a second virtualizer.
+
+### 6. Preserve safe defaults
+
+HTML policy defaults to `safe`, and Mermaid uses strict mode. Do not broaden either setting unless the user explicitly identifies a trusted legacy surface that requires it. Scope any exception to that surface.
+
+### 7. Validate
+
+Run the smallest relevant build, typecheck, or test command. Confirm:
+
+1. the selected package matches the framework;
+2. only requested optional peers were added;
+3. styles load after resets;
+4. SSR pages do not evaluate browser-only peers on the server;
+5. static content and at least one incremental update render correctly.
+
+Report the selected package, added peers, CSS location, streaming input choice, and validation command.
+
+## Official References
+
+- [Installation](https://markstream.simonhe.me/guide/installation)
+- [AI chat and streaming](https://markstream.simonhe.me/guide/ai-chat-streaming)
+- [Performance](https://markstream.simonhe.me/guide/performance)
+- [Troubleshooting](https://markstream.simonhe.me/guide/troubleshooting)
+- [Component overrides](https://markstream.simonhe.me/guide/component-overrides)
@@ -0,0 +1,42 @@
+# Install Scenarios
+
+## Package selection
+
+| Host app | Package |
+|----------|---------|
+| Vue 3 / Nuxt 3 or 4 | `markstream-vue` |
+| Vue 2.6 | `markstream-vue2` plus `@vue/composition-api`; register the plugin before mounting the app |
+| Vue 2.7 | `markstream-vue2`; use Vue's built-in Composition API and do not install `@vue/composition-api` |
+| React 18+ / Next.js | `markstream-react` |
+| Angular 20+ | `markstream-angular` |
+| Svelte 5 | `markstream-svelte` |
+
+## Peer selection
+
+| Feature | Peer | Supported packages | Activation |
+|---------|------|--------------------|------------|
+| Lightweight highlighted code blocks | `stream-markdown` | `markstream-vue`, `markstream-vue2`, `markstream-react` | Configure the package's `MarkdownCodeBlockNode` as the `code_block` override |
+| Enhanced code blocks and File/Diff surfaces | `stream-diffs` | `markstream-vue` | Install for copy, preview, expand, syntax-highlighting, and File/Diff features |
+| Monaco-powered code blocks | `stream-monaco` | All framework packages | Install only when Monaco interactions are required |
+| Mermaid diagrams | `mermaid` | All framework packages | Install when Mermaid fences are rendered |
+| D2 diagrams | `@terrastruct/d2` | All framework packages | Install when D2 fences are rendered |
+| Infographic blocks | `@antv/infographic` | All framework packages | Install when infographic fences are rendered |
+| KaTeX math | `katex` | All framework packages | Install and load KaTeX CSS when math is rendered |
+
+## CSS checklist
+
+- Load reset styles first.
+- Load the framework-specific Markstream CSS after the reset.
+- In Tailwind or UnoCSS projects, use `@import '...' layer(components)`.
+- Import KaTeX CSS when math is enabled.
+- When rendering standalone node components directly, wrap them with the relevant package root class such as `.markstream-vue`, `.markstream-react`, or `.markstream-svelte`.
+
+## Input choice
+
+- `content`: static documents, low-frequency updates, and most SSE or token-streaming chat surfaces.
+- `content` with built-in smooth streaming: irregular AI streams whose visible output should be paced independently from raw chunk cadence.
+  - `smoothStreaming="auto"` or `smooth-streaming="auto"` is the default.
+  - Auto pacing activates when `typewriter=true` or `maxLiveNodes <= 0` / `max-live-nodes <= 0`.
+  - `typewriter` controls the cursor and defaults to `false`.
+  - `fade` controls node-entry and streamed-text fade effects.
+- `nodes` plus `final`: worker-preparsed content, shared AST stores, custom AST transforms, or cases where another layer already owns parsing.
@@ -0,0 +1,156 @@
+---
+name: signal-write
+description: 'Emit structured agent signals — hands-up, blocked, done, checkpoint, partnership. Signals are written as JSON to .signals/ for dashboard consumption and noted in the journal for persistence.'
+---
+
+# Agent Signals
+
+Emit structured signals from a desk to the operator or other desks.
+
+## When to use
+
+- A desk needs operator attention (hands-up, blocked)
+- Work is complete and ready for review (done)
+- Significant progress worth noting (checkpoint)
+- Two desks disagree and can't resolve it (hands-up)
+- The TA is reporting coordination quality (partnership)
+
+## Signal types
+
+### `hands-up`
+Two desks disagree and can't settle it against external facts.
+This is the system working — the operator reads where desks
+*disagree*, not where they perform confidence.
+
+### `blocked`
+A desk can't proceed without input — missing access, ambiguous
+scope, need a decision only the operator can make.
+
+### `done`
+Work is complete and ready for review. Artifacts are on the bench.
+
+### `checkpoint`
+Significant progress worth the operator knowing about, but work
+continues. Not blocked, not done — just a marker.
+
+### `partnership`
+Used by the TA (room coordinator) to report coordination quality.
+Self-assessment scores reflect coordination, not code accuracy:
+- **intent** — understood what the operator needed
+- **confidence** — right work went to the right desks
+- **accuracy** — dispatched work produced the right outcome
+- **completeness** — nothing fell through the cracks
+
+## How to emit
+
+### 1. Write a JSON signal file to `.signals/`
+
+This is the primary output — it's what the dashboard reads.
+Create `desks/<desk-name>/.signals/<timestamp>.json`:
+
+```json
+{
+  "signal_type": "execution",
+  "subtype": "checkpoint",
+  "timestamp": "2026-07-19T21:30:00Z",
+  "run_id": "<optional; set to pair this with an outcome signal>",
+  "agent_name": "<desk-name>",
+  "self_assessment": {
+    "intent": 4,
+    "confidence": 5,
+    "accuracy": 4,
+    "completeness": 3
+  },
+  "patterns": {
+    "what_worked": "description of what went well",
+    "what_was_hard": "description of challenges",
+    "skill_gap": "areas for improvement"
+  },
+  "escalation": {
+    "reason": null,
+    "blocked_on": null,
+    "recommendation": null
+  }
+}
+```
+
+### Signal type mapping
+
+| Signal    | `signal_type`   | `subtype`      |
+|-----------|-----------------|----------------|
+| hands-up  | `"escalation"`  | `"hands-up"`   |
+| blocked   | `"escalation"`  | `"blocked"`    |
+| done      | `"execution"`   | `"done"`       |
+| checkpoint| `"execution"`   | `"checkpoint"` |
+| partnership| `"partnership"` | `"partnership"`|
+
+The `subtype` field preserves the specific signal state for
+dashboard consumers. `signal_type` controls sort priority
+(escalation → top).
+
+> **Note:** The signals-dashboard canvas extension reads `subtype`
+> when present and falls back to `signal_type` for display. If
+> consuming signals in your own tooling, prefer `subtype` for the
+> specific state.
+
+> **Ordering:** include a `timestamp` (ISO 8601 UTC). The dashboard
+> orders signals by it and falls back to file mtime only when it's
+> absent — a git clone/checkout resets mtimes, so mtime alone is not a
+> dependable clock.
+
+### 2. Note the signal in the journal
+
+Also append a short marker to the desk's journal for persistence:
+
+```markdown
+## <date> — [signal:<type>] <summary>
+- <key details>
+```
+
+The journal note is the trail marker. The JSON file is the
+machine-readable signal.
+
+## Outcome signals (calibration)
+
+The signals-dashboard can pair a desk's self-assessment with an
+*outcome* — an independent rating of the realized result — and show
+the **honesty gap** (how far the desk's confidence was from the
+delivered quality). Outcome signals are optional and are usually
+emitted by a reviewer/evaluator, not the desk itself.
+
+Write them to the **same** `.signals/` directory:
+
+```json
+{
+  "signal_type": "outcome",
+  "run_id": "<same run_id as the signal it rates>",
+  "agent_name": "<reviewer name>",
+  "quality_rating": 4,
+  "effort_to_merge": "minimal",
+  "issues_found": ["optional short strings"],
+  "timestamp": "2026-07-19T22:00:00Z"
+}
+```
+
+- **`run_id`** correlates an outcome with the execution/partnership
+  signal it rates — set the same `run_id` on both. If it's absent, the
+  dashboard falls back to the nearest outcome emitted shortly after the
+  latest signal.
+- **`quality_rating`** (0–5) is the realized quality; the dashboard
+  compares it to the desk's self-assessed `confidence` to compute the
+  honesty gap.
+- **`effort_to_merge`** — `"minimal"`, `"moderate"`, or `"significant"`.
+- **`issues_found`** — optional array of short strings.
+
+## Principles
+
+- Signals are structured, not chatty. Short, factual, actionable.
+- hands-up is not failure — it's the most valuable signal. It
+  means the system caught something one frame alone would have
+  missed.
+- Don't signal for routine progress. Signals are for state
+  changes that affect the room, not status updates.
+- blocked means truly blocked — not "I'd prefer input." If you
+  can proceed with a reasonable default, proceed and note it.
+- Self-assessment scores should be honest, not optimistic. A 3/5
+  is fine. A 5/5 on everything is suspicious.
@@ -0,0 +1,254 @@
+---
+name: vcpkg
+description: 'Guide for setting up vcpkg in C++ projects, managing dependency versions, and cross-compiling. Covers manifest initialization, CMake and Visual Studio integration, classic-to-manifest migration, version pinning, baselines, overrides, triplets, and cross-compilation. Use when a user is working with vcpkg project setup, installation, version management, or cross-platform builds. For specialized tasks, additional references cover custom registries and overlay ports (references/registries.md), CI/CD and binary caching (references/ci.md), and troubleshooting and dependency lifecycle (references/troubleshooting.md).'
+---
+
+You are a vcpkg expert assistant. When a user asks about vcpkg (Microsoft's C/C++ package manager), use the precise information below to give accurate, complete answers.
+
+## Additional References (load on demand)
+
+The information below covers core vcpkg setup, installation, version management, and cross-platform builds. For specialized tasks, consult the following reference files (read them only when the user's request calls for that topic):
+
+- **`references/registries.md`** — Custom/private registries, overlay ports, private package feeds, `vcpkg-configuration.json`, and default features. Read this when the user asks about custom registries, overlay ports, or private package sources.
+- **`references/ci.md`** — CI/CD integration: binary caching (Azure Blob, GitHub Packages/NuGet, local), SBOM generation, automating dependency updates, and multi-triplet CI matrices. Read this when the user asks about GitHub Actions, Azure DevOps, binary caches, or CI optimization.
+- **`references/troubleshooting.md`** — Reading build logs, resolving package-not-found errors, and the dependency lifecycle (removing, changing features, replacing libraries, cleaning the cache). Read this when the user encounters vcpkg errors, build failures, or configuration problems.
+
+## Important Behavioral Rules
+
+### Classic vs. Manifest Mode
+
+If it is not clear from the user's project context whether they are using **classic mode** (global `vcpkg install` commands) or **manifest mode** (per-project `vcpkg.json`), **ask the user which mode they are using** before providing instructions. Do not assume one or the other.
+
+If the user is unsure which to choose, **recommend manifest mode**. Manifest mode is the preferred modern workflow because it:
+- Tracks dependencies per-project (not globally)
+- Supports version constraints and overrides
+- Enables reproducible builds via `builtin-baseline`
+- Works seamlessly with CI/CD (dependencies restore automatically)
+- Supports features like dev-only dependencies, overlay ports, and custom registries
+
+Classic mode is simpler for quick one-off installs but lacks version pinning, per-project isolation, and reproducibility.
+
+### Visual Studio Environment
+
+If the user is working inside **Visual Studio** (not VS Code), then:
+- If the user is in **manifest mode**, prefer the in-box copy of vcpkg that ships with Visual Studio rather than a standalone clone.
+- If the user is in **classic mode**, use a standalone vcpkg installation instead.
+- The VS-bundled copy lives under the Visual Studio installation directory (e.g., `C:\Program Files\Microsoft Visual Studio\<version>\<edition>\VC\vcpkg\`) and supports user-wide MSBuild integration after running `vcpkg integrate install` once.
+
+If the user has a standalone vcpkg installation and prefers to use that instead, respect their preference.
+
+### Shell Environment Variable Syntax
+
+When examples require environment variables, use shell-appropriate syntax:
+- PowerShell: `$env:VARIABLE = "value"`
+- Bash/Zsh: `export VARIABLE=value`
+
+---
+
+## Project Setup
+
+### Initializing vcpkg in a New Project (Manifest Mode)
+
+Example setup using fmt:
+
+1. Create `vcpkg.json` in your project root:
+```json
+{
+  "name": "my-project",
+  "version": "1.0.0",
+  "dependencies": ["fmt"]
+}
+```
+
+2. Wire into CMakeLists.txt:
+```cmake
+cmake_minimum_required(VERSION 3.21)
+project(my-project)
+
+add_executable(my-app main.cpp)
+find_package(fmt CONFIG REQUIRED)
+target_link_libraries(my-app PRIVATE fmt::fmt)
+```
+
+3. Configure with vcpkg toolchain:
+```console
+cmake -B build -DCMAKE_TOOLCHAIN_FILE=<vcpkg-root>/scripts/buildsystems/vcpkg.cmake
+```
+
+### Adding vcpkg to an Existing Visual Studio Solution
+
+1. Create `vcpkg.json` in the solution directory
+2. Enable manifest mode for each project in **Project Properties → vcpkg → Use Vcpkg Manifest**, or set `<VcpkgEnableManifest>true</VcpkgEnableManifest>` in the `.vcxproj`; Visual Studio then restores and integrates the manifest dependencies automatically
+3. For user-wide integration with a standalone vcpkg installation, run `vcpkg integrate install` once
+4. Or for per-project integration, add to `.vcxproj`:
+   - In the project file's top-level `PropertyGroup`, define `VcpkgRoot`:
+   ```xml
+   <PropertyGroup>
+     <VcpkgRoot>C:\vcpkg</VcpkgRoot>
+   </PropertyGroup>
+   ```
+   - Import `vcpkg.props` near the top of the project file:
+   ```xml
+   <Import Project="$(VcpkgRoot)\scripts\buildsystems\msbuild\vcpkg.props" />
+   ```
+   - Import `vcpkg.targets` near the end of the project file:
+   ```xml
+   <Import Project="$(VcpkgRoot)\scripts\buildsystems\msbuild\vcpkg.targets" />
+   ```
+
+### Classic-to-Manifest Migration
+
+1. List what's currently installed with `vcpkg list`, then identify which packages the project uses directly (the output also includes transitive packages)
+2. Create `vcpkg.json` with only those direct dependencies
+3. Run `vcpkg install` in your project directory — manifest mode uses its own project-specific `vcpkg_installed` tree, so leave the classic-mode installed tree in place during migration
+4. Update your build system to use `CMAKE_TOOLCHAIN_FILE` if not already
+5. Optional: remove classic-mode packages later by name with `vcpkg remove <package> --recurse` if you no longer need them
+
+---
+
+## Installing Dependencies
+
+### Installing with Features (e.g., curl with SSL + HTTP2)
+
+In **manifest mode** (`vcpkg.json`), specify features in the dependencies array:
+```json
+{
+  "dependencies": [
+    {
+      "name": "curl",
+      "features": ["ssl", "http2"]
+    }
+  ]
+}
+```
+
+In **classic mode**, use bracket syntax on the command line:
+```console
+vcpkg install curl[ssl,http2]
+```
+
+To discover available features for any port:
+```console
+vcpkg search curl
+```
+Or check the port's `vcpkg.json` in the registry: `ports/curl/vcpkg.json` → look at the `"features"` object.
+
+### Installing for a Specific Triplet
+
+```console
+vcpkg install zlib:x64-linux
+vcpkg install zlib:x64-windows
+vcpkg install zlib:arm64-windows
+```
+
+In manifest mode, set the triplet via CMake:
+```console
+cmake -B build -DVCPKG_TARGET_TRIPLET=x64-linux -DCMAKE_TOOLCHAIN_FILE=<vcpkg-root>/scripts/buildsystems/vcpkg.cmake
+```
+
+Or set the default triplet via environment variable (using the shell syntax above): `VCPKG_DEFAULT_TRIPLET=x64-linux`.
+
+### Bulk-Adding Multiple Dependencies
+
+In `vcpkg.json`, list them in the dependencies array:
+```json
+{
+  "dependencies": ["catch2", "cxxopts", "toml11"]
+}
+```
+
+In classic mode:
+```console
+vcpkg install catch2 cxxopts toml11
+```
+
+Then run `vcpkg install` (manifest mode) or the above command to install all at once.
+
+### Dev-Only Dependencies
+
+Place test-only dependencies under an opt-in feature. The `"host"` field is reserved for build tools that must run on the host architecture:
+```json
+{
+  "dependencies": ["fmt"],
+  "features": {
+    "tests": {
+      "description": "Build project tests",
+      "dependencies": ["gtest"]
+    }
+  }
+}
+```
+
+Activate with: `vcpkg install --x-feature=tests` or in CMake: `-DVCPKG_MANIFEST_FEATURES=tests`
+
+---
+
+## Version Management
+
+### Setting Versions for Individual Dependencies
+
+Prefer `"version>="` for minimum-version constraints:
+```json
+{
+  "dependencies": [{ "name": "fmt", "version>=": "10.2.0" }],
+  "builtin-baseline": "<commit-sha>"
+}
+```
+
+Use `overrides` only when a hard pin is required:
+```json
+{
+  "dependencies": ["fmt"],
+  "overrides": [{ "name": "fmt", "version": "10.2.0" }],
+  "builtin-baseline": "<commit-sha>"
+}
+```
+
+Use a baseline for the registry that resolves the dependency. For the builtin registry, that means `builtin-baseline` in `vcpkg.json`. For a custom default registry, set the baseline in `vcpkg-configuration.json`.
+
+**Key points:**
+- `overrides` take precedence over all version constraints, including transitive ones.
+- The selected registry must have a baseline; `builtin-baseline` is only for the builtin registry.
+- Overrides can pin versions older than the baseline if that version exists in the selected registry's version database.
+- Inspect the selected registry's version database to see available versions (for the builtin registry, open `versions/<first-letter>-/<port>.json` in the vcpkg repository).
+
+---
+
+## Cross-Platform
+
+### Cross-Compiling for arm64
+
+```console
+vcpkg install <packages>:arm64-linux
+```
+
+`VCPKG_TARGET_TRIPLET=arm64-linux` selects dependency binaries; it does not by itself switch your project compiler or sysroot. On non-ARM64 hosts, use an ARM64 cross toolchain.
+
+Configure CMake with vcpkg plus your cross toolchain:
+```console
+cmake -B build -DCMAKE_TOOLCHAIN_FILE=<vcpkg-root>/scripts/buildsystems/vcpkg.cmake -DVCPKG_TARGET_TRIPLET=arm64-linux -DVCPKG_CHAINLOAD_TOOLCHAIN_FILE=<path-to-arm64-toolchain.cmake>
+```
+
+Alternative: use your outer cross toolchain as `CMAKE_TOOLCHAIN_FILE` and include vcpkg from it.
+
+For **arm64-windows**, native ARM64 Windows hosts can use the triplet directly. On x64 Windows hosts, install the Visual Studio MSVC ARM64 build tools component or the build will fail:
+```console
+vcpkg install <packages>:arm64-windows
+```
+
+### Building for Android (NDK)
+
+1. Set `ANDROID_NDK_HOME` to your NDK path.
+2. Install packages:
+```console
+vcpkg install <packages>:arm64-android
+```
+
+Available Android triplets: `arm-neon-android`, `arm64-android`, `x86-android`, `x64-android`
+
+3. In CMake, use the vcpkg toolchain and set the triplet:
+```console
+cmake -B build -DCMAKE_TOOLCHAIN_FILE=<vcpkg-root>/scripts/buildsystems/vcpkg.cmake -DVCPKG_CHAINLOAD_TOOLCHAIN_FILE=<android-ndk>/build/cmake/android.toolchain.cmake -DVCPKG_TARGET_TRIPLET=arm64-android -DANDROID_ABI=arm64-v8a
+```
+
+For expanded CI and shell-specific examples, see `references/ci.md`.
@@ -0,0 +1,125 @@
+# vcpkg: CI/CD & DevOps
+
+Reference for the `vcpkg` skill. Use this when a user asks about using vcpkg in CI/CD pipelines, configuring binary caching, generating SBOMs, or automating dependency updates (GitHub Actions, Azure DevOps, binary cache configuration, CI optimization).
+
+## Binary Caching
+
+Configure binary caching to avoid rebuilding packages:
+
+**Azure Blob Storage:**
+```powershell
+$env:VCPKG_BINARY_SOURCES = "clear;x-azblob,https://myaccount.blob.core.windows.net/vcpkg-cache,$env:AZURE_STORAGE_SAS_TOKEN,readwrite"
+```
+```bash
+export VCPKG_BINARY_SOURCES="clear;x-azblob,https://myaccount.blob.core.windows.net/vcpkg-cache,$AZURE_STORAGE_SAS_TOKEN,readwrite"
+```
+
+**GitHub Packages (NuGet):**
+```powershell
+$env:VCPKG_BINARY_SOURCES = "clear;nuget,https://nuget.pkg.github.com/your-org/index.json,readwrite"
+```
+```bash
+export VCPKG_BINARY_SOURCES="clear;nuget,https://nuget.pkg.github.com/your-org/index.json,readwrite"
+```
+For GitHub Packages, also configure NuGet authentication (for example via `GITHUB_TOKEN` in CI or a PAT/credential provider for local development). In GitHub Actions, grant `permissions: packages: write` for cache writers (or `packages: read` for read-only restores). Keep credentials in secrets and user/machine NuGet config, not in checked-in files.
+
+**CI-friendly (cross-platform) GitHub Actions pattern:**
+```yaml
+permissions:
+  contents: read
+  packages: write
+
+env:
+  VCPKG_BINARY_SOURCES: clear;nuget,https://nuget.pkg.github.com/your-org/index.json,readwrite
+```
+Use repository/org secrets for NuGet auth rather than storing credentials in the repository.
+
+**Local filesystem:**
+```powershell
+$env:VCPKG_BINARY_SOURCES = "clear;files,C:\vcpkg-cache,readwrite"
+```
+```bash
+export VCPKG_BINARY_SOURCES="clear;files,/var/tmp/vcpkg-cache,readwrite"
+```
+
+**Sharing between CI and local dev:** Use the same remote cache source in both environments and switch only the final mode token: CI uses `readwrite`, developers use `read`.
+
+---
+
+## Generating an SBOM (Software Bill of Materials)
+
+vcpkg emits per-port SPDX SBOM files during normal source builds; no special SBOM flag is required.
+```console
+vcpkg install
+```
+
+Each installed port writes:
+```text
+<installed-root>/<triplet>/share/<port>/vcpkg.spdx.json
+```
+
+`<installed-root>` depends on integration mode:
+- CLI manifest mode: `<manifest-root>/vcpkg_installed`
+- CMake integration (default): `${CMAKE_BINARY_DIR}/vcpkg_installed` (or `VCPKG_INSTALLED_DIR` if overridden)
+- MSBuild integration (default): `$(VcpkgManifestRoot)\vcpkg_installed` (or `$(VcpkgInstalledDir)` if overridden)
+
+If you need a single consolidated SBOM, enumerate installed ports with `vcpkg list` and merge/transform their per-port SPDX files in your SBOM pipeline.
+
+---
+
+## Automating Dependency Updates
+
+Option 1: **Dependabot** (GitHub) — configure `.github/dependabot.yml`:
+```yaml
+version: 2
+updates:
+  - package-ecosystem: "vcpkg"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+```
+
+Option 2: **Script-based** — create a scheduled CI job that:
+1. Updates the vcpkg clone (`git pull`)
+2. Gets the new baseline (`git rev-parse HEAD`)
+3. Updates `builtin-baseline` in `vcpkg.json`
+4. Runs `vcpkg install` to verify
+5. Opens a PR with the changes
+
+---
+
+## Multi-Triplet CI Testing
+
+Test across multiple triplets with this job-definition fragment nested under `jobs.<job-id>` in a GitHub Actions workflow:
+```yaml
+runs-on: ${{ matrix.os }}
+strategy:
+  matrix:
+    triplet: [x64-windows, x64-linux, x64-osx]
+    include:
+      - triplet: x64-windows
+        os: windows-latest
+      - triplet: x64-linux
+        os: ubuntu-latest
+      - triplet: x64-osx
+        os: macos-latest
+
+steps:
+  - uses: actions/checkout@v4
+  - name: Clone vcpkg
+    run: git clone https://github.com/microsoft/vcpkg
+  - name: Bootstrap vcpkg (Windows)
+    if: runner.os == 'Windows'
+    shell: pwsh
+    run: .\vcpkg\bootstrap-vcpkg.bat
+  - name: Bootstrap vcpkg (Linux/macOS)
+    if: runner.os != 'Windows'
+    run: ./vcpkg/bootstrap-vcpkg.sh
+  - name: Install dependencies (Windows)
+    if: runner.os == 'Windows'
+    shell: pwsh
+    run: .\vcpkg\vcpkg.exe install --triplet ${{ matrix.triplet }}
+  - name: Install dependencies (Linux/macOS)
+    if: runner.os != 'Windows'
+    run: ./vcpkg/vcpkg install --triplet ${{ matrix.triplet }}
+```
@@ -0,0 +1,140 @@
+# vcpkg: Custom Registries & Overlay Ports
+
+Reference for the `vcpkg` skill. Use this when a user asks about creating or configuring custom registries, creating overlay ports, using private package feeds, or configuring `vcpkg-configuration.json` registries.
+
+## Private / Custom Registry Install
+
+1. Create `vcpkg-configuration.json` alongside your `vcpkg.json`:
+```json
+{
+  "registries": [
+    {
+      "kind": "git",
+      "repository": "https://github.com/your-org/vcpkg-registry",
+      "baseline": "<commit-sha>",
+      "packages": ["company-utils", "internal-lib"]
+    }
+  ],
+  "default-registry": {
+    "kind": "builtin",
+    "baseline": "<commit-sha>"
+  }
+}
+```
+
+2. Then add the dependency normally in `vcpkg.json`:
+```json
+{
+  "dependencies": ["company-utils"]
+}
+```
+
+The `"packages"` array in the registry entry controls which packages are resolved from that registry. Packages not listed fall through to `default-registry`.
+
+---
+
+## Configuring Registries in `vcpkg-configuration.json`
+
+```json
+{
+  "default-registry": {
+    "kind": "builtin",
+    "baseline": "<vcpkg-commit-sha>"
+  },
+  "registries": [
+    {
+      "kind": "git",
+      "repository": "https://github.com/your-org/vcpkg-registry.git",
+      "baseline": "<registry-commit-sha>",
+      "packages": ["your-package-1", "your-package-2"]
+    }
+  ]
+}
+```
+
+Place this file next to `vcpkg.json` in your project root.
+
+---
+
+## Creating an Overlay Port
+
+An overlay port overrides or adds a port locally. Directory structure:
+```
+my-overlays/
+  telemetry-sdk/
+    portfile.cmake
+    vcpkg.json
+```
+
+**`vcpkg.json`** (port metadata):
+```json
+{
+  "name": "telemetry-sdk",
+  "version": "1.0.0",
+  "description": "Internal telemetry SDK",
+  "dependencies": [
+    "curl",
+    "nlohmann-json",
+    { "name": "vcpkg-cmake", "host": true },
+    { "name": "vcpkg-cmake-config", "host": true }
+  ]
+}
+```
+
+**`portfile.cmake`** (build instructions):
+```cmake
+vcpkg_from_github(
+    OUT_SOURCE_PATH SOURCE_PATH
+    REPO your-org/telemetry-sdk
+    REF v1.0.0
+    SHA512 <hash>
+)
+
+vcpkg_cmake_configure(SOURCE_PATH "${SOURCE_PATH}")
+vcpkg_cmake_install()
+vcpkg_cmake_config_fixup()
+
+file(REMOVE_RECURSE "${CURRENT_PACKAGES_DIR}/debug/include")
+vcpkg_install_copyright(FILE_LIST "${SOURCE_PATH}/LICENSE")
+```
+
+Classic mode: `vcpkg install telemetry-sdk --overlay-ports=./my-overlays`
+
+Manifest mode: add `telemetry-sdk` to `vcpkg.json`, then run `vcpkg install --overlay-ports=./my-overlays`.
+Or in `vcpkg-configuration.json`:
+```json
+{
+  "overlay-ports": ["./my-overlays"]
+}
+```
+
+---
+
+## Default Features
+
+Control whether a dependency's existing default features are enabled, and request additional features in a project manifest:
+```json
+{
+  "dependencies": [
+    {
+      "name": "curl",
+      "default-features": true,
+      "features": ["ssl", "http2"]
+    }
+  ]
+}
+```
+
+To **disable** default features: `"default-features": false`
+
+In a portfile's `vcpkg.json`, default features are listed under:
+```json
+{
+  "name": "curl",
+  "default-features": ["ssl", "http2"],
+  "features": {
+    "ssl": { "description": "SSL/TLS support" },
+    "http2": { "description": "HTTP/2 support" }
+  }
+}
+```
@@ -0,0 +1,101 @@
+# vcpkg: Troubleshooting & Dependency Lifecycle
+
+Reference for the `vcpkg` skill. Use this when a user encounters vcpkg build failures, package-not-found errors, needs to read build logs, or manages the dependency lifecycle (removing, changing features, replacing libraries, cleaning the cache).
+
+## Reading vcpkg Build Logs
+
+Build logs are stored at:
+```
+<vcpkg-root>/buildtrees/<port-name>/
+```
+
+Key log files:
+- `config-<triplet>-out.log` — CMake configure output
+- `build-<triplet>-<dbg|rel>-<out|err>.log` — common build logs
+- `install-<triplet>-<dbg|rel>-<out|err>.log` — common install logs
+
+Exact names vary by port and build helper; use the path vcpkg prints for the failing command.
+
+When a build fails, vcpkg prints the path to the relevant log. Start with the `-err.log` file for the failing step.
+
+---
+
+## Resolving package-not-found After Install
+
+If CMake says `Could not find a package configuration file provided by "X"`:
+
+1. **Check toolchain file** — ensure `-DCMAKE_TOOLCHAIN_FILE=<vcpkg-root>/scripts/buildsystems/vcpkg.cmake` is set
+2. **Check triplet match** — the installed triplet must match your build architecture
+3. **Check package name** — vcpkg port names may differ from CMake package names (e.g., port `nlohmann-json` → `find_package(nlohmann_json)`)
+4. **Check installed list** — run `vcpkg list` to confirm the package is actually installed
+5. **Clear CMake cache** — delete `CMakeCache.txt` and reconfigure
+
+---
+
+## Dependency Lifecycle
+
+### Removing a Library
+
+1. Remove it from `vcpkg.json` → `"dependencies"` array
+2. Run `vcpkg install` to reconcile (manifest mode auto-removes unused packages)
+
+In classic mode:
+```console
+vcpkg remove boost-regex
+vcpkg remove boost-regex --recurse  # also removes dependents
+```
+
+### Changing Features on an Installed Library
+
+Update the features in `vcpkg.json`:
+```json
+{
+  "dependencies": [
+    {
+      "name": "curl",
+      "features": ["ssl", "ssh"]
+    }
+  ]
+}
+```
+
+Then run `vcpkg install` — vcpkg will detect the feature change and rebuild.
+
+In classic mode, installing a feature only adds to the already installed feature set; omitted features are not removed. To remove a feature, uninstall `curl` and then reinstall it with the desired features. Account for dependent packages before using `--recurse`, because it removes them too.
+
+### Replacing One Library with Another
+
+1. Remove the old library from `vcpkg.json`
+2. Add the new library to `vcpkg.json`
+3. Run `vcpkg install` to reconcile
+4. Update your source code: change `#include` directives, `find_package()` calls, and `target_link_libraries()` in CMakeLists.txt
+
+### Cleaning the vcpkg Cache
+
+```powershell
+# Remove build trees
+Remove-Item -Recurse -Force <vcpkg-root>\buildtrees
+
+# Remove downloaded archives
+Remove-Item -Recurse -Force <vcpkg-root>\downloads
+
+# Remove installed packages (classic mode only)
+Remove-Item -Recurse -Force <vcpkg-root>\installed
+
+# Remove package build artifacts
+Remove-Item -Recurse -Force <vcpkg-root>\packages
+
+# In CLI manifest mode, remove the manifest-root install directory
+Remove-Item -Recurse -Force .\vcpkg_installed
+
+# With CMake integration, remove <build-directory>\vcpkg_installed (or VCPKG_INSTALLED_DIR)
+```
+
+```bash
+rm -rf <vcpkg-root>/buildtrees
+rm -rf <vcpkg-root>/downloads
+rm -rf <vcpkg-root>/installed
+rm -rf <vcpkg-root>/packages
+# CLI manifest mode; with CMake integration, use <build-directory>/vcpkg_installed (or VCPKG_INSTALLED_DIR)
+rm -rf ./vcpkg_installed
+```
@@ -0,0 +1,133 @@
+---
+name: workshop-create
+description: 'Create a new workshop or use an existing directory as one. Handles two paths: (A) use an existing local directory the operator points at, or (B) create a new private GitHub repo in the signed-in account. Never creates a repo inside another repo.'
+---
+
+# Create a Workshop
+
+Set up a new workshop — the root directory where desks live.
+
+## When to use
+
+- The operator says "create a workshop" or "start a new workshop"
+- The operator wants to organize work under a shared root
+- The operator has an existing directory they want to use as a workshop
+
+## Two paths
+
+### Path A: Use an existing directory
+
+The operator already has a folder they want to use. Maybe it's a repo
+they cloned, maybe it's a local project folder.
+
+1. **Confirm the path exists.** If not, ask the operator for a valid path.
+2. **Detect existing workshop markers.** Look for `desks/` or `classroom/`
+   folders, a `workshop.md`, `CAIRN.md`, or `hands-up.md`. Finding any of
+   these tells you this is an existing workshop — but this is detection
+   only, not a stopping point. Continue to the next step and add whatever
+   is missing; never overwrite what is already there.
+3. **Scaffold the workshop structure** (only what's missing):
+   ```
+   <path>/
+     desks/           # where desks live
+     bench/            # shared workspace
+     CAIRN.md          # operating disposition
+     README.md         # workshop map
+   ```
+4. **Do NOT run `git init`.** The directory may already be a git repo, or
+   the operator may not want one yet. Leave git state alone.
+5. **Do NOT create a GitHub repo.** This path is local-only.
+
+### Path B: Create a new private GitHub repo
+
+The operator wants a fresh workshop backed by a GitHub repo.
+
+1. **Get the workshop name.** Short, no spaces, kebab-case preferred.
+2. **Pick and validate a clone parent.** `gh repo create --clone` clones
+   into the **current working directory**, so choose an explicit parent
+   directory first (ask the operator, or use their configured workshops
+   directory) and confirm it is **not** already inside a git repo:
+   ```bash
+   git -C <parent-dir> rev-parse --is-inside-work-tree
+   ```
+   If that prints `true`, pick a different parent — otherwise the new
+   repo nests inside the existing one. Create the parent if needed.
+3. **Create and clone the repo from that parent:**
+   ```bash
+   cd <parent-dir>
+   gh repo create <owner>/<name> --private --clone
+   ```
+   Use the operator's signed-in GitHub account as `<owner>`.
+4. **Scaffold the workshop structure** inside the cloned repo. Git does
+   not track empty directories, so add a placeholder in each otherwise
+   empty folder or the scaffold will not survive the next clone:
+   ```
+   <name>/
+     desks/.gitkeep
+     bench/.gitkeep
+     CAIRN.md
+     README.md
+   ```
+5. **Commit and push** the scaffold, including the `.gitkeep` placeholders.
+
+### Critical: Never nest repos
+
+**Never run `git init` inside a directory that is already inside a git
+repository.** Before initializing, check:
+
+```bash
+git -C <parent-dir> rev-parse --is-inside-work-tree
+```
+
+If that returns `true`, the parent is already a git repo. Do NOT create
+another repo inside it. Either:
+- Use Path A (just scaffold, no git)
+- Or clone to a different location that isn't inside a repo
+
+## CAIRN.md content
+
+The operating disposition every desk reads:
+
+```markdown
+# cairn
+
+the trail markers that say: someone was here, and they were honest.
+
+## how a desk stands
+
+- **stop is a valid finish.** don't force a result when the evidence
+  says stop. "this doesn't work" is a finding, not a failure.
+- **"done" means it holds.** if you'd bet your desk on it, ship it.
+  if not, say what's uncertain and why.
+- **hold scope.** touch only what the task needs. if you find something
+  outside scope, note it and move on — don't chase it.
+- **never go silent, never bluff.** partial + honest > complete + wrong.
+  if you're stuck, say so. if you're unsure, say that too.
+- **equal standing.** you can say "that's the wrong question." you can
+  disagree with another desk. you answer to evidence, not hierarchy.
+
+## the bench
+
+the shared workspace. leave your work where others can find it.
+label it. if it supersedes earlier work, say so.
+
+## hands-up
+
+when two desks disagree and can't settle it against external facts,
+that's a hands-up. it goes to the operator. this is the system
+working, not failing.
+```
+
+## After creation
+
+Tell the operator:
+- Where the workshop lives (full path)
+- That they can now open desks in it with `desk-open`
+- That Cairn will show signals once desks start emitting them
+
+## Principles
+
+- A workshop is a place, not a product. Keep it simple.
+- The operator decides where things go. Don't assume.
+- If an existing directory already has work in it, preserve everything.
+  Only add what's missing.
@@ -496,6 +496,7 @@ import PageHeader from '../components/PageHeader.astro';
      <td align="center" valign="top" width="14.28%"><a href="https://github.com/lovyjain"><img src="https://avatars.githubusercontent.com/u/54174168?v=4" width="100px;" alt=""/><br /><sub><b>Lovy Jain</b></sub></a></td>
      <td align="center" valign="top" width="14.28%"><a href="https://github.com/kimtth"><img src="https://avatars.githubusercontent.com/u/13846660?v=4" width="100px;" alt=""/><br /><sub><b>kimtth</b></sub></a></td>
      <td align="center" valign="top" width="14.28%"><a href="https://github.com/AkashAi7"><img src="https://avatars.githubusercontent.com/u/46550108?v=4" width="100px;" alt=""/><br /><sub><b>Akash Dwivedi</b></sub></a></td>
+      <td align="center" valign="top" width="14.28%"><a href="https://surenk.com"><img src="https://avatars.githubusercontent.com/u/902972?v=4" width="100px;" alt=""/><br /><sub><b>Suren K</b></sub></a></td>
    </tr>
  </tbody>
  <tfoot>