Recipe Draft Email From Doc
googleworkspace/cli
Read content from a Google Doc and use it as the body of a Gmail message.
Decide which family a doc belongs to before drafting — SDK/developer, user/product, or working-group (WG) — since family sets the audience, home, and tone.
Apache-2.0Auto-check passed
Install Docs
$ npx skills add gridaco/grida --skill docs -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install gridaco/grida docs --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/gridaco/grida.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/docs .claude/skills/docs && rm -rf skills-srcUse ~/.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/
Install the "docs" agent skill from https://github.com/gridaco/grida/tree/main/.agents/skills/docs into .claude/skills/docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs", 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 install https://github.com/gridaco/grida/tree/main/.agents/skills/docsType 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.
$ npx skills add gridaco/grida --skill docs -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install gridaco/grida docs --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gridaco/grida.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/docs .agents/skills/docs && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "docs" agent skill from https://github.com/gridaco/grida/tree/main/.agents/skills/docs into .agents/skills/docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs", 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.
$ npx skills add gridaco/grida --skill docs -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install gridaco/grida docs --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gridaco/grida.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/docs .cursor/skills/docs && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "docs" agent skill from https://github.com/gridaco/grida/tree/main/.agents/skills/docs into .cursor/skills/docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs", 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 https://github.com/gridaco/grida.git --path .agents/skills/docs--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add gridaco/grida --skill docs -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install gridaco/grida docs --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gridaco/grida.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/docs .gemini/skills/docs && rm -rf skills-srcUse ~/.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/
Install the "docs" agent skill from https://github.com/gridaco/grida/tree/main/.agents/skills/docs into .gemini/skills/docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs", 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.
$ gh skill install gridaco/grida docsInstalls 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).
$ npx skills add gridaco/grida --skill docs -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/gridaco/grida.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/docs .github/skills/docs && rm -rf skills-srcUse ~/.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/
Install the "docs" agent skill from https://github.com/gridaco/grida/tree/main/.agents/skills/docs into .github/skills/docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs", 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.
$ npx skills add gridaco/grida --skill docs -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install gridaco/grida docs --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gridaco/grida.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/docs .opencode/skills/docs && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "docs" agent skill from https://github.com/gridaco/grida/tree/main/.agents/skills/docs into .opencode/skills/docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs", 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
docs- GitHub stars
- 2.7k
- Token cost
- ~1.9k tokens
- SKILL.md length
- 752 words
- Files
- 1
- Skills in repo
- 29
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Decide which family a doc belongs to before drafting — SDK/developer, user/product, or working-group (WG) — since family sets the audience, home, and tone.
- Works in 3 steps: **Is it about why a thing is designed… → Is the reader a person trying to use a… → **Is the reader an engineer (or agent)…
- Restructuring docs
- SKILL.md covers The three families, Routing — which family is this?, SDK / developer docs and Related skills
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Docs is an agent skill from gridaco/grida. Decide which family a doc belongs to before drafting — SDK/developer, user/product, or working-group (WG) — since family sets the audience, home, and tone. Use when creating, moving, or restructuring docs, when unsure which directory a doc belongs in, or when a request says "document this" / "write docs for X" without naming the kind. Routes to the specialized skill for each family.
Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The licence is Apache-2.0.
When your agent uses it
- Restructuring docs
- Unsure which directory a doc belongs in
- A request says document this / write docs for X without naming the kind
Example prompts
- “document this”
- “write docs for X”
- “/docs”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- **Is it about why a thing is designed the way it is, or what a
- Is the reader a person trying to use a shipped product?
- **Is the reader an engineer (or agent) trying to consume a package
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.
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
Docs loads about 1.9k tokens when it runs. Until then it costs about 98 tokens; SKILL.md has 752 words of instructions outside code blocks.
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). 752 words, ~1,929 tokens.
Download SKILL.mdSave it as
.claude/skills/docs/SKILL.md (or your agent's skills folder).- name
- docs
- description
- Decide which family a doc belongs to before drafting — SDK/developer, user/product, or working-group (WG) — since family sets the audience, home, and tone. Use when creating, moving, or restructuring docs, when unsure which directory a doc belongs in, or when a request says "document this" / "write docs for X" without naming the kind. Routes to the specialized skill for each family.
Docs
Documentation in Grida is not one thing. Before drafting, name the family — because the family decides the audience, the home directory, the tone, and which skill governs the rest. Writing the right content in the wrong family (a spec dump in a user guide, a marketing tone in an RFC) is the most common and most expensive docs mistake, because it is invisible until someone reads it for the wrong reason.
/docs/** is the source of truth, synced to /apps/docs/docs/** at
build and published at grida.co/docs. Edit the root /docs, never the
synced copy. The operational rules that apply to every family —
taxonomy (draft / unlisted / doc_tasks), frontmatter, MDX safety
(format: md), _history/, the structure table — live in
docs/AGENTS.md. Read it once; this skill does
not repeat it.
The three families
| Family | Audience | Home | Character | Governing skill |
|---|---|---|---|---|
| SDK / developer | engineers (and, implicitly, agents) consuming a package or API | packages/<pkg>/docs/ for spec-only; docs/reference/** for stable references | technical, example-dense, low-visual, precise | this skill (below) |
| User / product | humans using a Grida product | docs/editor/**, docs/forms/**, docs/platform/**, docs/with-figma/**, … | content-rich, screenshots, SEO-friendly, task-oriented | canvas editor (docs/editor/) → docs-canvas; cross-cutting → seo + docs-svg-kit; other surfaces have no dedicated skill yet — use docs/AGENTS.md + seo |
| WG / research / RFC-RFD | contributors and maintainers reasoning about why and what | docs/wg/** | spec-rich, language-agnostic, code-agnostic, factual | docs-wg |
If the request fits one family cleanly, hand off to its governing skill and stop reading here. The rest of this page covers the routing edges and the SDK family (which has no skill of its own).
Routing — which family is this?
Ask, in order:
- Is it about why a thing is designed the way it is, or what a
feature/spec should be — independent of any one implementation?
→ WG. Go to
docs-wg. - Is the reader a person trying to use a shipped product?
→ User docs. Content-rich and SEO-aware. For the canvas editor
(
docs/editor/) usedocs-canvas; for other surfaces (forms, platform, with-figma) there is no dedicated skill yet — followdocs/AGENTS.mdandseo.docs-svg-kitcovers SVG figures for any of them. - Is the reader an engineer (or agent) trying to consume a package or API correctly? → SDK docs (below).
The boundaries are real, not bureaucratic:
- Architecture / design rationale never goes in user docs. It belongs
in WG. (
docs-canvasenforces the same boundary from its side.) - A WG doc is not an SDK doc. WG says "this is what the feature is and
why"; SDK says "this is the API and how to call it." A WG doc that
drifts into API signatures has become an SDK doc in the wrong place —
see
docs-wgon staying code-agnostic. - Implementation-binding specs live with the code, not in
docs/wg. A spec that maps a universal contract onto one codebase — the concrete data a structure holds, this build's keymap, the contract→code mapping — is code-specific. It belongs in the package or crate's owndocs/, next to what it binds, sodocs/wgcan stay code-agnostic. It is neither a WG doc (too code-specific) nor an SDK doc (not for external consumers) — its home is the code. - Plans, TODO lists, and conversational logs are not docs of any
family. Plans live in untracked
*.plan.mdfiles (gitignored); they do not belong underdocs/.
Show full SKILL.md (226 more words)Show less
SDK / developer docs
SDK docs explain how to consume a package or API. They optimize for an engineer (and, without ever saying so, for an agent) who needs to get a call right on the first try.
Where they live:
packages/<pkg>/docs/— when the docs are spec-heavy and not visually rich. Co-locating with the package keeps the contract next to the code it describes and versioned with it. (Precedent:packages/grida-svg-editor/docs/.) A package'sREADME.mdandAGENTS.mdare the entry points;docs/holds the deeper material.docs/reference/**— for stable, cross-package technical references, glossaries, and specs that deserve a place on the published site. This tree is actively maintained alongsidedocs/wg/\*\*.
What good SDK docs look like:
- Example-dense. Every non-trivial API earns a short, runnable example. Examples carry more than prose for a consumer.
- Technical and precise about types, contracts, and edge cases — light on screenshots and marketing.
- Good for agents by being good, period. Do not write "for AI" — a clear, complete, example-backed reference is what an agent needs and what a human needs. The two goals do not diverge.
- Honest about stability. Mark experimental surfaces; an SDK doc that oversells a shaky API costs its readers time.
Related skills
docs-wg (WG authoring doctrine),
docs-canvas (canvas/editor user docs),
seo (frontmatter + search),
links (how to write any link),
grounding (find/reconcile the authoritative
doc before editing). Operational taxonomy and frontmatter:
docs/AGENTS.md.
© gridaco, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/docs of gridaco/grida.
Open the folder on GitHubat commit 165496f
Compare with similar skills
Docs 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Docs this skillgridaco/grida | 2.7k | — | ~1.9k | Automated safety check: Pass | Apache-2.0 | |
| Recipe Draft Email From Docgoogleworkspace/cli | 31k | — | ~197 | Automated safety check: Pass | Apache-2.0 | |
| Kedro Docs Draft Writerkedro-org/kedro | 11k | — | ~2.9k | Automated safety check: Pass | Custom licence | |
| Docnexu-io/open-design | 100k | — | ~266 | Automated safety check: Pass | Apache-2.0 | |
| Docsremotion-dev/remotion | 62k | — | ~248 | Automated safety check: Pass | Custom licence | |
| DocsPrefectHQ/fastmcp | 28k | — | ~1k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Kedro Docs Draft Writer
kedro-org/kedro
Draft or polish Kedro documentation. An agent skill from kedro-org/kedro.
Doc
nexu-io/open-design
Read, create, and edit .docx documents with formatting and layout fidelity via OpenAI's document skill.
- Official
Docs
remotion-dev/remotion
Start the Remotion docs site and open it in the Codex browser.
Docs
PrefectHQ/fastmcp
Write or revise a page under docs/ for gofastmcp.com. An agent skill from PrefectHQ/fastmcp.
Decide
alirezarezvani/claude-skills
/cs:decide <memo — Log a decision to two-layer memory via decision-logger.
More from gridaco/grida
All 29 skills in this repoDesktop
gridaco/grida
Grida Desktop Electron shell and release-impact work: BrowserWindow, preload, window.grida, menus, protocol/deep links, file associations, Forge, path-scoped bridge security, Electron-only UI bugs…
Io Figma
gridaco/grida
Guides work on the Figma I/O package (@grida/io-figma, packages/grida-canvas-io-figma/).
Opt Library
gridaco/grida
Set up, download, verify, and seed the optional Grida Library developer corpus into local Supabase.
Vision
gridaco/grida
Query images with a local Ollama vision model without loading the image into the main agent context.
AI Models
gridaco/grida
Research, compare, and update shared AI model JSON for TypeScript, web, and Rust consumers.
Agent System
gridaco/grida
Grida AI agent system work: @grida/daemon (DaemonServer, loopback HTTP perimeter, files/workspaces, secrets store, daemon discovery) and @grida/agent (the agent tenant: sessions, providers/BYOK…
Questions about Docs
What does Docs do?
Decide which family a doc belongs to before drafting — SDK/developer, user/product, or working-group (WG) — since family sets the audience, home, and tone. Docs is an agent skill from gridaco/grida. Decide which family a doc belongs to before drafting — SDK/developer, user/product, or working-group (WG) — since family sets the audience, home, and tone.
When should I use Docs?
Docs fits situations like: restructuring docs; unsure which directory a doc belongs in; A request says document this / write docs for X without naming the kind.
How do I install Docs in Claude Code?
Run `npx skills add gridaco/grida --skill docs -a claude-code`. Or copy the skill folder (.agents/skills/docs in gridaco/grida) into .claude/skills/docs in your project. Claude Code loads it when a task matches its description.
How do I install Docs in Codex?
Run `npx skills add gridaco/grida --skill docs -a codex`. Or copy the skill folder (.agents/skills/docs in gridaco/grida) into .agents/skills/docs in your project. Codex loads it when a task matches its description.
Can I use Docs 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 docs -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/docs, .gemini/skills/docs, .github/skills/docs and .opencode/skills/docs in your project.
What does Docs need to run?
SKILL.md names no scripts, command-line tools or credentials: Docs is instructions for the agent only.
Does Docs 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 Docs 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 Docs use?
Docs 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 Docs use?
About 1.9k tokens (SKILL.md is roughly 7.7k 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 Docs?
Skills that share tags, products or a category with Docs: Recipe Draft Email From Doc (googleworkspace/cli, 31k stars), Kedro Docs Draft Writer (kedro-org/kedro, 11k stars), Doc (nexu-io/open-design, 100k stars) and Docs (remotion-dev/remotion, 62k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Docs?
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.