Skill Detail

Operate Rails Active Job queues with Mission Control Jobs

Use Mission Control Jobs when an operator needs a Rails-mounted dashboard to inspect Active Job queues, review failed jobs, and retry or discard jobs with supervision.

Runbooks & DiagnosticsCustom Agents
Runbooks & Diagnostics Custom Agents Security Reviewed
⭐ 1.1k GitHub stars
COPY SKILL INSTRUCTIONS (OPTIONAL)
npx skills add agentskillexchange/skills --skill operate-rails-active-job-queues-with-mission-control-jobs Copy
Uses the third-party skills CLI, not an ASE-owned installer. Check your agent’s compatibility. This copies instructions; complete the upstream tool setup below separately.
At a glance
Tools required
Ruby on Rails, Active Job, mission_control-jobs gem, Resque or Solid Queue
Install & setup
Add gem "mission_control-jobs" to the Rails application's Gemfile, run bundle install, mount MissionControl::Jobs::Engine in routes.rb, and configure authentication before exposing the dashboard. For API-only Rails apps or custom asset pipelines, follow the upstream README's Propshaft and asset precompile guidance.
Author
Rails
Publisher
Open Source Project
Last updated
Aug 28, 2026
Quick brief

Use this skill when a Rails-based agent service or automation app relies on Active Job and needs a repeatable operations workflow for queue inspection and failed-job recovery. The agent should verify the app uses a supported adapter such as Resque or Solid Queue, confirm Mission Control Jobs is mounted behind appropriate admin access, then guide the operator through checking queue state, inspecting pending or failed jobs, and deciding whether to retry, discard, pause, or escalate work. This is not a generic Rails product card or a background-job framework listing. Keep the scope to operational runbooks around Rails Active Job queues: setup review, dashboard access checks, failed-job triage, adapter-specific limitations, and reviewable remediation steps. Prefer this over ad hoc console commands when the user needs a safer operator surface for production or staging job queues, especially when failed jobs affect agent workflows, scheduled automations, notifications, syncs, or data pipelines. Do not use it for non-Rails workers, unrelated observability, or arbitrary job scheduling design.