Agent skill

Arandu Async

by arandu-io in arandu-io/arandu

Work that does not happen inside the request in an Arandu (Go) application -- background jobs and the worker, scheduled tasks, domain events through the outbox, listeners, notifications, mail and…

MITAuto-check passedProductivity & Automation

Install Arandu Async

skills CLI
$ npx skills add arandu-io/arandu --skill arandu-async -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install arandu-io/arandu arandu-async --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/arandu-io/arandu.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/arandu-async .claude/skills/arandu-async && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
arandu-async
GitHub stars
281
Token cost
~2.7k tokens
SKILL.md length
1,115 words
Files
1
Skills in repo
12
Repo updated
First seen
Licence
MIT

At a glance

Work that does not happen inside the request in an Arandu (Go) application -- background jobs and the worker, scheduled tasks, domain events through the outbox, listeners, notifications, mail and…

  • Works in 6 steps: A fact that happened is an event. `aru… → A reaction to it is a listener. `aru… → Telling a person is a notification. `aru… → …
  • The request is to send an email
  • SKILL.md covers When to use, Before you start, Contracts and imports and Procedure, plus 8 more sections
  • Calls go and bash

What it does

Arandu Async is an agent skill from arandu-io/arandu. Work that does not happen inside the request in an Arandu (Go) application -- background jobs and the worker, scheduled tasks, domain events through the outbox, listeners, notifications, mail and console commands. Use when the request is to "send an email", "notify the user", "run this every night", "do this in the background", "react when X happens", "retry this", "add a command", or when a queue, the scheduler, the outbox, a listener or a notification is involved. Covers aru make:job, make:event, make:listener…

Its SKILL.md is about 2.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Productivity & Automation, covering Scheduled and recurring tasks and Background jobs. It works with React. The repository describes itself as: The Arandu project skeleton, which aru new clones. The licence is MIT.

When your agent uses it

  • The request is to send an email
  • Notify the user
  • Run this every night
  • Do this in the background

Example prompts

  • “send an email”
  • “notify the user”
  • “run this every night”
  • “/arandu-async”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. A fact that happened is an event. `aru make:event NotePublished
  2. A reaction to it is a listener. `aru make:listener NotifyNoteAuthor
  3. Telling a person is a notification. `aru make:notification NotePublished
  4. Work worth retrying is a job. `aru make:job SendNotesDigest
  5. Recurring work is a task that enqueues a job. Declare it in
  6. An operator's action is a command. aru make:command and a line in

What it can do on your machine

Read from SKILL.md and the folder at commit b8a4273. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • go
    • bash

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Arandu Async loads about 2.7k tokens when it runs. Until then it costs about 158 tokens; SKILL.md has 1,115 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~158
When it runs · the whole SKILL.md, loaded when a task matches
~2.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from arandu-io/arandu at commit b8a4273, republished under its MIT licence (© arandu-io). 1,115 words, ~2,706 tokens.

Download SKILL.mdSave it as .claude/skills/arandu-async/SKILL.md (or your agent's skills folder).
name
arandu-async
description
Work that does not happen inside the request in an Arandu (Go) application -- background jobs and the worker, scheduled tasks, domain events through the outbox, listeners, notifications, mail and console commands. Use when the request is to "send an email", "notify the user", "run this every night", "do this in the background", "react when X happens", "retry this", "add a command", or when a queue, the scheduler, the outbox, a listener or a notification is involved. Covers aru make:job, make:event, make:listener, make:notification, make:mail and make:command, and aru schedule:list, schedule:run and queue:work.
license
MIT

Background work, events and notifications

When to use

Anything that runs after the response, on a schedule, or because something happened: a job, a scheduled task, an event and its listeners, a notification, a mail, a console command. The service that a job or a listener calls is arandu-module; an external system it reaches is arandu-integrations.

Before you start

  • Read the example's chain: NoteService.Publish stores note.published; app/Listeners/NotifyNoteAuthor.go reacts and sends app/Notifications/NotePublished.go; AppServiceProvider.Schedule enqueues app/Jobs/SendNotesDigest.go every night, and the worker runs it.
  • Know where each runs. The relay and the scheduler run inside aru serve; jobs run in aru queue:work, the same binary with another argument.

Contracts and imports

piececontract
jobapp/Jobs/<Name>.go: a payload struct of facts and ids; Dispatch<Name>(ctx, q queue.Queue, g auth.Grant, in), which jobs.New builds with the Grant's tenant and action; a handler implementing queue.Handler -- Handle(ctx, g auth.Grant, j *jobs.Job) error -- with its services as fields
workerregisterHandlers(w, app) in bootstrap/background.go, custom block: w.Handle(appjobs.<Name>Name, appjobs.New<Name>Handler(app.Notes))
scheduled taska foundation.Task (github.com/arandu-io/hesape/foundation) returned by AppServiceProvider.Schedule: ID, five-field Spec, Scope (Global or PerTenant), Singleton, Timeout, Action, and Run(ctx, g auth.Grant) error; the Grant is built from Action and the tenant
eventapp/Events/<Name>.go: a past-tense name in the domain's words (note.published), a payload of facts, and Event(aggregateID) events.Event
storing itoutbox.Store(ctx, g, []events.Event{...}) inside database.Transaction, beside the write; the outbox is events.NewOutbox(db) from github.com/arandu-io/framework/events
listenerapp/Listeners/<Name>.go: an events.Publisher -- Publish(ctx, e events.Stored) error -- that returns early for other names and decodes the payload into a struct of its own
notificationapp/Notifications/<Name>.go: Key(), Via(to) []ChannelName and one method per channel (ToDatabase), sent with notifier.Send(ctx, g, to, n) where g is a Grant for notifications.ActionSend
commandapp/Console/Commands, registered in routes/console.go

Procedure

  1. A fact that happened is an event. aru make:event NotePublished --aggregate=note --event-name=note.published --fields "title:string". The service stores it in the transaction of the write it describes, so an event is never stored for a write that rolled back, and a write is never committed without its event.
  2. A reaction to it is a listener. aru make:listener NotifyNoteAuthor --event=note.published, then add it to listeners.Each in bootstrap/app.go. The relay calls it after the commit, at least once: what it does has to be safe to do twice -- an upsert keyed by e.ID, a call with an idempotency key -- and an error means "try again later", never "skip".
  3. Telling a person is a notification. aru make:notification NotePublished --channels=database writes the notification and its test; it is sent with the Notifier bootstrap builds (app.Notifier), from the listener or the service that decided to tell somebody.
  4. Work worth retrying is a job. aru make:job SendNotesDigest --event-name=notes.digest --fields "since:timestamp". The caller that holds the queue dispatches it: a listener, after the write that stored its event has committed, or a task in AppServiceProvider.Schedule, as the digest is. A service never does -- the job's package imports app/Services once its handler takes a service, and a service importing it back is an import cycle. The handler calls a service; j.UUID is stable across retries and is the key to deduplicate on.
  5. Recurring work is a task that enqueues a job. Declare it in AppServiceProvider.Schedule; the task decides what work exists and the job does it, with the retries a task does not get. A task that reads a tenant's rows is PerTenant, and runs for each tenant the scheduler's Tenants returns.
  6. An operator's action is a command. aru make:command and a line in routes/console.go.

Commands

  • aru make:job <Name> --event-name=<name> --fields "..." [--services=<Entity>,...]
  • aru make:event <Name> --aggregate=<entity> --event-name=<entity.verb> --fields "..."
  • aru make:listener <Name> --event=<entity.verb>
  • aru make:notification <Name> --channels=database
  • aru make:mail <Name> --subject "..." --fields "...", aru make:command <Name> --signature=notes:prune --description="..."
  • aru schedule:list, aru schedule:run <id> --tenant=<id>
  • aru queue:work, aru queue:failed --tenant=<id>, aru queue:retry --tenant=<id>

Example

A listener that reacts to the example's event, and a task that enqueues the example's job every Monday:

go
package example

import (
	"context"
	"time"

	"github.com/arandu-io/hesape/auth"
	"github.com/arandu-io/hesape/events"
	hfoundation "github.com/arandu-io/hesape/foundation"
	"github.com/arandu-io/hesape/log"
	"github.com/arandu-io/hesape/queue"

	appevents "<module>/app/Events"
	appjobs "<module>/app/Jobs"
	policies "<module>/app/Policies"
)

// LogPublication writes a line for every published note, after the write
// committed. A repeat writes the line again, which is safe.
type LogPublication struct{}

var _ events.Publisher = LogPublication{}

// Publish answers note.published and nothing else.
func (LogPublication) Publish(ctx context.Context, e events.Stored) error {
	if e.Name != appevents.NotePublishedName {
		return nil
	}
	var published struct {
		Title string `json:"title"`
	}
	if err := e.Decode(&published); err != nil {
		return err
	}
	log.For(ctx).Info("note published", "note", e.AggregateID, "title", published.Title)
	return nil
}

// WeeklyDigest decides that a digest is due, per tenant, and enqueues it.
func WeeklyDigest(q queue.Queue) hfoundation.Task {
	return hfoundation.Task{
		ID:        "notes.weekly-digest",
		Spec:      "0 8 * * 1",
		Scope:     hfoundation.PerTenant,
		Singleton: true,
		Timeout:   time.Minute,
		Action:    policies.NoteList,
		Run: func(ctx context.Context, g auth.Grant) error {
			return appjobs.DispatchSendNotesDigest(ctx, q, g, appjobs.SendNotesDigest{
				Since: time.Now().AddDate(0, 0, -7),
			})
		},
	}
}
Show full SKILL.md (486 more words)Show less

Do not

  • Start a goroutine in a constructor, a service or Boot to do work later: it dies with the process and nobody retries it. A job does.
  • Call a listener, publish an event or send a notification from inside the transaction that produced it: the reader sees a write that may still roll back. Store the event; the relay publishes after the commit.
  • Dispatch a job from a service. The handler calls services, so the job's package imports app/Services, and the import back is a cycle the compiler refuses. Store an event; its listener dispatches the job.
  • Share the producer's payload type with a listener. The listener decodes into a struct of its own, so the two deploy apart.
  • Return nil from a listener or a handler that failed: the outbox and the queue keep the work only when told it was not done.
  • Use auth.SystemGrant in a listener without its reason on the line before: //arandu:system-grant <reason>. The example's listener rebuilds the Grant from the tenant sealed into the outbox row, for sending a notification and nothing else.

Extending it

The handler's collaborators, the listener's work and a notification's fields and payload go in their custom blocks. A second listener for the same event is a second type in listeners.Each, never a switch in the first. A task is one more entry in Schedule.

Wiring

All in two files, by hand:

  • bootstrap/app.go: the listener in listeners.Each, built with what it needs (the example's takes the notifier); the notifier itself, with its channels; the scheduler's Tenants; the services a handler takes, returned in App; the queue handed to the provider with WithQueue.
  • bootstrap/background.go: the handler, in the custom block of registerHandlers, built from app. aru make:job --services=<Entity> writes the constructor with those services and prints the registerHandlers line that passes them from app, with the App fields to add when they are not there yet.

Acceptance test

  • An event: the write and the outbox row in one transaction, and a refused write storing none (TestTheAuthorPublishesANoteOnceWithItsEvent).
  • A listener: drive the application's own relay with app.Relay.Drain(ctx) and read its effect (TestTheAuthorOfAPublishedNoteIsToldThroughTheOutbox).
  • A notification: its generated test, and its payload.
  • A task and its job: the declared schedule, RunNow on the path the scheduler takes, the job on the queue, and a worker running it with fakes (TestTheNightlyDigestIsScheduledQueuedAndSentWithoutTheNetwork).

Limits

There is no mail channel for notifications: the notifier needs a channels.Mailer, and none is built over the application's mail.Mailer, so a notification that names mail is refused with notifications.ErrNoChannel. Mail itself works through app.Mail and aru make:mail. Delivery is at-least-once everywhere and nothing checks that an effect is safe to repeat; aru doctor reads the code, it does not run it. A PerTenant task runs only for the tenants the scheduler's Tenants returns -- this project returns the one tenant every login belongs to.

Gates

Run them all, in this order, as AGENTS.md lists them:

sh
export GOWORK=off
aru model:build --check
aru view:build
gofmt -l $(find . -name '*.go' -not -path '*/testdata/*' -not -name '*.kyse.go')
go vet ./...
bash tests/test-layout-guard.sh
go test -race ./...
go build ./...
aru doctor
<!-- arandu:begin custom -->
<!-- arandu:end custom -->

© arandu-io, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/arandu-async of arandu-io/arandu.

Open the folder on GitHubat commit b8a4273

Compare with similar skills

Arandu Async next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Arandu Async compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Arandu Async this skillarandu-io/arandu281—~2.7kAutomated safety check: PassMIT
Inngest Durable FunctionsAsymmetric-al/core381—~4kAutomated safety check: PassAGPL-3.0
AI Automation WorkflowsNeverSight/learn-skills.dev2171 repos~2.6kAutomated safety check: PassNone
Minimal Web Baas DemoTencentCloudBase/CloudBase-AI-Toolkit1.1k1 repos~2.3kAutomated safety check: PassMIT
Trigger.dev Background Taskspapermark/papermark9.2k—~2.1kAutomated safety check: PassCustom licence
Frappe App Devfrappe/skills147—~943Automated safety check: PassNone

Similar skills

  • Inngest Durable Functions

    Asymmetric-al/core

    A skill your agent uses when building functions that must survive process crashes, retry automatically on failure, run on a schedule, react to events, or maintain state across infrastructure…

    381 GitHub stars~4k tokensUpdated yesterday
    Backend & APIsAuto-check passed
  • AI Automation Workflows

    NeverSight/learn-skills.dev

    Build automated AI workflows combining multiple models and services.

    217 GitHub starsUsed in 1 repo~2.6k tokens
    Productivity & AutomationAuto-check passed
  • Minimal Web Baas Demo

    TencentCloudBase/CloudBase-AI-Toolkit

    Fast path for a minimal CloudBase Web + database demo (最小前后端 / 最小可用 fullstack / Lovable-like BaaS).

    1.1k GitHub starsUsed in 1 repo~2.3k tokens
    Productivity & AutomationAuto-check passed
  • Trigger.dev Background Tasks

    papermark/papermark

    Guides building durable background tasks, scheduled jobs and queues with Trigger.dev, including retries, waits, idempotency and concurrency limits.

    9.2k GitHub stars~2.1k tokensUpdated 1 mo ago
    Backend & APIsAuto-check passed
  • Frappe App Dev

    frappe/skills

    Builds full-stack Frappe Framework applications end-to-end. An agent skill from frappe/skills.

    147 GitHub stars~943 tokensUpdated yesterday
    Backend & APIsAuto-check passed
  • Schked

    bibendi/schked

    Guide for working with Schked, a Ruby recurring-job scheduler built on top of rufus-scheduler.

    138 GitHub stars~454 tokensUpdated 1 mo ago
    Backend & APIsAuto-check passed

More from arandu-io/arandu

All 12 skills in this repo
  • Arandu API

    arandu-io/arandu

    Answering a program rather than a person in an Arandu (Go) application -- a JSON Resource, a JSON answer from the same routes the pages use, problem+json errors, bearer-token authentication and…

    281 GitHub stars~2.5k tokensUpdated yesterday
    Auto-check passed
  • Decides whether a feature belongs in the application or in one of five shared Arandu modules before adding permissions, wallets, tags, Markdown rendering or API docs.

    281 GitHub stars~1.8k tokensUpdated yesterday
    Auto-check passed
  • Arandu Feature

    arandu-io/arandu

    Start here for any change to an Arandu (Go) application that adds or changes behaviour -- "add invoices", "let users publish a post", "send a weekly report", "call the payment provider", "expose…

    281 GitHub stars~2.5k tokensUpdated yesterday
    Auto-check passed
  • Arandu HTTP

    arandu-io/arandu

    Controllers, requests and routes of an Arandu (Go) application -- the seven resource actions, a resource nested under another, a singleton, a single-action (invokable) controller, a named action…

    281 GitHub stars~2.5k tokensUpdated yesterday
    Auto-check passed
  • Arandu Integrations

    arandu-io/arandu

    Reaching other systems from an Arandu (Go) application, and letting them reach it -- the client of an external API with its interface and fake, webhooks sent and received, and tools, resources and…

    281 GitHub stars~3.1k tokensUpdated yesterday
    Auto-check passed
  • Arandu Module Generator

    arandu-io/arandu

    Adds a new entity, resource or CRUD module to an Arandu Go application by writing a YAML specification instead of hand-writing the Go code.

    281 GitHub stars~2.4k tokensUpdated yesterday
    Auto-check passed

Works with

Questions about Arandu Async

What does Arandu Async do?

Work that does not happen inside the request in an Arandu (Go) application -- background jobs and the worker, scheduled tasks, domain events through the outbox, listeners, notifications, mail and…. Arandu Async is an agent skill from arandu-io/arandu. Work that does not happen inside the request in an Arandu (Go) application -- background jobs and the worker, scheduled tasks, domain events through the outbox, listeners, notifications, mail and console commands.

When should I use Arandu Async?

Arandu Async fits situations like: the request is to send an email; notify the user; run this every night; do this in the background.

How do I install Arandu Async in Claude Code?

Run `npx skills add arandu-io/arandu --skill arandu-async -a claude-code`. Or copy the skill folder (.agents/skills/arandu-async in arandu-io/arandu) into .claude/skills/arandu-async in your project. Claude Code loads it when a task matches its description.

How do I install Arandu Async in Codex?

Run `npx skills add arandu-io/arandu --skill arandu-async -a codex`. Or copy the skill folder (.agents/skills/arandu-async in arandu-io/arandu) into .agents/skills/arandu-async in your project. Codex loads it when a task matches its description.

Can I use Arandu Async in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add arandu-io/arandu --skill arandu-async -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/arandu-async, .gemini/skills/arandu-async, .github/skills/arandu-async and .opencode/skills/arandu-async in your project.

What does Arandu Async need to run?

Going by SKILL.md and its folder, Arandu Async needs the command-line tools its instructions call (go and bash).

Does Arandu Async access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Arandu Async safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Arandu Async use?

Arandu Async is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Arandu Async use?

About 2.7k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Arandu Async?

Skills that share tags, products or a category with Arandu Async: Inngest Durable Functions (Asymmetric-al/core, 381 stars), AI Automation Workflows (NeverSight/learn-skills.dev, 217 stars), Minimal Web Baas Demo (TencentCloudBase/CloudBase-AI-Toolkit, 1.1k stars) and Trigger.dev Background Tasks (papermark/papermark, 9.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Arandu Async?

arandu-io (a GitHub organization) maintains it in arandu-io/arandu, which has 281 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on October 10, 2026.

Source: arandu-io/arandu on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.