sociuu/sociuu-skills

sociuu-investigate

Explain ambiguous Sociuu reports using code, configuration, tenant-scoped evidence and task history.

View source

How to use

  1. Copy the installation command and review the source package before installing it in your own agent environment.
  2. Check the source document for required tools, credentials and supported hosts.
  3. Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/sociuu/sociuu-skills --skill sociuu-investigate

Before you start

  • Installation does not include a model subscription, API allowance or permission to access your files.
  • Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

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.

Related by task

from this repository

More skills

All skills