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:fernandezbaptiste/rails_ai_agents --skill form-object-patterns95
Does it follow best practices?
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 the form object 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
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill with excellent actionability and conciseness. It provides complete, executable TDD examples for multiple form object patterns without unnecessary explanation. The main weakness is that the content could benefit from being split across multiple files for better progressive disclosure, as the single file is quite long.
Suggestions
Split detailed patterns (wizard forms, search forms, contact forms) into separate reference files like WIZARD_FORMS.md, SEARCH_FORMS.md, keeping only the multi-model registration example in the main skill
Add a quick reference section at the top with links to each pattern file for faster navigation
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, jumping directly into actionable patterns without explaining what form objects are conceptually or how ActiveModel works. Every section provides concrete value without padding. | 3 / 3 |
Actionability | Fully executable Ruby code throughout with complete specs, implementations, controllers, and views. All examples are copy-paste ready with proper file paths and realistic business logic. | 3 / 3 |
Workflow Clarity | Clear TDD workflow with explicit RED/GREEN progression, checklist at the end, and step-by-step process. The workflow includes validation through specs before implementation, which serves as the feedback loop. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and a decision table, but it's a monolithic 400+ line file. The wizard forms, search forms, and contact forms could be split into separate reference files with the main SKILL.md providing an overview. | 2 / 3 |
Total | 11 / 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.