Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Batch Processing Patterns
v1.0.0批量处理与长时任务编排模式。涵盖队列管理、并发调度、中断恢复、熔断器、远程任务轮询、进度报告和反风控策略。适用于批量文件处理、AI API 调用、爬虫和后台任务场景。
⭐ 0· 425·1 current·1 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (batch processing, polling, retries, circuit breakers, abort/recovery) match the SKILL.md content. No unrelated binaries, env vars, or config paths are requested.
Instruction Scope
SKILL.md contains code patterns and implementation guidance (concurrency pools, abort controller, circuit breaker, polling, retry/backoff). It references reading/writing progress to disk and calling remote APIs via placeholders (loadCompletedFromDisk, queryTaskStatus) — these are expected for this domain and are scoped to batch processing. The instructions do not tell the agent to read arbitrary system files, exfiltrate data, or send results to unexpected external endpoints.
Install Mechanism
No install spec and no code files beyond SKILL.md. Because it's instruction-only, nothing is downloaded or executed by the installer and there is no elevated install risk.
Credentials
The skill declares no required environment variables, secrets, or credentials. The content mentions handling API errors (401/403/429) but does not request API keys itself; this is proportional for guidance material.
Persistence & Privilege
always is false; the skill is user-invocable and can be invoked autonomously (default), which is normal. The skill does not request persistent system presence or modify other skills' configuration.
Assessment
This SKILL.md is purely instructional and appears coherent for building batch jobs. Before using the patterns in production: (1) review and implement the placeholder functions (disk persistence, network calls) carefully so you don't accidentally read/write sensitive paths or persist secrets; (2) enforce input validation, limits, and timeouts to avoid runaway jobs; (3) set conservative circuit-breaker and retry parameters and respect remote API rate limits/quotas; (4) run implementations in a staging environment and audit what files/network endpoints they access. If you plan to integrate with real APIs, provide credentials only to your implementation code and not to this document — the skill itself does not request credentials.Like a lobster shell, security has layers — review code before you run it.
latestvk97ajfqdsrzzm5356frr1p4z09823jjh
License
MIT-0
Free to use, modify, and redistribute. No attribution required.