CtrlK
BlogDocsLog inGet started
Tessl Logo

grounding

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.

68

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A lean, highly actionable skill body that externalizes its tooling to a real script and gives concrete copy-paste commands plus explicit reconciliation/validation heuristics. It could be slightly tighter at the top and is organized topically rather than as a numbered workflow.

DimensionReasoningScore

Conciseness

Dense and project-specific with no generic concept padding, but the opening re-states the grounding concept already covered by the description and the 'Intentional seed' blockquote is meta-content that could be trimmed.

4 / 5

Actionability

Provides copy-paste-ready executable commands — 'rg PATTERN editor/grida-canvas packages', 'rg PATTERN -g "!**/docs/_history/**"', and a full 'uv run $S tags/find/show' example set — covering the common cases.

5 / 5

Workflow Clarity

Gives a clear reconciliation decision rule with validation heuristics ('git log -1 recency', 'what the running entrypoint imports', 'what tests assert', 'draft: true', 'surface a material conflict to the user'), though it is organized by topic rather than as an explicit numbered sequence.

4 / 5

Progressive Disclosure

Well-organized into clear sections, externalizes the search tool to a real one-level-deep script (scripts/docsearch.py, verified present) referenced via 'S=.agents/skills/grounding/scripts/docsearch.py', and links related skills; minor organization gaps remain around inlined project specifics.

4 / 5

Total

17

/

20

Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that clearly states both capability and trigger conditions with concrete reconciliation language. Its only weakness is the slightly over-broad 'before any grep/find/explore' trigger, which risks overlap with general search skills.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'locate the authoritative source and reconcile sources that disagree', 'scoped ripgrep', 'docs/tags.yml + docsearch.py index' — but stays at a conceptual altitude rather than enumerating discrete operations, so it falls just short of comprehensive.

4 / 5

Completeness

Explicitly answers both 'what' ('Establish what is actually true and current… locate the authoritative source and reconcile sources that disagree') and 'when' ('Use before any grep/find/explore… when a doc or memory conflicts with the code') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural trigger phrasing a user would say ('grep/find/explore of the codebase', 'a doc or memory conflicts with the code', 'which of several definitions is the real one'); a few common synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

Carves a clear source-of-truth/reconciliation niche, but the broad trigger 'Use before any grep/find/explore of the codebase' creates minor overlap risk with adjacent research/database skills.

4 / 5

Total

17

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
gridaco/grida
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.