form-object-patterns
Creates form objects for complex form handling with TDD. Use when building multi-model forms, search forms, wizard forms, or when user mentions form objects, complex forms, virtual models, or non-persisted forms.
Install with Tessl CLI
npx tessl i github:ThibautBaissac/rails_ai_agents --skill form-object-patterns89
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/skillAgent success when using this skill
Validation for skill structure
Discovery
100%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 is a well-crafted skill description that excels across all dimensions. It clearly specifies the capability (form objects with TDD), provides comprehensive trigger terms that developers would naturally use, and explicitly states both what it does and when to use it. The description is concise yet complete, with excellent distinctiveness from related form-handling skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Creates form objects', 'complex form handling', 'TDD', and specific form types like 'multi-model forms, search forms, wizard forms'. Uses proper third person voice. | 3 / 3 |
Completeness | Clearly answers both what ('Creates form objects for complex form handling with TDD') and when ('Use when building multi-model forms, search forms, wizard forms, or when user mentions form objects, complex forms, virtual models, or non-persisted forms'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'form objects', 'complex forms', 'virtual models', 'non-persisted forms', 'multi-model forms', 'search forms', 'wizard forms'. These are terms developers naturally use when discussing this pattern. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting form objects pattern with distinct triggers like 'form objects', 'virtual models', 'non-persisted forms'. Unlikely to conflict with general form validation or basic form building skills. | 3 / 3 |
Total | 12 / 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 strong, highly actionable skill with excellent TDD workflow clarity and complete, executable code examples. The main weaknesses are moderate verbosity (explanatory content Claude doesn't need) and the monolithic structure that could benefit from progressive disclosure through separate pattern files. The consistent Spec First -> Implementation pattern is well-executed.
Suggestions
Remove the Overview section and 'When to Use Form Objects' table - the skill description already provides this context and Claude understands form object purposes
Consider splitting into SKILL.md (overview + base class + one example) with references to PATTERNS.md for the detailed multi-model, search, wizard, and contact form patterns
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with good code examples, but includes some unnecessary elements like the overview bullet points explaining what form objects do (Claude knows this) and the 'When to Use Form Objects' table which is somewhat redundant given the skill description already specifies when to use it. | 2 / 3 |
Actionability | Excellent actionability with fully executable Ruby code examples throughout. The specs are complete and copy-paste ready, the implementations are concrete, and the controller/view integration examples are practical and immediately usable. | 3 / 3 |
Workflow Clarity | Clear TDD workflow with explicit steps (RED -> GREEN), progress checklist at the start, and the pattern of 'Spec First' followed by 'Implementation' is consistently applied. The final checklist provides validation checkpoints for the overall process. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and patterns, but it's a monolithic document that could benefit from splitting detailed patterns into separate files. The 500+ lines of content would be better served with a quick-start overview and references to pattern-specific files. | 2 / 3 |
Total | 10 / 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 |
|---|---|---|
skill_md_line_count | SKILL.md is long (612 lines); consider splitting into references/ and linking | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
Total | 9 / 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.