form-builder-helper
Form Builder Helper - Auto-activating skill for Business Automation. Triggers on: form builder helper, form builder helper Part of the Business Automation skill category.
34
0%
Does it follow best practices?
Impact
99%
1.01xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/19-business-automation/form-builder-helper/SKILL.mdQuality
Discovery
0%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 is essentially a placeholder with no substantive content. It fails on every dimension: it lists no concrete actions, provides no natural trigger terms beyond its own repeated name, lacks any 'Use when...' guidance, and is indistinguishable from other business automation skills. It would be nearly useless for skill selection among a set of available skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates web forms, configures input validation, designs multi-step form workflows, generates form templates for data collection.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create a form, build a survey, add input fields, design a questionnaire, or set up data collection forms.'
Remove the redundant duplicate trigger term and replace with varied natural language terms users would actually say, such as 'form', 'survey', 'input fields', 'web form', 'registration form', 'contact form'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. It only names itself ('Form Builder Helper') and a category ('Business Automation') without describing what it actually does—no mention of creating forms, validating inputs, generating form layouts, or any other specific capability. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is meaningfully answered. There is no 'Use when...' clause and no description of capabilities beyond the generic category label 'Business Automation'. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'form builder helper' repeated twice, which is the skill's own name rather than natural keywords a user would say. Missing natural terms like 'create form', 'input fields', 'survey', 'questionnaire', 'web form', 'form design', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic—'Business Automation' could overlap with dozens of other skills. Without specific actions or distinct trigger terms, there is nothing to differentiate this from any other business or form-related skill. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty placeholder with no actual content. It consists entirely of generic boilerplate that restates the skill name in various ways without providing any concrete instructions, code, examples, or workflows for form building. It fails on every dimension because there is simply nothing substantive to evaluate.
Suggestions
Define what 'form builder helper' actually means—specify the technology stack (e.g., HTML forms, Google Forms API, specific form libraries) and provide executable code examples for creating forms.
Add a concrete workflow with numbered steps, such as: gather field definitions → generate form schema → validate schema → render/deploy form, with validation checkpoints at each stage.
Include at least one complete, copy-paste-ready example showing input (e.g., a form specification) and output (e.g., generated form code or configuration).
Remove all generic filler sections ('When to Use', 'Example Triggers', 'Capabilities' with vague bullets) and replace them with actual technical content that teaches Claude something it doesn't already know.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler with no substantive information. It repeatedly restates the skill name without providing any actual instructions, code, or concrete guidance. Every section is padded with generic boilerplate that tells Claude nothing it doesn't already know. | 1 / 3 |
Actionability | There is zero actionable content—no code, no commands, no specific steps, no concrete examples. Every bullet point is a vague, abstract description like 'Provides step-by-step guidance' without actually providing any such guidance. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequences, no validation checkpoints. The skill claims to provide 'step-by-step guidance' but contains none. | 1 / 3 |
Progressive Disclosure | There is no meaningful content to organize, no references to external files, and no layered structure. The sections are superficially organized but contain no real information to disclose progressively. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
c8a915c
- 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.