Name: formdesk
Rating: 62.4 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

formdesk

Formdesk integration. Manage Forms, Users, Themes, Workspaces. Use when the user wants to interact with Formdesk data.

Quality

74%

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/formdesk/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 skill body delivers highly executable CLI guidance with a well-checkpointed connection workflow and clear section structure. Its main weaknesses are mild verbosity in the introductory prose and minor workflow cross-reference inconsistencies, plus a long inline action table that could be split out.

Suggestions

Trim the opening "Formdesk is a web form builder..." paragraph and editorial asides (e.g., "This is the fastest way to get a connection") to reduce token overhead.

Fix the step cross-references: label the connection steps consistently (e.g., "Step 1a"/"Step 1b"/"Step 2") so "skip to Step 2" and the "1b" heading resolve unambiguously.

Consider moving the 20-row Popular actions table into a references file (e.g., ACTIONS.md) with a brief inline pointer, improving progressive disclosure and token budget.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes unnecessary padding such as the opening paragraph explaining what Formdesk is and editorial asides like "This is the fastest way to get a connection," placing it at the mostly-efficient-but-could-be-tightened anchor.	3 / 5
Actionability	Commands like `membrane login --tenant --clientName=<agentType>`, `membrane connection ensure "https://en.formdesk.com/" --json`, and `membrane action run <actionId> --connectionId=CONNECTION_ID --input '{...}' --json` are fully executable, copy-paste ready, and cover the common cases.	5 / 5
Workflow Clarity	The connection setup is clearly sequenced with explicit state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a re-poll feedback loop, but cross-references like "skip to Step 2" and a "1b" heading without a matching labeled Step 1/Step 2 introduce minor sequencing gaps.	4 / 5
Progressive Disclosure	The body is well-organized into clear sections (Install, Authentication, Connecting, Searching, Popular actions, Running actions, Proxy, Best practices) with no bundle files present, though the 20-row inline Popular actions table is content that could arguably live in a separate reference file.	4 / 5
	Total	16 / 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 clearly names a distinct product niche and supplies an explicit "Use when" trigger, but its action language is limited to the single generic verb "Manage" and the trigger phrase is somewhat abstract. It is solid and triggerable, just not maximally vivid.

Suggestions

Replace the generic verb "Manage" with 2-3 concrete actions (e.g., "List, create, and update Forms, Users, Themes, and Workspaces") to lift specificity.

Make the "when" trigger more concrete by adding natural user phrasing such as "Use when the user wants to list forms, retrieve submissions, or manage Formdesk users and workspaces."

Add common synonyms or form-related terms (e.g., "submissions", "form results") so trigger coverage reaches comprehensive.

Dimension	Reasoning	Score
Specificity	"Manage Forms, Users, Themes, Workspaces" names the domain and several concrete entities, but the single generic verb "Manage" is the only action described, which matches the anchor naming a domain with limited concrete actions rather than a list of several specific operations.	3 / 5
Completeness	It states both what ("Manage Forms, Users, Themes, Workspaces") and when ("Use when the user wants to interact with Formdesk data"), but the "when" trigger is somewhat generic rather than a concrete, vivid trigger phrase, matching the anchor for both-present-but-could-be-more-explicit.	4 / 5
Trigger Term Quality	Keywords "Formdesk", "Forms", "Users", "Themes", and "Workspaces" give good coverage of natural terms a user would say, falling just short of comprehensive synonyms/file-extension coverage that would warrant a 5.	4 / 5
Distinctiveness Conflict Risk	"Formdesk integration" with a product-specific trigger ("interact with Formdesk data") carves out a clear niche with minimal risk of firing for unrelated skills.	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/formdesk/SKILL.md
Commit: f484c82

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