agentleFS
Sign inStart free
syofyanzuhadsyofyanzuhad/uptime-kita/.github/skills/configuring-horizon/SKILL.md

configuring-horizon

Skill184 starsChanged 2 months agoApache-2.0View on GitHub

Use this skill whenever the user mentions Horizon by name in a Laravel context. Covers the full Horizon lifecycle: installing Horizon (horizon:install, Sail setup), configuring config/horizon.php (supervisor blocks, queue assignments, balancing strategies, minProcesses/maxProcesses), fixing the dashboard (authorization via Gate::define viewHorizon, blank metrics, horizon:snapshot scheduling), and troubleshooting production issues (worker crashes, timeout chain ordering, LongWaitDetected notifications, waits config). Also covers job tagging and silencing. Do not use for generic Laravel queues without Horizon, SQS or database drivers, standalone Redis setup, Linux supervisord, Telescope, or job batching.

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 0 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use search-docs for detailed Horizon patterns and documentation covering configuration, supervisors, balancing, dashboard authorization, …

    line 13
  2. Very specific:

    Run php artisan horizon and visit /horizon

    line 73
  3. Very specific:

    Check that metrics populate after scheduling horizon:snapshot

    line 75
  4. Very specific:

    Always check config/horizon.php before making changes to understand the current supervisor and environment configuration.

    line 81
  5. Very specific:

    Always use search-docs for the latest Horizon documentation rather than relying on this skill alone.

    line 85

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Horizon Configuration

Documentation

Use search-docs for detailed Horizon patterns and documentation covering configuration, supervisors, balancing, dashboard authorization, tags, notifications, metrics, and deployment.

For deeper guidance on specific topics, read the relevant reference file before implementing:

  • references/supervisors.md covers supervisor blocks, balancing strategies, multi-queue setups, and auto-scaling
  • references/notifications.md covers LongWaitDetected alerts, notification routing, and the waits config
  • references/tags.md covers job tagging, dashboard filtering, and silencing noisy jobs
  • references/metrics.md covers the blank metrics dashboard, snapshot scheduling, and retention config

Basic Usage

Installation

php artisan horizon:install

Supervisor Configuration

Define supervisors in config/horizon.php. The environments array merges into defaults and does not replace the whole supervisor block:

<!-- Supervisor Config -->
'defaults' => [
    'supervisor-1' => [
        'connection' => 'redis',
        'queue' => ['default'],
        'balance' => 'auto',
        'minProcesses' => 1,
        'maxProcesses' => 10,
        'tries' => 3,
    ],
],

'environments' => [
    'production' => [
        'supervisor-1' => ['maxProcesses' => 20, 'balanceCooldown' => 3],
    ],
    'local' => [
        'supervisor-1' => ['maxProcesses' => 2],
    ],
],

Dashboard Authorization

Restrict access in App\Providers\HorizonServiceProvider:

<!-- Dashboard Gate -->
protected function gate(): void
{
    Gate::define('viewHorizon', function (User $user) {
        return $user->is_admin;
    });
}

Verification

  1. Run php artisan horizon and visit /horizon
  2. Confirm dashboard access is restricted as expected
  3. Check that metrics populate after scheduling horizon:snapshot

Common Pitfalls

  • Horizon only works with the Redis queue driver. Other drivers such as database and SQS are not supported.
  • Redis Cluster is not supported. Horizon requires a standalone Redis connection.
  • Always check config/horizon.php before making changes to understand the current supervisor and environment configuration.
  • The environments array overrides only the keys you specify. It merges into defaults and does not replace it.
  • The timeout chain must be ordered: job timeout less than supervisor timeout less than retry_after. The wrong order can cause jobs to be retried before Horizon finishes timing them out.
  • The metrics dashboard stays blank until horizon:snapshot is scheduled. Running php artisan horizon alone does not populate metrics.
  • Always use search-docs for the latest Horizon documentation rather than relying on this skill alone.

Download now (ZIP)

Trending

Steady: 1 new project took it in the last 4 weeks, 1× the 4 weeks before.thin data

Week of Aug 30: 0 new projectsWeek of Sep 6: 1 new projectWeek of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 1 new projectWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projects
Aug 2026Sep 2026Oct 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 2 in all, so this is a hint, not a trend.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free