高风险
默认录屏可能捕获敏感画面，并在仅提供 Slack 线程上下文时自动回传
原文依据：5 处发现了什么
代理被要求默认录制整个复现过程；只要提供了 Slack 频道和线程上下文，指令就要求把录屏发回该线程，而不是再次取得明确发布授权。虽然另有不得包含私密信息的规则，但录制发生在检查或脱敏之前，动态弹窗、通知、账户信息和内部 URL 仍可能进入视频。
为什么需要注意
录屏可能把客户数据、内部界面、通知内容或会话信息分享给频道中不应看到这些内容的成员；上传后可能受 Slack 的保留、下载和转发规则影响。
技能默认录制复现过程，并在提示中存在 Slack 频道与线程时要求把录屏发回该线程；该条件并未同时要求另一次明确的发布授权。虽然指令明确禁止在制品中包含私密信息，这降低了风险，但录屏仍可能意外捕获通知、账户信息或私有 URL，随后被上传。风险只在提供 Slack 线程上下文并可执行发布时成立。用户可要求上传前人工检查/裁剪录屏，并把“提供线程标识”和“授权发布”分开。
- Reproduce the reported behavior as faithfully as possible.- Capture a screen recording of the reproduction by default; most UI bugs involve motion, a transition, or a multi-step interaction, so a clip is stronger proof than stills. Capture screenshots as a supplement, or as the primary artifact only for a genuinely static render.- If the provided steps are unclear or incomplete, use codebase and product knowledge to identify plausible app states that could produce the reported behavior, then test the assigned hypothesis.查看另外 4 个位置
- Do not ask the public reporter for credentials, tokens, private repos, private workspace names, or private account identifiers.- Do not include secrets, auth tokens, private URLs, Authorization headers, refresh tokens, or other private account details in recordings, screenshots, logs, manifests, or final reports.- Do not create or sign into an account unless the prompt and repository-specific guidance explicitly authorize a safe test-auth workflow.- If the assigned report cannot be exercised within the allowed auth/state constraints, stop and report the blocker.- Do not post comments to GitHub, Linear, or external services unless explicitly instructed. When a Slack thread context is provided (a channel id and thread), post the reproduction proof (the recording) back to that thread so the requester sees it; do not post to any other channel or service.- Avoid destructive actions. If a repro requires deleting app state, delete only test state for the current repro environment and report exactly what was reset.- Create a dedicated artifact directory named for your variant, such as `~/bug-repro-primary`.- Record a screen recording of the reproduction by default and save it in the artifact directory with a descriptive name such as `repro.mp4`.- Capture screenshots as a supplement (or as the primary artifact only for a genuinely static render) with ordered filenames, such as `01-initial-state.png`, `02-before-click-settings.png`, and `03-after-click-settings.png`. - whether the screenshot shows the reported bug- If the harness supports built-in screenshot or artifact upload, use it. Otherwise leave artifacts in the directory and report the paths.- If the assigned report cannot be exercised within the allowed auth/state constraints, stop and report the blocker.- Do not post comments to GitHub, Linear, or external services unless explicitly instructed. When a Slack thread context is provided (a channel id and thread), post the reproduction proof (the recording) back to that thread so the requester sees it; do not post to any other channel or service.- Avoid destructive actions. If a repro requires deleting app state, delete only test state for the current repro environment and report exactly what was reset.