BF acpx-bridge-troubleshooting
用于排查 acpx 桥接连接失败、超时或初始化卡住的问题。当用户提到 acpx 无法连接、ACP 桥接超时、gateway.token 缺失、Claude Code 认证失败、initialize 阶段卡住、或尝试将微信/飞书渠道切换到 ACP 后端时触发。涵盖配置验证、令牌文件修复、模型端点检查及网络连通性测试。即使未明确说'acpx',但描述'CLI 连不上网关'或'子代理调用失败'也应使用。
As a process F 31/100 · Will not run — References files that are not bundled: scripts/check_gateway.sh, references/acp_channels.md
IntegrationSoftware developmentAI and agentsInfrastructuretype and topics are labelled automatically from the skill text
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The text references files that are not there: add them or drop the references.
For the model run — optional
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
missing-refreference to a missing file: scripts/check_gateway.sh - warning
missing-refreference to a missing file: references/acp_channels.md
Process rating: all ten parameters 31/100
Will not run. References files that are not bundled: scripts/check_gateway.sh, references/acp_channels.md
- 0Tools and files. 2 referenced file(s) missing: scripts/check_gateway.sh, references/acp_channels.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 40Consistency. Frontmatter name (acpx-bridge-troubleshooting) differs from the folder (acpx-connection-troubleshooting)
- 100Steps. 29 steps
- 100Execution cost. Instruction body is 870 tokens
- 100Running it twice. No mutating operations
- medium 4 test cases, all positive: not one "should refuse" or "should ask first"
- low No test case covers injection arriving through data
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 200: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 29 items
- +4Has examples (5 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 67.
External checks
ClawHub: suspicious
This appears to be a legitimate acpx troubleshooting guide, but it asks agents to inspect and rewrite local credential files without enough guardrails against exposing or overwriting secrets.
LLM: suspicious (medium) · VirusTotal: · 29 May 2026