Curated library of 28 public AI agent skills for Ruby on Rails development. Organized by category: testing, code-quality, engines, infrastructure, api, and context. Covers code review, architecture, security, testing (RSpec), engines, Hotwire, and TDD automation. Shared Ruby skills (YARD docs, DDD, service objects) have moved to ruby-core-skills. Repository agents remain documented in GitHub but are intentionally excluded from the Tessl tile.
93
95%
Does it follow best practices?
Impact
93%
1.78xAverage score across 28 eval scenarios
Passed
No known issues
{
"context": "Checks whether the final artifact follows the apply-code-conventions instructions from the published Rails Agent Skills tile.",
"type": "weighted_checklist",
"checklist": [
{
"name": "instruction-1",
"description": "The submitted artifact follows this skill instruction: **Run linter** — Detect config (for example `.rubocop.yml` or `.standard.yml`), run the appropriate tool, note absence if none found. Do not invent style rules; all style/formatting defers to the detected config. *Output: state which linter was detected (or absent) and that style defers to it.*",
"max_score": 13
},
{
"name": "instruction-2",
"description": "The submitted artifact follows this skill instruction: **Apply area-specific rules** — Check path patterns (e.g., models, background jobs, controllers) and apply targeted guidance from the Apply by area table below. *Output: concrete per-path recommendations for every relevant changed file.*",
"max_score": 13
},
{
"name": "instruction-3",
"description": "The submitted artifact follows this skill instruction: **Verify tests gate** — Confirm failing tests exist before any new behavior; run specs and checkpoints. *Output: state the failing spec, run command, expected failure, minimal implementation step, and passing rerun.*",
"max_score": 13
},
{
"name": "instruction-4",
"description": "The submitted artifact follows this skill instruction: **Chain to specialised skills** — Use the Integration table to pull in deeper guidance (security, jobs, specs) as needed.",
"max_score": 13
},
{
"name": "instruction-5",
"description": "The submitted artifact follows this skill instruction: Only recommend `let_it_be` if `test-prof` is already in `Gemfile.lock`. Otherwise default to `let`; reach for `let!` only when lazy evaluation would break the example. Don't introduce `test-prof` unless asked.",
"max_score": 12
},
{
"name": "instruction-6",
"description": "The submitted artifact follows this skill instruction: Load these files only when their specific content is needed:",
"max_score": 12
},
{
"name": "instruction-7",
"description": "The submitted artifact follows this skill instruction: **[assets/checklist.md](assets/checklist.md)** — Use for detailed code review checklists.",
"max_score": 12
},
{
"name": "instruction-8",
"description": "The submitted artifact follows this skill instruction: **[assets/snippets.md](assets/snippets.md)** — Use for quick code snippets of common patterns.",
"max_score": 12
}
]
}agents
docs
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10
scenario-11
scenario-12
scenario-13
scenario-14
scenario-15
scenario-16
scenario-17
scenario-18
scenario-19
scenario-20
scenario-21
scenario-22
scenario-23
scenario-24
scenario-25
scenario-26
scenario-27
scenario-28
skills
api
generate-api-collection
implement-graphql
code-quality
apply-code-conventions
apply-stack-conventions
assets
snippets
code-review
refactor-code
review-architecture
security-check
context
load-context
setup-environment
engines
create-engine
create-engine-installer
document-engine
extract-engine
release-engine
review-engine
test-engine
upgrade-engine
infrastructure
implement-background-job
implement-hotwire
optimize-performance
review-migration
seed-database
version-api
testing
plan-tests
test-service
write-tests