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

Blog Docs Log in Get started

glide

Glide integration. Manage Applications. Use when the user wants to interact with Glide data.

Quality

67%

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/glide/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 concrete CLI commands and a clear connection state machine, but it explains concepts Claude already knows and exposes destructive row operations without verification steps. Trimming the intro and adding pre-flight checks for deletes/updates would lift the two mid scores.

Suggestions

Remove or condense the opening "Glide is a no-code platform..." paragraph and the vague "Use action names and parameters as needed." line; assume Claude knows what a no-code platform is.

Add a validation checkpoint before destructive operations — e.g. query the target row to confirm identity before running delete-single-row or update-single-row, or dry-run via the proxy first.

Dimension	Reasoning	Score
Conciseness	Most of the body is tight, executable commands, but the opening paragraph explains what Glide is (general knowledge) and filler like "When to use which actions: Use action names and parameters as needed." adds padding, fitting the mostly-efficient-but-could-be-tightened anchor (3) rather than fully lean (5).	3 / 5
Actionability	It provides copy-paste-ready commands throughout (install, login, connection ensure, action list/run, request) plus a popular-actions table with concrete keys, covering the common cases and matching the fully-executable anchor (5) rather than mostly-executable-with-gaps (4).	5 / 5
Workflow Clarity	The connect→poll→search→run sequence is clear with state-based feedback loops (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but destructive row actions (delete/update) are surfaced without any verify-before-commit guidance, and the rubric caps destructive/batch workflows without validation at 3.	3 / 5
Progressive Disclosure	The single file is well-organized into clear sections (Overview, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices) with no bundle files to over-nest, but it is over 50 lines with detailed material (the connection state machine, full proxy flag table) inlined, fitting good-structure-minor-gaps (4) rather than the ideal overview-pointing-to-references (5).	4 / 5
	Total	15 / 20 Passed

Description

66%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 pairs a what and an explicit when clause and names a distinct platform, but its action vocabulary is generic. Listing concrete Glide operations (query/add/update/delete rows, tables, apps) would sharpen both specificity and trigger-term coverage.

Suggestions

Replace the generic "Manage Applications" with concrete operations a user would request, e.g. "Query, add, update, and delete rows in Glide tables and list Glide apps".

Add natural trigger phrases users actually say — "Glide apps", "Glide tables", "spreadsheet-backed apps" — alongside "interact with Glide data".

Dimension	Reasoning	Score
Specificity	The description names the Glide domain and two action phrases ("Manage Applications", "interact with Glide data"), but both are generic rather than concrete operations like query/add/update rows, so it lands between the generic-actions anchor (2) and the 1-2-concrete-actions anchor (3).	3 / 5
Completeness	Both halves are present — a what ("Glide integration. Manage Applications.") and an explicit when ("Use when the user wants to interact with Glide data."), but the what is somewhat generic so it fits the both-present-but-could-be-more-specific anchor (4) rather than the fully-concrete anchor (5).	4 / 5
Trigger Term Quality	It surfaces "Glide", "Applications", and "Glide data", which are relevant keywords, but it omits common variations users would actually say ("Glide apps", "Glide tables", spreadsheets), matching the some-keywords-but-missing-synonyms anchor (3) rather than the comprehensive anchor (5).	3 / 5
Distinctiveness Conflict Risk	"Glide" names a specific no-code platform with a distinct trigger ("interact with Glide data"), giving it a clear niche with minimal overlap risk, matching the clear-niche-minimal-conflict anchor (5); it is not merely "mostly distinct" (4) because the platform name is fully specific.	5 / 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/glide/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.