io-grida

Guides work on the Grida file format (.grida) from the TS side: the I/O packages that read/write it (loading, archive packing, clipboard) and the frozen schema bindings. Use when working with .grida files in the editor or packages, or debugging format round-trip issues. (The schema and the Rust decoder live in the engine repo.)

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

86%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 tight, high-signal orientation skill for the .grida TS-side I/O packages: precise locations, API names, and runnable verification commands with a clearly sequenced cross-repo schema-change procedure. The only real weakness is the deliberately under-specified re-snapshot step, which is concrete in intent but lacks an executable example.

Dimension	Reasoning	Score
Conciseness	The body is lean and dense — tables for variants and key locations, terse function listings, and no padding or explanation of concepts Claude already knows; version strings (pinned flatc v25.12.19, "0.91.0-beta+20260311") are factual pins rather than date-conditional guidance.	5 / 5
Actionability	Gives exact package paths, concrete API names (io.load, io.is_grida, io.archive.pack/unpack) and copy-paste verification commands, but the 're-snapshot the frozen bindings' step in the schema-change workflow is described only in prose with no command or snippet, leaving a minor executability gap.	4 / 5
Workflow Clarity	The schema-change lockstep is a clearly numbered 1–3 sequence with explicit version-sync requirements and a Verification section of runnable commands, plus stated rejection behavior for old files; the minor gap is that the re-snapshot step is not explicitly tied back to running the verification commands.	4 / 5
Progressive Disclosure	A well-sectioned single-file overview with no nested references; the only external links (engine-repo .fbs, Rust io crates, format/AGENTS.md) are clearly signaled one level deep, and no content is bulky enough to warrant a separate reference file.	5 / 5
	Total	18 / 20 Passed

Description

87%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 description: third-person, concrete, and explicit about both scope (TS-side I/O packages and frozen bindings) and triggers (.grida files, round-trip debugging), with deliberate boundary marking against the engine-repo skill. Its only shortfall is modest coverage breadth in the action list and trigger synonyms.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions ('loading, archive packing, clipboard', 'frozen schema bindings') in third person, but omits schema-version bumping and verification work, so it stops short of the comprehensive coverage of the anchor 5 example.	4 / 5
Completeness	Clearly answers both: what it does ('Guides work on the Grida file format (.grida) from the TS side: the I/O packages that read/write it...') and when to use it via an explicit 'Use when working with .grida files... or debugging format round-trip issues' clause with concrete triggers.	5 / 5
Trigger Term Quality	Good natural trigger phrases including the file extension ('working with .grida files', 'debugging format round-trip issues', 'in the editor or packages'), though synonym coverage beyond '.grida' and 'round-trip' is limited, falling just short of the comprehensive anchor 5.	4 / 5
Distinctiveness Conflict Risk	The '.grida' extension is a highly distinctive trigger with minimal conflict risk, and the parenthetical '(The schema and the Rust decoder live in the engine repo.)' explicitly disambiguates it from the sibling engine-repo skill.	5 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: gridaco/grida
Path: .agents/skills/io-grida/SKILL.md
Commit: d086528

Reviewed: 7 days ago

Table of Contents

Discovery Implementation Validation

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.