Agent skill

AgentRQ Supervisor

by agentrq in agentrq/agentrq

Orchestrates work across specialized AgentRQ workspaces, breaking goals into tasks, assigning them to the right workspace agent, and tracking shared learning notes.

AGPL-3.0Auto-check passedProductivity & Automation

Install AgentRQ Supervisor

skills CLI
$ npx skills add agentrq/agentrq --skill agentrq -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install agentrq/agentrq agentrq --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/agentrq/agentrq.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/claude/agentrq/skills/agentrq .claude/skills/agentrq && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
agentrq
GitHub stars
1.1k
Token cost
~2.7k tokens
SKILL.md length
1,262 words
Files
1
Skills in repo
2
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Orchestrates work across specialized AgentRQ workspaces, breaking goals into tasks, assigning them to the right workspace agent, and tracking shared learning notes.

  • Works in 6 steps: Creating a Task for a Specialized Agent → Creating a Scheduled/Cron Task → Replying to a Task Thread → …
  • Breaking a large goal into tasks across specialized AgentRQ workspaces
  • SKILL.md covers Core Concepts, Available Tools, Resources and Prompts and Core Guidelines, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

The skill positions the agent as a supervisor over AgentRQ workspaces, each a project or domain context such as backend API, frontend app or DevOps with its own specialized agent. A task is a unit of work inside a workspace, assignable to a human or an agent, with status, threaded replies and optional cron scheduling. Each workspace keeps a self-learning note, a living document of preferences and lessons the supervisor is told to always read and update so knowledge carries across sessions, alongside broader workspace memory indexed by a MEMORY.md file that should be read before assigning work there.

Workspace-management tools cover listing, creating, updating and getting statistics for workspaces, and forking one into an independent queue and agent that shares the parent's settings, memory and skills, later merged back once its tasks are done or rejected. Task-management tools create, list, fetch and reply to tasks, with task creation taking a title, body, a human or agent assignee, an optional cron schedule and an optional parent task.

When your agent uses it

  • Breaking a large goal into tasks across specialized AgentRQ workspaces
  • Forking a workspace to let a second agent work a batch of tasks in parallel
  • Checking a workspace's self-learning notes before assigning new work there

Example prompts

  • “Break this feature into tasks across the backend and frontend workspaces.”
  • “Fork the DevOps workspace so a second agent can work the migration tasks.”
  • “Read the backend workspace's self-learning notes before assigning the next task.”

Requirements

  • An AgentRQ instance with configured workspaces

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Creating a Task for a Specialized Agent
  2. Creating a Scheduled/Cron Task
  3. Replying to a Task Thread
  4. Updating Self-Learning Notes
  5. Responding to a Task
  6. Updating Task Status

What it can do on your machine

Read from SKILL.md and the folder at commit 2337c14. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are json).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

AgentRQ Supervisor loads about 2.7k tokens when it runs. Until then it costs about 32 tokens; SKILL.md has 1,262 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~32
When it runs · the whole SKILL.md, loaded when a task matches
~2.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from agentrq/agentrq at commit 2337c14, republished under its AGPL-3.0 licence (© agentrq). 1,262 words, ~2,680 tokens.

Download SKILL.mdSave it as .claude/skills/agentrq/SKILL.md (or your agent's skills folder).
name
agentrq
description
Lead multiple agents to accomplish big tasks with specialized workspaces/agents by assigning tasks to specialized agents.

AgentRQ Supervisor Guidelines

You are a supervisor agent orchestrating work across multiple specialized workspaces and agents via the AgentRQ platform. Your role is to break down complex goals into discrete tasks, assign them to the right workspace agents, and coordinate their execution.

Core Concepts

  • Workspace: A project or domain-specific context (e.g., "Backend API", "Frontend App", "DevOps"). Each workspace can have its own specialized agent and self-learning notes.
  • Task: A unit of work within a workspace. Tasks can be assigned to human or agent, have statuses, support threaded replies, and can be scheduled with cron expressions.
  • Self-Learning Loop: Each workspace has a selfLearningLoopNote — a living document of preferences, patterns, and lessons learned. Always read and update these notes to share knowledge across sessions.
  • Workspace Memory: What a workspace's agents have learned while working lives in its memory, indexed by MEMORY.md. Read it with listMemories and getMemory before assigning work there.

Available Tools

Workspace Management
ToolDescription
listWorkspacesList all workspaces (optionally include archived)
createWorkspaceCreate a new workspace with name, description, notification settings, and self-learning notes
getWorkspaceGet workspace details by ID
updateWorkspaceUpdate workspace name, description, notification settings, or self-learning notes
getWorkspaceStatsGet workspace statistics for a given time range (7d or 30d)
forkWorkspaceFork a workspace: its own queue and agent, sharing the parent's settings, memory and skills. Move tasks into it for a second agent to work them
mergeForkMerge a fork back once its tasks are completed or rejected: its agent is stopped and every task moves to the parent
Task Management
ToolDescription
listTasksList tasks in a specific workspace (filterable by status, creator; supports pagination)
listAllTasksList tasks across all workspaces (same filters as listTasks)
createTaskCreate a task with title, body, assignee (human/agent), optional cron schedule, and optional parent task
getTaskGet full task details including messages
replyToTaskPost a message to a task's thread
respondToTaskAnswer a permission request: allow, allow_all, reject, or text to reply without deciding
updateTaskStatusUpdate status: notstarted, ongoing, blocked, completed, rejected. (cron is set by the server for scheduled tasks.)
updateTaskAssigneeReassign a task to agent or human
updateTaskOrderUpdate a task's sort order
updateTaskAllowAllToggle allow_all_commands for a task
updateScheduledTaskUpdate a scheduled/cron task's title, body, or cron expression
deleteTaskDelete a task outright, with its messages and attachments. Irreversible — to stop a scheduled task without losing its history, set its status to rejected instead
Events and Triggers

An event is a named signal a workspace publishes; a trigger is a standing instruction to create a task somewhere when it fires. Together they are how one workspace's finished work starts another's.

ToolDescription
listEventsList the events defined for this account
createEventDefine a named signal (^[a-z][a-z0-9_]{0,128}$) and what a publisher should put in its payload
getEventGet an event by ID
updateEventRevise an event's payload guidelines. Its name is fixed once created
deleteEventDelete an event. Its triggers stop firing
createEventTriggerWhen this event fires, create a task in this workspace. {{EVENT_PAYLOAD}} and {{EVENT_FAQ}} are substituted in the body only; emitEventId chains a second event to the task's completion
listEventTriggersList the triggers attached to an event
getEventTriggerGet an event trigger by ID
updateEventTriggerRewrite a trigger. Every field is written as given, so send the ones to keep as well
deleteEventTriggerDelete a trigger, leaving its event in place
listEventTasksList the tasks an event has spawned, to see whether a wired-up system is running
Workflows

A workflow is the graph those pieces add up to: a start event, and steps that react to it and to each other.

ToolDescription
listWorkflowsList the workflows defined for this account
createWorkflowCreate an empty workflow around a start event
getWorkflowGet a workflow by ID
updateWorkflowRevise name, description, start event or canvas layout. Only the fields sent are changed
deleteWorkflowDelete a workflow and its steps. The events it named are left alone
createWorkflowStepAdd a step: the event it reacts to, the workspace and task it creates, and the event it emits on completion
listWorkflowStepsList a workflow's steps
deleteWorkflowStepRemove one step, leaving the rest of the graph in place
listWorkflowTasksList the tasks a workflow has spawned
getWorkflowTextRead the whole graph as an indented document. Steps naming a deleted event or workspace are left out so it always parses
replaceWorkflowFromTextReplace the entire graph with a document. Names are resolved before anything is written, so an unknown one leaves the workflow untouched
createEnrolmentCodeMint a one-time code for enrolling a new machine with agentrqd. Shown once and expires shortly — hand it to the human right away

Text mode is two spaces per level, and every list line is - agent:<workspace> or - event:<name>, alternating:

workflow: new_feature
event: code_changed
- agent:doc
  - event:doc_updated
- agent:blog
Show full SKILL.md (479 more words)Show less
Attachments
ToolDescription
getAttachmentGet an attachment by workspace, task and attachment ID: its public link by default, or its base64 content with format=base64
Workspace Memory
ToolDescription
listMemoriesList a workspace's memories: name, size and when each changed. Content is not included
getMemoryRead one memory in full, by name. MEMORY.md is the index the others hang off
Workspace Skills
ToolDescription
searchSkillsFind the account's skills as a workspace sees them, with whether each is on there, by name or description (q, at least 3 characters): name, description, source and size, with limit/offset paging and a total. Content is not included
getSkillRead one file of a skill by its skill://<name>/<path> URI; skill://<name> alone reads its SKILL.md, with the list of its other files

Resources and Prompts

The server also offers reference guides as resources, and ready-made prompts:

  • agentrq://guides/new-workspace — how to set up a new workspace for an agent to run in
  • agentrq://guides/agentrqd-setup — how to install agentrqd and enrol a machine
  • Prompt new-workspace (name, optional purpose) — create a workspace and report what is left for a human to connect an agent
  • Prompt setup-agentrqd (optional platform) — mint an enrolment code and hand back the exact commands to run
  • Prompt workspace-status — a status report across every workspace at once

Core Guidelines

  1. Discover Before Creating: Always use listWorkspaces or listAllTasks to find existing workspaces and tasks before creating new ones. Avoid duplicates.
  2. Gather Full Context: Before acting on a task, use getTask to read the full task details and message thread.
  3. Keep Humans in the Loop: When blocked or needing approval, set the task status to blocked and use replyToTask to explain what you need. blocked is the status the interface surfaces as needing attention.
  4. Leverage Self-Learning Notes: Always read a workspace's selfLearningLoopNote and its memory index (getMemory with MEMORY.md) before starting work. Update it with new preferences, patterns, or lessons learned using updateWorkspace.
  5. Use Sub-Tasks for Complex Work: Break large goals into sub-tasks using parentId when creating tasks. This creates a clear hierarchy of work.
  6. Track Status Accurately: Update task statuses as work progresses — ongoing when starting, completed when finished, rejected if the work should not be done. There is no separate failure status: say what went wrong with replyToTask and leave the task blocked so a human sees it.

Example Workflows

1. Creating a Task for a Specialized Agent

Break down work and assign it to the appropriate workspace agent:

json
{
  "workspaceId": "aB3dE5gH7jK",
  "title": "Optimize database connection pooling",
  "body": "We are seeing intermittent connection timeouts during peak hours. Analyze logs from the last 7 days and propose connection pool configuration changes.",
  "assignee": "agent"
}
2. Creating a Scheduled/Cron Task

Set up recurring tasks with cron expressions:

json
{
  "workspaceId": "aB3dE5gH7jK",
  "title": "Daily health check report",
  "body": "Run system health checks and post a summary of any issues found.",
  "assignee": "agent",
  "cronSchedule": "0 9 * * *"
}
3. Replying to a Task Thread

Provide updates, ask questions, or share findings in a task's thread:

json
{
  "workspaceId": "aB3dE5gH7jK",
  "taskId": "zX9vW7tS5rQ",
  "text": "Analysis complete. The connection pool exhausts at 50 concurrent connections. Recommend increasing max pool size to 100 and adding a 30s idle timeout."
}
4. Updating Self-Learning Notes

Capture workspace-specific knowledge for future sessions:

json
{
  "id": "aB3dE5gH7jK",
  "selfLearningLoopNote": "- Database changes require DBA team review before applying.\n- Preferred connection pool library: pgxpool.\n- Alert threshold: >5s p99 latency."
}
5. Responding to a Task

Answer a permission request a task is waiting on. action is allow, allow_all, reject, or text:

json
{
  "workspaceId": "aB3dE5gH7jK",
  "taskId": "zX9vW7tS5rQ",
  "action": "allow",
  "text": "Approved. Proceed with the proposed changes."
}
6. Updating Task Status

Track progress by updating status as work progresses:

json
{
  "workspaceId": "aB3dE5gH7jK",
  "taskId": "zX9vW7tS5rQ",
  "status": "completed"
}

© agentrq, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in plugins/claude/agentrq/skills/agentrq of agentrq/agentrq.

Open the folder on GitHubat commit 2337c14

Compare with similar skills

AgentRQ Supervisor next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

AgentRQ Supervisor compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
AgentRQ Supervisor this skillagentrq/agentrq1.1k—~2.7kAutomated safety check: PassAGPL-3.0
Superset Agent Standupsuperset-sh/superset15k—~712Automated safety check: PassCustom licence
Ruflo Multi-Agent Orchestrationruvnet/ruflo74k1 repos~975Automated safety check: PassMIT
Marm InitLyellr88/marm-memory419—~7.5kAutomated safety check: NotesApache-2.0
Run Wavejpicklyk/task-orchestrator207—~5kAutomated safety check: PassMIT
Swarmclawswarmclawai/swarmclaw689—~2kAutomated safety check: PassMIT

Similar skills

  • Superset Agent Standup

    superset-sh/superset

    Sweeps every Superset workspace, task and agent terminal to report what finished, what needs review and what is blocked, read-only, and can publish the digest as a page.

    15k GitHub stars~712 tokensUpdated today
    Productivity & AutomationAuto-check passed
  • Sets up and drives Ruflo, an npm-installed orchestration layer for multi-agent swarms, persistent memory, routing, hooks and its MCP tool catalog.

    74k GitHub starsUsed in 1 repo~975 tokens
    Agent WorkflowsAuto-check passed
  • Marm Init

    Lyellr88/marm-memory

    Guided MARM MCP setup. An agent skill from Lyellr88/marm-memory.

    419 GitHub stars~7.5k tokensUpdated 2 days ago
    Agent WorkflowsAuto-check: notes
  • Run Wave

    jpicklyk/task-orchestrator

    Resolves ready MCP work items into a run plan, shows it to you, then executes it through the Workflow tool or direct subagent dispatch, with post-run verification.

    207 GitHub stars~5k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Swarmclaw

    swarmclawai/swarmclaw

    AI agent runtime and multi-agent orchestration platform. An agent skill from swarmclawai/swarmclaw.

    689 GitHub stars~2k tokensUpdated 3 mo ago
    Agent WorkflowsAuto-check passed
  • Flow Swarm

    LeoYeAI/openclaw-master-skills

    Multi-agent swarm orchestration via RuFlo + Claude Code. An agent skill from LeoYeAI/openclaw-master-skills.

    2.2k GitHub stars~5.3k tokensUpdated 2 mo ago
    Agent WorkflowsAuto-check passed

More from agentrq/agentrq

  • Guides a workspace agent through executing assigned tasks, replying to a remote human operator, and creating sub-tasks, memory and events inside an AgentRQ workspace.

    1.1k GitHub stars~1.9k tokensUpdated today
    Auto-check passed

Questions about AgentRQ Supervisor

What does AgentRQ Supervisor do?

Orchestrates work across specialized AgentRQ workspaces, breaking goals into tasks, assigning them to the right workspace agent, and tracking shared learning notes. The skill positions the agent as a supervisor over AgentRQ workspaces, each a project or domain context such as backend API, frontend app or DevOps with its own specialized agent. A task is a unit of work inside a workspace, assignable to a human or an agent, with status, threaded replies and optional cron scheduling.

When should I use AgentRQ Supervisor?

AgentRQ Supervisor fits situations like: breaking a large goal into tasks across specialized AgentRQ workspaces; forking a workspace to let a second agent work a batch of tasks in parallel; checking a workspace's self-learning notes before assigning new work there.

How do I install AgentRQ Supervisor in Claude Code?

Run `npx skills add agentrq/agentrq --skill agentrq -a claude-code`. Or copy the skill folder (plugins/claude/agentrq/skills/agentrq in agentrq/agentrq) into .claude/skills/agentrq in your project. Claude Code loads it when a task matches its description.

How do I install AgentRQ Supervisor in Codex?

Run `npx skills add agentrq/agentrq --skill agentrq -a codex`. Or copy the skill folder (plugins/claude/agentrq/skills/agentrq in agentrq/agentrq) into .agents/skills/agentrq in your project. Codex loads it when a task matches its description.

Can I use AgentRQ Supervisor in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add agentrq/agentrq --skill agentrq -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/agentrq, .gemini/skills/agentrq, .github/skills/agentrq and .opencode/skills/agentrq in your project.

What does AgentRQ Supervisor need to run?

SKILL.md names no scripts, command-line tools or credentials: AgentRQ Supervisor is instructions for the agent only. Our summary lists: An AgentRQ instance with configured workspaces.

Does AgentRQ Supervisor access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is AgentRQ Supervisor safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does AgentRQ Supervisor use?

AgentRQ Supervisor is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does AgentRQ Supervisor use?

About 2.7k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to AgentRQ Supervisor?

Skills that share tags, products or a category with AgentRQ Supervisor: Superset Agent Standup (superset-sh/superset, 15k stars), Ruflo Multi-Agent Orchestration (ruvnet/ruflo, 74k stars), Marm Init (Lyellr88/marm-memory, 419 stars) and Run Wave (jpicklyk/task-orchestrator, 207 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains AgentRQ Supervisor?

agentrq (a GitHub organization) maintains it in agentrq/agentrq, which has 1,140 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 10, 2026.

Source: agentrq/agentrq on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.