使い方
- インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
- 必要なツール、認証情報、対応環境を原文で確認します。
- 入力と成果物を指定し、出力を資料と照合します。
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.
