Token导航 LogoToken导航

Agent Skill · 开发

async-jobs(异步作业)

async-jobs 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

async-jobs 是开发类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证信息还不明确,第三方扫描已通过,按安装量在开发类的 21,746 个 Skill 里排第 9,008。

总安装 2,904周安装 121GitHub Stars 160下载 968核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:async-jobs(异步作业)
来源仓库:https://github.com/yonatangross/orchestkit
仓库路径:skills/async-jobs
安装命令:
npx skills add https://github.com/yonatangross/orchestkit --skill async-jobs
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/yonatangross/orchestkit --skill async-jobs

这个 Skill 是做什么的

开发类 Skill 面向写代码、改代码和排查问题,一般会读写仓库文件,部分还会执行构建或测试命令。

async-jobs 提供异步任务处理模式,支持 Celery、ARQ 和 Redis 等主流工具。适用于需要后台任务队列、工作流编排、重试策略及生产监控的场景。通过引用规则文件按需加载,涵盖配置、路由、工作流和限流等模块。安装方式:github,建议确认权限范围和维护状态后再部署使用。

注意可能涉及联网、命令执行或文件读写操作,需评估安全风险。

来源仓库内路径:skills/async-jobs

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/yonatangross/orchestkit --skill async-jobs;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

async-jobs 怎么安装?

在终端执行 npx skills add https://github.com/yonatangross/orchestkit --skill async-jobs。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

async-jobs 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

async-jobs 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

async-jobs 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

async-jobs 用的人多吗?

公开数据是累计安装 2,904 次,近一周安装 121 次,下载 968 次,GitHub 160 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

async-jobs 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理开发类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

开发类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
skill-vetter

技能审查员 · OpenClaw

8,779,018986操作浏览器MIT-0通过
ontology

本体论 · OpenClaw

6,636,960576只读MIT-0通过
entra-app-registration

内部应用程序注册 · Codex、Claude

6,631,872764接触敏感数据未明确通过
entra-app-registration

内部应用程序注册 · Codex、Claude

3,757,680201接触敏感数据未明确通过
nano-banana-pro

纳米香蕉专业版 · OpenClaw

3,526,898364接触敏感数据MIT-0有提醒
async-jobs

异步作业 · 本页

2,904160需要联网未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Async Jobs

Patterns for background task processing with Celery, ARQ, and Redis. Covers task queues, canvas workflows, scheduling, retry strategies, rate limiting, and production monitoring. Each category has individual rule files in references/ loaded on-demand.

Quick Reference

CategoryRulesImpactWhen to Use
Configurationcelery-configHIGHCelery app setup, broker, serialization, worker tuning
Task Routingtask-routingHIGHPriority queues, multi-queue workers, dynamic routing
Canvas Workflowscanvas-workflowsHIGHChain, group, chord, nested workflows
Retry Strategiesretry-strategiesHIGHExponential backoff, idempotency, dead letter queues
Schedulingscheduled-tasksMEDIUMCelery Beat, crontab, database-backed schedules
Monitoringmonitoring-healthMEDIUMFlower, custom events, health checks, metrics
Result Backendsresult-backendsMEDIUMRedis results, custom states, progress tracking
ARQ Patternsarq-patternsMEDIUMAsync Redis Queue for FastAPI, lightweight jobs
Temporal Workflowstemporal-workflowsHIGHDurable workflow definitions, sagas, signals, queries
Temporal Activitiestemporal-activitiesHIGHActivity patterns, workers, heartbeats, testing

Total: 10 rules across 9 categories

Quick Start

@app.task(bind=True, max_retries=3, default_retry_delay=60)
def process_payment(self, order_id: str):
    try:
        return gateway.charge(order_id)
    except TransientError as exc:
        raise self.retry(exc=exc, countdown=2 ** self.request.retries * 60)

Load more examples: Read("${CLAUDE_SKILL_DIR}/references/quick-start-examples.md") for Celery retry task and ARQ/FastAPI integration patterns.

Configuration

Production Celery app configuration with secure defaults and worker tuning.

Key Patterns

  • JSON serialization with task_serializer="json" for safety
  • Late acknowledgment with task_acks_late=True to prevent task loss on crash
  • Time limits with both task_time_limit (hard) and task_soft_time_limit (soft)
  • Fair distribution with worker_prefetch_multiplier=1
  • Reject on lost with task_reject_on_worker_lost=True

Key Decisions

DecisionRecommendation
SerializerJSON (never pickle)
Ack modeLate ack (task_acks_late=True)
Prefetch1 for fair, 4-8 for throughput
Time limitsoft < hard (e.g., 540/600)
TimezoneUTC always

Task Routing

Priority queue configuration with multi-queue workers and dynamic routing.

Key Patterns

  • Named queues for critical/high/default/low/bulk separation
  • Redis priority with queue_order_strategy: "priority" and 0-9 levels
  • Task router classes for dynamic routing based on task attributes
  • Per-queue workers with tuned concurrency and prefetch settings
  • Content-based routing for dynamic workflow dispatch

Key Decisions

DecisionRecommendation
Queue count3-5 (critical/high/default/low/bulk)
Priority levels0-9 with Redis x-max-priority
Worker assignmentDedicated workers per queue
Prefetch1 for critical, 4-8 for bulk
RoutingRouter class for 5+ routing rules

Canvas Workflows

Celery canvas primitives for sequential, parallel, and fan-in/fan-out workflows.

Key Patterns

  • Chain for sequential ETL pipelines with result passing
  • Group for parallel execution of independent tasks
  • Chord for fan-out/fan-in with aggregation callback
  • Immutable signatures (si()) for steps that ignore input
  • Nested workflows combining groups inside chains
  • Link error callbacks for workflow-level error handling

Key Decisions

DecisionRecommendation
SequentialChain with s()
ParallelGroup for independent tasks
Fan-inChord (all must succeed for callback)
Ignore inputUse si() immutable signature
Error in chainReject stops chain, retry continues
Partial failuresReturn error dict in chord tasks

Retry Strategies

Retry patterns with exponential backoff, idempotency, and dead letter queues.

Key Patterns

  • Exponential backoff with retry_backoff=True and retry_backoff_max
  • Jitter with retry_jitter=True to prevent thundering herd
  • Idempotency keys in Redis to prevent duplicate processing
  • Dead letter queues for failed tasks requiring manual review
  • Task locking to prevent concurrent execution of singleton tasks
  • Base task classes with shared retry configuration

Key Decisions

DecisionRecommendation
Retry delayExponential backoff with jitter
Max retries3-5 for transient, 0 for permanent
IdempotencyRedis key with TTL
Failed tasksDLQ for manual review
SingletonRedis lock with TTL

Scheduling

Celery Beat periodic task configuration with crontab, database-backed schedules, and overlap prevention.

Key Patterns

  • Crontab for time-based schedules (daily, weekly, monthly)
  • Interval for fixed-frequency tasks (every N seconds)
  • Database scheduler with django-celery-beat for dynamic schedules
  • Schedule locks to prevent overlapping long-running scheduled tasks
  • Adaptive polling with self-rescheduling tasks

Key Decisions

DecisionRecommendation
Schedule typeCrontab for time-based, interval for frequency
DynamicDatabase scheduler (django-celery-beat)
OverlapRedis lock with timeout
Beat processSeparate process (not embedded)
TimezoneUTC always

Monitoring

Production monitoring with Flower, custom signals, health checks, and Prometheus metrics.

Key Patterns

  • Flower dashboard for real-time task monitoring
  • Celery signals (task_prerun, task_postrun, task_failure) for metrics
  • Health check endpoint verifying broker connection and active workers
  • Queue depth monitoring for autoscaling decisions
  • Beat monitoring for scheduled task dispatch tracking

Key Decisions

DecisionRecommendation
DashboardFlower with persistent storage
MetricsPrometheus via celery signals
HealthBroker + worker + queue depth
AlertingSignal on task_failure
AutoscaleQueue depth > threshold

Result Backends

Task result storage, custom states, and progress tracking patterns.

Key Patterns

  • Redis backend for task status and small results
  • Custom task states (VALIDATING, PROCESSING, UPLOADING) for progress
  • update_state() for real-time progress reporting
  • S3/database for large result storage (never Redis)
  • AsyncResult for querying task state and progress

Key Decisions

DecisionRecommendation
Status storageRedis result backend
Large resultsS3 or database (never Redis)
ProgressCustom states with update_state()
Result queryAsyncResult with state checks

ARQ Patterns

Lightweight async Redis Queue for FastAPI and simple background tasks.

Key Patterns

  • Native async/await with arq for FastAPI integration
  • Worker lifecycle with startup/shutdown hooks for resource management
  • Job enqueue from FastAPI routes with enqueue_job()
  • Job status tracking with Job.status() and Job.result()
  • Delayed tasks with _delay=timedelta() for deferred execution

Key Decisions

DecisionRecommendation
Simple asyncARQ (native async)
Complex workflowsCelery (chains, chords)
In-process quickFastAPI BackgroundTasks
LLM workflowsLangGraph (not Celery)

Tool Selection

Load: Read("${CLAUDE_SKILL_DIR}/references/quick-start-examples.md") for the full tool comparison table (ARQ, Celery, RQ, Dramatiq, FastAPI BackgroundTasks).

Anti-Patterns (FORBIDDEN)

Load details: Read("${CLAUDE_SKILL_DIR}/references/anti-patterns.md") for full list.

Key rules: never run long tasks in request handlers, never block on results inside tasks, never store large results in Redis, always use idempotency for retried tasks.

Temporal Workflows

Durable execution engine for reliable distributed applications with Temporal.io.

Key Patterns

  • Workflow definitions with @workflow.defn and deterministic code
  • Saga pattern with compensation for multi-step transactions
  • Signals and queries for external interaction with running workflows
  • Timers with workflow.wait_condition() for human-in-the-loop
  • Parallel activities via asyncio.gather inside workflows

Key Decisions

DecisionRecommendation
Workflow IDBusiness-meaningful, idempotent
DeterminismUse workflow.random(), workflow.now()
I/OAlways via activities, never directly

Temporal Activities

Activity and worker patterns for Temporal.io I/O operations.

Key Patterns

  • Activity definitions with @activity.defn for all I/O
  • Heartbeating for long-running activities (> 60s)
  • Error classification with ApplicationError(non_retryable=True) for business errors
  • Worker configuration with dedicated task queues
  • Testing with WorkflowEnvironment.start_local()

Key Decisions

DecisionRecommendation
Activity timeoutstart_to_close for most cases
Error handlingNon-retryable for business errors
TestingWorkflowEnvironment for integration tests

Related Skills

  • ork:python-backend - FastAPI, asyncio, SQLAlchemy patterns
  • ork:langgraph - LangGraph workflow patterns (use for LLM workflows, not Celery)
  • ork:distributed-systems - Resilience patterns, circuit breakers
  • ork:monitoring-observability - Metrics and alerting

Capability Details

Load details: Read("${CLAUDE_SKILL_DIR}/references/capability-details.md") for full keyword index and problem-solution mapping across all 8 capabilities.

平台分布

Codex

35.53%
按下载量换算344

Claude

29.26%
按下载量换算283

Cursor

20.41%
按下载量换算198

Gemini CLI

9.04%
按下载量换算88

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills