123formbuilder
123FormBuilder integration. Manage data, records, and automate workflows. Use when the user wants to interact with 123FormBuilder data.
75
70%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/123formbuilder/SKILL.mdQuality
Discovery
75%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 adequately identifies the specific product (123FormBuilder) and provides an explicit 'Use when' clause, making it complete and distinctive. However, the capability descriptions are somewhat generic ('manage data, records, and automate workflows') and could benefit from more specific concrete actions. Trigger terms could also be expanded to cover more natural user phrasings.
Suggestions
Replace vague actions with specific concrete capabilities, e.g., 'retrieve form submissions, create and update forms, export records, and automate workflows'.
Add natural trigger term variations such as 'form submissions', 'form responses', 'form builder', or '123 form builder' to improve matching.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (123FormBuilder) and some actions ('manage data, records, and automate workflows'), but these are fairly generic and not comprehensive — it doesn't list specific concrete actions like 'retrieve form submissions', 'create forms', or 'export records'. | 2 / 3 |
Completeness | Answers both 'what' (manage data, records, automate workflows) and 'when' (Use when the user wants to interact with 123FormBuilder data), with an explicit 'Use when...' clause. | 3 / 3 |
Trigger Term Quality | Includes '123FormBuilder' as a key trigger term and mentions 'data', 'records', and 'workflows', but misses natural variations users might say like 'form submissions', 'form builder', 'form responses', or '123 form builder'. | 2 / 3 |
Distinctiveness Conflict Risk | The explicit mention of '123FormBuilder' as a specific product creates a clear niche that is unlikely to conflict with other skills, since it targets a named integration. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a functional integration skill with strong actionability — every operation has a concrete CLI command. Its main weaknesses are the unnecessary introductory explanation of 123FormBuilder, some redundancy in best practices, and a lack of explicit validation/error-recovery steps in the workflow. The entity overview section feels like a placeholder that doesn't add value.
Suggestions
Remove the opening paragraph explaining what 123FormBuilder is — Claude already knows this, and the skill description already provides context.
Add explicit validation checkpoints to the workflow, e.g., verify connection succeeded with `membrane connection list --json` before proceeding to action discovery.
Either flesh out the entity overview (Form → Submission, User → Account) with actionable details or remove it — currently it adds no value.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explaining what 123FormBuilder is (web-based form builder, used by businesses, etc.) is unnecessary context Claude already knows. The rest is reasonably efficient but could be tightened — e.g., the 'Best practices' section repeats information already covered (like credential handling). | 2 / 3 |
Actionability | The skill provides concrete, copy-paste-ready CLI commands for every step: installation, authentication, connecting, searching actions, creating actions, running actions with parameters. Each command includes specific flags and expected behavior. | 3 / 3 |
Workflow Clarity | The steps are listed in a logical sequence (install → authenticate → connect → search → create/run), and the action creation flow includes polling with state checking. However, there are no explicit validation checkpoints or error recovery feedback loops for the overall workflow — e.g., no guidance on what to do if connection fails, or how to verify a connection succeeded before proceeding. | 2 / 3 |
Progressive Disclosure | The content is reasonably structured with clear sections, but it's somewhat monolithic — the overview section with the entity hierarchy (Form → Submission, User → Account) is underdeveloped and doesn't link to deeper resources. The official docs link is mentioned but not leveraged for progressive disclosure of advanced topics. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- membranedev/application-skills
- Commit
56d7336
- Reviewed
Table of Contents
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.