Name: gryd
Rating: 58.4 (1 reviews)
Author: membranedev

gryd

Gryd integration. Manage Organizations, Projects, Pipelines, Users, Goals, Filters. Use when the user wants to interact with Gryd data.

Quality

68%

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

Fix and improve this skill with Tessl

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

Quality

Content

68%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 body is highly actionable with comprehensive executable Membrane CLI commands and a sensible setup workflow. It loses points on conciseness (some padded phrasing) and workflow clarity (no validation checkpoints for destructive proxy operations).

Suggestions

Add explicit validation checkpoints, e.g. after `membrane connect` verify the connection with `membrane connection list` before running actions, and advise checking action responses for errors before proceeding.

Trim filler phrases ("so you can focus on the integration logic rather than auth plumbing", "This will burn less tokens") to tighten conciseness.

Reconcile the "Gryd Overview" section (Project/Task/Member/Time Entry) with the actual popular actions (vehicle/ULEZ/MOT/DVLA) or move generic overview detail into a separate reference file.

Dimension	Reasoning	Score
Conciseness	Mostly efficient command documentation, but includes unnecessary padding such as "so you can focus on the integration logic rather than auth plumbing" and "This will burn less tokens and make communication more secure".	3 / 5
Actionability	Provides copy-paste-ready, fully executable commands across install, login (incl. headless), connect, list connections, action search/run with JSON params, and proxy with a complete flag table — covering the common cases.	5 / 5
Workflow Clarity	The setup sequence (install → login → connect → discover → run) is clearly ordered, but no validation or verification checkpoints exist, and the proxy supports destructive methods (DELETE/PUT/PATCH) without feedback loops, capping the score at 3.	3 / 5
Progressive Disclosure	Well-organized into clearly headed sections with no external references needed, but the top "Gryd Overview" bullets (Project/Task/Member/Time Entry) are disconnected from the vehicle-focused popular actions, a minor organization gap.	4 / 5
	Total	15 / 20 Passed

Description

67%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 pairs a concrete resource list with an explicit Use-when clause, giving good specificity and completeness. It is held back by thin trigger-term coverage (little beyond the brand name) and a slightly generic when phrase.

Suggestions

Expand trigger terms with natural synonyms users might say (e.g., "Gryd CRM", "real estate data", "commercial property listings") rather than only "interact with Gryd data".

Replace the single "Manage" verb with a few concrete actions (e.g., "Create, list, and update Organizations, Projects, Pipelines...") to lift specificity from 4 to 5.

Tighten the when clause to name concrete intents (e.g., "Use when the user wants to query or update Gryd Organizations, Projects, or Pipelines").

Dimension	Reasoning	Score
Specificity	"Manage Organizations, Projects, Pipelines, Users, Goals, Filters" lists several specific concrete resources the skill operates on, with only minor verb/action gaps (a single "Manage" verb covers all objects).	4 / 5
Completeness	It states both what ("Manage Organizations, Projects, Pipelines, Users, Goals, Filters") and when ("Use when the user wants to interact with Gryd data"), though the when clause is somewhat generic.	4 / 5
Trigger Term Quality	The trigger "Use when the user wants to interact with Gryd data" offers the brand keyword but misses common variations or synonyms, paralleling the "Works with PDF files" anchor.	3 / 5
Distinctiveness Conflict Risk	Tying triggers to the branded "Gryd" platform gives it a clear niche with minimal conflict risk, though the generic "interact with data" phrasing leaves minor overlap with other data skills.	4 / 5
	Total	15 / 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/gryd/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.