rails-query-object
Creates query objects for complex database queries following TDD. Use when encapsulating complex queries, aggregating statistics, building reports, or when user mentions queries, stats, dashboards, or data aggregation.
Install with Tessl CLI
npx tessl i github:fernandezbaptiste/rails_ai_agents --skill rails-query-object83
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
82%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 solid description that clearly communicates both purpose and trigger conditions. The explicit 'Use when...' clause with multiple trigger terms is a strength. However, the description could be more specific about the concrete actions performed and could better differentiate itself from other data/reporting related skills.
Suggestions
Add more specific concrete actions like 'builds ActiveRecord scopes, creates SQL aggregations, implements query caching' to improve specificity
Include distinguishing details like the specific framework or ORM pattern used (e.g., 'Rails Query Objects', 'Repository pattern') to reduce conflict risk with general database or reporting skills
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (database queries, TDD) and mentions actions like 'encapsulating complex queries, aggregating statistics, building reports', but lacks specific concrete actions like 'create SQL joins, build aggregation pipelines, generate parameterized queries'. | 2 / 3 |
Completeness | Clearly answers both what ('Creates query objects for complex database queries following TDD') and when ('Use when encapsulating complex queries, aggregating statistics, building reports, or when user mentions queries, stats, dashboards, or data aggregation'). | 3 / 3 |
Trigger Term Quality | Good coverage of natural terms users would say: 'queries', 'stats', 'dashboards', 'data aggregation', 'reports', 'statistics'. These are terms users naturally use when needing this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | The TDD aspect and 'query objects' pattern provide some distinction, but terms like 'reports', 'dashboards', and 'data aggregation' could overlap with reporting skills, analytics skills, or general database skills. | 2 / 3 |
Total | 10 / 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 concrete, executable examples. The TDD approach is well-documented with clear RED-GREEN checkpoints. Main weaknesses are moderate verbosity (some redundancy between sections) and all content being inline rather than using progressive disclosure for the multiple patterns.
Suggestions
Remove the Quick Start section since it duplicates the TDD Workflow steps, or consolidate them into a single workflow section
Consider moving Patterns 2 and 3 to a separate PATTERNS.md file, keeping only Pattern 1 as the primary example in the main skill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some redundancy - the TDD workflow steps are repeated in both the Quick Start and detailed sections, and some patterns could be more condensed. The code examples are appropriate but the overall document could be tightened. | 2 / 3 |
Actionability | Provides fully executable, copy-paste ready Ruby code examples with complete spec templates, implementation patterns, and bash commands. The patterns are concrete and immediately usable. | 3 / 3 |
Workflow Clarity | Clear 4-step TDD sequence (RED-GREEN) with explicit validation checkpoints ('Run spec to confirm RED/GREEN'). The workflow includes feedback loops inherent to TDD and ends with a comprehensive checklist for verification. | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear sections, but everything is inline in a single file. For a skill of this length (~150 lines), the multiple patterns could be split into a separate PATTERNS.md file with the main skill providing just one example pattern. | 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.