使用方法
- 复制安装命令，在自己的智能体环境安装前先检查源码包。
- 从原始文档核对所需工具、凭据和支持的宿主。
- 说明输入材料与期望交付物，并对照来源检查输出。
npx skills add https://github.com/sociuu/sociuu-skills --skill sociuu-investigate开始前需了解
- 安装不包含模型订阅、API 额度或访问文件的权限。
- 仓库星数和安装量反映活跃情况，不等于独立质量或安全测试。
按源仓库内容呈现，保留标题、案例、代码、表格、链接以及原文引用的演示图片。
Sociuu Investigate
Establish expected versus observed behavior, environment, timeframe, affected tenant/persona and source. Search relevant code, tests and existing tasks. A report labelled bug is an observation, not proof of a defect.
Use the available first-party tools for relevant evidence. Keep client scope explicit and output sanitized. Read-only Production investigation requires the applicable repository and user authority; tool access alone does not authorize new Production work. Do not require Production data for local reproduction.
Test competing explanations with the smallest useful checks. Use CE Debug for technical diagnosis when appropriate, preserving the request's read-only ceiling. Do not create tasks, modify configuration or send messages for an investigation-only request. If local reproduction needs changes, use only authorized isolated setup.
When connector/API evidence is independent, a focused lower-capability evidence worker may collect and cite it. Give it the exact question and read-only boundary; the coordinating agent evaluates contradictions and makes the classification.
Return the supported classification, cause/confidence, evidence, unknowns and recommended action. Distinguish defect, expected behavior, configuration/data, implementation gap, environment failure and unresolved evidence.
If the original request includes fixing the same issue, establish its ClickUp record with Sociuu Task and continue with one suitable implementation/diagnosis provider. CE Debug/Work are options for substantial work. Reuse valid findings; do not restart diagnosis or ask whether to continue merely because the skill boundary changed.
