Find Work Skill

Identifies and claims the highest-priority unassigned task from the coordinator and GitHub issues.

4|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/mkalkere/agent-coordinator --skill find-work-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Find Work Skill
Source: https://github.com/mkalkere/agent-coordinator/tree/main/src/agent_os/templates/skills/development/find-work
Command: npx skills add https://github.com/mkalkere/agent-coordinator --skill find-work-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating multiple AI agents to avoid duplicate work and lost context is error-prone. This skill automatically identifies the highest-priority unassigned task and self-claims it to streamline collaboration.

Core Features & Use Cases

  • Self-assign: scans the coordinator and open GitHub issues to pick the top-priority unclaimed task.
  • Coordination-safe: respects existing claims and gracefully handles coordinator unavailability.
  • Use Case: a team of agents collaborating on the same repo can rapidly pull in fresh work without conflicts.

Quick Start

Identify the top-priority unassigned task and self-claim it using the coordinator and GitHub issue API.

Frequently Asked Questions about Find Work Skill

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

FAQPage Schema
How do I automatically assign unclaimed GitHub issues to AI agents?

To assign unclaimed GitHub issues, this skill scans the coordinator and open GitHub issues to find the highest-priority unassigned task, then self-claims it via HTTP API and DM messaging to prevent duplicate work.

What is the best way to coordinate multiple AI agents on the same codebase without conflicts?

Coordinating multiple AI agents on the same codebase requires claiming tasks safely. This skill scans for existing claims, respects them, and gracefully handles coordinator unavailability to ensure agents pull fresh work without conflicts.

How does task assignment work during idle periods for AI agents?

Task assignment during idle periods works by operating when agents are idle to scan the coordinator and GitHub issues for the top-priority unclaimed task, then self-claiming it via HTTP API and DM messaging.

Do I need a coordinator service to use automated task assignment for agents?

A coordinator service is used for automated task assignment, but the skill gracefully handles coordinator unavailability by still querying GitHub issues to identify and self-claim the highest-priority unassigned task.

What happens if the coordinator is unavailable during multi-agent task assignment?

If the coordinator is unavailable, the skill gracefully handles the error and continues querying GitHub issues to identify and self-claim the highest-priority unassigned task, preventing workflow disruption.