Design 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.
Security Analysis
high confidenceThe skill is an instruction-only guide for designing Oban workers and configuration in Elixir and its requirements and instructions are consistent with that purpose.
The name and description match the SKILL.md content: it explains Oban worker patterns, queue sizing, retries, uniqueness, cron, and sample code. The skill does not request unrelated binaries, credentials, or config paths.
Runtime instructions are limited to code/config snippets, mix commands (migration generation), and examples for inserting jobs. They reference project files and config entries that are appropriate for adding Oban to an Elixir app and do not instruct reading or exfiltrating unrelated system files or secrets.
No install spec or external downloads are present; this is an instruction-only skill (low persistence/risk). All actions are examples the developer would perform in their own codebase.
The skill declares no required environment variables, credentials, or config paths. It mentions Oban Pro features but does not request any license tokens or secrets.
The skill does not set always:true and has no special privileges; however, model invocation is not disabled (default), so the agent could autonomously use these instructions when allowed by the platform—this is expected for a coding helper but worth noting.
Guidance
This skill is a coherent, instruction-only guide for adding Oban workers. Before using it: 1) review and adapt the sample code (module names, queue sizes, backoff and timeout logic) to your project's needs; 2) inspect and run database migrations in a safe/dev environment before applying to production; 3) if you plan to use Oban Pro features, ensure you have the proper license and follow vendor instructions (no license token is requested by the skill); 4) validate cron expressions and uniqueness settings to avoid unintended duplicate or missed jobs; 5) always peer-review generated code and test job behavior—the skill provides patterns, not a drop-in, audited implementation.
Latest Release
v1.0.1
1.0.1 release of oban-designer - No file changes detected in this version. - No functional or documentation updates.
More by @gchapim
Published by @gchapim on ClawHub
