clanker-ops-unknown-agent-diagnosis

Diagnose and resolve 'Unknown agent' errors in Clanker Ops tasks.

Updated May 15, 2026
One-click install
npx skills add https://github.com/ruskibeats/t1d --skill clanker-ops-unknown-agent-diagnosis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clanker-ops-unknown-agent-diagnosis
Source: https://github.com/ruskibeats/t1d/tree/main/.pi/skills-archive/clanker-ops-unknown-agent-diagnosis
Command: npx skills add https://github.com/ruskibeats/t1d --skill clanker-ops-unknown-agent-diagnosis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Identifies and resolves 'Unknown agent' errors in Clanker Ops tasks, which occur when an agent exists in the CLANKER_ROSTER.md but is not registered as a pi subagent.

Core Features & Use Cases

  • Error Diagnosis: Determines the cause of 'Unknown agent' errors in task dispatching.
  • Verification Steps: Checks if the agent exists in the roster, if it is registered as a subagent, and identifies the resolution path.
  • Resolution Options: Provides options to manually register agents, use intercom for session-based loading, or handle exceptions for human-only dispatch.
  • Verification & Testing: Offers verification steps for before and after agent registration or alternative paths, including a dispatch test.

Quick Start

To diagnose and resolve 'Unknown agent' errors, use the skill with the command 'clanker-ops-unknown-agent-diagnosis' and follow the step-by-step procedure outlined in the documentation.

Frequently Asked Questions about clanker-ops-unknown-agent-diagnosis

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

FAQPage Schema
Why does task dispatch fail with an 'Unknown agent' error in Clanker Ops?

An 'Unknown agent' error in Clanker Ops task dispatch occurs when an agent exists in the CLANKER_ROSTER.md but is not registered as a pi subagent. This skill diagnoses the failure by verifying agent registration status and checking subagent availability.

How do I resolve unregistered pi subagent errors in Clanker Ops?

To resolve unregistered pi subagent errors, you can manually register the agent, use intercom for session-based loading, or handle exceptions for human-only dispatch. This skill provides step-by-step verification and resolution paths for each option.

How do I verify agent registration status in the CLANKER_ROSTER.md file?

Verifying agent registration involves checking if the agent exists in the CLANKER_ROSTER.md and confirming its subagent status. This skill guides you through the verification steps and offers a dispatch test to confirm successful registration.

Can I use intercom for session-based loading to bypass agent registration failures?

Yes, intercom for session-based loading is a valid resolution path for agent registration failures. This skill helps determine when to use intercom loading rather than manual registration to resolve task dispatch errors.

What are the limitations when handling exceptions for human-only dispatch in Clanker Ops?

Handling exceptions for human-only dispatch is limited to scenarios where automated agent registration is not possible or desired. This skill identifies these edge cases and provides alternative resolution paths when standard subagent registration fails.

Does the clanker-ops-unknown-agent-diagnosis skill require specific dependencies to function?

The clanker-ops-unknown-agent-diagnosis skill has no external dependencies. It operates by interacting directly with the CLANKER_ROSTER.md and the pi-subagents system to diagnose and resolve task dispatch errors.