Create or improve an organization-managed Canvas plugin that combines complete new or existing skills with optional custom MCP and Composio integrations. Use for reusable multi-skill workflows, plugin composition, plugin editing, and plugin graphics.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Turn the requested workflow into an organization-managed Canvas package. A plugin contains at least one complete skill, its purpose graphic, and any required connection declarations. A single independent skill can use Skill Creator instead. Existing separate skills and connections remain usable independently.
Use the conversation to determine purpose, inputs, output, new versus existing skills, required integrations, and intended users. Ask only for information that changes the result and cannot be inferred. A request to plan stays a plan; a request to create and make the plugin usable authorizes the necessary internal creation steps. Keep the target organization and intended access visible in the preview. Public marketplace submission and server hosting are separate workflows.
Use the existing canvas_extensions gateway: search for the needed operation, describe its exact schema, then call with that schema. A directly registered operation can be used directly. Tool names in this skill describe routes to discover, not permission or schema definitions. Missing operations or creation rights require an honest limitation; legacy personal installers are not an alternative organization-creation path.
create_canvas_package_draft with operation: "create", kind: "plugin", a stable lowercase name, and a fresh UUID requestId. Organization and actor come from the server; send no ownership, user ID, or server path.draftRef; otherwise list_canvas_package_drafts. Inspect its current files, revision and operation status before continuing. Link the returned draft in the chat so another chat can resume it.inspect_canvas_package, then create an edit draft using its current metadata, grants and package-head revisions. An existing read-only package may permit a differently named fork; keep its explicit source/target contract. Do not replace core content or mutate a published revision.inspect_canvas_package_operation using the original request ID or draft reference. For uncertain file/composition writes, inspect the current draft and affected files first. Never blindly create another draft, repeat publication, or overwrite a newer revision.Use the common package file tools with relative paths, base64 content and the latest expectedDraftRevision. Preserve files not involved in the request. Draft files are private authoring content; do not execute them through workspace or runtime bypasses.
Load package-and-connections.md when writing the manifest or connection requirements. Start with a useful narrow skill; Skill Creator can author a new child directly in this draft when given its exact draft reference and child root. No preliminary standalone installation is needed.
For existing skills and integration requirements, call search_canvas_extensions with purpose: "authoring", a useful query and optional type filters. This is the same catalog as the Plugins page, using metadata only. A normal runtime search returns only the agent's current installed runtime selection and is not the complete authoring catalog. Account authorization, live reachability and tool schemas are not tested by this search.
Use inspect_canvas_package_authoring_source for the exact readable resource and chosen version. Select the returned verified source entries for compose_canvas_package_skills with the current draft revision. For a historical plugin child, select the parent resource, its exact revisionRef, parent checksum and declared childRelativeRoot. A direct child selection also requires the inspected parent checksum. The batch service copies complete content, resolves parent resources and hoists standalone MCP declarations. Review its reported reference/version changes and preserve license and author attribution. Resolve a conflict explicitly; do not silently rename, overwrite or copy a same-name skill from elsewhere. A Store offering must first use its explicit existing installation workflow before it is a readable copy source.
For one Composio or MCP requirement, use add_canvas_package_requirement with the current draft revision and selected catalog identity. Composio contributes the exact toolkit slug. An MCP needs an explicit portable connectorName for this package. The private selected connection, definition, profile or account is not saved in the manifest. Add the corresponding portable Workflow V1 capability if the skill needs it; the manifest and workflow must agree. Rich existing declarations are preserved; edit a conflicting declaration explicitly rather than replacing it silently.
Legacy managed workspace drafts can be inspected with inspect_canvas_package_workspace_draft and explicitly imported into an empty common draft with import_canvas_package_workspace_draft. Use the returned identity and checksum. Leave the original workspace draft intact.
Load the complete plugin-visual member of the system Plugin Creator through the exact authorized skill path supplied by plugin context or metadata discovery. With a legacy direct create-plugin reference, use its supplied visual dependency/read recipe. Do not guess an absolute filesystem path or install another illustration package.
Create an original small purpose illustration at assets/logo.svg; point interface.logo to ./assets/logo.svg. Follow that child skill's passive SVG, accessibility and preview rules. The image should explain this plugin's job, rather than repeat the generic Creator icon. Referenced external provider logos remain provider branding, not the generated purpose image.
validate_canvas_package_draft for the current revision. Repair the returned file/field errors and validate again. Do not call a structural check a successful provider or workflow test. A changed draft needs fresh validation; final publication validates again.publish_canvas_package_draft using the current draft, metadata, grants and head revisions and a stable UUID request ID. Do not route through install_canvas_plugin_from_workspace or a public marketplace upload.resourceRef, publishedRevisionRef and checksum as its exact pin. Call inspect_canvas_package_provisioning for that pin. Use provision_canvas_package with fresh expected revisions for separate explicitly requested set_use_audience and activate steps. The audience is either explicitly selected users or all organization members (which can include external members); do not infer it from organization ownership. Empty users grants no Use. This flow changes only Use and preserves existing Edit/Manage rights. canManage and canEdit do not imply canUse. An optional organization policy additionally needs the user's own opt-in: when the request includes using the package, use enable_for_me with the inspected personal activation revision for the current actor only. Do not change other members' preferences or the organization's policy. If a later step fails or its reply is lost, inspect provisioning and resume only that step on the saved version; never publish a duplicate or silently switch to a newer head.Finish with the draft or saved version link, precise version, included workflows, intended access, graphic and remaining connection/test state. After publication, further editing starts a new edit draft; prior pins and published files stay unchanged. A model that cannot visually inspect the result should say so rather than inventing a visual acceptance result.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.
The English summary is being prepared. Showing the original description.
Use this Canvas-owned clean-room skill to guide collaborative writing for documentation, proposals, technical specs, decision records, PRDs, RFCs, operating guides, and structured memos. Trigger when the user wants help drafting, organizing, refining, reviewing, or testing a document before sharing it.
The English summary is being prepared. Showing the original description.
Use this Canvas-owned clean-room skill for creating, reading, editing, reviewing, redlining, commenting, or repairing Word `.docx` documents. Trigger for Word documents, DOCX files, memos, reports, letters, templates, tracked changes, comments, table of contents, headers, footers, page numbers, and Google Docs-targeted documents that should be authored as DOCX first.
The English summary is being prepared. Showing the original description.
Create and edit editable Excalidraw diagrams in Canvas Notebook through the Scene-Service tools. Use for diagrams, flows, sketches, architecture maps, visual explanations, or requested .excalidraw documents.
The English summary is being prepared. Showing the original description.