123formbuilder
123FormBuilder integration. Manage data, records, and automate workflows. Use when the user wants to interact with 123FormBuilder data.
61
72%
Does it follow best practices?
Impact
—
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
67%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 identifies the integration target and includes an explicit 'Use when' clause, which is good. However, the capabilities listed are quite generic ('manage data, records, and automate workflows') and don't convey specific concrete actions. The trigger terms could be expanded to include natural variations users might use when referring to this tool.
Suggestions
List more specific concrete actions such as 'retrieve form submissions, create new forms, update records, export responses' instead of the generic 'manage data, records, and automate workflows'.
Add natural trigger term variations to the 'Use when' clause, e.g., 'form submissions', 'form responses', 'form builder', '123 forms', or '123FB'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (123FormBuilder) and some actions ('manage data, records, and automate workflows'), but the actions are fairly generic and not comprehensive — it doesn't specify concrete operations like creating forms, exporting submissions, updating fields, etc. | 2 / 3 |
Completeness | It answers both 'what' (manage data, records, automate workflows) and 'when' (explicitly states 'Use when the user wants to interact with 123FormBuilder data'), satisfying the explicit trigger guidance requirement. | 3 / 3 |
Trigger Term Quality | Includes '123FormBuilder' as a strong 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'. | 2 / 3 |
Distinctiveness Conflict Risk | The '123FormBuilder' brand name provides good distinctiveness, but the generic terms 'manage data, records, and automate workflows' could overlap with many other integration or workflow automation skills. The 'when' clause also only references '123FormBuilder data' without narrowing further. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
77%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 skill with strong actionability and clear workflow sequencing for the connection setup process. Its main weaknesses are some unnecessary verbosity (explaining what 123FormBuilder is, restating Membrane benefits) and a monolithic structure that could benefit from splitting detailed reference material into separate files. The proxy request table and state machine documentation are well done.
Suggestions
Remove the opening paragraph explaining what 123FormBuilder is — Claude already knows this and it wastes tokens.
Remove or condense the best practices section, as most points repeat guidance already given inline (e.g., 'Let Membrane handle credentials' restates the auth section).
Consider splitting the proxy request reference table and connection state machine details into separate referenced files to improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explains what 123FormBuilder is, which is unnecessary context for Claude. The Membrane CLI instructions are mostly efficient but include some redundant explanations (e.g., 'Membrane handles authentication and credentials refresh automatically — so you can focus on the integration logic rather than auth plumbing'). The best practices section repeats information already covered in the body. | 2 / 3 |
Actionability | The skill provides concrete, executable CLI commands for every step: installation, authentication, connection setup, action discovery, action execution, and proxy requests. Commands are copy-paste ready with clear flag descriptions and parameter placeholders. | 3 / 3 |
Workflow Clarity | The multi-step connection workflow is clearly sequenced with explicit state checks (READY, BUILDING, CLIENT_ACTION_REQUIRED, error states) and feedback loops (poll until ready, handle client actions, then proceed). The numbered steps and conditional branching are well-structured for error recovery. | 3 / 3 |
Progressive Disclosure | The content is a single monolithic file with no references to supporting files, despite being long enough (~150 lines) that sections like proxy request details, best practices, or the connection state machine could be split out. The overview section listing Form/Submission/User/Account is underdeveloped and doesn't link to anything useful. | 2 / 3 |
Total | 10 / 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
f484c82
- 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.