RubyGems packages software. Ruby Skills packages the engineering knowledge that lives in your team's heads — versioned, installable, and shareable across projects and coding agents.
gem install ruby-skills
Coming soon — follow development on GitHub
Whether you maintain a gem, lead an engineering team, or contribute to open source — Ruby Skills gives you a way to share what you know.
Your gem already includes the code. Now ship the patterns, conventions, and best practices your users should follow. Skills install alongside your gem — no separate setup needed.
# Users get this automatically:
skill "example/job-queues" # via gem
Encode your team's Ruby conventions, architectural decisions, and code standards as a private skill. Every engineer and every coding agent follows the same playbook — versioned and locked.
# Example private skill:
skill "example/team-conventions"
Write skills for the Ruby patterns you care about — functional programming, concurrency, performance, testing. Publish to the public registry. Let the community improve them over time.
# Example public skill:
skill "example/fp-patterns"
A skill is a directory of Markdown files describing patterns, conventions, and heuristics — plus a skill.toml manifest. Write it once, version it, publish it.
skill.tomlname = "example/job-queues"
version = "0.1.0"
description = "Example job-queue conventions"
license = "MIT"
authors = ["@example"]
[dependencies]
ruby = ">= 3.1"## Idempotency
All jobs MUST be idempotent.
Your job runner retries on failure.
## Queue naming
Never use the default queue for
critical work. Define named queues:
critical, default, low.
## Retry limits
Set explicit retry limits on every
job class. Default is 25 — too high
for most production work.Help us make that knowledge installable. Join early access and shape how Ruby Skills evolves.