foxctl Overseer

Compute pagerank and critical_path to score and prioritize tasks for multi-agent orchestration.

3|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/joshka0/foxctl --skill foxctl-overseer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: foxctl Overseer
Source: https://github.com/joshka0/foxctl/tree/main/configs/skills-condensed/foxctl-overseer
Command: npx skills add https://github.com/joshka0/foxctl --skill foxctl-overseer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams avoid stalled planning by automatically ranking tasks for multi-agent execution using the communication context and the repo/workflow graph.

Core Features & Use Cases

  • Task Scoring for Prioritization: Computes a composite score using critical-path position, PageRank centrality, unread admin/overseer counts, and recency to decide what to do next.
  • Graph Analysis for Workflow Insight: Produces pagerank, critical_path, cycles, and topological_order so you can understand bottlenecks, loops, and ordering constraints.
  • Coordination Across an Agent Hierarchy: Structures work across an overseer planner, coder agents, and deeper subagents to support durable delegation.

Quick Start

Run foxctl with the overseer recommendation operation to get the top 5 prioritized tasks for your current inbox and workflow state.

Frequently Asked Questions about foxctl Overseer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prioritize tasks for multi-agent orchestration when facing unread message backlogs?

Multi-agent orchestration task prioritization ranks outstanding work using critical-path position, PageRank centrality, and unread admin or overseer message recency. This scoring mechanism computes composite task scores to determine execution order and prevent stalled planning.

How does graph analysis identify workflow bottlenecks in task scheduling?

Graph analysis for workflow insight identifies bottlenecks by computing pagerank, extracting the critical path, and detecting cycles via topological_sort. This reveals ordering constraints and structural loops that block multi-agent execution progress.

What's the best way to coordinate work across an agent hierarchy with planner and subagent roles?

Coordinating work across an agent hierarchy structures tasks across an overseer planner, coder agents, and deeper subagents to support durable delegation. Task scoring integrates unread admin and overseer counts to align execution order with hierarchy signals.

Can I use topological_sort to detect cycles and ordering constraints in my workflow graph?

Topological_sort detects cycles and ordering constraints within the workflow graph. It processes the repo graph to return a topological order, exposing loops and dependencies that affect multi-agent task scheduling and execution sequences.

Does task scoring for scheduling require recency scoring and unread message context?

Task scoring for scheduling requires recency scoring and unread message context to compute execution order. The system merges unread admin and overseer counts with pagerank and critical path metrics to return scored tasks for intake and workflow management.