Name: gigasheet
Rating: 60 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

gigasheet

Gigasheet integration. Manage Workbooks, Users, Teams, Shares. Use when the user wants to interact with Gigasheet data.

Quality

70%

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/gigasheet/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 content is highly actionable with copy-paste-ready commands and a clear state-driven connection workflow including feedback loops. Its weak spots are a padded intro paragraph, inconsistent step numbering, and a lack of progressive splitting of reference-heavy material into separate files.

Suggestions

Trim the introductory paragraph and the awkward agent-types sentence ("Those will be used to adjust tooling to be used best with your harness") to remove over-explanation and tighten conciseness toward anchor 4.

Fix the step labeling: define an explicit "Step 1"/"Step 2" structure and relabel or remove the orphaned "1b" heading so the connection workflow sequence is unambiguous.

Move the full popular-actions catalog and proxy flag reference table into separate one-level-deep reference files (e.g. ACTIONS.md, PROXY.md) to improve progressive disclosure toward anchor 5.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean command-driven content, but the intro paragraph over-explains what Gigasheet is ("used by data analysts, marketers, and researchers who need to work with large datasets that exceed the limits of traditional spreadsheets") and the agent-types sentence is padded, matching anchor 3 rather than 4.	3 / 5
Actionability	Copy-paste-ready commands with concrete flags appear throughout (install, login, connection ensure, action run with --input JSON, proxy request), backed by a real action-key table and a proxy flag table covering common cases, matching anchor 5.	5 / 5
Workflow Clarity	The connection lifecycle has a clear state-driven sequence with explicit checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a re-poll feedback loop, but step labeling is inconsistent — "Step 2" is referenced but never defined and "1b" has no "1a" — keeping it at anchor 4.	4 / 5
Progressive Disclosure	The single-file body is well-organized into clear sections with a popular-actions table and a proxy flag table and contains no nested or buried references, but the action catalog and proxy flag reference could be split into one-level reference files rather than fully inline, so it is anchor 4 not 5.	4 / 5
	Total	16 / 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 cleanly answers both what the skill does and when to use it, anchored to a distinctive product name. Its main weakness is generic action verbs and a single narrow trigger phrase rather than broader keyword coverage.

Suggestions

Replace the generic verb "Manage" with specific concrete actions (e.g., "Create and filter Workbooks, manage Users, Teams, and Shares") to lift specificity toward anchor 4-5.

Broaden the trigger phrase to include natural synonyms a user might say, e.g. "Use when the user wants to work with Gigasheet spreadsheets, datasets, workbooks, or big-data files."

Add concrete when-triggers tied to file types or tasks (e.g. filtering, exporting, sharing datasets) so completeness can reach anchor 5.

Dimension	Reasoning	Score
Specificity	The description names the domain and several concrete objects ("Manage Workbooks, Users, Teams, Shares") but the verb "Manage" is generic rather than listing discrete actions, so it sits between anchor 3 and 4 — concrete nouns present, actions not comprehensive.	3 / 5
Completeness	Both the "what" ("Gigasheet integration. Manage Workbooks, Users, Teams, Shares.") and the "when" ("Use when the user wants to interact with Gigasheet data.") are explicit, but the trigger is a single generic phrase rather than multiple concrete triggers, so it is anchor 4 not 5.	4 / 5
Trigger Term Quality	"Gigasheet" is the natural product keyword a user would say, and "interact with Gigasheet data" is a natural when-clause, but common synonyms like spreadsheets, datasets, or big data are missing as triggers, matching anchor 3.	3 / 5
Distinctiveness Conflict Risk	"Gigasheet" is a unique product name that establishes a clear niche with minimal conflict risk against other skills, matching the anchor 5 example of distinct triggers tied to a specific product.	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/gigasheet/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.