performance-optimization
Identifies and fixes Rails performance issues including N+1 queries, slow queries, and memory problems. Use when optimizing queries, fixing N+1 issues, improving response times, or when user mentions performance, slow, optimization, or Bullet gem.
Install with Tessl CLI
npx tessl i github:ThibautBaissac/rails_ai_agents --skill performance-optimization85
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/skillAgent success when using this skill
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 an excellent skill description that follows best practices. It uses third person voice, lists specific concrete capabilities (N+1 queries, slow queries, memory problems), includes an explicit 'Use when...' clause with natural trigger terms, and is clearly scoped to Rails performance optimization making it highly distinguishable from other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Identifies and fixes Rails performance issues including N+1 queries, slow queries, and memory problems.' These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Identifies and fixes Rails performance issues including N+1 queries, slow queries, and memory problems') AND when ('Use when optimizing queries, fixing N+1 issues, improving response times, or when user mentions performance, slow, optimization, or Bullet gem'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'performance', 'slow', 'optimization', 'N+1', 'Bullet gem', 'optimizing queries', 'response times'. These are terms developers naturally use when discussing Rails performance. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on Rails performance optimization with distinct triggers like 'N+1', 'Bullet gem', and Rails-specific query optimization. Unlikely to conflict with general coding or other framework skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%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, highly actionable Rails performance optimization skill with excellent code examples and practical patterns. Its main weaknesses are verbosity (explaining concepts Claude knows) and being monolithic rather than using progressive disclosure. Adding explicit validation workflows (benchmark before/after optimization) would strengthen the guidance for safe performance tuning.
Suggestions
Remove explanatory sections like 'The Problem' that explain N+1 queries conceptually - Claude knows this; jump straight to the solution patterns
Add explicit validation workflow: 'Measure baseline -> Apply fix -> Verify improvement -> Commit' with specific benchmarking commands
Split into multiple files: keep Quick Start and common patterns in SKILL.md, move Memory Optimization, Query Analysis, and Testing sections to linked reference files
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some explanatory content Claude already knows (e.g., explaining what N+1 queries are with 'The Problem' section). The SQL comments showing generated queries add value, but some sections could be tightened. | 2 / 3 |
Actionability | Excellent executable code throughout - all examples are copy-paste ready with complete Ruby/Rails code, specific gem configurations, migration syntax, and working test setups. The Quick Fixes Reference table provides immediate actionable guidance. | 3 / 3 |
Workflow Clarity | The Performance Checklist provides a good sequence, but the document lacks explicit validation checkpoints and feedback loops. For performance optimization (which can have destructive impacts on production), there should be clearer 'measure before/after' validation steps. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear headers and tables, but it's a monolithic 300+ line document. Advanced topics like memory profiling, EXPLAIN analysis, and Rack Mini Profiler could be split into separate reference files with links from the main skill. | 2 / 3 |
Total | 9 / 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.