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

appsmith

Appsmith integration. Manage data, records, and automate workflows. Use when the user wants to interact with Appsmith 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/appsmith/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 body is highly actionable with executable commands and a solid connection state-machine workflow. It loses points mainly to an unnecessary conceptual intro paragraph and inline API-reference material that a separate reference file would absorb.

Suggestions

Trim the opening paragraph that explains what Appsmith is and who uses it; Claude knows this, and the official-docs link already suffices.

Fix step numbering so 'Step 1'/'Step 2' referenced in the connection flow are explicitly labeled, and reconcile the orphan '#### 1b' heading.

Move the clientAction object field breakdown and the proxy options table into a dedicated references file, signaling it clearly from the main body.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient command-and-table content, but the opening conceptual paragraph explaining what Appsmith is and the auth-plumbing framing are padding Claude does not need.	3 / 5
Actionability	Copy-paste-ready, executable commands cover the full path from install and auth through connecting, searching, running actions, and proxying, with real flags and a complete options table.	5 / 5
Workflow Clarity	The connection flow has explicit state handling and a real poll -> user-acts -> poll-again feedback loop, but step numbering is inconsistent ('skip to Step 2' and '1b' without a labeled Step 1/2).	4 / 5
Progressive Disclosure	Content is organized into clear, well-scoped sections with no broken or nested references, but reference-like material (the clientAction field breakdown and proxy options table) is inlined and no external reference files are signaled.	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 covers both what the skill does and when to use it, anchored on a distinctive product name. Its main weakness is generic action verbs rather than concrete Appsmith-specific capabilities and limited trigger-term variety.

Suggestions

Replace generic verbs ('manage data, records, automate workflows') with concrete Appsmith actions such as 'create apps, build pages, add widgets, run queries, and connect datasources'.

Broaden the 'Use when' clause to cover the workflows the 'what' promises, e.g. 'Use when the user wants to build or modify Appsmith apps, run queries, or automate Appsmith workflows'.

Add a few natural trigger variants (e.g. 'Appsmith apps', 'Appsmith datasources', 'Appsmith queries') so the description matches a wider range of user phrasings.

Dimension	Reasoning	Score
Specificity	Names the Appsmith domain plus three actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete Appsmith capabilities like creating widgets or running queries.	3 / 5
Completeness	Both 'what' ('Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with Appsmith data') are explicitly present, though the 'when' is narrower than the 'what' it promises.	4 / 5
Trigger Term Quality	The natural trigger is the product name 'Appsmith' / 'Appsmith data', which users would actually say, but coverage is limited to the product name with no richer phrases like 'Appsmith apps' or 'datasources'.	3 / 5
Distinctiveness Conflict Risk	Anchored on a distinct product name ('Appsmith integration', 'interact with Appsmith data'), giving it a clear niche with minimal conflict risk against unrelated skills.	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/appsmith/SKILL.md
Commit: f484c82

Reviewed: 3 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.