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
Quality
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 all dimensions by providing only a skill name, a generic category, and redundant trigger terms. There is no information about what the skill does, what capabilities it has, or when it should be selected over other skills.
Suggestions
Add specific capabilities describing what the skill does, e.g., 'Creates web forms, configures form fields, sets up validation rules, designs multi-step forms'
Add a 'Use when...' clause with natural trigger terms like 'create a form', 'add input fields', 'form validation', 'contact form', 'survey', 'questionnaire'
Specify the type of forms and platforms supported to distinguish from other potential form-related skills, e.g., 'HTML forms', 'Google Forms', 'Typeform', etc.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Form Builder Helper' is just a name, and 'Business Automation' is an abstract category. There are no verbs describing what the skill actually does. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' (no capabilities listed) and 'when should Claude use it' (no use cases or scenarios). It only provides a category label and redundant trigger terms. | 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 users would say. Missing terms like 'create form', 'build form', 'form fields', 'input validation', etc. | 1 / 3 |
Distinctiveness Conflict Risk | 'Business Automation' is extremely generic and could overlap with dozens of other skills. 'Form Builder Helper' as a trigger is too vague - it doesn't specify what kind of forms, what platforms, or what specific form-building tasks. | 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 a placeholder template with no actual content. It describes capabilities in abstract terms without providing any concrete guidance, code, examples, or actionable instructions for form building. The entire document could be replaced with a single sentence and would convey the same (zero) information.
Suggestions
Add concrete code examples showing how to create forms (e.g., HTML form generation, form validation logic, or integration with specific form builder tools)
Define specific form builder patterns with executable examples - what fields, validation rules, and submission handlers look like
Include a clear workflow: 1) Define form schema, 2) Generate form, 3) Add validation, 4) Handle submission - with code for each step
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with actual form-building instructions
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler that waste tokens without adding value. | 1 / 3 |
Actionability | No concrete code, commands, or specific instructions are provided. The entire skill describes what it does abstractly ('provides step-by-step guidance') without actually providing any guidance, examples, or executable content. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains zero actual steps. There are no validation checkpoints or sequences of any kind. | 1 / 3 |
Progressive Disclosure | No structure beyond generic headings. No references to detailed documentation, no links to examples or advanced content. The content is both monolithic and empty - it doesn't point anywhere useful. | 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
0c08951
- 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.