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

87%

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

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 well-organized, actionable reference with concrete commands, named APIs, and a strong validation-gated schema-change workflow. Minor gains are available by trimming the tombstone rationale and time-sensitive version tokens, and adding a validate-then-proceed loop to the load/edit path.

Suggestions

Trim the tombstone explanatory prose and remove the pinned flatc date / example build string to recover tokens; the actionable rule is 'do not edit frozen bindings — re-snapshot deliberately'.

Add an explicit validate-checkpoint to the load/edit workflow (e.g. run the typecheck/test commands before committing changes) to mirror the schema-change feedback loop.

Consider extracting the schema-evolution and compatibility-logic detail into a dedicated reference file so the SKILL.md overview stays leaner.

Dimension	Reasoning	Score
Conciseness	The body is dense and assumes competence (no padding about what FlatBuffers or ZIP archives are), but the tombstone rationale and the schema-compatibility prose could be trimmed slightly, and time-sensitive values like the flatc pin date and example version '20260311' add tokens without aiding action.	4 / 5
Actionability	Concrete, copy-pasteable verification commands are provided, named API entry points (io.load, io.is_grid, io.archive.pack/unpack, io.clipboard.encode/decode) are enumerated with file paths, and the schema-change workflow gives exact edit locations and behavior.	5 / 5
Workflow Clarity	The schema-change section is a clearly numbered lockstep sequence with an explicit validation step (old files rejected via isSchemaCompatible) and compatibility rules, but the load/edit path itself lacks a validate-then-proceed feedback loop comparable to the schema-change checklist.	4 / 5
Progressive Disclosure	Well-sectioned overview with key-path tables and clearly signaled one-level-deep links to engine-repo files; no nested reference indirection, though the schema-evolution detail arguably could live in a dedicated reference rather than inline.	4 / 5
	Total	17 / 20 Passed

Description

92%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 precise, third-person description that cleanly states both the capability scope (TS I/O + frozen bindings) and the use triggers, with an explicit cross-repo boundary that reduces conflict risk. The only gap is keyword synonym coverage for less technical users.

Suggestions

Add a few plain-language synonyms alongside '.grida' (e.g. 'Grida documents', 'Grida files') to broaden trigger matching for non-specialist phrasing.

Dimension	Reasoning	Score
Specificity	Names the concrete actions (loading, archive packing, clipboard read/write) plus the frozen schema bindings, and scopes them to the TS I/O side with the engine repo boundary — comprehensive concrete coverage rather than generic verbs.	5 / 5
Completeness	Explicitly answers both what it does ('I/O packages that read/write it... loading, archive packing, clipboard' plus 'frozen schema bindings') and when to use it ('Use when working with .grida files in the editor or packages, or debugging format round-trip issues').	5 / 5
Trigger Term Quality	Includes natural triggers like '.grida files', 'round-trip issues', and 'editor or packages', plus the file extension, but is missing several common user-facing synonyms a non-specialist might say.	4 / 5
Distinctiveness Conflict Risk	The Grida/.grida TS-side niche with an explicit engine-repo boundary is highly specific and unlikely to fire for unrelated skills; the boundary note further disambiguates it from the engine-repo schema skill.	5 / 5
	Total	19 / 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: 8ef5e53

Reviewed: about 11 hours 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.