Name: forms-on-fire
Rating: 64.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

forms-on-fire

Forms On Fire integration. Manage Forms, Users, Groups. Use when the user wants to interact with Forms On Fire data.

Quality

78%

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/forms-on-fire/SKILL.md

Quality

Content

82%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 highly actionable and well-structured, with executable commands and a clear connection-workflow feedback loop. The main gaps are minor editorial padding, a dangling "Step 2" reference, and an inlined action catalog that could live in a separate reference file.

Suggestions

Resolve the dangling "skip to Step 2" reference by adding an explicit "Step 2: Run actions" header or rewording the pointer.

Move the 20-row popular-actions table into a separate references file (e.g., actions.md) and link to it from a concise summary, improving progressive disclosure.

Add a brief validation/verification note for batch CRUD operations (create/update/delete users, groups) so Claude confirms results after destructive writes.

Trim editorial phrasing like "so you can focus on the integration logic rather than auth plumbing" to tighten token efficiency.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands and a compact action table, but contains minor editorial padding (e.g., "so you can focus on the integration logic rather than auth plumbing") that could be trimmed.	4 / 5
Actionability	Provides copy-paste-ready CLI commands throughout (connection ensure, action list/run, request proxy) plus a 20-row action catalog and a proxy-flag reference table, fully covering the common cases.	5 / 5
Workflow Clarity	The connection flow is clearly sequenced with state-based checkpoints and a poll-after-action feedback loop, but the "skip to Step 2" reference is dangling and batch CRUD actions lack explicit per-operation validation guidance.	4 / 5
Progressive Disclosure	Well-organized into clear sections with no nested references and no bundle files to manage, though the 20-row action table is reference-like bulk inlined in the main file rather than split into a separate catalog.	4 / 5
	Total	17 / 20 Passed

Description

73%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 third-person, distinct, and answers both "what" and "when" with an explicit trigger clause. It is held back from the top tier by a single generic action verb ("Manage") instead of multiple concrete actions and by trigger phrasing that is somewhat general.

Suggestions

Replace the generic "Manage" with two or three specific actions (e.g., "List, create, update, and delete Forms, Users, and Groups") to lift specificity.

Expand the "Use when" clause with concrete trigger scenarios (e.g., listing users, creating tasks, searching form entries) to make the trigger more explicit.

Add natural synonyms or common phrasings users might say (e.g., "form entries", "dispatches", "folders") to broaden keyword coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and three concrete entities ("Manage Forms, Users, Groups") but relies on a single generic action verb rather than listing several specific actions, so it is not comprehensive.	3 / 5
Completeness	Provides a clear "what" (Forms On Fire integration, manage Forms/Users/Groups) and an explicit "when" ("Use when the user wants to interact with Forms On Fire data"), but the trigger could name more concrete scenarios to reach the top anchor.	4 / 5
Trigger Term Quality	Includes the distinct product name "Forms On Fire" plus natural entity terms (Forms, Users, Groups) and an explicit "Use when..." trigger; missing some common synonyms or file extensions keeps it just below the top anchor.	4 / 5
Distinctiveness Conflict Risk	"Forms On Fire" is a clearly named product with a distinct mobile-forms niche and trigger terms keyed to that product name, giving minimal conflict risk with other skills.	5 / 5
	Total	16 / 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/forms-on-fire/SKILL.md
Commit: f484c82

Reviewed: ~20 hours 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.