Name: google-appsheet
Rating: 55.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

google-appsheet

Google Appsheet integration. Manage Apps. Use when the user wants to interact with Google Appsheet data.

Quality

61%

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

Quality

Content

61%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 delivers concrete, mostly executable CLI guidance in a well-organized single file, but it explains concepts Claude already knows and lacks validation checkpoints for potentially destructive operations.

Suggestions

Remove the introductory paragraph defining AppSheet and trim marketing prose like 'so you can focus on the integration logic rather than auth plumbing'.

Add a verification step after `connect` (e.g. confirm the connection appears in `connection list --json`) and a validate-after-run note for destructive `action run`/proxy POST/DELETE operations to lift the workflow_clarity cap.

Provide one fully worked end-to-end example with real-looking IDs to bridge the placeholder gap in actionability.

Dimension	Reasoning	Score
Conciseness	The body is mostly tight CLI snippets, but the opening paragraph explains what AppSheet is (a concept Claude already knows) and includes marketing prose like 'so you can focus on the integration logic rather than auth plumbing', fitting 'mostly efficient but includes some unnecessary explanation' rather than the lean score 4.	3 / 5
Actionability	Concrete, copy-pasteable CLI commands with exact flags (--connectorId, --connectionId, --input, --json) and extraction hints like output.items[0].element?.id are provided, but ACTION_ID/CONNECTION_ID placeholders require substitution and no fully worked end-to-end example exists, matching 'mostly executable guidance with minor gaps' rather than the fully copy-paste-ready score 5.	4 / 5
Workflow Clarity	The login -> connect -> action list -> action run/proxy sequence is clearly ordered with headers, but there are no validation checkpoints (e.g. verifying a connection succeeded) for operations that can be destructive or batch (action run, proxy POST/DELETE); per the rubric this caps workflow clarity at 3 even though the sequence is otherwise solid.	3 / 5
Progressive Disclosure	The single-file SKILL.md is well-organized with clear section headers and no nested references, but the body exceeds the ~50-line simple-skill threshold and some inline content (the proxy flag table, best practices) could be factored out, fitting 'good structure with minor organization gaps' rather than the ideal score 5.	4 / 5
	Total	14 / 20 Passed

Description

61%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 answers both what and when with an explicit trigger tied to the distinct Google AppSheet product name, but its capability statement ('Manage Apps') is vague and trigger keyword coverage is limited to the brand name.

Suggestions

Replace 'Manage Apps' with concrete capabilities, e.g. 'Create and manage AppSheet apps, query tables, and read/write rows.'

Expand the 'Use when' clause with common natural phrasings users say, such as 'AppSheet apps, tables, rows, or app data'.

Add a synonym or related term (e.g. 'AppSheet tables and rows') so the trigger matches more user phrasings.

Dimension	Reasoning	Score
Specificity	The description names the domain and one action via 'Manage Apps.' but 'Manage Apps' is generic rather than a concrete capability (no mention of tables, rows, or specific operations), matching the 'names the domain but actions are minimal or generic' anchor rather than the 1-2 concrete actions of score 3.	2 / 5
Completeness	Both 'what' ('Google Appsheet integration. Manage Apps.') and an explicit 'when' ('Use when the user wants to interact with Google Appsheet data.') are present, but the 'what' is somewhat vague and the 'when' could be more specific, matching the score-4 anchor rather than the comprehensive both-answered score 5.	4 / 5
Trigger Term Quality	'Google Appsheet' and 'Appsheet data' are the natural product-name keywords a user would say, but coverage is thin with no synonyms or variations beyond the brand name, fitting 'some relevant keywords but missing common variations or synonyms' rather than the fuller coverage of score 4.	3 / 5
Distinctiveness Conflict Risk	The description is tightly bound to the 'Google Appsheet' product name, giving it a clear niche with distinct triggers and minimal overlap risk with other skills, matching the score-5 anchor.	5 / 5
	Total	14 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: membranedev/application-skills
Path: skills/google-appsheet/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.