Error handling

MCP kullanım/abonelik/faturalandırma hataları verirse kullanıcıya ne yapması gerektiğini söyleyin:

yazan kuscubasiece·8 Eylül 2026

Kaynak: davepoon/claude-code-subagents-collection · MIT

Kurulum

mkdir -p .claude/skills/error-handling && curl -sL https://www.antrophiclove.com/api/kaynak/error-handling/raw -o .claude/skills/error-handling/SKILL.md

Hedef dosya: .claude/skills/error-handling/SKILL.md

Önizleme Ham metin ⑂ Kendi sürümünü oluştur

# Error handling

## Usage or subscription errors

If MCP returns usage/subscription/billing errors, tell the user what to do:

> HookRadar could not complete this because the workspace needs billing or usage attention. Open https://platform.hookradar.net/billing to manage your subscription and limits, then retry.

Do not blindly retry paid/write actions when usage is exhausted.

## Pending async jobs

For `add_*` and `analyze_*`:

- `started`: job is running. Poll `get_task_status` only briefly.
- `already_running`: do not start another job; read current data or wait.
- `already_done`: read analysis/result now.
- `not_applicable` or `failed`: terminal; explain the message.

If results are not ready, say the source/analysis is still collecting and avoid claiming that top results exist.

## Empty result after adding a source

Immediately empty results usually mean the parser has not finished. Say that clearly and suggest checking again soon.

## Auth/team errors

If no teams exist, offer `create_team`. If the team slug is unknown, call `list_teams` and ask the user to pick.