Agent skill

Messenger Retry Failures

by dev-toolings in dev-toolings/superpowers-symfony

Handle message failures with retry strategies, failure transport, and recovery in Symfony Messenger (Recoverable/Unrecoverable exceptions)

MITAuto-check: notes

Install Messenger Retry Failures

skills CLI
$ npx skills add dev-toolings/superpowers-symfony --skill messenger-retry-failures -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install dev-toolings/superpowers-symfony messenger-retry-failures --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/dev-toolings/superpowers-symfony.git skills-src && mkdir -p .claude/skills && cp -r skills-src/content/skills/messenger-retry-failures .claude/skills/messenger-retry-failures && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
messenger-retry-failures
GitHub stars
222
Token cost
~566 tokens
SKILL.md length
240 words
Files
2
Skills in repo
44
Repo updated
First seen
Licence
MIT

At a glance

Handle message failures with retry strategies, failure transport, and recovery in Symfony Messenger (Recoverable/Unrecoverable exceptions)

  • Works in 6 steps: Classify each failure:… → Set retry_strategy per transport and… → Implement RetryStrategyInterface only… → …
  • SKILL.md covers Use when, Default workflow, Guardrails and Progressive disclosure, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Messenger Retry Failures is an agent skill from dev-toolings/superpowers-symfony. Handle message failures with retry strategies, failure transport, and recovery in Symfony Messenger (Recoverable/Unrecoverable exceptions)

Its SKILL.md is about 570 tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `reference.md`).

It works with Symfony. The repository describes itself as: Claude Code plugin for Symfony 7.4 LTS & 8.x — 44 skills, 7 AI subagents & 13 commands for API Platform v4, Doctrine ORM 3, TDD (Pest/PHPUnit), Messenger, security & DDD. The licence is MIT.

Example prompts

  • “/messenger-retry-failures”

Requirements

  • Pre-approved tools (allowed-tools): Read, Glob, Grep, Write, Edit, Bash

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Classify each failure: UnrecoverableMessageHandlingException when retrying cannot help, RecoverableMessageHandlingException when the cause…
  2. Set retry_strategy per transport and point failure_transport to a dedicated queue.
  3. Implement RetryStrategyInterface only when the built-in backoff is not enough, and register it through retry_strategy.service.
  4. Make the handler idempotent, with a stable idempotency key for external calls.
  5. Triage with messenger:failed:show, then messenger:failed:retry or messenger:failed:remove.
  6. Subscribe to WorkerMessageFailedEvent and alert only when willRetry() is false.

What it can do on your machine

Read from SKILL.md and the folder at commit 459bcd0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Glob
    • Grep
    • Write
    • Edit
    • Bash

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Messenger Retry Failures loads about 566 tokens when it runs. Until then it costs about 41 tokens; SKILL.md has 240 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~41
When it runs · the whole SKILL.md, loaded when a task matches
~566

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Glob, Grep, Write, Edit, Bash

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from dev-toolings/superpowers-symfony at commit 459bcd0, republished under its MIT licence (© dev-toolings). 240 words, ~566 tokens.

Download SKILL.mdSave it as .claude/skills/messenger-retry-failures/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
messenger-retry-failures
description
Handle message failures with retry strategies, failure transport, and recovery in Symfony Messenger (Recoverable/Unrecoverable exceptions)
allowed-tools
Read, Glob, Grep, Write, Edit, Bash
capabilities
read, search, edit, shell
tags
messenger

Messenger Retry Failures (Symfony)

Use when

  • A handler fails and you must decide between retrying and giving up.
  • Tuning retry_strategy (max_retries, delay, multiplier, max_delay) for a transport.
  • Inspecting, retrying, or removing messages in the failure transport.
  • Alerting when a message fails for good.

Default workflow

  1. Classify each failure: UnrecoverableMessageHandlingException when retrying cannot help, RecoverableMessageHandlingException when the cause is transient.
  2. Set retry_strategy per transport and point failure_transport to a dedicated queue.
  3. Implement RetryStrategyInterface only when the built-in backoff is not enough, and register it through retry_strategy.service.
  4. Make the handler idempotent, with a stable idempotency key for external calls.
  5. Triage with messenger:failed:show, then messenger:failed:retry or messenger:failed:remove.
  6. Subscribe to WorkerMessageFailedEvent and alert only when willRetry() is false.

Guardrails

  • Never retry what cannot succeed, such as invalid input or a declined card.
  • Keep max_retries modest (3-5 usually) with exponential backoff, so a failing service is not hammered.
  • retryDelay and forceRetry on the recoverable exception are marked 8.1+ in the reference, and forceRetry: true goes past max_retries: verify the version before relying on them.
  • messenger:failed:retry is interactive unless --force: read the message with -vv first.

Progressive disclosure

  • Use this file for execution posture and risk controls.
  • Open references when deep implementation details are needed.

Output contract

  • The exception class chosen for each failure mode of the handler.
  • Retry settings per transport, and the failure transport.
  • The failed-message runbook (show, retry, remove) and the alert on final failure.

References

  • reference.md

© dev-toolings, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in content/skills/messenger-retry-failures of dev-toolings/superpowers-symfony.

  • SKILL.md
  • reference.md

Open the folder on GitHubat commit 459bcd0

Compare with similar skills

Messenger Retry Failures next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Messenger Retry Failures compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Messenger Retry Failures this skilldev-toolings/superpowers-symfony222—~566Automated safety check: NotesMIT
Sync Translationssymfony/symfony31k—~1.9kAutomated safety check: PassMIT
Bug Triagesymfony/symfony31k—~1.9kAutomated safety check: PassMIT
Merge Upsymfony/symfony31k—~4kAutomated safety check: PassMIT
PR Mergesymfony/symfony31k—~3.1kAutomated safety check: PassMIT
Security Triagesymfony/symfony31k—~2.6kAutomated safety check: PassMIT

Similar skills

  • Sync Translations

    symfony/symfony

    Synchronize translation catalogs across maintained Symfony branches: find messages that newer branches added to the English catalogs but that are still missing from the oldest maintained branch…

    31k GitHub stars~1.9k tokensUpdated yesterday
    Writing & ContentAuto-check passed
  • Bug Triage

    symfony/symfony

    Decide whether open Bug PRs target the correct branch. An agent skill from symfony/symfony.

    31k GitHub stars~1.9k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Merge Up

    symfony/symfony

    Cascade-merge maintained Symfony branches from oldest to newest (e.g.

    31k GitHub stars~4k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • PR Merge

    symfony/symfony

    Merge a reviewed pull request the way the Symfony core team does: one --no-ff merge commit per PR, whose message archives the whole discussion, with the review gates checked first.

    31k GitHub stars~3.1k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Security Triage

    symfony/symfony

    Triage a reported security finding into a disposition: a private CVE (coordinated disclosure + advisory), a public hardening PR (fix in the open, no CVE), or not-a-security-issue (reply to reporter).

    31k GitHub stars~2.6k tokensUpdated yesterday
    SecurityAuto-check passed
  • Review a change (a PR, the current branch diff, or a set of files) or audit a component or the whole tree for missing or incorrect security hardening.

    31k GitHub stars~2.9k tokensUpdated yesterday
    SecurityAuto-check passed

More from dev-toolings/superpowers-symfony

All 44 skills in this repo
  • Symfony Scheduler

    dev-toolings/superpowers-symfony

    Schedule recurring tasks with the Symfony Scheduler component (native since 7.x); define schedules, triggers, and integrate with Messenger

    222 GitHub stars~526 tokensUpdated 3 days ago
    Auto-check: notes
  • API Platform Dto Resources

    dev-toolings/superpowers-symfony

    Map entities to API DTOs in API Platform (v5, 4.4, 4.3) with the Symfony Object Mapper ([Map], stateOptions) for decoupled input/output contracts

    222 GitHub stars~593 tokensUpdated 3 days ago
    Auto-check: notes
  • API Platform Filters

    dev-toolings/superpowers-symfony

    Implement API Platform filters - Parameters API (QueryParameter, v5/4.4/4.3) and the [ApiFilter] attribute deprecated since 4.4 - for search, date, range, boolean, and custom filtering

    222 GitHub stars~610 tokensUpdated 3 days ago
    Auto-check: notes
  • API Platform Resources

    dev-toolings/superpowers-symfony

    Configure API Platform resources (v5, 4.4, 4.3) with explicit operations, pagination, and typed OpenAPI for clean, versioned REST/GraphQL APIs

    222 GitHub stars~560 tokensUpdated 3 days ago
    Auto-check: notes
  • API Platform Security

    dev-toolings/superpowers-symfony

    Secure API Platform resources with security expressions, voters, securityPostValidation, and operation-level access control

    222 GitHub stars~551 tokensUpdated 3 days ago
    Auto-check: notes
  • API Platform Serialization

    dev-toolings/superpowers-symfony

    Control API Platform serialization with groups, [Context], IRI links (readableLink/writableLink), and custom context builders

    222 GitHub stars~519 tokensUpdated 3 days ago
    Auto-check: notes

Works with

Questions about Messenger Retry Failures

What does Messenger Retry Failures do?

Handle message failures with retry strategies, failure transport, and recovery in Symfony Messenger (Recoverable/Unrecoverable exceptions). Messenger Retry Failures is an agent skill from dev-toolings/superpowers-symfony.

How do I install Messenger Retry Failures in Claude Code?

Run `npx skills add dev-toolings/superpowers-symfony --skill messenger-retry-failures -a claude-code`. Or copy the skill folder (content/skills/messenger-retry-failures in dev-toolings/superpowers-symfony) into .claude/skills/messenger-retry-failures in your project. Claude Code loads it when a task matches its description.

How do I install Messenger Retry Failures in Codex?

Run `npx skills add dev-toolings/superpowers-symfony --skill messenger-retry-failures -a codex`. Or copy the skill folder (content/skills/messenger-retry-failures in dev-toolings/superpowers-symfony) into .agents/skills/messenger-retry-failures in your project. Codex loads it when a task matches its description.

Can I use Messenger Retry Failures in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add dev-toolings/superpowers-symfony --skill messenger-retry-failures -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/messenger-retry-failures, .gemini/skills/messenger-retry-failures, .github/skills/messenger-retry-failures and .opencode/skills/messenger-retry-failures in your project.

What does Messenger Retry Failures need to run?

SKILL.md names no scripts, command-line tools or credentials: Messenger Retry Failures is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Glob, Grep, Write, Edit, Bash.

Does Messenger Retry Failures access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Messenger Retry Failures safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Messenger Retry Failures use?

Messenger Retry Failures is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Messenger Retry Failures use?

About 566 tokens (SKILL.md is roughly 2.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Messenger Retry Failures?

Skills that share tags, products or a category with Messenger Retry Failures: Sync Translations (symfony/symfony, 31k stars), Bug Triage (symfony/symfony, 31k stars), Merge Up (symfony/symfony, 31k stars) and PR Merge (symfony/symfony, 31k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Messenger Retry Failures?

dev-toolings (a GitHub organization) maintains it in dev-toolings/superpowers-symfony, which has 222 GitHub stars. The repository holds 44 skills in this directory. The repository was last updated on October 5, 2026.

Source: dev-toolings/superpowers-symfony on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.