Name: formidable-forms
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

formidable-forms

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

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/formidable-forms/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 content is highly actionable with executable CLI commands and a strong connection-state feedback loop, but it is weakened by an unnecessary background intro, padding commentary, and an absence of validation guidance for its destructive actions. Structure and navigation are good for a single-file skill.

Suggestions

Trim the introductory paragraph about what Formidable Forms is and who uses it, and remove commentary like 'This is the fastest way to get a connection.'

Add a validation/confirmation checkpoint before destructive actions (e.g. 'Before running delete-form or delete-entry, confirm the target ID with the user and consider listing it first').

Provide at least one fully worked action-run example with realistic input JSON so the pattern is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-paste commands and tables, but the opening paragraph explaining what Formidable Forms is and who uses it is background Claude already knows, and phrases like 'so you can focus on the integration logic rather than auth plumbing' and 'This is the fastest way to get a connection' are padding that could be trimmed.	3 / 5
Actionability	It provides concrete, copy-paste-ready CLI commands with flags (login, connection ensure, action list/run, request) plus a popular-actions table and a proxy-options table, but the running-actions section shows only the command pattern without a fully worked example using realistic input values.	4 / 5
Workflow Clarity	The connection flow has a genuine feedback loop (poll state, branch on READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR, re-poll after user action), but the skill prominently features destructive actions ('Delete Form — Permanently deletes a form and all of its fields') with no validation or confirmation guidance before running them, which caps this dimension at 3.	3 / 5
Progressive Disclosure	Content is well organized into clearly headed sections (Install, Auth, Connecting, Searching, Popular actions, Running, Proxy, Best practices) with no nested references, though the full action table and proxy flag table are inlined rather than split into a separate reference file.	4 / 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 clearly identifies a distinct niche and provides both a 'what' and a 'when', but its action verbs are generic ('Manage') and it omits natural synonyms like 'entries' or 'submissions'. It is solid but not maximally specific.

Suggestions

Replace generic 'Manage Forms, Users, Roles' with concrete verbs, e.g. 'Create, list, update, and delete Forms, Entries, Fields, Users, and Roles'.

Add natural trigger synonyms such as 'form entries' or 'submissions' so users phrasing the need differently still match.

Make the 'Use when' clause scenario-specific, e.g. 'Use when the user wants to create forms, retrieve or update entries, or manage roles in Formidable Forms'.

Dimension	Reasoning	Score
Specificity	It names the domain ('Formidable Forms integration') and lists three managed entities ('Forms, Users, Roles'), but 'Manage' is a generic verb rather than concrete actions like create/delete/update, so it sits at the named-domain-plus-actions level rather than comprehensive specific verbs.	3 / 5
Completeness	Both 'what' ('Manage Forms, Users, Roles') and 'when' ('Use when the user wants to interact with Formidable Forms data') are present and explicit, though the trigger clause is somewhat circular and could name concrete scenarios to reach a 5.	4 / 5
Trigger Term Quality	'Formidable Forms' and 'Forms' are natural terms a user would say, but common variations such as 'entries', 'submissions', or 'field data' are missing, leaving keyword coverage partial rather than comprehensive.	3 / 5
Distinctiveness Conflict Risk	'Formidable Forms' is a specific named WordPress plugin giving it a clear niche with distinct triggers and minimal overlap risk against generic skills.	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/formidable-forms/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.