123formbuilder
123FormBuilder integration. Manage data, records, and automate workflows. Use when the user wants to interact with 123FormBuilder data.
Install with Tessl CLI
npx tessl i github:membranedev/application-skills --skill 123formbuilder75
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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.
This description adequately identifies the integration and provides explicit trigger guidance, making it functional for skill selection. However, the capability descriptions are somewhat generic ('manage data, records') and could benefit from more specific actions. The product-specific naming provides good distinctiveness.
Suggestions
Replace generic terms like 'Manage data, records' with specific actions such as 'retrieve form submissions, create new forms, update form fields, export response data'
Add natural trigger term variations users might say: 'form submissions', 'form responses', '123 forms', 'form data'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (123FormBuilder) and mentions some actions ('Manage data, records, and automate workflows'), but these are fairly generic and not comprehensive - doesn't specify concrete actions like 'create forms', 'export submissions', or 'configure notifications'. | 2 / 3 |
Completeness | Clearly answers both what ('Manage data, records, and 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 'data', 'records', 'workflows', but missing natural variations users might say like 'form submissions', 'form responses', 'form builder', or '123 form'. | 2 / 3 |
Distinctiveness Conflict Risk | The specific product name '123FormBuilder' creates a clear niche that is unlikely to conflict with other skills - it's a distinct, named integration rather than a generic capability. | 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 skill provides solid, actionable CLI commands for 123FormBuilder integration with good structure. However, it wastes tokens explaining what 123FormBuilder is (Claude knows this) and lacks validation/error handling guidance in workflows. The content is functional but could be tightened.
Suggestions
Remove the opening paragraph explaining what 123FormBuilder is - Claude already knows this context
Add validation steps after connection creation (e.g., 'Verify connection: membrane connection list --json | grep CONNECTION_ID')
Include error handling guidance for common failure scenarios (auth failures, invalid action IDs)
Remove or condense the entity hierarchy overview section which provides minimal actionable value
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explaining what 123FormBuilder is wastes tokens on information Claude already knows. The CLI setup and best practices sections are reasonably efficient, but the overview section with the entity hierarchy adds little value. | 2 / 3 |
Actionability | Provides fully executable CLI commands throughout with clear syntax examples. Commands are copy-paste ready with proper flags, JSON output options, and parameter passing examples. | 3 / 3 |
Workflow Clarity | Steps are listed for setup and connection flows, but lacks explicit validation checkpoints. No feedback loops for error recovery when commands fail, and no verification steps after connection creation. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but everything is inline in one file. The proxy request options table and best practices could potentially be separate references, though for this skill length it's borderline acceptable. | 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 | |
- 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.