Agent skill

Grounding

by gridaco in gridaco/grida

Establish what is actually true and current for the surface you are about to change — not just search.

Apache-2.0Auto-check passedBusiness, Finance & HR

Install Grounding

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

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

GitHub CLI
$ gh skill install gridaco/grida grounding --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/.agents/skills/grounding .claude/skills/grounding && 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/

Facts

Skill name
grounding
GitHub stars
2.7k
Token cost
~1.1k tokens
SKILL.md length
427 words
Files
2 (incl. scripts)
Skills in repo
29
Repo updated
First seen
Licence
Apache-2.0

At a glance

Establish what is actually true and current for the surface you are about to change — not just search.

  • Tasks that involve Accounting and bookkeeping
  • SKILL.md covers Source of truth (scoped to the…, Dead-tree traps, Grounding the docs and Related skills
  • Runs Python scripts from its folder; calls uv, rg and git

What it does

Grounding is an agent skill from gridaco/grida. Establish what is actually true and current for the surface you are about to change — not just search. Grounding = locate the authoritative source and reconcile sources that disagree (code vs doc, migration vs schema, memory vs current code, live vs archived), not take the first hit. Use before any grep/find/explore of the codebase or docs, when deciding which of several definitions is the real one, or when a doc or memory conflicts with the code. Covers the source-of-truth hierarchy, reconciliation discipline…

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including scripts (for example `scripts/docsearch.py`).

It sits in Business, Finance & HR, covering Accounting and bookkeeping. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Accounting and bookkeeping

Example prompts

  • “/grounding”

Requirements

  • Python 3

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

    Ships 1 file in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • uv
    • rg
    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • github.com

    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

Grounding loads about 1.1k tokens when it runs. Until then it costs about 147 tokens; SKILL.md has 427 words of instructions outside code blocks.

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

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); the scripts in this folder are not scanned.

SKILL.md

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

Download SKILL.mdSave it as .claude/skills/grounding/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
grounding
description
Establish what is actually true and current for the surface you are about to change — not just search. Grounding = locate the authoritative source and reconcile sources that disagree (code vs doc, migration vs schema, memory vs current code, live vs archived), not take the first hit. Use before any grep/find/explore of the codebase or docs, when deciding which of several definitions is the real one, or when a doc or memory conflicts with the code. Covers the source-of-truth hierarchy, reconciliation discipline, scoped ripgrep, and the docs/tags.yml + docsearch.py index.

Grounding

Grounding is establishing what is actually true and current for the surface you are about to change, then acting on that — not on a guess, a memory, or the first grep hit. The hard part is not search; it is picking the authoritative source and reconciling sources that disagree.

Intentional seed. This holds only Grida-specific facts that are not obvious from CLAUDE.md/AGENTS.md. Grow it from real, discovered specifics (concept→file anchors that bite repeatedly, conflicts that actually happened and how they resolved). Do not pad it with generic search advice a competent agent already knows.

Source of truth (scoped to the surface)

Authority is per-surface — the engine model and its TS mirror can each be right for their own surface and still disagree. Name the surface, then trust:

  • Canvas render/node model → the Rust engine, now in the engine repo: https://github.com/gridaco/nothing/blob/main/crates/grida/src/node/schema.rs. The TS mirror editor/grida-canvas/ is authoritative for editor behavior and can lag the engine.
  • DB schema → supabase/migrations/ (applied, immutable); supabase/schemas/*.sql is a readable projection that can lag — use the database skill.
  • Shared AI catalogue and input contracts → repository-root data/ai/facts.json, data/ai/service.json, and data/ai/inputs.json. Edit these authored sources; marked TypeScript literals and crates/grida-ai/data/ assets are generated consumers. Follow ai-models for authoring and regeneration.
  • Directory contract → the nearest AGENTS.md/README.md.
  • "I remember API X…" → re-read current code; a memory is a claim about a past state, verify before acting.

Disagreement → decide which wins and why (git log -1 recency, what the running entrypoint imports, what tests assert); don't average; surface a material conflict to the user. Never authoritative even when they match: docs/_history/, docs/@designto-code/ (synced — truth is upstream), .ref/. docs/cli/ is the replacement CLI's maintained user guide; only its explicitly retired legacy pages are historical. Follow docs/AGENTS.md for that boundary.

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

Dead-tree traps

Some directories are git-tracked but dead — a bare rg from repo root returns obsolete hits that look like confirmation: docs/_history/, .ref/. (The legacy editor trees .legacy/ and packages/.legacy/ were retired May 2026 in #759; recover from the snapshot/legacy-with-2023-grida-code-editor-at-202505 branch.) rg already skips gitignored build dirs (node_modules/, .next/, …); don't waste flags there. Scope positively, or exclude the dead trees:

sh
rg PATTERN editor/grida-canvas packages
rg PATTERN -g '!**/docs/_history/**'

Grounding the docs

~360 markdown files; only docs/wg/** and docs/reference/** (plus the user-facing trees in docs/AGENTS.md) are maintained. docs/tags.yml is the controlled vocabulary; tags: frontmatter is the navigation signal. Use the index, don't grep bodies — scripts/docsearch.py reads frontmatter only, self-installs via uv, runs from any cwd:

sh
S=.agents/skills/grounding/scripts/docsearch.py
uv run $S tags                          # vocabulary + usage counts + drift
uv run $S find --tag figma --tag wg     # AND (--any=OR); + --has K --field K=V
uv run $S show wg/feat-fig/glossary/fig.kiwi.md   # one file's frontmatter only

Before trusting a doc over code: draft: true = proposal not built yet (intent ahead); doc_tasks: or stale git log -1 = likely behind.

database (DB source-of-truth), research (upstream/peer projects), naming (where new things belong).

© 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

SKILL.md and 1 other file (scripts) in .agents/skills/grounding of gridaco/grida.

  • SKILL.md
  • scripts/docsearch.py

Open the folder on GitHubat commit 165496f

Compare with similar skills

Grounding 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.

Grounding compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Grounding this skillgridaco/grida2.7k—~1.1kAutomated safety check: PassApache-2.0
Sync Upstreamnyaruka/phonenumbers1.6k—~2.8kAutomated safety check: PassMIT
Longbridge Value Investinghelsome/folio2692 repos~1.2kAutomated safety check: PassMIT
Radiology Tablehuang-sir1/radiology-skills1.9k—~1.3kAutomated safety check: PassCustom licence
Odoo Agency Fleet Reviewerpipe-org/mcp-odoo419—~699Automated safety check: PassMIT
ERPClaw ERP Controlleravansaber/erpclaw114—~15kAutomated safety check: PassGPL-3.0

Similar skills

  • Sync Upstream

    nyaruka/phonenumbers

    Sync this Go port with a new upstream google/libphonenumber release — regenerate the embedded metadata and reconcile the ported Java logic.

    1.6k GitHub stars~2.8k tokensUpdated 5 days ago
    Business, Finance & HRAuto-check passed
  • Value investing analysis using Graham (NCAV/net-net/defensive-investor) and Buffett (economic moat/ROE/FCF) methodologies.

    269 GitHub starsUsed in 2 repos~1.2k tokens
    Business, Finance & HRAuto-check passed
  • Radiology Table

    huang-sir1/radiology-skills

    Create/audit editable publication tables with source reconciliation; not figures or statistical inference.

    1.9k GitHub stars~1.3k tokensUpdated 16 days ago
    Business, Finance & HRAuto-check passed
  • Odoo Agency Fleet Review

    erpipe-org/mcp-odoo

    Review many client Odoo databases at once through odoo-mcp's cross-instance tools — fleet-wide accounting health, per-client aging, partial-failure triage — for agencies and partners managing 5–50…

    419 GitHub stars~699 tokensUpdated 1 mo ago
    Business, Finance & HRAuto-check passed
  • ERPClaw ERP Controller

    avansaber/erpclaw

    Operates the ERPClaw self-hosted ERP in plain language: accounting, invoicing, inventory, purchasing, tax, HR, payroll and reports, treating the ERP as the single source of truth.

    114 GitHub stars~15k tokensUpdated yesterday
    Business, Finance & HRAuto-check passed
  • Beancount Close

    bex-co/beancount-io

    Close an accounting period in a Beancount ledger by reconciling each active account through beancount-reconcile, checking assertions and recurring gaps, reviewing flags, then proposing a commit with…

    294 GitHub stars~1.4k tokensUpdated today
    Business, Finance & HRAuto-check passed

More from gridaco/grida

All 29 skills in this repo
  • Desktop

    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…

    2.7k GitHub stars~3.2k tokensUpdated yesterday
    Auto-check: notes
  • Io Figma

    gridaco/grida

    Guides work on the Figma I/O package (@grida/io-figma, packages/grida-canvas-io-figma/).

    2.7k GitHub stars~2.2k tokensUpdated yesterday
    Auto-check: notes
  • Opt Library

    gridaco/grida

    Set up, download, verify, and seed the optional Grida Library developer corpus into local Supabase.

    2.7k GitHub stars~1.4k tokensUpdated yesterday
    Auto-check passed
  • Vision

    gridaco/grida

    Query images with a local Ollama vision model without loading the image into the main agent context.

    2.7k GitHub stars~1.5k tokensUpdated yesterday
    Auto-check passed
  • AI Models

    gridaco/grida

    Research, compare, and update shared AI model JSON for TypeScript, web, and Rust consumers.

    2.7k GitHub stars~5.7k tokensUpdated yesterday
    Auto-check passed
  • 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…

    2.7k GitHub stars~3.4k tokensUpdated yesterday
    Auto-check passed

Questions about Grounding

What does Grounding do?

Establish what is actually true and current for the surface you are about to change — not just search. Grounding is an agent skill from gridaco/grida. Establish what is actually true and current for the surface you are about to change — not just search.

When should I use Grounding?

Grounding fits situations like: tasks that involve Accounting and bookkeeping.

How do I install Grounding in Claude Code?

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

How do I install Grounding in Codex?

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

Can I use Grounding 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 grounding -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/grounding, .gemini/skills/grounding, .github/skills/grounding and .opencode/skills/grounding in your project.

What does Grounding need to run?

Going by SKILL.md and its folder, Grounding needs Python for the scripts in its folder and the command-line tools its instructions call (uv, rg and git). Our summary lists: Python 3.

Does Grounding access the network?

SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.

Is Grounding 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Grounding use?

Grounding 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 Grounding use?

About 1.1k tokens (SKILL.md is roughly 4.4k 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 Grounding?

Skills that share tags, products or a category with Grounding: Sync Upstream (nyaruka/phonenumbers, 1.6k stars), Longbridge Value Investing (helsome/folio, 269 stars), Radiology Table (huang-sir1/radiology-skills, 1.9k stars) and Odoo Agency Fleet Review (erpipe-org/mcp-odoo, 419 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Grounding?

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.