菜单
Create, update, validate, and package Canvas Plugins. Use when users want to build a Canvas plugin, bundle multiple skills into a plugin, define plugin metadata, add icons or logos, declare recommended Composio, Canvas Email, or MCP connectors, prepare a marketplace entry, or submit a plugin to the Canvas Plugin Store.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until it reaches the repository's configured Greptile merge threshold with zero unresolved actionable comments, or until the five-review maximum is reached. Triggers Greptile review, fixes all actionable comments, pushes/re-shelves, re-triggers review only for new head SHAs unless a 5/5 score is already published, and repeats. Use when the user wants to optimize a PR/MR/CL against Greptile's code review standards without creating runaway review loops.
Publish a new Canvas Notebook release. Use this skill whenever the user asks to bump a version, prepare release notes, update CHANGELOG.md, create or push a git tag, publish a GitHub Release, deploy, or automate the release workflow. This skill covers the full release sequence for this repository: inspect commits/tags, push completed product-code commits first when authorized, confirm the pushed code has built on GitHub, choose the next calendar version, update package and CLI versions, update the changelog, run the required local build, commit, push the release commit, wait for the remote Build and Push worker on the pushed branch, tag, push the tag, and publish the release.
Fetch dependency source code to give AI agents deeper implementation context. Use when the agent needs to understand how a library works internally, read source code for a package, fetch implementation details for a dependency, or explore how an npm/PyPI/crates.io package is built. Triggers include "fetch source for", "read the source of", "how does X work internally", "get the implementation of", "opensrc path", or any task requiring access to dependency source code beyond types and docs.
Create, edit, review, preview, and export polished Marp Markdown slide decks in Canvas Notebook. Use when the user wants Markdown-native presentations, `.marp.md` or `.slides.md` files, version-controlled decks, Marp PDF/image/PPTX/HTML export, speaker notes, dashboard-style slides, data cards, or better looking decks that should remain close to plain text.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Canvas brand colors, typography, and visual polish to artifacts that benefit from a consistent product look-and-feel. Use it when brand colors, style guidelines, visual formatting, or company design standards apply.
| name | create-plugin |
| description | Create, update, validate, and package Canvas Plugins. Use when users want to build a Canvas plugin, bundle multiple skills into a plugin, define plugin metadata, add icons or logos, declare recommended Composio, Canvas Email, or MCP connectors, prepare a marketplace entry, or submit a plugin to the Canvas Plugin Store. |
| compatibility | Requires filesystem access to the Canvas repository or plugin marketplace repository |
| metadata | {"version":"1.0.0","author":"canvas-studios"} |
Use this skill to create production-ready Canvas Plugins.
A Canvas Plugin is a bundle that combines:
.canvas-plugin/plugin.jsonskills/assets/icon.svg and assets/logo.svgPlugins should teach the agent which workflows belong together. They should not secretly install external services, write connector configuration, or store secrets.
Clarify the plugin's audience, workflows, bundled skills, and connector recommendations.
Choose a stable plugin name in lowercase kebab-case.
Scaffold the plugin package:
plugins/<plugin-name>/<version>/
├── .canvas-plugin/plugin.json
├── assets/
│ ├── icon.svg
│ └── logo.svg
├── connectors/
│ └── optional-example.mcp.json
├── skills/
│ └── <skill-name>/
│ ├── SKILL.md
│ └── agents/canvas.yaml
└── LICENSE
Validate that every bundled skill has a unique name and a useful trigger-focused description.
Add connector recommendations only as metadata. The user must explicitly connect Composio apps, Canvas Email accounts, or MCP servers in the UI.
For a personal Canvas installation, call install_canvas_plugin_from_workspace with the package directory. To update an installed plugin, first call inspect_canvas_plugin, then call update_canvas_plugin_from_workspace with its version and checksum.
Use set_canvas_plugin_enabled to toggle it and remove_canvas_plugin to remove it. Removal deliberately stops when a materialized skill was edited, so the agent must preserve or resolve that user work explicitly.
Package or commit the plugin to the marketplace repository only after validation passes.
Use this shape for .canvas-plugin/plugin.json:
{
"name": "sales-operations",
"version": "1.0.0",
"description": "Coordinate sales workflows with CRM, email, and research connector recommendations.",
"license": "MIT",
"author": {
"name": "Canvas Studios"
},
"source": "https://github.com/canvascoding/canvas-notebook-plugin-marketplace/tree/main/plugins/sales-operations/1.0.0",
"skills": "./skills",
"interface": {
"displayName": "Sales Operations",
"shortDescription": "Prepare account research and sales follow-ups",
"category": "Sales",
"brandColor": "#0F766E",
"icon": "./assets/icon.svg",
"logo": "./assets/logo.svg",
"defaultPrompt": [
"Use /sales-account-brief to prepare a target-account brief."
]
},
"connectors": {
"composio": [
{
"toolkit": "hubspot",
"label": "HubSpot",
"recommended": true,
"reason": "Use CRM records and company data during sales workflows."
}
],
"email": [
{
"kind": "mailbox",
"label": "Sales inbox",
"providers": ["gmail", "imap-smtp"],
"recommended": true,
"reason": "Read and send sales email through Canvas Email, not through Composio Gmail."
}
],
"mcp": [
{
"name": "sales-research",
"label": "Sales Research MCP",
"configPath": "./connectors/sales-research.mcp.json",
"recommended": true,
"env": ["SALES_RESEARCH_API_KEY"],
"oauth": true,
"reason": "Optional external research tools for account enrichment."
}
]
}
}
Composio recommendations:
hubspot, slack, or linear.label, reason, and recommended or required.Canvas Email recommendations:
connectors.email[] for mailbox needs.gmail and imap-smtp.MCP recommendations:
connectors.mcp[] for optional MCP servers.connectors/*.mcp.json.env.oauth: true when OAuth may be required.Each bundled skill should be narrow enough to be useful independently and clear enough to trigger correctly.
Use this skill layout:
skills/<skill-name>/SKILL.md
skills/<skill-name>/agents/canvas.yaml
SKILL.md frontmatter should include:
---
name: sales-account-brief
description: "Use this skill to prepare a target-account sales brief from CRM context, email context, and research notes."
license: "MIT"
metadata:
version: "1.0.0"
---
agents/canvas.yaml should include UI metadata:
interface:
display_name: Sales Account Brief
short_description: Prepare a target-account sales brief
brand_color: "#0F766E"
icon_small: "./icon.svg"
When preparing an official marketplace entry, add the plugin to registry.json in the marketplace repo.
Required fields:
namedisplayNamedescriptionlatestVersionversions[version].downloadUrlversions[version].packagePathversions[version].checksumversions[version].manifestPathThe checksum should be the Canvas Plugin package checksum, not a checksum of the whole git repository.
Before handing off:
.canvas-plugin/plugin.json exists and is valid JSON.name is lowercase kebab-case.version is semantic, for example 1.0.0.skills points to a package-local directory.connectors.mcp[].configPath points to an existing file.