archibate/dotfiles-opencode / skills/pueue
pueue
UnverifiedThis skill should be used before running non-interactive long-running tasks, computation intensive tasks, background tasks, or needs guidance on the pueue CLI tool usage. TRIGGER when user says "use pueue", "run in background", "queue this task", or when about to run any long-running (>2 min) task.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 2.5 KB |
| references/pueue.md | markdown | 3.9 KB |
| scripts/run_in_pueue.shexecutable | script | 1.2 KB |
scripts/run_in_pueue.sh
View on GitHub#!/bin/bash
set -euo pipefail
# Usage
if [[ $# -ne 1 ]]; then
echo "Usage: $0 'command arg1 arg2'" >&2
echo " Wraps pueue add with auto daemon start, per-project grouping, and follow." >&2
exit 1
fi
command="$1"
# 1. Derive project group name from current working directory
# Replace / with - and strip leading -
group_name="$(pwd | sed 's|/|-|g; s|^-||')"
# 2. Ensure pueue daemon is running
if ! pueue status &>/dev/null; then
echo "π Starting pueue daemon..."
pueued -d
sleep 1
if ! pueue status &>/dev/null; then
echo "β Failed to start pueue daemon" >&2
exit 1
fi
echo "β
Daemon started"
fi
# 3. Create project group if it doesn't exist
if ! pueue group --json 2>/dev/null | jq -e --arg g "$group_name" '.[$g]' &>/dev/null; then
pueue group add -p 0 "$group_name"
echo "β
Created group: $group_name (parallel: unlimited)"
fi
# 4. Add the task
id=$(pueue add -g "$group_name" --print-task-id -- "$command")
if [[ -z "$id" ]]; then
echo "β Failed to add task" >&2
exit 1
fi
echo "β
Task #$id added to group '$group_name'"
echo ""
echo "π Task output:"
# 5. Follow the task output
exec pueue follow "$id"
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why β repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" β or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself β your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |