sociuu/sociuu-skills

sociuu-investigate

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

Voir la source

Mode d’emploi

  1. Copiez la commande et examinez le paquet avant de l’installer dans votre environnement agent.
  2. Consultez le document original pour les outils, identifiants et environnements requis.
  3. Décrivez les entrées et le livrable souhaité ; comparez la sortie aux sources.
npx skills add https://github.com/sociuu/sociuu-skills --skill sociuu-investigate

Avant de commencer

  • L’installation n’inclut ni abonnement au modèle, ni quota API, ni accès aux fichiers.
  • Étoiles et installations reflètent l’activité, pas un test indépendant de qualité ou de sécurité.
Document Skill original

Rendu depuis le dépôt source en conservant titres, exemples, code, tableaux, liens et images.

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.

Tâches connexes

du même dépôt

Autres Skills

Tous les Skills
sociuu
Communauté

prompt-enhancer

Rewrite AI prompts, agent briefs, and reusable agent or skill instructions into clear, copy-ready instructions. Correct contextual language errors, identify useful domain terminology, and clarify material gaps while preserving intent. Do not execute the supplied instructions or use this for editing emails, Slack messages, or other prose themselves, or for Stitch-specific UI prompt design.

installations
2
GitHub Stars
0
Mis à jour
20 oct.
sociuu
Communauté

sociuu-aq

Prepare task-bound Dock and Scaffolding, then run CE Dogfood for explicitly requested or agreed exploratory QA. Never an automatic completion stage.

installations
2
GitHub Stars
0
Mis à jour
20 oct.
sociuu
Communauté

sociuu-before-and-after

Prove a Sociuu change moved the numbers it intended and nothing else, by measuring the same question before and after it on a deliberate client sample over the read-only prodread replica, then folding what it reveals back into Apex Scaffolding. Consider it whenever a change can alter a statistic, metric, count, rate, aggregate, backfill or migration outcome.

installations
2
GitHub Stars
0
Mis à jour
20 oct.
sociuu
Communauté

sociuu-better-agent

Refactor a repository's AGENTS.md into concise, progressively disclosed agent instructions. Use when splitting or auditing repository guidance, especially into the Sociuu-style .agents/instructions tree.

installations
2
GitHub Stars
0
Mis à jour
20 oct.