canva-connect

This skill wraps the canva connect interface to list and search designs, create blank documents, export finished designs as image or pdf, manage folders, move items between them, upload images as assets, and autofill brand templates with data. What makes it trustworthy is that the documentation states its boundaries plainly. It cannot add text, shapes, or elements to a design, cannot edit existing design content, cannot upload documents since only images are accepted, and does not do generative design work. The setup cost is registered client credentials, and the scopes requested must match the operations used. Treat it as an asset and export pipeline, not a design editor.

Use case: automating asset upload and export around a design workflow

This skill talks to a design platform's connect interface so that designs, assets and folders can be listed, organised and exported without a browser. It is unusually explicit about its edges: it moves files and metadata around, and it never touches the contents of a design. ## What it does - Lists and searches designs and folders. - Exports finished designs as image or document formats. - Uploads images into the asset library. - Creates blank designs and fills brand templates with data. - Moves items between folders to keep the workspace tidy. ## When it is the wrong choice It cannot add content to a design, edit existing design content, upload documents, or generate anything with a model. That rules it out as a design tool and limits it to the pipeline around design: exporting, uploading, organising and template filling. It also depends on a pair of credentials from the platform plus the interactive authorization step that produces the stored access, so a headless first run needs a person to complete that once. The template filling path additionally assumes the template already exists and has the right fields set up, since building one is outside the scope entirely. And the operations worth automating all assume the account already holds the designs being worked on, so this is a step that follows design rather than replacing it. ```bash {baseDir}/scripts/canva.sh auth ``` ## Working notes - The authorization step opens a browser once and stores the resulting access. - Credentials come from a client id and a client secret held in the environment. - Folders are the organising layer that supported operations act on.