Aegis gateway diagnostics
Skill HaloForgeAI/aegis-agent-plugins/claude-code/aegis/skills/aegis-gateway-diagnostics
Public Codex, Claude Code, and agent skill packages for Aegis.
npx -y skills add HaloForgeAI/aegis-agent-plugins --skill aegis-gateway-diagnosticsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Diagnose Aegis Gateway, channels, delivery queues, MCP, and local worker readiness. Use when Aegis reports no tools/local worker despite connected Gateway status, or when Telegram/WeCom/HaloForge delivery/runtime behavior needs evidence.
SKILL.md
1.1 KB, 208 tokens by cl100k_base, as published. Nobody here has run it
Aegis Gateway Diagnostics
Gateway connected is not the same as a complete tool execution path. Diagnose the layer precisely.
Procedure
- Call
aegis_mcp_status. - Call
aegis_gateway_status. - Call
aegis_gateway_accounts. - Call
aegis_gateway_deliverieswhen delivery or channel reply behavior is involved. - If the user references a WorkItem or agent run, inspect board/report context before recommending action.
Labels
Use the most accurate label:
mcp_unavailableauth_or_owner_scopeserver_side_readygateway_account_unhealthyworker_connected_not_tool_readyworker_tool_readyprovider_planner_missingdelivery_queue_failure
Output
Give observed state, likely layer, evidence, and one next operational check. Do not say "no tools" when server-side tools exist or only local worker execution is missing.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.