CtrlK
BlogDocsLog inGet started
Tessl Logo

configuring-horizon

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.

69

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-organized, mostly executable skill body that uses progressive disclosure effectively with real reference files. Minor conciseness redundancies and the absence of explicit error-recovery loops in verification keep it just below the top band on two dimensions.

Suggestions

Remove the duplicate 'environments array merges into defaults' note — keep it in Common Pitfalls and reference it from the Supervisor Config section, or vice versa.

Add a brief feedback loop to Verification (e.g. 'If metrics stay blank after scheduling horizon:snapshot, confirm the scheduler is running and the Redis queue driver is set').

Drop the closing 'Always use search-docs...' line since the Documentation section already establishes search-docs as the primary source.

DimensionReasoningScore

Conciseness

Lean body with executable code and Horizon-specific gotchas rather than generic explanations; docked one point for the duplicated 'environments array merges into defaults and does not replace it' note (in both the Supervisor section and Common Pitfalls) and the mildly redundant closing 'Always use search-docs...' line that echoes the Documentation section.

4 / 5

Actionability

Provides copy-paste-ready commands and config (horizon:install, full supervisor/defaults PHP array, Gate::define block, horizon:snapshot); minor gaps because notifications, metrics, and tags are delegated to references without inline examples for those common cases.

4 / 5

Workflow Clarity

Logical install → configure → authorize sequence with a 3-step Verification checklist ('Run php artisan horizon and visit /horizon', 'Confirm dashboard access is restricted', 'Check that metrics populate'), but lacks explicit error-recovery feedback loops (e.g. what to do if metrics stay blank), so it stops short of a 5.

4 / 5

Progressive Disclosure

Clear concise overview with four well-signaled one-level-deep references (references/supervisors.md, notifications.md, tags.md, metrics.md), each summarizing its scope; all referenced files exist and content is appropriately split for easy navigation.

5 / 5

Total

17

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that defines a clear Horizon-only niche with concrete capabilities, an explicit trigger, and thorough out-of-scope boundaries. Slightly heavy on technical jargon versus natural user phrasing, but otherwise excellent.

DimensionReasoningScore

Specificity

Lists multiple concrete actions across the full lifecycle — 'installing Horizon (horizon:install, Sail setup)', 'configuring config/horizon.php (supervisor blocks... minProcesses/maxProcesses)', 'fixing the dashboard (authorization via Gate::define viewHorizon... horizon:snapshot scheduling)', 'troubleshooting production issues (worker crashes, timeout chain ordering, LongWaitDetected notifications)' — with comprehensive coverage.

5 / 5

Completeness

Explicitly answers both 'what' (enumerated lifecycle capabilities) and 'when' ('Use this skill whenever the user mentions Horizon by name in a Laravel context') with a concrete trigger phrase, plus explicit out-of-scope guidance.

5 / 5

Trigger Term Quality

Good keyword coverage including natural terms ('Horizon by name', 'Laravel', 'queues', 'dashboard') plus technical identifiers (horizon:install, config/horizon.php, LongWaitDetected); a few natural user synonyms (e.g. 'Laravel Horizon dashboard', 'queue monitor') are absent, keeping it just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

Clear Horizon-only niche with explicit exclusions ('Do not use for generic Laravel queues without Horizon, SQS or database drivers, standalone Redis setup, Linux supervisord, Telescope, or job batching') minimizing overlap with adjacent skills.

5 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
yaojingang/GEOFlow
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.