rails-controller
Creates Rails controllers with TDD approach - request spec first, then implementation. Use when creating new controllers, adding controller actions, implementing CRUD operations, or when user mentions controllers, routes, or API endpoints.
Install with Tessl CLI
npx tessl i github:fernandezbaptiste/rails_ai_agents --skill rails-controller90
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation 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 TDD methodology (request spec first), lists concrete actions, includes an explicit 'Use when...' clause with natural trigger terms, and carves out a distinct niche for Rails controller development specifically.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Creates Rails controllers', 'TDD approach', 'request spec first, then implementation', 'adding controller actions', 'implementing CRUD operations'. | 3 / 3 |
Completeness | Clearly answers both what ('Creates Rails controllers with TDD approach - request spec first, then implementation') AND when ('Use when creating new controllers, adding controller actions, implementing CRUD operations, or when user mentions controllers, routes, or API endpoints'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'controllers', 'controller actions', 'CRUD operations', 'routes', 'API endpoints'. These are terms Rails developers naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche combining Rails + controllers + TDD approach. The specific focus on request specs and controller-specific terminology makes it distinct from general Rails skills or testing skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with excellent workflow clarity and executable code examples. The TDD approach is well-documented with clear RED-GREEN validation steps. Main weakness is the length - the complete CRUD templates make it verbose, and some content could be extracted to reference files for better progressive disclosure.
Suggestions
Extract the full CRUD spec and controller templates to a separate TEMPLATES.md file, keeping only a minimal example in the main skill
Consider condensing the request spec example to show 1-2 actions with a note that the pattern applies to all CRUD operations
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some redundancy - the full CRUD controller template is quite long and could be trimmed. The project conventions section is appropriately brief, but the complete spec and controller examples could be more concise with just key patterns shown. | 2 / 3 |
Actionability | Provides fully executable, copy-paste ready code for both request specs and controller implementations. Includes specific commands for running specs, concrete examples of authorization patterns, Turbo Stream responses, and namespaced controllers. | 3 / 3 |
Workflow Clarity | Clear 5-step TDD workflow with explicit RED-GREEN-REFACTOR cycle. Each step is numbered with specific actions and bash commands. The checklist at the end provides validation checkpoints for the complete process. | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear sections, but the skill is somewhat monolithic - the full CRUD examples could be split into a separate reference file. The Turbo Stream and namespaced controller patterns are appropriately placed as advanced sections but could benefit from being linked references. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
Total | 10 / 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.