ZappushZappush
SkillsUse CasesBenchmarkCommunitySign In
      Back to Skills
      gchapim

      Safety Report

      Oban

      @gchapim

      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.

      1,347Downloads
      0Installs
      0Stars
      1Versions
      Workflow Automation3,323File Management2,100Project Management1,537Calendar & Scheduling1,462

      Security Analysis

      high confidence
      Clean0.04 risk

      The skill's instructions, examples, and requirements are coherent with its stated purpose (designing and implementing Oban workers for Elixir) and do not request unrelated credentials or installs.

      Feb 11, 20263 files1 concern
      Purpose & Capabilityok

      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 Scopenote

      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 Mechanismok

      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.

      Credentialsok

      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 & Privilegeok

      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.

      Guidance

      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).

      Latest Release

      v1.0.0

      Initial release of oban-designer. - Guides users in designing and implementing Oban workers for Elixir. - Covers configuration of queues, retry/backoff strategies, and job uniqueness. - Includes instructions for cron scheduling, error handling, and inserting jobs. - Documents Oban Pro features (batch, workflow, chunk processing). - Provides setup and usage examples for testing Oban jobs. - Offers monitoring guidance and key metrics to track.

      More by @gchapim

      Hacker News

      8 stars

      Readwise & Reader API

      2 stars

      Phoenix API Generator

      0 stars

      Ecto Migrator

      0 stars

      Elixir Dev

      0 stars

      Oban Designer

      0 stars

      Published by @gchapim on ClawHub

      Zappush© 2026 Zappush
      HomeGuaranteeSupport

      Something feels unusual? We want to help: [email protected]