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

Blog Docs Log in Get started

formio

Form.io integration. Manage Forms, Projects. Use when the user wants to interact with Form.io 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/formio/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 is a well-structured, largely executable guide to driving Form.io through the Membrane CLI with a solid connection-state feedback loop. Its main weaknesses are token waste in the marketing intro and the all-"No description" actions table, plus a broken Step 2 reference.

Suggestions

Delete the opening Form.io marketing paragraph or compress it to one line; Claude does not need a platform pitch.

Replace the 20-row Popular actions table whose descriptions are all "No description" with a handful of actions each shown with a real `membrane action run` example and concrete `--input` JSON, or move the full list to a reference file.

Fix the "skip to Step 2" cross-references by labeling the Searching/Running sections as Step 2/Step 3, and add an explicit verify step after create/update actions.

Dimension	Reasoning	Score
Conciseness	Most of the body is efficient (CLI commands, state tables), but the opening Form.io marketing paragraph explains concepts Claude largely knows and the 20-row Popular actions table where every description is "No description" is pure padding, matching the 3 anchor.	3 / 5
Actionability	Copy-paste-ready commands cover the common cases (login, connection ensure/get, action list/run, request proxy), but no example runs a real action with concrete input and the actions table lacks descriptions, leaving minor gaps that keep it below 5.	4 / 5
Workflow Clarity	The connect-and-poll flow has explicit checkpoints and a feedback loop (CLIENT_ACTION_REQUIRED -> re-poll), but the "skip to Step 2" references point to no clearly labeled Step 2 and post-action validation for create/update is only implicit.	4 / 5
Progressive Disclosure	No bundle files exist and the body is organized into clear sections (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices); at ~165 lines it exceeds the simple-skill threshold and the inline low-value actions table is a minor organization gap, so 4 rather than 5.	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 cleanly states a what and a when tied to a distinct platform (Form.io), but its action list is thin and generic and trigger coverage lacks synonyms. It is solid but not exemplary.

Suggestions

Replace the generic "Manage Forms, Projects" with several concrete verbs (e.g., "List, create, update, and delete Forms, Submissions, Projects, Roles, and Users") to lift specificity.

Add natural trigger variations to the 'Use when' clause, e.g., "Use when the user mentions Form.io, forms, submissions, or project data."

Keep the third-person imperative voice (already correct) and avoid adding marketing fluff about what Form.io is.

Dimension	Reasoning	Score
Specificity	Names the domain ("Form.io integration") and two concrete-ish actions ("Manage Forms, Projects"), but "Manage" is generic and coverage is not comprehensive, matching the 3 anchor rather than the multi-action 4.	3 / 5
Completeness	Both what ("Manage Forms, Projects") and when ("Use when the user wants to interact with Form.io data") are explicitly stated, but the what is only two actions and the when offers a single trigger rather than the multiple concrete triggers of a 5.	4 / 5
Trigger Term Quality	Relevant keywords ("Form.io", "Forms", "Projects", "Form.io data") are present but lack common variations or synonyms, fitting the 3 anchor rather than the broader coverage of 4.	3 / 5
Distinctiveness Conflict Risk	"Form.io integration" is a clear niche with a distinct platform trigger, but the generic "Manage Forms, Projects" could overlap with other form-tool skills, so it sits at 4 rather than the minimal-conflict 5.	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/formio/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.