Queue

v2.0.1

Manage message queues with priorities and retry logic. Use when adding jobs, planning retry strategies, tracking delivery status, reviewing failed items.

0· 220·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description (queue management with priorities/retry/track/review) matches the provided CLI commands and behavior. The script implements the listed commands and stores data locally; nothing requested is out of scope for a simple local queue tool.
Instruction Scope
SKILL.md and the script confine operations to local file storage (~/.local/share/queue) and standard shell utilities. Caveat: exported JSON/csv are produced by simple text concatenation and do not escape field contents, so entries containing quotes/newlines/commas may produce malformed exports. Also, because data is stored locally, users should avoid putting secrets into queue entries.
Install Mechanism
No install spec (instruction-only with an included script) — low surface area. The skill does not download remote code or add system-wide installers. The script is a plain bash script included in the package.
Credentials
No environment variables, credentials, or external config paths are requested. The script only uses HOME (standard) to derive a data directory; this is proportional to the stated purpose.
Persistence & Privilege
always is false and the skill does not request elevated privileges or modify other skills or system configuration. It persists data only under the user's ~/.local/share/queue directory, which is appropriate for a local CLI tool.
Assessment
This skill appears to do what it says: a local bash queue manager that writes logs to ~/.local/share/queue and does not make network calls or request credentials. Before installing or using it: 1) inspect any entries you plan to save — do not store secrets or passwords in queue items since data is plain text; 2) be aware exports are produced by simple concatenation and may be malformed if entries contain quotes/newlines/commas; 3) verify file permissions on ~/.local/share/queue if other users share the system; and 4) if you want the script on your PATH, review and control where you place/execute it. Overall there are no red flags for network exfiltration or excessive privileges.

Like a lobster shell, security has layers — review code before you run it.

latestvk978j75mj2ws829z1vcpp1pghd8356x9

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments