Skip to content

LeoYeAI/agent-master-skills / skills/autonomous-task-runner

task-runner

Verified

Persistent task queue system. Users add tasks at any time via natural language; tasks are stored in a single persistent queue file and executed asynchronously via subagents. A heartbeat/cron dispatcher wakes periodically to check pending tasks, spawn workers, and report completions. The system never "finishes" — it always remains ready for the next task.

FileKindSize
CHANGELOG.mdmarkdown2.8 KB
README.mdmarkdown6.4 KB
SKILL.mdskill md16.1 KB
STATUS.jsonconfig653 B
_meta.jsonconfig301 B
references/queue-schema.mdmarkdown10.0 KB
references/task-types.mdmarkdown9.9 KB
references/verification-guide.mdmarkdown10.2 KB
skill.ymlconfig6.0 KB
tests/test-triggers.jsonconfig6.3 KB

STATUS.json

View on GitHub
{
  "skill": "task-runner",
  "stage": "published",
  "tier": "general",
  "version": "2.0.3",
  "created": "2026-02-17",
  "last_updated": "2026-02-18",
  "author": "skill-engineer",
  "selfPlayDate": "2026-02-17",
  "selfPlayResult": "pass",
  "notes": "v2.0.1: Added Step 0 First Run Auto-Setup. On first INTAKE invocation (queue file absent), the agent automatically creates the task directory, initializes the queue, registers the heartbeat entry in HEARTBEAT.md, and registers the backup cron job. No manual setup required. Idempotency guaranteed. v2.0.0 base: Persistent queue + heartbeat dispatcher; self-play passed INTAKE+DISPATCHER modes."
}
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: 471kUpdated Claude CodeCodexVerifiedInstall
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: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 availableStars: 322kUpdated Claude CodeCodexVerifiedInstall