Name: jotform
Rating: 59.2 (1 reviews)
Author: membranedev

jotform

Jotform integration. Manage data, records, and automate workflows. Use when the user wants to interact with Jotform data.

Quality

68%

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

Quality

Content

76%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 executable commands and a clear connection workflow including polling checkpoints, but it omits validation guidance for destructive actions and inlines a large actions table that could be split out.

Suggestions

Add a pre-flight verification step before destructive commands (e.g. re-fetch the form/submission and confirm with the user before running delete-form/delete-submission).

Trim the opening paragraph that defines what Jotform is — Claude already knows this — and keep only integration-relevant context.

Consider moving the full popular-actions catalog to a references file and keeping only the handful most relevant inline.

Dimension	Reasoning	Score
Conciseness	The body is command- and table-heavy and mostly lean, but opens by explaining what Jotform is ('an online form builder that allows users to create custom forms...') and includes a few prose asides Claude could do without, fitting 'efficient; minor instances of over-explanation that could be trimmed'.	4 / 5
Actionability	It provides copy-paste-ready commands throughout (install, login, connection ensure/get, action list/run, request with full flag tables) plus a concrete actions table with keys, matching 'fully executable; copy-paste ready commands covering common cases'.	5 / 5
Workflow Clarity	The connection flow is well sequenced with explicit state polling and feedback loops (READY/BUILDING/CLIENT_ACTION_REQUIRED), but the skill exposes destructive actions (delete-form, delete-submission, delete-folder, delete-webhook) with no validation or verification guidance, so the destructive-operation cap holds it at 3.	3 / 5
Progressive Disclosure	It is a single, well-organized file with clear section headers and no nested references (good), but the large inline popular-actions table is content that could reasonably live in a separate reference, fitting 'good structure; most content appropriately placed; minor organization gaps'.	4 / 5
	Total	16 / 20 Passed

Description

61%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 identifies a distinct Jotform niche and includes an explicit 'Use when' clause, but its action language is generic and it omits the natural Jotform-specific terms (forms, submissions) users would actually say.

Suggestions

Replace generic verbs with concrete Jotform actions, e.g. 'Create and manage forms, list and update submissions, and configure webhooks.'

Add natural trigger terms users say — 'forms', 'form submissions', 'Jotform forms' — to the 'Use when' clause.

Broaden the trigger beyond 'interact with Jotform data' to cover concrete intents like collecting responses or automating submission workflows.

Dimension	Reasoning	Score
Specificity	It names the domain ('Jotform integration') but the actions — 'Manage data, records, and automate workflows' — are generic and not concrete, matching the 'names the domain but actions are minimal or generic' anchor rather than the 3-anchor which requires concrete actions like 'extracts content'.	2 / 5
Completeness	It states both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Jotform data'), matching the 4-anchor where both are present but the 'when' could be more specific; it is not a 5 because the trigger is narrow and lacks concrete use-case phrases.	4 / 5
Trigger Term Quality	It includes the natural keyword 'Jotform' and 'Jotform data' but misses common variations users would say such as 'forms', 'submissions', or 'form data', fitting 'some relevant keywords but missing common variations or synonyms'.	3 / 5
Distinctiveness Conflict Risk	'Jotform integration ... interact with Jotform data' carves out a clear, named SaaS niche with a distinct trigger and minimal overlap with other skills, matching the 5-anchor for a clear niche with minimal conflict risk.	5 / 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/jotform/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.