Oban
v1.0.0Design and implement Oban background job workers for Elixir. Configure queues, retry strategies, uniqueness constraints, cron scheduling, and error handling. Generate Oban workers, queue config, and test setups. Use when adding background jobs, async processing, scheduled tasks, or recurring cron jobs to an Elixir project using Oban.
⭐ 1· 1.6k·0 current·0 all-time
by@gchapim
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name and description match the provided SKILL.md and reference files: examples show Oban configuration, worker implementation patterns, uniqueness, retries, cron, and testing. Nothing in the bundle requests unrelated binaries, credentials, or config paths.
Instruction Scope
The instructions are code-level examples and configuration snippets appropriate for adding Oban workers. They do, however, include worker patterns that perform network calls (webhook delivery via Req.post) and file I/O (ImportCSV reading a file_path). That's expected for these use cases, but it means user code will potentially send data to external endpoints or read local files based on job arguments — ensure job args are validated and sensitive secrets are not placed in job args.
Install Mechanism
Instruction-only skill with no install spec and no downloaded code. Nothing will be written to disk or executed by the skill itself; risk from install mechanism is minimal.
Credentials
The skill declares no environment variables, credentials, or config paths. The content references application config (repo, Oban config) and typical Elixir project files, which is proportionate to the described purpose.
Persistence & Privilege
always:false (default) and no installation behavior, so the skill does not request persistent or privileged presence. It does not modify other skills or agent-wide settings.
Assessment
This skill is an instructional bundle for building Oban workers and appears internally consistent. Before using the examples in production: (1) review any webhook worker targets and ensure you only send data to trusted endpoints; avoid putting secrets in job args (the webhook signature example uses a secret passed in args — prefer storing secrets in secure config), (2) sanitize and validate file_path arguments to avoid reading arbitrary files in ImportCSV, (3) run tests with Oban in manual mode during CI to avoid unexpected background execution, and (4) review the migration and config changes in a staging environment before applying to production. If you need the skill to run code for you or to access your repo, verify its source and origin first (this bundle has no homepage/source listed).Like a lobster shell, security has layers — review code before you run it.
latestvk979m2n6sg1mgpcgq39vpexpxn80fbe2
License
MIT-0
Free to use, modify, and redistribute. No attribution required.