Name: smartsheet
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

smartsheet

Smartsheet integration. Manage Sheets. Use when the user wants to interact with Smartsheet data.

Quality

63%

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/smartsheet/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 content delivers concrete, executable Membrane CLI commands with a clear connection/state workflow, but it carries padding (a marketing intro and a useless all-"No description" action table) and omits validation checkpoints around destructive and batch operations. It is a solid, mostly actionable single-file skill with room to tighten and to safeguard risky actions.

Suggestions

Remove the marketing intro paragraph and either drop the Popular actions table or populate its descriptions, since 20 rows of "No description" waste tokens.

Add explicit validation/verification steps for destructive and batch actions (e.g., confirm before delete-sheet/delete-rows, verify row counts after add-rows/update-rows) to lift workflow clarity above the 3 cap.

Consider splitting the large action table and proxy flag reference into a references/ file so the SKILL.md overview stays lean and signals one-level-deep detail.

Dimension	Reasoning	Score
Conciseness	The operational CLI commands are tight, but the marketing intro ("dynamic work and project management platform... launch new ideas fast") and the 20-row Popular actions table whose every description is "No description" are unnecessary padding Claude doesn't need, fitting the 'mostly efficient but includes some unnecessary explanation' anchor.	3 / 5
Actionability	Provides concrete, copy-paste-ready commands (npm install, membrane login, connection ensure, action run, request) plus a flags table, but minor gaps remain—placeholders need substitution and the "No description" table leaves action semantics unclear, keeping it just below fully executable 5.	4 / 5
Workflow Clarity	The connect flow is well-sequenced with state polling checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED), but destructive (delete-sheet, delete-rows) and batch operations (add-rows, update-rows) lack validation/verification steps; per the rubric this caps workflow clarity at 3.	3 / 5
Progressive Disclosure	The single-file body is well-organized into clear sections (Install, Auth, Connecting, Searching, Running, Proxy, Best practices), but at ~170 lines with a large inlined action table and flag tables and no reference layer to split into, it shows minor organization gaps rather than the ideal overview→reference split of a 5.	4 / 5
	Total	14 / 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 clearly identifies the Smartsheet niche and includes an explicit 'Use when' trigger, but it is thin on concrete capabilities (only 'Manage Sheets') and lacks synonyms or richer trigger phrases. It is distinctive but not comprehensive.

Suggestions

Expand the action list in the description beyond 'Manage Sheets' to concrete verbs (e.g., create/update sheets, add rows, manage workspaces) to lift specificity.

Add natural trigger variations and synonyms such as 'sheets', 'spreadsheets', 'rows', or 'Smartsheet workspaces' to improve trigger-term coverage.

Make the 'when' clause more concrete by naming specific user intents (e.g., 'Use when the user wants to list, create, or update Smartsheet sheets and rows').

Dimension	Reasoning	Score
Specificity	Names the domain ("Smartsheet integration") and one concrete action ("Manage Sheets"), matching the '1-2 concrete actions but not comprehensive' anchor; it falls short of 4 which requires several specific actions.	3 / 5
Completeness	Both 'what' ("Smartsheet integration. Manage Sheets.") and 'when' ("Use when the user wants to interact with Smartsheet data.") are present with an explicit trigger clause, but neither is maximally concrete, so it sits above 3 yet below the 5 anchor's concrete multi-trigger phrasing.	4 / 5
Trigger Term Quality	"Smartsheet" and "interact with Smartsheet data" are relevant natural keywords, but common variations/synonyms (sheets, spreadsheets, rows, columns) are missing, fitting the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	"Smartsheet integration" names a specific, distinct product niche with minimal conflict risk against other skills, matching the 'clear niche with distinct triggers' anchor.	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/smartsheet/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.