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.

Quality

77%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/json-typed-attributes/SKILL.md

Quality

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 clearly defines a specific Rails pattern (typed attributes on JSON fields), includes an explicit 'Use when' clause with meaningful triggers, and enumerates supported types for additional clarity. The description is concise, uses third-person voice, and occupies a distinct niche that minimizes conflict with other skills.

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 with type casting, validations, form integration) and 'when' (explicit 'Use when models need flexible data storage with type casting, validations, and form integration').	3 / 3
Trigger Term Quality	Includes strong natural keywords a Rails developer would use: 'typed attributes', 'JSON fields', 'Rails models', 'type casting', 'validations', 'form integration', and specific type names. These are terms developers would naturally mention when seeking this functionality.	3 / 3
Distinctiveness Conflict Risk	Highly specific niche: typed attributes backed by JSON fields in Rails models. This is unlikely to conflict with general Rails skills, database migration skills, or other model-related skills due to the precise focus on JSON-backed typed attributes.	3 / 3
	Total	12 / 12 Passed

Implementation

55%

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 examples covering all supported types, but it is far too verbose for its purpose. It over-explains standard Rails concepts (validations, strong parameters, form helpers, scopes) that Claude already understands, and packs everything into a single monolithic file rather than using progressive disclosure to separate reference material from core usage patterns.

Suggestions

Cut the content by 60%+: remove 'When to Use', 'Troubleshooting', 'Best Practices', and explanations of standard Rails concepts (strong params, validations, form helpers). Keep only the API surface of StoreJsonAttributes.

Extract the type reference (String, Integer, Decimal, Boolean, Date, Array, Text) into a separate TYPES_REFERENCE.md and link to it from the main skill.

Move the 'Scopes and Queries', 'Working with Forms', and 'Common Patterns' sections into a separate PATTERNS.md file, referenced from the main skill with one-line descriptions.

Reduce each type's documentation to just the declaration syntax and one-line casting behavior note, removing the 'Example usage' blocks that demonstrate obvious behavior.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~300+ lines. Explains basic Rails concepts Claude already knows (strong parameters, validations, form helpers, scopes). The 'When to Use' section, 'Best Practices' section, and 'Troubleshooting' section are largely unnecessary padding. The same content could be conveyed in under 80 lines.	1 / 3
Actionability	Provides fully executable, copy-paste ready code examples for every type, including migrations, model definitions, form templates, validations, scopes, and strong parameters. Examples are concrete with realistic input/output pairs.	3 / 3
Workflow Clarity	The setup is clearly sequenced (1. migration, 2. include concern, 3. define attributes). For a non-destructive, single-concern skill like this, the workflow is unambiguous and doesn't require validation checkpoints beyond what's shown.	3 / 3
Progressive Disclosure	Monolithic wall of text with no references to external files. Content like the complete type reference, form examples, query patterns, and troubleshooting could easily be split into separate reference files. Everything is inlined in one massive document.	1 / 3
	Total	8 / 12 Passed

Validation

100%

Warnings & errors only

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: 4d83977

Reviewed: 14 days ago

Table of Contents

Discovery Implementation Validation

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.