Curated library of 16 public Ruby AI agent skills: 10 atomic skills (YARD docs, service objects, calculator pattern, API clients, DDD, bug triage, code review, skill routing), 5 process-discipline skills (TDD, refactoring, review, security, test planning), and 1 planning skill (TDD task generation). Zero agents — this is a foundational library consumed by framework-specific tiles like rails-agent-skills and hanakai-yaku.
95
96%
Does it follow best practices?
Impact
95%
1.05xAverage score across 16 eval scenarios
Passed
No known issues
{
"context": "Checks whether the final artifact follows the respond-to-review instructions from the published Ruby Core Skills tile.",
"type": "weighted_checklist",
"checklist": [
{
"name": "instruction-1",
"description": "The submitted artifact follows this skill instruction: VERIFY: Check the suggestion against the actual codebase",
"max_score": 17
},
{
"name": "instruction-2",
"description": "The submitted artifact follows this skill instruction: Never respond with performative agreement that skips verification. See [assets/response_templates.md](assets/response_templates.md) for copy-ready patterns and a full list of forbidden phrases.",
"max_score": 17
},
{
"name": "instruction-3",
"description": "The submitted artifact follows this skill instruction: Push back when a suggestion is technically incorrect for the codebase. Use this structure:",
"max_score": 17
},
{
"name": "instruction-4",
"description": "The submitted artifact follows this skill instruction: **Never:** Push back without technical evidence. If unsure, verify before claiming it's fine.",
"max_score": 17
},
{
"name": "instruction-5",
"description": "The submitted artifact follows this skill instruction: **Verify** no regressions — run full suite before requesting re-review",
"max_score": 16
},
{
"name": "instruction-6",
"description": "The submitted artifact follows this skill instruction: **Reasoned pushback** — When a suggestion is incorrect, use the pushback structure: reviewer concern, codebase constraint/evidence, and alternative or no-change rationale. Never push back without technical evidence.",
"max_score": 16
}
]
}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
skills
code-quality
respond-to-review
ddd
define-domain-language
model-domain
review-domain-boundaries
docs
write-yard-docs
orchestration
skill-router
patterns
create-service-object
implement-calculator-pattern
planning
generate-tdd-tasks
process
testing
triage-bug