Adjust priority weights for task arbitration in the Orchestrator harness.
npx skills add https://github.com/AesopScott/mojo --skill priority-tuner
Please help me install this Agent Skill. Skill: priority-tuner Source: https://github.com/AesopScott/mojo/tree/main/harnesses/skills/priority-tuner Command: npx skills add https://github.com/AesopScott/mojo --skill priority-tuner
This Skill addresses performance bottlenecks and inefficient resource allocation within the Orchestrator harness by tuning priority weights to reduce wasted attention slices.
Use the priority-tuner skill to analyze the current Orchestrator performance metrics and propose a configuration change to reduce task latency.
High-intent search queries and answers about installing and using this skill.
To reduce high latency and wasted attention slices, you need to tune priority weights for task arbitration. Adjusting recency, blast-radius, and deadline weights optimizes resource allocation and resolves scheduling bottlenecks within the Orchestrator harness.
The best way to optimize task throughput during resource contention is tuning priority weights. Reconfiguring the weighting model for task arbitration reduces wasted attention slices and resolves inefficient resource allocation.
Adjust priority weights by analyzing current arbitration logs and configuration parameters. This structured runbook identifies stalled lanes or over-synchronized workflows and implements effective recency, blast-radius, and deadline weighting adjustments.
Inefficient task scheduling and repeated work occur because of suboptimal priority weights in task arbitration. Adjusting the recency, blast-radius, and deadline weights addresses these performance bottlenecks and reduces wasted attention slices.
Yes, you need current arbitration logs and configuration parameters to start performance tuning. Analyzing these metrics is required to implement effective priority weighting adjustments and reduce task latency within the Orchestrator.
Avoid priority weight tuning when you cannot access current arbitration logs or configuration parameters. Without these inputs, proposing effective configuration changes to reduce task latency and resolve bottlenecks is not possible.
timurgaleevDetect performance regressions by comparing page load timings and resource metrics.
AesopScottAdjust router latency-versus-quality weights and warm-pool settings from configuration files and logs.
srobinsonReport blockers and progress to the orchestrator via the nancy message command.
m2ai-portfolioEnumerate unsourced claims, stale data, and calculation errors in AI-generated documents.
