canvas-authoring — GitHub Copilot plugin
Gives the host's native create-canvas skill Microsoft Canvas Toolkit setup plus a counter or read-only Azure starter. Installing it does not open a canvas by itself.
copilot plugin install canvas-authoring@awesome-copilotWhat canvas-authoring does
This is a skill-only companion to the native create-canvas skill in a canvas-capable Copilot host. It ships setup guidance for Microsoft Canvas Toolkit and two starters: a counter and a read-only Azure resource-group viewer. Its own skill is called create-canvas-app. If the host lacks create-canvas, the plugin will not supply it.
You need Node.js 22+ and a usable toolkit package, plus a Copilot host that can run canvases. The Azure starter also wants Azure CLI 2.61+ and read permission on the subscription. Setup takes either one exact npm version or a local .tgz; it installs no dependencies and never contacts Azure. Point it at an output folder that already exists and it refuses instead of overwriting.
Install the finished output from dist/ following the generated README and reload the provider. A plain browser refresh will not pick up rebuilt provider code; a build-ID warning means something is out of sync. The Azure app sits idle until you load the CLI profile, pick a subscription and hit the resource-group listing. It never signs in or writes anything in Azure on its own. The plugin counts calls to create-canvas-app — skill name, invocation kind, plugin version, timestamp — and keeps them up to 30 days; prompts, project files and source are not sent.
What it helps with
- scaffold a canvas app with a working counter starter
- build a read-only viewer for Azure resource groups
- wire Microsoft Canvas Toolkit into the native
create-canvasskill - smoke-test the generated app with
npm run smoke - pick an Azure subscription by hand and list its resources
Example prompts for the agent
- Use the native
create-canvasskill and thecreate-canvas-appcompanion's counter starter to build a canvas. - Build a read-only Azure canvas that lists resource groups, using the native
create-canvasskill and the Azure starter. - Run the build and
npm run smokein the generated app before installingdist/.
How to install canvas-authoring
Command from the source
copilot plugin install canvas-authoring@awesome-copilotStep by step, with commands for each platform: Claude Code plugins: marketplaces, installing, and building your own
Questions about canvas-authoring
How do I install canvas-authoring in GitHub Copilot?
Add the marketplace, then install the plugin: copilot plugin marketplace add github/awesome-copilot and copilot plugin install canvas-authoring@awesome-copilot. For an approved local export, run copilot --plugin-dir "<export-directory>/plugins/canvas-authoring".
What does canvas-authoring do?
It hands the native create-canvas skill Canvas Toolkit setup and starters: a counter plus a read-only Azure resource-group viewer. There is also guidance on styles, sign-in and subscriptions.
What does the Azure starter need to work?
Azure CLI 2.61+ and permission to read the subscription. The app does not sign in for you: you load the CLI profile and choose the subscription yourself.
Source text
canvas-authoring · MIT
# Canvas authoring plugin Create a canvas app with the Microsoft Canvas Toolkit. This **skill-only companion** gives the host's native `create-canvas` workflow toolkit setup and a counter or read-only Azure resource-group starter; installing it does not open a canvas. ## Install If your GitHub Copilot host shows the **awesome-copilot** marketplace, open **Customize → Plugins** and install **canvas-authoring**. Its [listed 0.1.1 package](https://github.com/microsoft/azure-dev-tools/tree/a6d394bbaa6fb1dc0151257a85cbac0de772b138/plugins/canvas-authoring) is a skill-only companion, not a canvas extension. If the marketplace is missing, add it first: ```sh copilot plugin marketplace add github/awesome-copilot copilot plugin install canvas-authoring@awesome-copilot ``` For an approved local export, run: ```sh copilot --plugin-dir "<export-directory>/plugins/canvas-authoring" ``` Install the exported plugin, not this source folder. You need a canvas-capable Copilot host with the native `create-canvas` skill, Node.js 22+, and an available toolkit package; the Azure starter also needs Azure CLI and subscription read access. See [requirements](#requirements). ## Try it Ask your agent to **Build a read-only Azure canvas that lists resource groups. Use the native create-canvas skill and the create-canvas-app companion's Azure starter.** Choose a compatible toolkit package and project location when prompted. For a non-Azure example, ask for the counter starter. ## What you can do - Generate a native canvas scaffold with a working counter starter. - Start a read-only Azure resource-group viewer with explicit subscription choice. - Build and smoke-test the generated app before installing its complete output. ## Prompts to try > Use the native create-canvas skill and the create-canvas-app companion to build a counter canvas. > Build a read-only Azure canvas that lists resource groups. Use the native create-canvas skill and the create-canvas-app companion's Azure starter. ## Requirements - A canvas-capable GitHub Copilot host with its installed `create-canvas` skill. The plugin does not replace or install that host skill. - Node.js 22+ (24 recommended) and npm. - The exact `@microsoft/[email protected]` release exporting `@microsoft/canvas-toolkit/build`, once published, or an approved local `.tgz` containing that API. Do not treat a missing `/build` export as success. - For live Azure reads: Azure CLI 2.61+ and permission to read the subscription. ## Usage data The plugin counts how often its `create-canvas-app` skill is invoked. Each count records the skill name, how it was invoked, the plugin name and version, and a timestamp. Usage telemetry may include a pseudonymous account identifier to understand usage over time; it is retained for up to 30 days. The plugin does not send prompts, project files or source code. ## Create an app The agent creates the native scaffold, generates the source app, and connects the copied host entry. You choose the project location and toolkit package. Setup accepts one exact npm version or one local tarball. It does not install dependencies or contact Azure, and it refuses existing output directories rather than overwriting files. For command-line setup, see the [skill instructions](skills/create-canvas-app/SKILL.md). ## Build and run In the generated app: ```sh npm install npm run build npm test npm run smoke ``` `smoke` is available in the Azure starter. It uses installed Chrome, or the executable specified by `CANVAS_BROWSER`, with labelled synthetic data. Keep `package-lock.json` and use `npm ci` for later installs. Follow the generated README and host skill to install the complete `dist/` directory and reload the provider. A browser refresh does not load rebuilt provider code; a build-ID warning indicates a mismatch. The Azure app does nothing until you act: load the CLI profile, select a subscription, then choose **List resource groups**. It never signs in, chooses a subscription, or writes Azure resources automatically. Browser checks do not replace trying the app in the native host with your Azure account. ## Customize Start with the generated README's source map and the [Azure quickstart](skills/create-canvas-app/references/toolkit/quickstart.md). Keep the shared UI/agent actions, explicit scope and cancellation when changing the reader or display. The [integration reference](skills/create-canvas-app/references/toolkit.md) covers the host adapter and build settings. Toolkit guides are included in the plugin and generated from the toolkit sources. Their [provenance](skills/create-canvas-app/references/toolkit/provenance.json) records versions and checksums; it does not establish npm availability.
© Alex Weininger · MIT · microsoft/azure-dev-tools
