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

getform

Getform integration. Manage data, records, and automate workflows. Use when the user wants to interact with Getform 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/getform/SKILL.md

Quality

Content

67%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 delivers concrete, executable Membrane CLI guidance with a solid connection-state workflow, but it carries unnecessary padding and a structural redundancy that hold it back from the top tier. Step numbering is slightly incoherent.

Suggestions

Remove the marketing intro paragraph ("Getform is a form backend platform...") and the empty "Getform Overview" bullet tree; Claude does not need the product background.

Merge the redundant "Popular actions" section into "Searching for actions" so the action-list command appears once.

Fix the step numbering so references to "Step 2" and "1b" map to explicitly labeled headers, making the connection-to-action flow unambiguous.

Dimension	Reasoning	Score
Conciseness	The CLI guidance is mostly efficient, but the marketing-style intro paragraph, the near-empty "Getform Overview" tree, and the redundant "Popular actions" section add tokens Claude does not need.	3 / 5
Actionability	Concrete, executable commands appear throughout (connection ensure, action run, request with a full flag table); the only gaps are placeholders like CONNECTION_ID and --intent "QUERY" that require substitution.	4 / 5
Workflow Clarity	The install→auth→connect→poll→search→run sequence is clear with a strong state-machine feedback loop (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), though the step numbering references unlabeled "Step 2" and "1b" headers.	4 / 5
Progressive Disclosure	Sections are well organized and a single file is appropriate for this CLI skill with no bundle files, but the redundant Popular actions section and thin Overview leave minor organization gaps.	4 / 5
	Total	15 / 20 Passed

Description

62%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 functional with a clear brand anchor and an explicit Use-when clause, but its action verbs are generic and its trigger terms lack natural synonyms. It answers what and when without being distinctive enough to score higher.

Suggestions

Replace the generic verbs ("Manage data, records, and automate workflows") with concrete Getform capabilities such as creating forms, retrieving and listing submissions, deleting submissions, and configuring form webhooks.

Add natural trigger phrases users actually say alongside "Getform data", such as form submissions, form backend, and collect form responses.

Dimension	Reasoning	Score
Specificity	Names the domain (Getform) and lists 2-3 actions ("Manage data, records, and automate workflows"), but the actions are generic rather than concrete Getform capabilities like creating forms or retrieving submissions.	3 / 5
Completeness	Both a "what" (Getform integration, manage data/records/workflows) and an explicit "when" ("Use when the user wants to interact with Getform data") are present, though the when-clause is generic rather than specific.	4 / 5
Trigger Term Quality	Relevant keywords (Getform, data, records, workflows) are present but common natural variations a user might say (form submissions, form backend, collect form responses) are missing.	3 / 5
Distinctiveness Conflict Risk	The Getform brand anchor makes the skill mostly distinct with minimal conflict risk, though the generic action verbs leave minor overlap with other data-collection skills.	4 / 5
	Total	14 / 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/getform/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.