Name: formstack
Rating: 58.4 (1 reviews)
Author: membranedev

formstack

Formstack integration. Manage Forms, Users, Roles, Groups, Folders, Themes and more. Use when the user wants to interact with Formstack data.

Quality

67%

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

Quality

Content

61%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 concrete commands and a strong connection-setup state machine, but loses points for an unnecessary marketing intro, a missing destructive-operation validation step, and the absence of any progressive file-splitting.

Suggestions

Trim the opening marketing paragraph ("Formstack is an online form builder... improve customer experiences") and prose filler; Claude does not need the product pitch.

Add a validation/verification checkpoint before destructive actions (e.g., confirm the form/submission ID and verify the result after Delete/Update) so the destructive workflow clears the validation cap.

Wire one concrete end-to-end example that ties an action key from the catalog (e.g. list-forms) into the run command with a real-shaped input, replacing the generic {"key":"value"} placeholder.

Dimension	Reasoning	Score
Conciseness	The bulk is dense, useful commands and tables, but the opening marketing paragraph ("online form builder... businesses of all sizes... streamline workflows, and improve customer experiences") and prose asides like "focus on the integration logic rather than auth plumbing" explain concepts Claude does not need.	3 / 5
Actionability	Provides many copy-paste-ready commands with real flags (install, login, connection ensure, action list/run, proxy) plus a 20-row action catalog and a proxy flag table, with only minor gaps such as placeholders (<actionId>, CONNECTION_ID) not wired into a concrete end-to-end example and a generic {"key":"value"} input sample.	4 / 5
Workflow Clarity	The connection setup has an excellent state-machine sequence with polling and feedback loops (READY / CLIENT_ACTION_REQUIRED / error states), but the skill exposes destructive operations (Delete Form, Delete Submission, Update Form) with no validation or verification guidance, which caps workflow clarity at 3 per the destructive-operations rule.	3 / 5
Progressive Disclosure	No bundle files exist and all content is inline, but it is well-organized into clearly headed sections (Install, Authentication, Connecting, Searching, Popular actions, Running, Proxy, Best practices); the inline 20-row action catalog is an acceptable quick-reference rather than a monolithic wall, though no content is split into separate files.	4 / 5
	Total	14 / 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 product-specific and clearly answers both what and when, with good natural keyword coverage, but is held back by a single generic action verb, vague "and more" padding, and a generic when clause.

Dimension	Reasoning	Score
Specificity	Names six concrete Formstack resources ("Forms, Users, Roles, Groups, Folders, Themes") but applies a single generic verb ("Manage") and pads with vague "and more", so it lists concrete nouns rather than multiple distinct actions, fitting the domain-plus-concrete-anchor rather than the several-actions anchor.	3 / 5
Completeness	Explicitly answers both what ("Manage Forms, Users, Roles, Groups, Folders, Themes and more") and when ("Use when the user wants to interact with Formstack data"), but the when clause is generic rather than concrete trigger phrases.	4 / 5
Trigger Term Quality	Includes natural terms users would say ("Formstack", "Forms", "Folders", "Themes") and an explicit trigger clause, but omits major concepts shown in the body ("Submissions", "Webhooks") and the trigger phrasing "interact with Formstack data" is somewhat generic.	4 / 5
Distinctiveness Conflict Risk	"Formstack" is a specific named product with triggers tied to Formstack data, giving it a clear niche with minimal overlap risk against other 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/formstack/SKILL.md
Commit: f484c82

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