Name: smartsuite
Rating: 60.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

smartsuite

Smartsuite integration. Manage Organizations. Use when the user wants to interact with Smartsuite data.

Quality

71%

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/smartsuite/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 content is highly actionable, full of copy-paste Membrane CLI commands, and the connection workflow has solid state-based validation checkpoints. It is held back by an unnecessary product-explainer opener and vague filler that hurt conciseness, and by the absence of verification guidance for destructive record operations that caps workflow clarity.

Suggestions

Delete the opening paragraph explaining what SmartSuite is and the filler line "When to use which actions: Use action names and parameters as needed." to improve conciseness.

Add a verification step before destructive actions, e.g. run get-record to confirm the target before delete-record, and show how to inspect the action output to confirm success.

Move the Popular actions table and the proxy flag reference into separate reference files (e.g. ACTIONS.md, PROXY.md) and link them one level deep from the overview.

Dimension	Reasoning	Score
Conciseness	Most of the body is lean commands and tables, but it opens by explaining what SmartSuite is ("a work management platform that combines project management, CRM, and database functionalities...") and includes vague filler ("When to use which actions: Use action names and parameters as needed."), fitting anchor 3 (mostly efficient with some unnecessary explanation); it is below 4 due to these padded/over-explained passages and above 2 because the bulk is genuinely tight.	3 / 5
Actionability	The body provides fully executable, copy-paste-ready commands for every common case (install, login, connection ensure/get, action list, action run with JSON input, proxy request) plus a concrete actions table with keys and descriptions, matching anchor 5.	5 / 5
Workflow Clarity	The connection setup is clearly sequenced with explicit state-based checkpoints (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and a re-poll feedback loop, but the skill exposes destructive actions (delete-record, update-record) with no verification step before execution, so the destructive-operations cap holds workflow clarity at anchor 3.	3 / 5
Progressive Disclosure	The single SKILL.md is organized into well-labeled sections (Overview, Install, Authentication, Connecting, Searching, Popular actions, Running actions, Proxy, Best practices) with no nested references and easy navigation, matching anchor 4; it does not reach 5 because the inline Popular actions table and proxy flag reference are content that could be split out for a >50-line skill.	4 / 5
	Total	15 / 20 Passed

Description

73%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 third-person, includes an explicit "Use when..." trigger, and names the specific Smartsuite product, giving it strong distinctiveness and decent completeness. Its main weakness is thin specificity and trigger breadth, naming only "Manage Organizations" rather than the tables/records/solutions operations the skill covers.

Suggestions

Replace the single "Manage Organizations" action with the concrete operations the skill supports, e.g. "Manage Smartsuite solutions, tables, records, and views."

Broaden the trigger phrase with natural user phrasings, e.g. "Use when the user wants to list, create, update, or delete Smartsuite records and tables."

Add the .smartsuite.com domain or "SmartSuite CRM/work management" terms to capture more natural search phrasings.

Dimension	Reasoning	Score
Specificity	The description names the Smartsuite domain and one concrete action ("Manage Organizations"), but stops there rather than listing the tables/records/solutions/view operations the skill actually supports, fitting anchor 3 (domain + 1-2 concrete actions, not comprehensive); it is above anchor 2 because a real entity action is named, and below 4 because coverage is a single generic-verb action.	3 / 5
Completeness	It provides both a "what" ("Smartsuite integration. Manage Organizations.") and an explicit "when" ("Use when the user wants to interact with Smartsuite data."), matching anchor 4; it does not reach 5 because the trigger phrase is broad ("interact with Smartsuite data") rather than enumerating concrete trigger scenarios.	4 / 5
Trigger Term Quality	"Smartsuite" and "interact with Smartsuite data" give good natural-keyword coverage of the product name a user would actually say; it sits below anchor 5 because no synonyms or entity-level terms (records, tables, CRM) are included, and above 3 because the core product trigger is stated naturally.	4 / 5
Distinctiveness Conflict Risk	Smartsuite is a specific named product, so "Smartsuite integration" establishes a clear niche with distinct triggers and minimal conflict risk against other skills, matching anchor 5.	5 / 5
	Total	16 / 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/smartsuite/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.