rails-architecture
Guides modern Rails 8 code architecture decisions and patterns. Use when deciding where to put code, choosing between patterns (service objects vs concerns vs query objects), designing feature architecture, refactoring for better organization, or when user mentions architecture, code organization, design patterns, or layered design.
Install with Tessl CLI
npx tessl i github:fernandezbaptiste/rails_ai_agents --skill rails-architecture99
Does it follow best practices?
Validation 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 follows best practices. It clearly specifies the domain (Rails 8 architecture), lists concrete actions and pattern types, includes an explicit 'Use when...' clause with both situational triggers and keyword triggers, and uses proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'deciding where to put code', 'choosing between patterns (service objects vs concerns vs query objects)', 'designing feature architecture', 'refactoring for better organization'. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Guides modern Rails 8 code architecture decisions and patterns') and when ('Use when deciding where to put code, choosing between patterns... or when user mentions architecture, code organization, design patterns, or layered design'). Has explicit 'Use when...' clause. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'architecture', 'code organization', 'design patterns', 'layered design', 'service objects', 'concerns', 'query objects', 'refactoring'. Good coverage of both general and Rails-specific terminology. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on Rails 8 architecture decisions and code organization patterns. The specific mention of 'Rails 8', pattern types (service objects, concerns, query objects), and architecture focus makes it distinct from general coding or other framework skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an exemplary skill file that efficiently guides Rails 8 architecture decisions. It uses visual decision trees, clear tables, and concrete code examples while maintaining excellent progressive disclosure through well-organized references to related skills and documentation. The content respects Claude's intelligence by focusing on decision criteria and patterns rather than explaining basic concepts.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is highly efficient, using tables, decision trees, and diagrams instead of verbose prose. It assumes Claude understands Rails concepts and doesn't explain basics like what a controller or model is. | 3 / 3 |
Actionability | Provides concrete, executable Ruby code examples for good/bad patterns, specific line count thresholds for refactoring decisions (e.g., 'Controller action > 15 lines'), and clear decision criteria with actionable outcomes. | 3 / 3 |
Workflow Clarity | The decision tree provides an unambiguous workflow for architectural decisions. The 'New Feature Checklist' gives a clear numbered sequence. The layer interaction diagram shows explicit flow with validation points (authenticate, authorize before delegating). | 3 / 3 |
Progressive Disclosure | Excellent structure with overview content in the main file and clear one-level-deep references to detailed skills (e.g., 'See rails-service-object skill') and reference files (e.g., 'See layer-interactions.md'). Navigation is well-signaled throughout. | 3 / 3 |
Total | 12 / 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.