Name: grab
Rating: 55.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

grab

Grab integration. Manage Recordses. Use when the user wants to interact with Grab data.

Quality

62%

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/grab/SKILL.md

Quality

Content

67%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 well-structured and highly actionable, with executable commands and a connection workflow that includes real validation checkpoints. The main weaknesses are mild marketing prose that could be trimmed and a dangling 'Step 2' reference that breaks the workflow numbering.

Suggestions

Define or remove the undefined 'Step 2' reference so the connection-to-action flow has a coherent numbered sequence.

Trim promotional prose such as 'so you can focus on the integration logic rather than auth plumbing' to keep the body lean.

Add at least one fully-resolved action example (real actionId and input JSON) to turn the generic placeholders into copy-paste-ready guidance.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient command blocks and tables, but includes padding such as 'so you can focus on the integration logic rather than auth plumbing' and 'Use the available actions to discover its full capabilities', fitting 'mostly efficient but includes some unnecessary explanation'.	3 / 5
Actionability	It provides concrete, copy-paste-ready commands with flags for install, login, connection, search, run, and proxy, but relies on generic placeholders (CONNECTION_ID, QUERY, actionId) without a fully worked example, matching 'mostly executable guidance with minor gaps'.	4 / 5
Workflow Clarity	The connection flow has a clear sequence with explicit state-polling validation and feedback loops (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but it references an undefined 'Step 2', leaving a minor sequencing gap.	4 / 5
Progressive Disclosure	The single SKILL.md is well-organized into clear sections (Authentication, Connecting, Searching, Proxy, Best practices) with no bundle files needed, though the proxy flags table and connection-state detail could be split out, matching 'good structure with minor organization gaps'.	4 / 5
	Total	15 / 20 Passed

Description

57%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 correctly includes both a what and an explicit when clause tied to a distinct platform, but it is generic in its action language ('Manage Recordses') and weak on trigger synonyms. Tightening the verb list and adding natural phrasings would lift specificity and trigger quality.

Suggestions

Replace the generic 'Manage Recordses' with concrete operations, e.g. 'Create, read, update, delete, and list Grab Records'.

Add natural trigger phrasings and synonyms such as 'Use when the user wants to query, create, or update Grab Records or Grab data'.

Fix the non-standard plural 'Recordses' to 'Records' for more natural keyword matching.

Dimension	Reasoning	Score
Specificity	"Manage Recordses" names the domain (Grab Records) but the verb is generic and no concrete operations are listed, matching the 'names the domain but actions are minimal or generic' anchor; it is not a 3 because no specific actions like create/read/update are stated.	2 / 5
Completeness	It states a 'what' ("Grab integration. Manage Recordses.") and an explicit 'when' ("Use when the user wants to interact with Grab data"), matching the anchor where both are present but the 'when' could be more specific.	4 / 5
Trigger Term Quality	"Use when the user wants to interact with Grab data" includes the natural keyword 'Grab' but misses common synonyms, and 'Recordses' is an unnatural pluralization, fitting 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	Grab is a specific named platform giving a clear niche with minimal conflict risk, but the trigger phrasing ('interact with Grab data') is somewhat generic within that niche, so it does not reach the fully-distinct anchor 5.	4 / 5
	Total	13 / 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/grab/SKILL.md
Commit: f484c82

Reviewed: 5 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.