Name: sheety
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

sheety

Sheety integration. Manage data, records, and automate workflows. Use when the user wants to interact with Sheety data.

Quality

66%

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

Quality

Content

75%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 a well-structured, command-driven integration guide with executable CLI examples and a strong validation loop for the connection step. Its weaknesses are inconsistent step numbering, a redundant section, lack of any concrete Sheety-specific action example, and no validation guidance on the (potentially destructive) proxy path.

Suggestions

Add at least one concrete Sheety-specific action example (e.g. listing or adding a row) with realistic values so users see an end-to-end case beyond generic Membrane syntax.

Fix the step numbering (label the connection section 'Step 1' to match the referenced 'Step 2', or remove the orphaned references) and merge the redundant 'Popular actions' section into 'Searching for actions'.

Add a validation/verification checkpoint for the proxy path when destructive methods (DELETE/PUT/PATCH) are used, e.g. 'GET the resource before mutating and confirm the affected id' to satisfy the destructive-operation feedback-loop expectation.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and command-focused, with only minor padding such as the product line 'Sheety turns anything into an API...' and rationale like 'burn less tokens'; it is not 5 because a few explanatory/marketing phrases could be trimmed.	4 / 5
Actionability	It provides concrete, executable commands (install, login, connection ensure, action list/run, request) plus a flag table; it is not 5 because only generic Membrane syntax is shown with no concrete Sheety-specific action example, and placeholders like CONNECTION_ID limit copy-paste readiness.	4 / 5
Workflow Clarity	The install->auth->connect->search->run sequence is clear and includes an explicit validation feedback loop for the connection state machine (READY/CLIENT_ACTION_REQUIRED/ERROR with polling); it is not 5 due to inconsistent step numbering (orphaned 'Step 2', a '1b' with no '1a'), the redundant 'Popular actions' section, and missing validation guidance on the proxy path that enables destructive methods.	4 / 5
Progressive Disclosure	No bundle files exist, but the body is self-contained and organized into clear, navigable sections; it is not 5 because there is no file-level disclosure and minor redundancy ('Popular actions' repeats 'Searching for actions').	4 / 5
	Total	16 / 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 is well-formed: third-person, names the domain, and includes an explicit Use-when trigger clause. Its main weakness is generic action verbs ('manage data, records, automate workflows') that lack concrete, specific capabilities, and a single general trigger phrase rather than multiple natural trigger terms.

Suggestions

Replace generic verbs with concrete Sheety-specific actions, e.g. 'Create, read, update, and delete rows in Sheety spreadsheets via their API.'

Expand the trigger clause with natural variations users would say, e.g. 'Use when the user wants to query, add, update, or delete rows in a Sheety-backed sheet, or automate workflows over Sheety data.'

Mention the underlying artifact type ('Google Sheets as a database') in the description so the trigger is distinguishable from generic data skills.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Sheety integration') and lists actions ('Manage data, records, and automate workflows'), but those verbs/nouns are generic rather than concrete (e.g. not 'extract text, fill forms'), matching the anchor where actions are minimal or generic; not a 3 because none of the actions are concrete.	2 / 5
Completeness	Both 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when...') are present, and the explicit Use-when clause avoids the cap at 3; it is not 5 because the trigger is a single general phrase rather than multiple concrete trigger phrases.	4 / 5
Trigger Term Quality	'Use when the user wants to interact with Sheety data' supplies the natural brand keyword 'Sheety' with 'data' support, but coverage lacks synonyms or variations, fitting 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	The 'Sheety' brand name gives a clear niche with minimal conflict risk, but the generic 'manage data, automate workflows' verbs create minor overlap with general data/automation skills, so it is not 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/sheety/SKILL.md
Commit: f484c82

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