igmarin/rails-agent-skills

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.

1.78x

Quality

95%

Does it follow best practices?

Impact

93%

1.78x

Average score across 28 eval scenarios

Securityby

Passed

No known issues

Eval Provenance Policy

Name: igmarin/rails-agent-skills
Rating: 93.21 (1 reviews)
Author: igmarin

This repository uses two public eval source areas and one generated staging area.

Path	Purpose	Commit policy
`tessl-evals/`	Tessl-native scenarios for publishable skills in `tile.json`.	Tracked.
`personal-evals/`	Open examples for the upcoming `ruby-skill-bench` full-context evaluator.	Tracked.
`evals/`	Generated Tessl staging output produced from `tessl-evals/`.	Ignored; do not commit.

Tessl currently validates skills, not repository workflows. Tessl-native scenarios must target only publishable skills from tile.json.

ruby-skill-bench is planned as a Ruby gem for validating skills and workflows with full context. Its personal-evals/ examples load SKILL.md plus companion resources as XML. They do not need to be Tessl-compatible while Tessl only consumes SKILL.md.

Generated scenarios from third-party services or private workflows must stay out of tracked paths. Store them locally in ignored directories such as private-evals/ when needed for private validation.

Root evals/ is generated Tessl staging output only. The release workflow stages tessl-evals/ into evals/ immediately before publishing.

Public eval examples must meet one of these criteria:

They are authored specifically for this repository and released under the repository license.
They are derived from a permissively licensed source, with attribution and license notes included beside the example.

Do not rename generated scenarios to make them look original. Provenance must describe where the scenario came from and why it can be redistributed.