dynamic-nested-attributes

Implement Rails nested attributes with dynamic add/remove functionality using Turbo Streams and Simple Form. Use when building forms where users need to manage multiple child records (has_many associations), add/remove nested items without page refresh, or create bulk records inline.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

76%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Highly actionable content with comprehensive executable examples across every component, weakened only by a missing validation/feedback loop for a destructive batch operation and mild duplication of the description in the body.

Suggestions

Add a verification step to the Implementation Checklist (e.g. submit the form, confirm an added item persists and a removed item is marked _destroy) so the batch/destructive workflow has an explicit validation checkpoint.

Remove or condense the Overview and When-to-Use sections since they restate the frontmatter description verbatim, freeing token budget.

Move the Stimulus controller JavaScript and the routes/strong-parameters examples into reference files to keep SKILL.md a lean overview pointing one level deep.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and assumes Rails competence (no padding about what nested attributes are), though the Overview and When-to-Use sections duplicate the frontmatter description and could be trimmed.	4 / 5
Actionability	Copy-paste-ready slim, ruby, and JavaScript examples cover all six components (form, partial, controller, turbo stream, stimulus controller, routes/params), spanning the common cases.	5 / 5
Workflow Clarity	A sequenced Implementation Checklist is present, but this is a batch/destructive operation (add/remove nested records) with no validation or verification checkpoints, so the rubric cap of 3 applies.	3 / 5
Progressive Disclosure	Well-organized into clear sections with no nested references; at ~165 lines some material (Stimulus JS, route/param examples) could be split into reference files, but the single-file structure navigates well.	4 / 5
	Total	16 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A tight, third-person description that clearly states what the skill does and when to use it, with concrete trigger terms and a distinct Rails-specific niche. Only minor synonym coverage is missing on trigger terms.

Dimension	Reasoning	Score
Specificity	Names the domain and multiple concrete actions/components — "dynamic add/remove functionality using Turbo Streams and Simple Form" — with comprehensive coverage of the what.	5 / 5
Completeness	Explicitly answers both what ("Implement Rails nested attributes with dynamic add/remove functionality...") and when ("Use when building forms where users need to manage multiple child records...") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Strong natural trigger terms ("nested attributes", "add/remove nested items", "multiple child records", "has_many associations", "bulk records inline") that users would actually say; a few synonyms (e.g. "nested forms", "cocoon") are absent.	4 / 5
Distinctiveness Conflict Risk	A clear niche (Rails nested attributes + Turbo Streams + Simple Form) with distinct triggers and minimal overlap risk against other skills.	5 / 5
	Total	19 / 20 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: RoleModel/rolemodel-skills
Path: skills/dynamic-nested-attributes/SKILL.md
Commit: 6d600e9

Reviewed: 6 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.