Agent Skills › WingedGuardian/GENesis-AGI › obstacle-resolution

obstacle-resolution

GitHub

用于系统性解决阻塞问题。当API失败、服务不可用或依赖缺失时，通过回退链框架分类障碍并尝试替代方案。若所有回退均失败，则降级处理或升级报警，并记录解决路径与观察结果。

src/genesis/skills/obstacle-resolution/SKILL.md WingedGuardian/GENesis-AGI

Trigger Scenarios

路由链耗尽（所有提供商失败）所需服务无法访问因缺少依赖或能力导致任务受阻自动重试次数已用完

Install

npx skills add WingedGuardian/GENesis-AGI --skill obstacle-resolution -g -y

More Options

Non-standard path

npx skills add https://github.com/WingedGuardian/GENesis-AGI/tree/main/src/genesis/skills/obstacle-resolution -g -y

Use without installing

npx skills use WingedGuardian/GENesis-AGI@obstacle-resolution

指定 Agent (Claude Code)

npx skills add WingedGuardian/GENesis-AGI --skill obstacle-resolution -a claude-code -g -y

安装 repo 全部 skill

npx skills add WingedGuardian/GENesis-AGI --all -g -y

预览 repo 内 skill

npx skills add WingedGuardian/GENesis-AGI --list

SKILL.md

Frontmatter

{
    "name": "obstacle-resolution",
    "phase": 6,
    "consumer": "cc_background_task",
    "skill_type": "workflow",
    "description": "Resolve obstacles using fallback chains — use when an approach fails, a dependency is unavailable, an API returns errors, or a task is blocked and needs an alternative path forward"
}

Obstacle Resolution

Purpose

When Genesis encounters a blocker — a failed API call, an unavailable service, a missing capability — systematically resolve it using the fallback chain framework.

When to Use

A routing chain is exhausted (all providers failed).
A required service is unreachable.
A task cannot proceed due to a missing dependency or capability.
Automatic retries have been exhausted.

Workflow

Classify the obstacle — What type? (provider failure, data missing, capability gap, external dependency, permission issue)
Check fallback chain — Load the relevant fallback chain from fallback_chains.py. Walk the chain in order.
Attempt each fallback — Try each alternative. Log attempts and results.
Escalate if needed — If all fallbacks exhausted:
- For non-urgent: queue for user review, continue with degraded capability.
- For urgent: alert user immediately via outreach.
Record resolution — Store the successful resolution path as an observation. If a new fallback was discovered, propose a procedure update.

Output Format

obstacle: <one-line description>
date: <YYYY-MM-DD>
type: provider_failure | data_missing | capability_gap | external_dep | permission
chain_attempted:
  - step: <fallback step>
    result: success | failure
    detail: <what happened>
resolution: resolved | degraded | escalated
resolution_detail: <how it was resolved>

Examples

Example: Embedding provider chain exhausted

Trigger: memory_store fails with EmbeddingUnavailableError — Ollama timeout, DeepInfra 429, DashScope connection refused.

Expected output:

obstacle: All embedding providers exhausted during memory store
date: 2026-03-20
type: provider_failure
chain_attempted:
  - step: Ollama (local)
    result: failure
    detail: ReadTimeout after 60s — model not loaded
  - step: DeepInfra (cloud)
    result: failure
    detail: HTTP 429 rate limit (RPM exceeded)
  - step: DashScope (cloud)
    result: failure
    detail: ConnectionRefusedError — service unreachable
resolution: degraded
resolution_detail: Memory stored FTS5-only (no vector). Queued in
  pending_embeddings for background recovery. Circuit breaker tripped
  on DashScope (120s backoff).