Skill Detail

Run .NET background and recurring agent jobs with Hangfire

Use Hangfire to enqueue, schedule, retry, and supervise durable .NET jobs that support agent maintenance, ingestion, reports, and workflow handoffs.

Templates & WorkflowsCustom Agents
Templates & Workflows Custom Agents Security Reviewed
⭐ 10.1k GitHub stars
COPY SKILL INSTRUCTIONS (OPTIONAL)
npx skills add agentskillexchange/skills --skill run-dotnet-background-recurring-agent-jobs-with-hangfire 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
.NET or .NET Core application, Hangfire NuGet packages, SQL Server/Redis/SQL Azure/MSMQ or supported storage, Hangfire Dashboard
Install & setup
Install the Hangfire NuGet package, configure storage with GlobalConfiguration.Configuration.UseSqlServerStorage(...) or another supported provider, add UseHangfireServer() and UseHangfireDashboard(), then enqueue, schedule, or register recurring jobs from the .NET service.
Author
HangfireIO
Publisher
Organization
Last updated
Sep 21, 2026
Quick brief

Use Hangfire when a .NET-based agent workflow needs reliable fire-and-forget, delayed, recurring, or chained background jobs with dashboard visibility instead of ad hoc timers, local cron, or web-request side effects. The operator wires Hangfire into the .NET application, configures SQL Server, Redis, SQL Azure, or another supported store, starts workers, and has agent-adjacent tasks such as ingestion refreshes, report generation, cleanup, webhooks, batch imports, or evaluation sweeps enqueue named jobs that can be retried and inspected.

How it works

What this skill actually does

Invoke this instead of using Hangfire as a normal app library when the job is to keep supervised agent operations durable and reviewable inside a .NET service. The scope boundary is operating background and recurring work for agent workflows in Hangfire: define jobs, schedule them, monitor the dashboard, retry failures, and keep long-running work out of chat or request handlers. It is not a generic .NET framework, queueing theory, or full Hangfire feature survey.