recoil-labs/recoil-link / .agents/skills/denylist-stuck-messages
denylist-stuck-messages
VerifiedAdd message IDs to the relayer denylist. Use after investigating stuck messages with /investigate-stuck-messages, or when you have specific message IDs to denylist.
Denylist Stuck Messages
Add message IDs to the relayer denylist configuration, create a PR, and deploy.
When to Use
-
After investigation:
- User ran
/investigate-stuck-messagesand wants to denylist the found messages - User says "denylist these" or "add these to blacklist"
- User ran
-
Direct denylist request:
- User provides specific message IDs to denylist
- User pastes message IDs from explorer or logs
Input Parameters
/denylist-stuck-messages <message_ids> [app_context=NAME] [reason=REASON]
| Parameter | Required | Default | Description |
|---|---|---|---|
message_ids | Yes | - | Space or newline separated message IDs (0x...) |
app_context | No | Inferred or "Unknown" | App context name for the comment |
reason | No | "stuck in prepare queue" | Reason for denylisting (for comment) |
environment | No | mainnet3 | Deployment environment |
Examples:
/denylist-stuck-messages 0xabc123 0xdef456 app_context=USDC/mainnet-cctp-v2-standard
/denylist-stuck-messages
0xabc123
0xdef456
0x789ghi
Workflow
Step 1: Parse Message IDs
Extract all message IDs from the input. Valid formats:
- Space-separated:
0xabc 0xdef 0x123 - Newline-separated
- Comma-separated:
0xabc, 0xdef, 0x123
Validate each ID:
- Must start with
0x - Must be 66 characters (0x + 64 hex chars)
Step 2: Confirm with User
Ask the user to confirm:
Ready to denylist X messages for [APP_CONTEXT]:
| Message ID |
|------------|
| 0xabc123... |
| 0xdef456... |
Proceed?
Options:
- "Yes, denylist all" (Recommended)
- "Let me modify the list"
- "Cancel"
Step 3: Get User's GitHub Handle
Ask for GitHub handle if not known:
What is your GitHub handle for the branch name?
Step 4: Update Blacklist Configuration
Edit typescript/infra/config/environments/mainnet3/customBlacklist.ts:
- Read the current file
- Add new message IDs to the
blacklistedMessageIdsarray - Include a comment with:
- App context name
- Date (YYYY-MM-DD format)
- Reason
Example addition:
// [APP_CONTEXT] [REASON] [YYYY-MM-DD]
'0xabc123...',
'0xdef456...',
Add entries near the end of the array, before the closing bracket.
Step 5: Create Branch and Pull Request
# Checkout main and pull latest
git checkout main && git pull origin main
# Create branch
git checkout -b <github_handle>/denylist-<app_context>
# Stage changes
git add typescript/infra/config/environments/mainnet3/customBlacklist.ts
# Commit
git commit -m "chore: denylist <APP_CONTEXT> stuck messages
Added X message IDs to denylist for <APP_CONTEXT> route.
Reason: <REASON>
"
# Push and create PR
git push -u origin HEAD
gh pr create --title "chore: denylist <APP_CONTEXT> stuck messages" --body "$(cat <<'EOF'
## Summary
- Added X message IDs to the relayer denylist
- App context: `<APP_CONTEXT>`
- Reason: <REASON>
## Message IDs
<list of message IDs>
## Test plan
- [ ] Review message IDs are correct
- [ ] Deploy relayer with updated denylist
EOF
)"
Step 6: Output Slack Message
Before asking about deployment, output the Slack message:
**Slack Message (copy/paste to #relayer-alerts):**
:no_entry_sign: *Denylist PR created*
App context: `<APP_CONTEXT>`
Messages denylisted: X
Reason: <REASON>
PR: <PR_URL>
Step 7: Ask About Deployment
Ask the user:
PR created. Deploy the relayer now with the updated denylist?
Options:
- "Yes, deploy now" (Recommended)
- "No, I'll deploy later"
If user confirms, deploy every mainnet3 relayer context. They share the same blacklist, so deploying only hyperlane leaves rc and fastpath relaying the messages:
for context in hyperlane rc fastpath; do
pnpm --dir typescript/infra exec tsx ./scripts/agents/deploy-agents.ts -e mainnet3 --context "$context" --role relayer
done
If user skips, output the command for later use.
Step 8: Update Slack Message After Deploy
If deployed, update the Slack message:
:no_entry_sign: *Denylist deployed*
App context: `<APP_CONTEXT>`
Messages denylisted: X
Reason: <REASON>
PR: <PR_URL>
Grouping by Destination
If message IDs are for multiple destinations (from investigation output), group them in the blacklist file:
// [APP_CONTEXT] stuck messages [YYYY-MM-DD]
// dest: arbitrum
'0xabc123...',
'0xdef456...',
// dest: optimism
'0x789ghi...',
'0xjkl012...',
Error Handling
- Invalid message ID format: Show which IDs are invalid, ask user to fix
- Git conflicts: Pull latest main and retry
- PR creation fails: Check gh auth status
- Deployment fails: Show error, suggest manual deployment
Prerequisites
ghCLI authenticated- Git configured with push access to the repo
- For deployment:
kubectlconfigured with mainnet cluster access
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |