Name: seatable
Rating: 64 (1 reviews)
Author: membranedev

seatable

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

Quality

76%

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

Quality

Content

82%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 strong, actionable CLI integration guide with copy-paste commands, a well-branched connection workflow, and clear section organization. Its main weaknesses are a dangling "Step 2" reference, a slightly padded intro, and no validation guidance for destructive action runs.

Suggestions

Resolve the "Step 2" reference by adding an explicit numbered "## Step 2: Search and run actions" heading, or reword the cross-references to use section names.

Trim the conceptual opening paragraph (the Google Sheets/Excel comparison) since it explains background Claude can infer.

Add a brief validation/check step before running actions that could mutate or delete records (e.g. confirm the target table and preview the input), which would also lift workflow_clarity.

Dimension	Reasoning	Score
Conciseness	The body is command-and-code heavy and largely lean, with only minor over-explanation such as the opening "Think of it as a more powerful...alternative to Google Sheets or Excel" framing that could be trimmed.	4 / 5
Actionability	It provides copy-paste-ready commands throughout (install, login, connection ensure, action list/run, request) plus a complete proxy flags table, covering the common cases with fully executable guidance.	5 / 5
Workflow Clarity	The connection flow is clearly sequenced with state-based branching and feedback loops (poll until READY, re-poll after CLIENT_ACTION_REQUIRED), but the dangling "Step 2" reference with no matching heading and absent validation guidance for potentially destructive action runs are minor gaps.	4 / 5
Progressive Disclosure	The single file is well-organized into clearly headed sections (Overview, Authentication, Connecting, Searching, Actions, Proxy, Best practices) that are easy to navigate; a 140-line CLI usage guide reasonably lives in one file, though some inline material (proxy flags, clientAction details) could be split out.	4 / 5
	Total	17 / 20 Passed

Description

70%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 with an explicit Use-when clause and a distinctive named-product trigger, but its action list leans on generic verbs and omits the richer domain vocabulary (base/table/row, spreadsheet, database) that would make it more specific and trigger-rich.

Suggestions

Replace generic verbs with concrete SeaTable actions, e.g. "Create and update bases, tables, and rows; filter and sort records; trigger automations."

Broaden the trigger clause to include natural synonyms: "Use when the user wants to manage SeaTable bases, tables, rows, or spreadsheets, or automate SeaTable workflows."

Add the domain terms (base, table, row, spreadsheet, database) so users phrasing requests in those words reliably hit this skill.

Dimension	Reasoning	Score
Specificity	Names the SeaTable domain and three action areas ("Manage data, records, and automate workflows") but the verbs are generic rather than concrete, so it falls short of the multi-specific-action anchor at 4.	3 / 5
Completeness	Explicitly answers both what ("Manage data, records, and automate workflows") and when ("Use when the user wants to interact with SeaTable data"), but the trigger clause is narrow and could name more concrete invocation scenarios to reach 5.	4 / 5
Trigger Term Quality	Includes natural keywords a user would say ("SeaTable", "data", "records", "workflows") with an explicit trigger phrase, but misses common synonyms like spreadsheet, database, base, table, or row that the body itself uses.	4 / 5
Distinctiveness Conflict Risk	Tying the skill to the named product SeaTable gives it a clear, distinct trigger, but the generic "manage data, records" actions carry minor overlap risk with broader data-handling skills.	4 / 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/seatable/SKILL.md
Commit: f484c82

Reviewed: ~20 hours 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.