json-typed-attributes
Define typed attributes backed by JSON fields in Rails models. Use when models need flexible data storage with type casting, validations, and form integration. Supports integer, decimal, string, text, boolean, date, and array types.
71
63%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/json-typed-attributes/SKILL.mdQuality
Discovery
85%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 strong description that clearly defines a specific Rails pattern, explicitly states when to use it, and enumerates supported types. The main weakness is that trigger terms could be broader to capture more natural user phrasings like 'jsonb columns', 'store_accessor', or 'virtual attributes'.
Suggestions
Add alternative trigger terms users might naturally say, such as 'jsonb', 'store_accessor', 'virtual attributes', or 'schemaless columns' to improve discoverability.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions and capabilities: 'Define typed attributes backed by JSON fields', 'type casting, validations, and form integration', and enumerates supported types (integer, decimal, string, text, boolean, date, array). | 3 / 3 |
Completeness | Clearly answers both what ('Define typed attributes backed by JSON fields in Rails models') and when ('Use when models need flexible data storage with type casting, validations, and form integration') with an explicit 'Use when' clause. | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'JSON fields', 'Rails models', 'typed attributes', 'type casting', 'validations', and 'form integration', but misses common user phrasings like 'store_accessor', 'jsonb', 'virtual attributes', 'schemaless', or 'flexible columns' that users might naturally use. | 2 / 3 |
Distinctiveness Conflict Risk | Highly specific niche: typed attributes backed by JSON fields in Rails models. This is unlikely to conflict with other skills due to the precise combination of Rails, JSON fields, and typed attributes. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is highly actionable with excellent executable code examples covering all supported types, but it is far too verbose for a SKILL.md file. It explains many concepts Claude already knows (Rails validations, strong parameters, form helpers), repeats patterns across multiple sections, and dumps everything into a single monolithic file rather than using progressive disclosure with linked references.
Suggestions
Reduce content by 60-70%: remove the 'When to Use' section, 'Best Practices' (mostly duplicates earlier content), 'Troubleshooting' (obvious debugging), and explanations of standard Rails concepts like strong parameters and validations.
Extract the full type reference, form integration examples, and query patterns into separate linked files (e.g., TYPES.md, FORMS.md, QUERIES.md) and keep SKILL.md as a concise overview with quick-start examples.
Consolidate the type definitions into a compact table or brief list rather than giving each type its own subsection with redundant structure.
Remove duplicate content: constants-for-validation pattern appears in 'Complete Example', 'Common Patterns', and 'Best Practices' sections.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~300 lines. It explains basic Rails concepts Claude already knows (strong parameters, validations, form helpers, scopes), repeats patterns multiple times (constants for validation appear in both 'Complete Example', 'Common Patterns', and 'Best Practices'), and includes a lengthy troubleshooting section with obvious debugging steps. The 'When to Use' section explains what JSON columns are for, which is unnecessary. | 1 / 3 |
Actionability | The skill provides fully executable, copy-paste ready code examples throughout. Every type has concrete usage examples with input/output, migrations are shown, and form integration includes real Slim template code. The examples are specific and complete. | 3 / 3 |
Workflow Clarity | The setup section provides a clear 3-step sequence (ensure column, include concern, define attributes), but there are no validation checkpoints. For a skill involving database migrations and JSON column setup, there's no verification step to confirm the column exists or that attributes are working correctly before proceeding. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of text with no references to external files. Content like the full type reference, form integration patterns, query examples, and troubleshooting could easily be split into separate reference files. Everything is inlined in one massive document, making it expensive to load for simple use cases. | 1 / 3 |
Total | 7 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- RoleModel/rolemodel-skills
- Commit
097ad6b
- 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.