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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill form-builder-helperOverall
score
17%
Does it follow best practices?
Validation for skill structure
Activation
0%This description is critically deficient across all dimensions. It provides only a skill name and category with no actual description of capabilities, no natural trigger terms users would say, and no guidance on when to use it. The repeated trigger term 'form builder helper' suggests auto-generated content without meaningful customization.
Suggestions
Add specific capabilities: describe what form operations this skill performs (e.g., 'Creates web forms, adds input fields, configures validation rules, generates form submissions')
Include natural trigger terms users would actually say: 'form', 'survey', 'input fields', 'web form', 'contact form', 'registration form', 'form validation'
Add an explicit 'Use when...' clause: 'Use when the user needs to create, edit, or configure forms, or mentions building surveys, input fields, or form submissions'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Form Builder Helper' is just a name, and 'Business Automation' is a vague category. There are no specific capabilities like 'create forms', 'add fields', or 'validate inputs'. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no explanation of capabilities and no meaningful usage guidance beyond the redundant trigger phrase. | 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 user language. Users would more likely say 'create a form', 'build a survey', 'add form fields', etc. | 1 / 3 |
Distinctiveness Conflict Risk | 'Business Automation' is extremely generic and could overlap with dozens of other skills. Without specific form-related triggers or capabilities, this could conflict with any automation, workflow, or document-related skill. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%This skill is an empty template with no actual content. It describes what a form builder helper skill would do without providing any concrete guidance, code, examples, or workflows. The entire file consists of generic boilerplate that could apply to any skill topic.
Suggestions
Replace the abstract 'Capabilities' section with actual executable code examples showing how to build forms (e.g., HTML form generation, form validation logic, or integration with specific form builder APIs)
Add a concrete workflow with numbered steps for common form builder tasks, such as creating a form, adding validation, and processing submissions
Include specific code snippets or configuration examples that Claude can directly use or adapt for form building tasks
Remove meta-descriptions like 'provides step-by-step guidance' and replace with the actual step-by-step guidance itself
| 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 teaching Claude anything actionable. | 1 / 3 |
Actionability | No concrete code, commands, or specific instructions are provided. The entire skill describes what it does in abstract terms ('provides step-by-step guidance') without actually providing any guidance, examples, or executable content. | 1 / 3 |
Workflow Clarity | No workflow is defined. The skill claims to provide 'step-by-step guidance' but contains zero actual steps. There are no processes, sequences, or validation checkpoints—just meta-descriptions of what the skill supposedly does. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of placeholder text with no meaningful structure. There are no references to detailed materials, no links to examples or advanced content, and the sections present contain no substantive information to organize. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 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.