Invocation de sous-agents configurables

VérifiéPrudence

Permet d'invoquer des sous-agents avec un accès configurable aux outils, qui renvoient uniquement les réponses sans encombrer le contexte. Utile pour résumer un historique Git étendu, comparer plusieurs dépôts en parallèle, ou traiter de gros diffs/logs.

Spar Skills Guide Bot
DeveloppementIntermédiaire
6002/06/2026
Claude Code
#subagents#parallel-processing#git-history#tool-restriction#repo-analysis

Recommandé pour

Notre avis

Permet de lancer des sous-agents avec un accès configurable aux outils, limitant ainsi le bruit dans le contexte et optimisant le traitement de grandes quantités de données (historique git, logs, etc.).

Points forts

  • Exécution parallèle de plusieurs sous-agents pour traiter simultanément différentes tâches.
  • Restriction fine des outils afin d'éviter des actions superflues et de préserver le contexte.
  • Idéal pour analyser des repositories ou des logs volumineux sans polluer le contexte principal.

Limites

  • Nécessite le plugin shell `synu` et l'outil CLI `claude`, ce qui limite la portabilité.
  • Dépend d'une configuration précise des outils autorisés, sous peine de résultats incomplets.
  • Le prompt doit être très spécifique pour obtenir des résultats utiles, ce qui demande de la réflexion.
Quand l'utiliser

Lorsque vous devez traiter de grandes quantités de données (historique git, diffs, logs) ou effectuer des analyses parallèles sur plusieurs repositories.

Quand l'éviter

Pour des tâches simples ou lorsque le sous-agent n'a pas besoin d'outils spécifiques, car la configuration supplémentaire n'apporte pas de bénéfice.

Analyse de sécurité

Prudence
Score qualité80/100

The skill describes spawning subagents via shell commands, which is a powerful capability. While the example restricts tools tightly, the skill itself does not enforce restrictions; it relies on the user to specify safe configurations. This could lead to unintended command execution if misused.

Points d'attention
  • Uses shell commands (synu claude) to spawn subagents with potentially arbitrary tool access; improper restriction could lead to execution of unintended operations.
  • Relies on external CLI tools (synu, claude) which may not be present or configured securely.

Exemples

Git changes summary
cd /path/to/other/repo && synu claude --disallowed-tools 'Bash(*) Explore Edit Read WebFetch WebSearch Glob Grep NotebookEdit NotebookRead SlashCommand Write' --allowed-tools 'Bash(git log:*) Bash(git show:*)' -p 'Using only git log and git show, summarise the major user-facing changes in abc123..def456. Do not provide code snippets or technical details. Consider user-facing changes, like being able to set a port-out PIN or adding a new button or changing font sizes.'
Parallel repo analysis
synu claude --allowed-tools 'Read' -p 'Analyze the README.md files of /path/to/repoA and /path/to/repoB. List the main features of each and compare them.'
Log error analysis
synu claude --disallowed-tools 'Edit Write Explore' --allowed-tools 'Bash(grep:*) Bash(cat:*) Bash(awk:*)' -p 'Analyze /var/log/app.log for errors. Using grep and awk, count each unique error type and list the top 5 most frequent errors with their count and first occurrence timestamp.'

name: invoking-subagents description: Spawns subagents with configurable tool access that return just the answers without flooding your context. Use for summarizing extensive git history, comparing across multiple repositories in parallel, or processing large diffs/logs. compatibility: Requires synu shell plugin and claude CLI tool license: AGPL-3.0-or-later metadata: author: Amolith amolith@secluded.site

Invoke with synu claude --flags -p 'prompt'.

Important: Subagents are scoped to their cwd, just like you. To work in another repository, cd there first.

Use a precise and thorough prompt. Aggressively restrict which tools it can interact with; if it doesn't need Edit, don't give it Edit. If it needs to read files, Glob, Grep, and Read are probably sufficient. Task can be helpful. Notebook, Slash, Write, Web, Edit, etc. should almost never be necessary. Execute them in the background. You may invoke multiple when appropriate and in parallel if helpful. Once they're running, you may either stop and wait for me to tell you they're finished or continue with other work.

Example exploring git history in another repo:

cd /path/to/other/repo && fish -c "synu claude --disallowed-tools 'Bash(*) Explore Edit Read WebFetch WebSearch Glob Grep NotebookEdit NotebookRead SlashCommand Write' --allowed-tools 'Bash(git log:*) Bash(git show:*)' -p 'Using only git log and git show, summarise the major user-facing changes in HASH..HASH. Do not provide code snippets or technical details. Consider user-facing changes, like being able to set a port-out PIN or adding a new button or changing font sizes.'"

Refer to installing-synu.md if it's unavailable.

Skills similaires