Agent skill

Dotcanvas

Author and edit a Grida .canvas board — a .canvas.json manifest plus document files (references, generated images, notes) placed on an infinite canvas.

Apache-2.0Auto-check passedDocuments & Office

Install Dotcanvas

skills CLI

$ npx skills add gridaco/grida --skill dotcanvas -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install gridaco/grida dotcanvas --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/gridaco/grida.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/dotcanvas .claude/skills/dotcanvas && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "dotcanvas" agent skill from https://github.com/gridaco/grida/tree/main/skills/dotcanvas into .claude/skills/dotcanvas/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dotcanvas", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/gridaco/grida/tree/main/skills/dotcanvas

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add gridaco/grida --skill dotcanvas -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install gridaco/grida dotcanvas --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/gridaco/grida.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/dotcanvas .agents/skills/dotcanvas && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "dotcanvas" agent skill from https://github.com/gridaco/grida/tree/main/skills/dotcanvas into .agents/skills/dotcanvas/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dotcanvas", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add gridaco/grida --skill dotcanvas -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install gridaco/grida dotcanvas --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/gridaco/grida.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/dotcanvas .cursor/skills/dotcanvas && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "dotcanvas" agent skill from https://github.com/gridaco/grida/tree/main/skills/dotcanvas into .cursor/skills/dotcanvas/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dotcanvas", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/gridaco/grida.git --path skills/dotcanvas

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add gridaco/grida --skill dotcanvas -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install gridaco/grida dotcanvas --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/gridaco/grida.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/dotcanvas .gemini/skills/dotcanvas && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "dotcanvas" agent skill from https://github.com/gridaco/grida/tree/main/skills/dotcanvas into .gemini/skills/dotcanvas/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dotcanvas", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install gridaco/grida dotcanvas

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add gridaco/grida --skill dotcanvas -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/gridaco/grida.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/dotcanvas .github/skills/dotcanvas && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "dotcanvas" agent skill from https://github.com/gridaco/grida/tree/main/skills/dotcanvas into .github/skills/dotcanvas/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dotcanvas", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add gridaco/grida --skill dotcanvas -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install gridaco/grida dotcanvas --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/gridaco/grida.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/dotcanvas .opencode/skills/dotcanvas && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "dotcanvas" agent skill from https://github.com/gridaco/grida/tree/main/skills/dotcanvas into .opencode/skills/dotcanvas/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dotcanvas", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: dotcanvas
GitHub stars: 2.7k
Token cost: ~1.2k tokens
SKILL.md length: 579 words
Files: 1
Skills in repo: 29
Repo updated: Oct 6, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Author and edit a Grida .canvas board — a .canvas.json manifest plus document files (references, generated images, notes) placed on an infinite canvas.

Working on a .canvas bundle
SKILL.md covers Structure, Working pattern and Show the result
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
Arranging visuals/design work spatially

What it does

Dotcanvas is an agent skill from gridaco/grida. Author and edit a Grida .canvas board — a .canvas.json manifest plus document files (references, generated images, notes) placed on an infinite canvas. Use when working on a .canvas bundle or arranging visuals/design work spatially. For a linear deck/presentation, use the slides skill instead.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Documents & Office, covering Slides and decks. The licence is Apache-2.0.

When your agent uses it

Working on a .canvas bundle
Arranging visuals/design work spatially

Example prompts

“/dotcanvas”

What it can do on your machine

Read from SKILL.md and the folder at commit 165496f. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are json).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Dotcanvas loads about 1.2k tokens when it runs. Until then it costs about 78 tokens; SKILL.md has 579 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~78
When it runs · the whole SKILL.md, loaded when a task matches: ~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from gridaco/grida at commit 165496f, republished under its Apache-2.0 licence (© gridaco). 579 words, ~1,161 tokens.

Download SKILL.mdSave it as .claude/skills/dotcanvas/SKILL.md (or your agent's skills folder).

name: dotcanvas
description: Author and edit a Grida `.canvas` board — a `.canvas.json` manifest plus document files (references, generated images, notes) placed on an infinite canvas. Use when working on a `.canvas` bundle or arranging visuals/design work spatially. For a linear deck/presentation, use the `slides` skill instead.

A .canvas is a Grida design board — a directory bundle, not a single file. You work it like any other files: with read_file / write_file / edit_file (no special canvas tool). It is the durable, spatial home for a piece of work: reference images, generated outputs, and notes, arranged on an infinite canvas. Prefer a .canvas board for freeform visual/design work; for a linear deck / presentation / pitch / slideshow, use the slides skill.

Structure

The bundle is a folder whose name ends in .canvas (e.g. poster.canvas/).
.canvas.json (the manifest) holds the STRUCTURE: which documents are on the board, their placement, order, and the editor mode.
Each document's CONTENT is a separate file (or a URL) referenced by its src.

Manifest shape (only src is required per document):

json

{
  "editor": "board",
  "documents": [
    {
      "src": "https://…/ref.jpg",
      "id": "ref1",
      "layout": { "x": 0, "y": 0, "w": 480, "h": 320 }
    },
    {
      "src": "outputs/hero.png",
      "id": "hero",
      "layout": { "x": 520, "y": 0, "w": 768, "h": 512 }
    }
  ]
}

editor: "board" = freeform infinite canvas (placement via layout). editor: "slides" = linear deck (order) — see the slides skill.
layout is { x, y, w, h, z? } in world space (z = paint order, optional). A document with no layout is unplaced — the host positions it; set a layout to place it deliberately.

Working pattern

To start, make the bundle folder first — a NEW directory whose name ends in .canvas (e.g. poster.canvas/); a plain folder, or files loose in the workspace root, is NOT a board and won't open. Then write_file its .canvas.json and each document file INSIDE that folder. To add to an existing board, read_file .canvas.json first (preserve version/$schema/editor and any unknown fields), then write the FULL updated manifest back.
A document's src may be a URL (a pointable reference — a picked library image, used as-is, no download) OR a file path inside the bundle. Both are first-class placed documents.
To place a generated image (or any produced file) on the board: materialize it into the bundle, then reference it. Copy it from your scratch dir into the bundle with the shell — e.g. cp <scratch>/image-….png <board>.canvas/outputs/hero.png — then add a document whose src is that bundle-relative path. (A src can point at any file the host can read, but a file inside the bundle is the durable, portable choice.)
To move / resize / reorder, edit the layout (and document order) in the manifest. The human can also drag pins directly — re-read .canvas.json before editing so you don't clobber their changes (last write per file wins).

Show full SKILL.md (204 more words)Show less

Show the result

Treat presentation as the first production milestone, not the final "validate and open" step. For a new board, establish a meaningful renderable checkpoint early: the manifest references at least one existing, valid document with a basic visible composition. Call surface_open immediately with the workspace-rooted .canvas bundle directory (for example, /poster.canvas), then continue building and polishing it while the user can watch. Intentionally use a lightweight initial composition instead of authoring the finished board before opening it. Do not wait for all content, assets, polish, preview generation, exhaustive validation, or task completion.
Never open an empty bundle or a broken manifest. Open only when the manifest references at least one existing, renderable document. Pass the bundle directory, never its .canvas.json manifest.
For an existing primary board, open it after reading its manifest and before substantial edits.
If the .canvas bundle itself is mounted as / in a dedicated file surface, it is already presented; do not call surface_open just to reopen it.
Treat presentation as auxiliary: continue regardless of the result, never retry based on presentation status, and do not call surface_open after every write.
Use surface_list_open only when the current host surface state is materially useful. It is not required before surface_open.

Files

Just SKILL.md in skills/dotcanvas of gridaco/grida.

Open the folder on GitHubat commit 165496f

Compare with similar skills

Dotcanvas next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Dotcanvas compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Dotcanvas this skillgridaco/grida	2.7k	—	~1.2k	Automated safety check: Pass	Apache-2.0	yesterday
Image To Editable Pptningzimu/image-to-editable-ppt-skill	2.8k	—	~4.3k	Automated safety check: Pass	MIT	21 days ago
Slidesfcakyon/claude-codex-settings	1.2k	1 repos	~1.1k	Automated safety check: Pass	MIT	yesterday
Ppt Image FirstNyxTides/ppt-image-first	1.2k	—	~1.6k	Automated safety check: Pass	Apache-2.0	5 mo ago
Vibe to Agentic Engineering Frameworkshanraisshan/claude-code-best-practice	67k	—	~3.3k	Automated safety check: Pass	MIT	today
Gpt Image2 PptJuneYaooo/gpt-image2-ppt-skills	1.3k	—	~8.9k	Automated safety check: Notes	Apache-2.0	1 mo ago

Similar skills

Image To Editable Ppt
ningzimu/image-to-editable-ppt-skill
Rebuild slide images, scanned or image-based PPT/PPTX files, and PDF decks into object-level editable PowerPoint (.pptx), preserving speaker notes when supplied.
2.8k GitHub stars~4.3k tokensUpdated 21 days ago
Documents & OfficeAuto-check passed
Slides
fcakyon/claude-codex-settings
Create and edit presentation slide decks (.pptx) with PptxGenJS, bundled layout helpers, and render/validation utilities.
1.2k GitHub starsUsed in 1 repo~1.1k tokens
Documents & OfficeAuto-check passed
Ppt Image First
NyxTides/ppt-image-first
Build presentation plans for PPT / slides / decks through a conversation-first workflow, then propose multiple visual directions with preview images before writing deck specs.
1.2k GitHub stars~1.6k tokensUpdated 5 mo ago
Documents & OfficeAuto-check passed
Vibe to Agentic Engineering Framework
shanraisshan/claude-code-best-practice
Explains the conceptual model behind a presentation on moving from unstructured vibe coding to fully configured agentic engineering, including its 4-level scoring system and slide conventions.
67k GitHub stars~3.3k tokensUpdated today
Documents & OfficeAuto-check passed
Gpt Image2 Ppt
JuneYaooo/gpt-image2-ppt-skills
Generate visually striking PPT slides via OpenAI's gpt-image-2 -- use any style in styles/<collection/STYLEID.md or mimic a user-supplied .pptx template; outputs high-res slide PNGs and a 16:9 .pptx.
1.3k GitHub stars~8.9k tokensUpdated 1 mo ago
Documents & OfficeAuto-check: notes
Compiledeck
scunning1975/MixtapeTools
Create and compile beautiful Beamer presentations following the Rhetoric of Decks philosophy.
469 GitHub starsUsed in 2 repos~3.1k tokens
Documents & OfficeAuto-check passed

Questions about Dotcanvas

What does Dotcanvas do?

Author and edit a Grida .canvas board — a .canvas.json manifest plus document files (references, generated images, notes) placed on an infinite canvas. Dotcanvas is an agent skill from gridaco/grida.json manifest plus document files (references, generated images, notes) placed on an infinite canvas.

When should I use Dotcanvas?

Dotcanvas fits situations like: working on a .canvas bundle; arranging visuals/design work spatially.

How do I install Dotcanvas in Claude Code?

Run `npx skills add gridaco/grida --skill dotcanvas -a claude-code`. Or copy the skill folder (skills/dotcanvas in gridaco/grida) into .claude/skills/dotcanvas in your project. Claude Code loads it when a task matches its description.

How do I install Dotcanvas in Codex?

Run `npx skills add gridaco/grida --skill dotcanvas -a codex`. Or copy the skill folder (skills/dotcanvas in gridaco/grida) into .agents/skills/dotcanvas in your project. Codex loads it when a task matches its description.

Can I use Dotcanvas in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add gridaco/grida --skill dotcanvas -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/dotcanvas, .gemini/skills/dotcanvas, .github/skills/dotcanvas and .opencode/skills/dotcanvas in your project.

What does Dotcanvas need to run?

SKILL.md names no scripts, command-line tools or credentials: Dotcanvas is instructions for the agent only.

Does Dotcanvas access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Dotcanvas safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Dotcanvas use?

Dotcanvas is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Dotcanvas use?

About 1.2k tokens (SKILL.md is roughly 4.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Dotcanvas?

Skills that share tags, products or a category with Dotcanvas: Image To Editable Ppt (ningzimu/image-to-editable-ppt-skill, 2.8k stars), Slides (fcakyon/claude-codex-settings, 1.2k stars), Ppt Image First (NyxTides/ppt-image-first, 1.2k stars) and Vibe to Agentic Engineering Framework (shanraisshan/claude-code-best-practice, 67k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Dotcanvas?

gridaco (a GitHub organization) maintains it in gridaco/grida, which has 2,657 GitHub stars. The repository holds 29 skills in this directory. The repository was last updated on October 6, 2026.

Source: gridaco/grida on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Dotcanvas

Install Dotcanvas

Facts

At a glance

What it does

When your agent uses it

Example prompts

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Structure

Working pattern

Show the result

Files

Compare with similar skills

Similar skills

Image To Editable Ppt

Slides

Ppt Image First

Vibe to Agentic Engineering Framework

Gpt Image2 Ppt

Compiledeck

More from gridaco/grida

Desktop

Io Figma

Opt Library

Vision

AI Models

Agent System

Questions about Dotcanvas

Install Dotcanvas

Facts

At a glance

What it does

When your agent uses it

Example prompts

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Structure

Working pattern

Show the result

Files

Compare with similar skills

Similar skills

More from gridaco/grida

Related

Questions about Dotcanvas