Name: grist
Rating: 64.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

grist

Grist integration. Manage Workspaces, Users, Roles. Use when the user wants to interact with Grist data.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/grist/SKILL.md

Quality

Content

76%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.

The content is highly actionable with concrete CLI commands and a useful action reference, organized into clear sections. Its weak point is workflow safety: destructive and batch operations are exposed without explicit verification steps before execution.

Suggestions

Add a validation/verification checkpoint before destructive actions (e.g., list records/documents first, confirm the target ID, then delete), and a re-list-after-delete confirmation.

Trim the Grist overview paragraph and the "auth plumbing" aside to reduce token overhead on concepts that are not essential to executing the skill.

Consider splitting the 18-row popular-actions table into a references file so SKILL.md stays a lean overview, with the most common actions summarized inline.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient, dominated by concrete commands and a compact action table, but the opening paragraph explaining what Grist is and phrases like "so you can focus on the integration logic rather than auth plumbing" add mild over-explanation that could be trimmed.	4 / 5
Actionability	It provides copy-paste-ready commands for install, login, connection ensure/get, action list/run, and proxy requests, plus a full table of action keys covering common cases, with clearly marked placeholders for IDs.	5 / 5
Workflow Clarity	The connection flow is well-sequenced with state polling and a CLIENT_ACTION_REQUIRED feedback loop, but the skill exposes destructive actions (delete-records, delete-document, delete-workspace) with no validation/verification checkpoint, which caps workflow clarity at 3.	3 / 5
Progressive Disclosure	Content is single-file with clear section headers and no nested references, and the inline actions table is a reasonable quick-reference; there are no bundle files to link, and the structure is good with only minor organization gaps.	4 / 5
	Total	16 / 20 Passed

Description

78%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.

The description is solid: it names a specific product, lists concrete capability areas, and includes an explicit use-when trigger. Its main weakness is that the capability list understates what the skill actually does and the trigger guidance is a single clause rather than a richer set of natural phrases.

Suggestions

Expand the capability list to match the body (e.g. add Documents, Tables, Records, running SQL queries) for more comprehensive specificity.

Broaden the trigger with natural phrasings and synonyms, e.g. "Use when the user wants to query, create, update, or delete Grist records, tables, documents, or workspaces."

Replace the generic "Grist integration" lead with a concrete action verb phrase (e.g. "Manage Grist workspaces, documents, tables, and records...").

Dimension	Reasoning	Score
Specificity	Names the Grist domain and lists three concrete action areas ("Manage Workspaces, Users, Roles"), giving several specific capabilities, but omits documents/tables/records that the body actually covers, so coverage is not comprehensive enough for a 5.	4 / 5
Completeness	It states both a "what" (Grist integration; manage Workspaces/Users/Roles) and an explicit "when" trigger, but the generic "Grist integration" lead and single trigger clause keep it just short of the fully concrete dual-anchor at 5.	4 / 5
Trigger Term Quality	"Use when the user wants to interact with Grist data" supplies the natural product name and a likely user phrase, but lacks synonyms or file/extension variations, leaving a few natural terms missing.	4 / 5
Distinctiveness Conflict Risk	Grist is a specific named product with its own trigger phrase, giving it a clear niche and minimal overlap risk with unrelated skills.	5 / 5
	Total	17 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/grist/SKILL.md
Commit: f484c82

Reviewed: ~21 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.