ccb-self-chain

Repair CCB lineage issues with retry, resubmit, or ack actions.

17|2|Updated Jun 2, 2026
One-click install
npx skills add https://github.com/SeemSeam/agent-roles-spec --skill ccb-self-chain
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ccb-self-chain
Source: https://github.com/SeemSeam/agent-roles-spec/tree/main/roles/ccb-self/skills/ccb-self-chain
Command: npx skills add https://github.com/SeemSeam/agent-roles-spec --skill ccb-self-chain

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the challenge of repairing lineage issues in CCB, enabling targeted retry, resubmit, or ack decisions for job/message/attempt/reply/inbound-event/artifact IDs.

Core Features & Use Cases

  • Lineage Repair: Identify and resolve lineage issues in CCB.
  • Retry, Resubmit, Ack: Apply specific repair actions based on the nature of the issue.
  • Artifact Handling: Safely handle artifact-backed replies, ensuring integrity before acting.
  • Use Case: If a job or message fails due to lineage issues, use this Skill to automatically decide whether to retry, resubmit, or acknowledge the action, based on detailed analysis and user intent.

Quick Start

Run the ccb-self-chain skill with the lineage ID you wish to repair, e.g., 'ccb self-chain <job_id|message_id>'.

Frequently Asked Questions about ccb-self-chain

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

FAQPage Schema
How do I repair CCB lineage issues for failed jobs or messages?

To repair CCB lineage issues, you can use targeted retry, resubmit, or ack decisions based on lineage state and user intent. This handles job, message, attempt, reply, inbound-event, and artifact IDs.

What is the difference between retry, resubmit, and ack for CCB lineage repair?

Retry, resubmit, and ack are specific repair actions applied based on the nature of the lineage issue. The appropriate action is determined by analyzing the current lineage state and your intent.

How do I handle artifact verification during CCB lineage repair?

Artifact verification ensures integrity before acting on artifact-backed replies. The lineage repair process safely handles these artifacts to confirm their state before applying any repair actions.

Can I repair CCB lineage issues during concurrent repair attempts?

Yes, the CCB lineage repair process explicitly handles concurrent repair attempts. It manages simultaneous actions on job, message, or artifact IDs to prevent conflicts during the repair workflow.

What CCB ID types are supported for lineage repair?

CCB lineage repair supports job, message, attempt, reply, inbound-event, and artifact IDs. You can target any of these identifier types to resolve lineage issues using retry, resubmit, or ack.

When should I use an ack decision instead of a retry for CCB lineage repair?

You should use an ack decision instead of a retry when the lineage state and your intent indicate the issue should be acknowledged rather than reprocessed. The repair action is chosen based on detailed analysis of the specific failure.