AgentStack
SKILL verified MIT Self-run

Create Job

skill-alizharb-agent-skills-create-job · by AlizHarb

Use when creating or changing Laravel queued jobs, batches, asynchronous workflows, or retryable background work.

No reviews yet
0 installs
2 views
0.0% view→install

Install

$ agentstack add skill-alizharb-agent-skills-create-job

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Create Job? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Create Job

When To Use

Use this skill for asynchronous, slow, retryable, external, scheduled, or failure-tolerant work.

Inputs Needed

  • Work to perform, payload, queue, timeout, retries, uniqueness, idempotency, failure handling, and tests.

Workflow

  1. Inspect existing queue conventions.
  2. Create the job with Artisan.
  3. Prefer queue attributes such as #[Queue], #[Connection], #[Tries], #[Backoff], #[Timeout], #[MaxExceptions], #[Delay], #[UniqueFor], #[FailOnTimeout], #[DeleteWhenMissingModels], and #[WithoutRelations] for simple job metadata.
  4. Pass IDs or small serializable data instead of large mutable objects when practical.
  5. Inject services into handle() instead of calling app() from the job body.
  6. Set timeout, tries or retry strategy, backoff, and failure behavior.
  7. Make retries idempotent where possible.
  8. Dispatch after commit when the job depends on newly written data, or set queue connection after_commit behavior intentionally.
  9. Add tests with queue fakes or synchronous execution as appropriate.

Files That May Be Created

  • app/Jobs/*
  • Job tests.

Files That May Be Modified

  • Actions, listeners, commands, schedules, queue config, and tests.

Architecture Rules

  • Jobs run background work; Actions own primary business operations.
  • Jobs may call Actions or Services.
  • Jobs should not contain UI or HTTP response logic.
  • Job dependencies should be method-injected into handle() unless they must be serialized.

Testing Requirements

  • Test dispatch, payload, retry-sensitive behavior, failure handling, and idempotency where relevant.

Security Requirements

  • Re-authorize or validate assumptions for delayed work when permissions or state may change.
  • Avoid logging secrets.

Review Checklist

  • Is async work necessary?
  • Is the job retry-safe?
  • Are timeout and retry settings explicit?

Common Mistakes

  • Queueing non-idempotent work without safeguards.
  • Dispatching inside a transaction too early.
  • Storing user-provided secrets in job payloads.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.