CtrlK
BlogDocsLog inGet started
Tessl Logo

sheetdb

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

62

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/sheetdb/SKILL.md
SKILL.md
Quality
Evals
Security

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 content is highly actionable with concrete CLI commands and a strong connection-state feedback loop, and is well-organized into clear sections. Main gaps are minor over-explanation in the intro and an unlabeled "Step 2" reference.

Suggestions

Label the post-connection section as "Step 2" (or remove the "skip to Step 2" forward references) so the polling/search/run sequence is unambiguous.

Trim the introductory product pitch ("SheetDB turns Google Sheets into a JSON API... It's useful for simple data storage and retrieval needs") to the minimum needed for orientation.

Add a brief validation note for mutating actions (e.g. confirm a record id before update/delete) since `membrane action run` can perform destructive operations.

DimensionReasoningScore

Conciseness

The body is largely efficient with concrete commands, but contains minor over-explanation such as "It's useful for simple data storage and retrieval needs" and the introductory product pitch that could be trimmed, fitting the efficient-with-minor-trimming anchor.

4 / 5

Actionability

It provides fully executable, copy-paste-ready commands throughout (install, login, connection ensure, action list/run, request) plus a flags table, matching the fully-executable anchor covering the common cases.

5 / 5

Workflow Clarity

There is a clear install→login→connect→poll→search→run sequence with explicit state-checkpoint feedback (READY/BUILDING/CLIENT_ACTION_REQUIRED), but the "Step 2" reference is not clearly labeled and there is no validation guidance for potentially destructive data-mutating actions.

4 / 5

Progressive Disclosure

No bundle files exist, so all content lives in SKILL.md, but it is organized into clearly headed sections with no nested references; the single-file monolith is a minor organization gap rather than a structural problem.

4 / 5

Total

17

/

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 is well-targeted to a specific product with an explicit use-when clause, but its capability verbs are generic and its trigger coverage is limited to a single phrase. Tightening the actions and adding common synonyms would raise it.

Suggestions

Replace generic verbs with concrete SheetDB-specific actions, e.g. "Read, write, and update records in SheetDB spreadsheets" instead of "Manage data, records, and automate workflows".

Expand the trigger clause to cover natural phrasings users say, e.g. "Use when the user wants to read, write, or update SheetDB data, or interact with a Google Sheet via the SheetDB API."

DimensionReasoningScore

Specificity

The description lists several actions ("Manage data, records, and automate workflows") but they are generic rather than concrete, sitting between the single-action score-2 anchor and the concrete-actions score-3 anchor.

3 / 5

Completeness

It has a clear "what" (SheetDB integration; manage data/records/workflows) and an explicit "Use when..." trigger, but the "when" is a single trigger rather than the comprehensive list the score-5 anchor requires.

4 / 5

Trigger Term Quality

It includes relevant keywords ("SheetDB", "data", "records", "workflows") but misses natural variations a user might say such as "Google Sheets" or "spreadsheet", matching the some-keywords-but-missing-synonyms anchor.

3 / 5

Distinctiveness Conflict Risk

Naming the specific product "SheetDB" with a distinct trigger ("interact with SheetDB data") gives it a clear niche with minimal overlap risk, matching the score-5 anchor.

5 / 5

Total

15

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
Reviewed

Table of Contents

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.