Name: formcan
Rating: 56.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

formcan

FormCan integration. Manage Forms, Users, Roles. Use when the user wants to interact with FormCan data.

Quality

65%

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

Quality

Content

65%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 copy-paste-ready commands and a clear connection workflow, but it suffers from inlined reference bulk and lacks validation checkpoints around its destructive actions. Splitting the action/flag tables into a reference file and adding verify steps before deletes would improve both conciseness and workflow clarity.

Suggestions

Move the popular-actions and proxy-flags tables into a separate reference file (e.g. references/actions.md) and link to it from the body, keeping only a few key examples inline.

Add a verification step before destructive actions, e.g. retrieve the submission with get-submission and confirm with the user before running delete-submission.

Trim the opening overview paragraph ("FormCan is a form builder application..." / "It's typically used by businesses...") since Claude can infer the app's purpose; lead with the integration mechanics.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable commands, but it opens with an unnecessary overview sentence ("It's typically used by businesses and organizations to collect data...") and inlines a ~20-row popular-actions table and a proxy-flags table that could be trimmed or split, matching the anchor for mostly efficient content with some unnecessary explanation.	3 / 5
Actionability	Commands are fully executable and copy-paste ready ("membrane connection ensure", "membrane action run <actionId> --input '{...}'", "membrane request CONNECTION_ID /path"), with flag tables and JSON-input examples covering the common cases, matching the anchor for fully executable guidance.	5 / 5
Workflow Clarity	The connection flow is well-sequenced with explicit state branching (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and recovery, but destructive actions (delete-submission, delete-webhook) appear with no validation or verification checkpoint, which per the rubric caps workflow clarity at 3 even though the connection sequence is strong.	3 / 5
Progressive Disclosure	No bundle files exist, so all content is inline; section headers provide structure, but the large popular-actions and proxy-flags tables are bulk reference material inlined in SKILL.md rather than split into a separate file, matching the anchor where structure exists but content that should be separate is inline.	3 / 5
	Total	14 / 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-structured with explicit what/when guidance and a clearly distinct niche, but its trigger language and action verbs are generic. Tightening "Manage" into concrete verbs and "interact with FormCan data" into natural user phrases would raise specificity and trigger quality.

Suggestions

Replace the generic verb "Manage" with concrete actions, e.g. "Create and list forms, retrieve and update submissions, manage webhooks and roles."

Make the trigger phrase natural and specific, e.g. "Use when the user wants to create forms, view submissions, or manage FormCan users and roles."

Add common synonyms or file references users might mention (e.g. "form submissions", "form invitations", "form webhooks") to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	"Manage Forms, Users, Roles" names the domain and three entity areas, but the verb "Manage" is generic rather than enumerating concrete actions, fitting the anchor that lists domain and 1-2 concrete actions but is not comprehensive.	3 / 5
Completeness	It answers both what ("FormCan integration. Manage Forms, Users, Roles.") and when ("Use when the user wants to interact with FormCan data"), but the when clause is somewhat generic rather than concrete trigger phrases, fitting the anchor where both are present but when could be more specific.	4 / 5
Trigger Term Quality	"Forms, Users, Roles" and "FormCan" are relevant domain keywords with an explicit "Use when..." trigger, but "interact with FormCan data" is generic and misses natural synonyms or file extensions, matching the anchor for some relevant keywords with missing variations.	3 / 5
Distinctiveness Conflict Risk	"FormCan integration" names a specific app with a clear niche (forms, users, roles) and an app-specific trigger, giving minimal overlap risk with other skills, matching the anchor for a clear niche with distinct triggers.	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/formcan/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.