Creates presenter objects for view formatting using SimpleDelegator pattern with TDD. Use when extracting view logic from models, formatting data for display, creating badges/labels, or when user mentions presenters, view models, formatting, or display helpers.
Install with Tessl CLI
npx tessl i github:fernandezbaptiste/rails_ai_agents --skill rails-presenter90
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 provides specific concrete actions, includes natural trigger terms developers would use, explicitly states both what the skill does and when to use it, and carves out a distinct niche around the presenter pattern with SimpleDelegator.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Creates presenter objects', 'view formatting', 'SimpleDelegator pattern', 'TDD', 'extracting view logic from models', 'formatting data for display', 'creating badges/labels'. | 3 / 3 |
Completeness | Clearly answers both what ('Creates presenter objects for view formatting using SimpleDelegator pattern with TDD') and when ('Use when extracting view logic from models, formatting data for display, creating badges/labels, or when user mentions presenters, view models, formatting, or display helpers'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'presenters', 'view models', 'formatting', 'display helpers', 'badges/labels', 'view logic'. These cover common variations of how developers discuss this pattern. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche targeting the presenter/decorator pattern specifically with SimpleDelegator and TDD context. The combination of 'presenter', 'SimpleDelegator', and 'view formatting' creates a distinct trigger profile unlikely to conflict with general formatting or model 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 examples. The TDD process is well-documented with clear validation steps. Main weaknesses are moderate verbosity (showing 'already exists' code, duplicative patterns) and missed opportunities for progressive disclosure by splitting reference material into separate files.
Suggestions
Remove or significantly reduce the BasePresenter code block since it's labeled as already existing - a brief reference to its location is sufficient
Move 'Common Presenter Methods' section to a separate PRESENTER_PATTERNS.md reference file and link to it
Consolidate the spec and implementation examples to show one complete, focused example rather than multiple similar patterns
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some redundancy - the BasePresenter code block is shown despite being labeled 'Already Exists', and the common presenter methods section duplicates patterns already demonstrated in the main example. Some tightening possible. | 2 / 3 |
Actionability | Provides fully executable, copy-paste ready code examples throughout. The TDD workflow has concrete spec examples, implementation code, and exact bash commands to run. All code is complete and runnable. | 3 / 3 |
Workflow Clarity | Clear 4-step TDD workflow (RED → confirm RED → implement → GREEN) with explicit validation checkpoints. Each step has concrete commands and the checklist at the end provides verification. The feedback loop is inherent in the TDD process. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but it's a monolithic file that could benefit from splitting. The 'Common Presenter Methods' section could be a separate reference file, and the BasePresenter code could be omitted or linked rather than inline. | 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 | |
Table of Contents
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.