debug

分类: 工具与效率 | 上传者: afrotools | 下载: 0 | 版本: v1.0（最新）

仅当用户遇到专门基于 Afro.tools 规范的失败集成时才使用此技能 — 用户正在集成其规范存在于 Afro.tools 注册表中的提供商（Paycard、LengoPay、Djomy、Wave、NimbaSMS 等），并且遇到错误的状态代码、身份验证错误、Webhook 失败、意外响应字段或运行时错误。不要激活通用调试、非 afrotools 提供程序或不基于 Afro.tools 规范的集成。此技能可以诊断问题是否是规范错误、缺失的陷阱或未记录的 API 更改。 --- # Afro.tools — 调试技能当此技能激活时，获取受影响的提供程序和功能的规范，然后系统地将其与用户的实现进行比较以找到差距。 ## 工作流程 1. 从错误、代码片段或用户描述中识别提供程序 slug 和功能。如果不清楚就问——不要猜测。 2. 获取规范： ``` afrotools.get_spec({provider: "<slug>",capability: "<capability>" }) ``` 3. **首先检查陷阱。** 大多数集成失败直接映射到记录的陷阱。在寻找其他地方之前先阅读每个条目。 4. 根据规范交叉检查实现： - **Auth** - 正确的字段名称、位置（标头与正文）、格式字符串 - **Endpoint** - 正确的方法和 URL、正确位置的路径参数 - **字段名称** - 提供者字段通常是非标准的（例如“paycard-amount”，而不是“amount”）；将用户的有效负载与“input_schema”进行比较 - **状态值** - 枚举区分大小写（例如，LengoPay 使用“SUCCESS”，而不是“success”）； Paycard 上的“代码：0”表示“已找到”，而不是“已付款” - **Webhook** - 立即返回 HTTP 200，仅在回调时无法满足要求，某些提供商需要 HTTPS 5. 清楚地表达诊断： - 引用相关的规范字段或陷阱 - 显示代码的作用与规范的要求 - 提供最小的更正片段

更新日志: Source: GitHub https://github.com/afrotools/afrotools

目录结构

当前层级: tree/main/plugin/skills/debug/

📄 SKILL.md 2.0 KB

SKILL.md

---
name: debug
description: >
  Use this skill ONLY when the user has a failing integration that is specifically
  based on an Afro.tools spec — the user is integrating a provider whose spec exists
  in the Afro.tools registry (Paycard, LengoPay, Djomy, Wave, NimbaSMS, etc.) and
  encounters wrong status codes, auth errors, webhook failures, unexpected response
  fields, or runtime errors. Do NOT activate for generic debugging, non-afrotools
  providers, or integrations not based on an Afro.tools spec. This skill diagnoses
  whether the problem is a spec error, a missing gotcha, or an undocumented API change.
---

# Afro.tools — Debug skill

When this skill activates, fetch the spec for the affected provider and capability,
then systematically compare it against the user's implementation to find the gap.

## Workflow

1. Identify the provider slug and capability from the error, code snippet, or user
   description. Ask if unclear — don't guess.

2. Fetch the spec:
   ```
   afrotools.get_spec({ provider: "<slug>", capability: "<capability>" })
   ```

3. **Check gotchas first.** Most integration failures map directly to a documented
   gotcha. Read every entry before looking elsewhere.

4. Cross-check the implementation against the spec:
   - **Auth** — correct field name, location (header vs body), format string
   - **Endpoint** — correct method and URL, path params in the right place
   - **Field names** — provider fields are often non-standard (e.g. `paycard-amount`,
     not `amount`); compare the user's payload against `input_schema`
   - **Status values** — enums are case-sensitive (e.g. LengoPay uses `SUCCESS`,
     not `success`); `code: 0` on Paycard means "found", not "paid"
   - **Webhook** — returning HTTP 200 immediately, not fulfilling on callback alone,
     HTTPS required for some providers

5. Surface the diagnosis clearly:
   - Quote the relevant spec field or gotcha
   - Show what the code does vs. what the spec requires
   - Provide a minimal corrected snippet

登录后下载/点赞/收藏 ❤ 16 | ★ 0

debug

目录结构

SKILL.md

举报内容

提示