action-cable

Setup and use ActionCable for real-time features in Rails applications using WebSockets. Use when implementing real-time updates, live notifications, broadcasting changes, or when the user mentions WebSockets, ActionCable, channels, broadcasting, or Turbo Streams over cable.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

80%

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

A well-organized, executable ActionCable reference with lean code-first content and strong actionability. Its main gaps are the absence of explicit validation checkpoints in the setup sequence and the lack of progressive disclosure via separate reference files.

Suggestions

Add a short ordered setup workflow with a verification step, e.g. after wiring the connection and a channel, confirm the subscription logs "Connected" in the browser console before proceeding to broadcasting.

Split the broadcast API and security guidance into a separate reference file (e.g. BROADCASTING.md) and link to it one level deep so the main SKILL.md stays a concise overview.

Trim the duplicated broadcast pattern in the organization-scoped example or fold it into the reference file to reduce repetition.

Dimension	Reasoning	Score
Conciseness	The body is lean: minimal prose, no explanation of what WebSockets/Rails are, and code blocks that earn their place; it does not pad concepts Claude already knows, matching the lean-and-efficient anchor.	3 / 3
Actionability	Concrete, copy-paste-ready code is provided throughout (connection.rb, channel.rb, JS initializer, Turbo::StreamsChannel broadcast calls, cable.yml, routes), matching the fully-executable anchor.	3 / 3
Workflow Clarity	Setup is presented as numbered components (1. Connection, 2. Channel, 3. JavaScript) giving an implied sequence, but there are no validation checkpoints (e.g. verifying the connection subscribes) and the broadcasting/config sections are reference-style rather than a sequenced workflow; this fits the steps-present-but-checkpoints-implicit anchor and does not reach 3.	2 / 3
Progressive Disclosure	The skill is a single ~175-line monolithic file with clear sections but no bundle files and no one-level-deep references to split out advanced material; content that could live in a separate reference (full broadcast API, security notes) is inline, matching the some-structure-but-could-be-split anchor rather than the under-50-lines exception for a 3.	2 / 3
	Total	10 / 12 Passed

Description

90%

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 strong description with explicit what-and-when triggers and good natural keyword coverage. The only weakness is that the action verbs ("setup and use") are generic rather than enumerating concrete capabilities.

Suggestions

Replace generic verbs with concrete capabilities, e.g. "Create channels, authenticate connections, broadcast Turbo Stream updates, and subscribe clients to live changes."

Consider naming the specific deliverables users want (live notifications, presence, in-place DOM updates) to sharpen the capability list.

Dimension	Reasoning	Score
Specificity	"Setup and use ActionCable" names the domain and a couple of actions, but the verbs are generic compared to a score-3 anchor that lists multiple concrete actions like extract/fill/merge; it is not merely vague so it clears 2.	2 / 3
Completeness	It states what ("Setup and use ActionCable for real-time features in Rails applications using WebSockets") and an explicit when clause ("Use when implementing... or when the user mentions..."), satisfying both halves clearly.	3 / 3
Trigger Term Quality	Natural user-facing terms are well covered: "WebSockets, ActionCable, channels, broadcasting, or Turbo Streams over cable" alongside "real-time updates, live notifications, broadcasting changes", matching the good-coverage anchor.	3 / 3
Distinctiveness Conflict Risk	ActionCable and "Turbo Streams over cable" are Rails-specific niches with distinct triggers unlikely to fire for unrelated skills, matching the clear-niche anchor.	3 / 3
	Total	11 / 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: RoleModel/rolemodel-skills
Commit: f61959b

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