Canva

**Judgement:** This skill is a solid, practical integration for automating Canva workflows from OpenClaw. It exposes the most important Canva Connect operations for social and marketing use (templates → autofill → export), with clear documentation and example flows. **What it’s good for:** - Turning text or structured data into ready-to-post Canva designs (e.g., Instagram posts, carousels). - Exporting designs in bulk in common formats (PNG, JPG, PDF, MP4, GIF) with control over dimensions/quality. - Managing a basic content pipeline that uploads assets to Canva, fills brand templates, and exports outputs. **Main strengths / advantages:** - Uses Canva’s official OAuth 2.0 Connect API and handles token refresh, which simplifies long‑running usage. - Concrete examples for each core operation (list, get, create via autofills, export, upload, list templates) make it straightforward to integrate. - Explicit guidance on rate limits, scopes, and common error handling improves robustness if followed. **Key risks / limitations:** - **External dependency & setup:** Requires a Canva developer integration, client ID/secret configuration, and a first‑time OAuth flow. This is non‑trivial and may be a barrier for non-technical users. - **Reliance on Canva API stability:** Changes to Canva’s REST v1 endpoints, auth flows, or scopes could break the skill without updates. - **Rate limiting and async exports:** Export and upload are rate‑limited and asynchronous; users must implement polling and be cautious about batch volumes. - **Account access & scopes:** The skill needs broad Canva scopes (design and asset read/write, brand templates). Misconfigured or over‑permissive scopes could expose more of a user’s Canva account than necessary. **Recommended scenarios (where this skill is a good fit):** - Teams that already use Canva heavily and want to automate repetitive social content creation or bulk exports. - Content/marketing pipelines that generate text or design parameters in OpenClaw and then rely on Canva for actual visual rendering. - Agencies or creators who maintain standardized brand templates and need high‑volume, programmatic variation (e.g., per-product or per-client posts). **Less ideal scenarios:** - Environments where setting up OAuth credentials and managing secrets is difficult or not allowed. - Use cases needing very fine-grained control over every Canva feature; this skill surfaces core operations but not the full design-editing surface. - Workloads that exceed Canva’s rate limits or require hard real-time guarantees, since exports/uploads are async and capped by the API.