aicp-ops-dlq

Inspect and manage AICP Dead-Letter Queue entries via the aicp CLI.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/cyberpunk042/devops-expert-local-ai --skill aicp-ops-dlq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aicp-ops-dlq
Source: https://github.com/cyberpunk042/devops-expert-local-ai/tree/main/.claude/skills/aicp-ops-dlq
Command: npx skills add https://github.com/cyberpunk042/devops-expert-local-ai --skill aicp-ops-dlq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps operators inspect and manage the AICP Dead-Letter Queue using the CLI, ensuring failed tasks are visible, retriable, and auditable instead of being lost or forgotten.

Core Features & Use Cases

  • Inspect pending entries: surface the current DLQ state and preview up to the first few items for quick triage.
  • Retry pending entries: safely reprocess eligible DLQ items after confirming upstream issues are resolved.
  • Diagnose stuck entries: identify and diagnose entries that remain pending for long periods and guide remediation.
  • Tune DLQ policies: adjust retry windows and thresholds to balance reliability with retry budgets in production.
  • Use case: during post-incident reviews, run checks to verify no critical tasks remain stuck in the DLQ before closure.

Quick Start

Check the Dead-Letter Queue status with aicp --dlq-status and if needed retry eligible entries with aicp --retry-dlq after confirming upstream issues are resolved.

Frequently Asked Questions about aicp-ops-dlq

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

FAQPage Schema
How do I inspect pending dead-letter queue entries via the AICP CLI?

Inspect pending dead-letter queue entries by running aicp --dlq-status to surface the current DLQ state and preview the first few JSONL items for quick triage during reliability incidents.

What is the safest way to retry failed tasks in a dead-letter queue?

Retry failed DLQ tasks safely by confirming upstream issues are resolved first, then running aicp --retry-dlq to reprocess eligible items while respecting configured retry delay windows and status guardrails.

How do I diagnose stuck dead-letter queue entries that remain pending for a long time?

Diagnose stuck dead-letter queue entries by inspecting per-day JSONL DLQ files to identify long-pending items, then follow guided remediation steps to resolve the underlying task processing failures.

Can I tune dead-letter queue retry windows and thresholds for production reliability?

Tune DLQ retry windows and thresholds to balance production reliability with retry budgets, adjusting policies via the CLI to control how eligible pending entries are reprocessed without premature retries.

When should I check the dead-letter queue during post-incident reviews?

Check the dead-letter queue during post-incident reviews or post-outage audits to verify no critical tasks remain stuck in the DLQ before closure, ensuring failed items are visible and auditable rather than lost.

Do I need any external dependencies to manage AICP DLQ entries?

No external dependencies are required to manage AICP DLQ entries. The Skill operates standalone using the aicp CLI to read JSONL DLQ files, respect retry delays, and update task status.