Tessl • The management layer for AI agent skills

SkillPublic

123formbuilder

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

Quality

66%

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/123formbuilder/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 body delivers strong executable CLI guidance with genuinely good connection-state checkpoint handling, undermined by padding in the intro/overview sections, a duplicated command section, and broken step numbering ("Step 2" references with no Step 2). Tightening the prose and fixing the workflow labels would raise it solidly.

Suggestions

Remove the introductory paragraph explaining what 123FormBuilder is and either annotate the "Overview" entity tree with what each resource maps to or delete it; both assume knowledge Claude does not need from this file.

Fix the dangling "skip to **Step 2**" references — no Step 2 exists — by introducing an explicit numbered sequence (1. Install, 2. Authenticate, 3. Connect, 4. Discover and run actions) that the state-handling steps can point to.

Merge "Popular actions" into "Searching for actions" (they repeat the same discovery command) and either list a few real popular actions with example intents or drop the section.

Trim the Best practices section's justification prose (e.g. "This will burn less tokens") to bare directives.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-focused and efficient, but the opening paragraph explaining what 123FormBuilder is, the content-free "Overview" entity tree (Form/Submission/User/Account with no annotations), and the duplicated action-list command in "Popular actions" are unnecessary explanation. This fits 'mostly efficient but includes some unnecessary explanation'.	3 / 5
Actionability	Concrete, executable commands appear throughout — npm install, membrane login with headless fallback, connection ensure with polling, action list/run, and a proxy flag table — copy-paste ready. Not a 5: the "Popular actions" section lists no actual actions, and there is no worked example with a real action ID or intent query for forms or submissions.	4 / 5
Workflow Clarity	The connection state-handling has good checkpoints (poll with --wait, the clientAction state matrix, error states), but the text twice says "skip to Step 2" while no Step 2 label exists (only an orphaned "1b" subsection), and there is no explicit numbered end-to-end sequence from install to running an action. The dangling step references make the sequence ambiguous, fitting 'steps listed but gaps'.	3 / 5
Progressive Disclosure	A single, well-sectioned SKILL.md with clear headers (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) and no nested or buried references. Minor gaps: the proxy flag table and clientAction schema detail could live in reference files, and at ~140 lines it exceeds the simple-skill threshold, so it does not earn full marks.	4 / 5
	Total	14 / 20 Passed

Description

57%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 correctly names the target app and includes an explicit 'Use when...' trigger clause, but its capability statement is generic. Replacing buzzword phrasing with concrete 123FormBuilder actions and trigger synonyms would materially improve it.

Suggestions

Replace "Manage data, records, and automate workflows" with concrete actions, e.g. "Create and update forms, retrieve and manage submissions, and look up account and user records in 123FormBuilder."

Add natural trigger synonyms to the 'Use when' clause, such as forms, surveys, form submissions, or 123FormBuilder forms, so users phrasing the need without the product name still match.

Avoid generic integration boilerplate ("integration", "automate workflows") that could apply to any app connector; anchor the wording to form-builder-specific nouns.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the domain but the actions are generic — comparable to the "Processes PDF files" anchor — with no concrete capabilities such as creating forms or retrieving submissions. It is not a 1 because the domain and some action verbs are present, and not a 3 because no action is concrete.	2 / 5
Completeness	Both clauses are explicit: what ("Manage data, records, and automate workflows") and when ("Use when the user wants to interact with 123FormBuilder data"), satisfying the 'Use when...' requirement. Not a 5 because the 'what' is buzzword-vague rather than a list of concrete actions; not a 3 because the 'when' clause is present and explicit.	4 / 5
Trigger Term Quality	"123FormBuilder" is a strong natural keyword users would say, but common variations and synonyms — forms, surveys, form builder, submissions — are absent. Good single keyword, missing the surrounding vocabulary, which fits the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	"123FormBuilder" names a distinct app with a clear niche and the trigger is tied to it, so conflict risk is low. Minor overlap remains with other form-builder integrations because "manage data, records, and automate workflows" is generic, keeping it below the 'minimal conflict risk' anchor.	4 / 5
	Total	13 / 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/123formbuilder/SKILL.md
Revision: f484c82

Reviewed: 16 days ago

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.

123formbuilder

Table of Contents

Is this your skill?