Name: formsite
Rating: 62.4 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

formsite

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

Quality

73%

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

Quality

Content

81%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 fully executable, well-sequenced guidance with strong validation checkpoints for the connection lifecycle. Its main weakness is modest over-explanation of context Claude already knows, and some inlined reference material that could be more tightly organized.

Suggestions

Trim background explanation Claude already knows, such as the opening "Formsite is an online form builder..." sentence and the "rather than auth plumbing" aside.

Tighten the popular-actions table or proxy flag reference so the overview stays lean; keep only the most common examples inline.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but it includes unnecessary explanation such as "Formsite is an online form builder..." and "so you can focus on the integration logic rather than auth plumbing" that could be trimmed.	3 / 5
Actionability	It provides copy-paste-ready commands for install, login, connection ensure, action list/run, and proxying, plus a popular-actions table and flag reference that cover the common cases.	5 / 5
Workflow Clarity	The install -> login -> connection ensure -> poll-for-ready -> search -> run sequence is clearly laid out with explicit validation checkpoints (poll until not BUILDING, handle CLIENT_ACTION_REQUIRED, check CONFIGURATION_ERROR/SETUP_FAILED, re-poll after action).	5 / 5
Progressive Disclosure	The content is organized into well-labeled sections and stays one level deep with no nested or broken references, though all reference material is inlined in a single file with minor organization gaps.	4 / 5
	Total	17 / 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 is specific to a named app and includes an explicit Use-when clause, but the action verbs are generic and it omits common user synonyms like "surveys" or "submissions". It is clear and distinct but could be more comprehensive in trigger coverage.

Suggestions

Replace the generic verb "manage" with concrete operations, e.g. "List and retrieve forms, fetch form results, and manage webhooks and users."

Expand the Use-when clause with natural synonyms a user would say, e.g. "Use when working with Formsite forms, surveys, registrations, or form submissions and results."

Dimension	Reasoning	Score
Specificity	"Manage Forms, Users" names the domain and two entities but uses the generic verb "manage", matching the anchor that names domain plus minimal actions rather than a comprehensive list of concrete operations.	3 / 5
Completeness	It states both what ("Formsite integration. Manage Forms, Users.") and when ("Use when the user wants to interact with Formsite data"), though the trigger is somewhat broad.	4 / 5
Trigger Term Quality	Keywords "Formsite", "Forms", "Users", and "Formsite data" are relevant, but natural user phrases like "surveys", "form submissions", or "form results" are missing.	3 / 5
Distinctiveness Conflict Risk	"Formsite" names a specific application with distinct triggers, giving it a clear niche and minimal conflict risk with other 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/formsite/SKILL.md
Commit: f484c82

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