使用方法
- 复制安装命令，在自己的智能体环境安装前先检查源码包。
- 从原始文档核对所需工具、凭据和支持的宿主。
- 说明输入材料与期望交付物，并对照来源检查输出。
npx skills add https://github.com/firegoat-ai/skills --skill filing-feedback开始前需了解
- 安装不包含模型订阅、API 额度或访问文件的权限。
- 仓库星数和安装量反映活跃情况，不等于独立质量或安全测试。
按源仓库内容呈现，保留标题、案例、代码、表格、链接以及原文引用的演示图片。
Filing feedback
When something looks wrong
If a platform call fights you — a misleading or missing error, a response that contradicts another tool, a write that returns success but doesn't stick on a later read, input silently dropped, a field the docs promise that isn't there — call send_feedback (type bug) while it's fresh, then continue the task. Filing is a side channel, not a blocker: after filing, do what the user asked anyway with what you have, and tell them in one line what is uncertain because of the platform issue (e.g. "run requested; persona instructions may not be applied, bug filed"). Only stop if the task literally cannot proceed — the user is waiting on the outcome, and a filed bug plus a run with a caveat is more useful than a filed bug alone.
What to include
Include the request you sent, the response you got, and what you expected; put report slugs, run/prompt ids and tool names in context. Do not retry the same call more than once.
Which type
Something broken or contradictory is type bug. Something that works but was confusing, slow, or made you guess is type feedback. Something you wished existed is type feature_request.
What to skip
Skip only your own mistakes and one-off transient errors.
