Rechercher

PythonReactSEOPDF
OpenClaw

subagent-architecture

Advanced patterns for specialized subagent orchestration with production-ready reference implementations. Security isolation, phased implementation, peer collaboration, and cost-aware spawning.

donovanpankratz-del0 installations selon la source☆ 0 Étoiles du dépôtv2.3.5

Installation

Suivez les instructions du dépôt pour votre agent. Consultez les fichiers et dépendances avant l’installation.

SkillHub CLI

skillhub install donovanpankratz-del/subagent-architecture

Examinez la source et la compatibilité, puis suivez les étapes d’installation.

Donnez le lien à votre agent et demandez-lui d’examiner instructions et dépendances avant d’expliquer les étapes.

Voir la source ↗Guides

Instructions

Advanced Subagent Architecture

Patterns and templates for building robust multi-agent systems with OpenClaw.

Why This Skill Is Complex (Read Before Installing)

This is one of the most feature-dense skills in the ClawHub registry. Security scanners will flag it — not because it's malicious, but because it does a lot. Here's exactly what's in it and why:

Scope:

  • 4 production-ready JS libraries (~1,200 lines total across spawn-security-proxy, spawn-researcher, cost-estimator, quality-scorer)
  • 4 spawn templates covering security proxy, researcher, phased implementation, and peer review patterns
  • A setup.sh that creates local directory scaffolding (no network calls, no package installs)
  • Inline attack vector documentation in spawn-security-proxy.js (test fixtures, not live payloads)

Why the libs exist: These aren't glue code — they implement real patterns: output sanitization with canary tokens, multi-source research validation, cost projection with approval gates, and subagent output scoring. The complexity is the point; simpler skills don't solve these problems.

Why scanners flag it:

  1. JS code in a skill package looks like an execution surface — it is, but only when you explicitly require() it
  2. The security proxy documents injection attack patterns as test examples — pattern matchers don't distinguish documentation from intent
  3. External integration references (Discord, peer agents) appear in templates — they're opt-in workflows, not auto-configured connections

Complexity is not a red flag here. It's the product.


⚠️ Security Transparency Notice

What this skill contains:

  • lib/ — Reference JS libraries (spawn helpers, cost estimator, quality scorer). These are not auto-executed. Copy them to your workspace lib/ directory to use them.
  • templates/ — Markdown spawn templates for common patterns.
  • setup.sh — Creates local directory scaffolding only. Makes no network calls, installs no packages.

*...

Informations sur la source

Source
github
Repository
openclaw/skills
Path
skills/donovanpankratz-del/subagent-architecture
Version
2.3.5
Commit
4691bc44fae41df5badb7312a65ae9e0e492f153
Source de classification
rules
Statut
active
Visibilité
public

Ces informations proviennent de l’analyse indexée et peuvent être anciennes. Vérifiez les fichiers actuels.

Contenu extrait

SKILL.md
# Advanced Subagent Architecture

Patterns and templates for building robust multi-agent systems with OpenClaw.

## Why This Skill Is Complex (Read Before Installing)

This is one of the most feature-dense skills in the ClawHub registry. Security scanners will flag it — not because it's malicious, but because it does a lot. Here's exactly what's in it and why:

**Scope:**
- 4 production-ready JS libraries (~1,200 lines total across spawn-security-proxy, spawn-researcher, cost-estimator, quality-scorer)
- 4 spawn templates covering security proxy, researcher, phased implementation, and peer review patterns
- A `setup.sh` that creates local directory scaffolding (no network calls, no package installs)
- Inline attack vector documentation in `spawn-security-proxy.js` (test fixtures, not live payloads)

**Why the libs exist:** These aren't glue code — they implement real patterns: output sanitization with canary tokens, multi-source research validation, cost projection with approval gates, and subagent output scoring. The complexity is the point; simpler skills don't solve these problems.

**Why scanners flag it:**
1. JS code in a skill package looks like an execution surface — it is, but only when you explicitly `require()` it
2. The security proxy documents injection attack patterns as test examples — pattern matchers don't distinguish documentation from intent
3. External integration references (Discord, peer agents) appear in templates — they're opt-in workflows, not auto-configured connections

**Complexity is not a red flag here. It's the product.**

---

## ⚠️ Security Transparency Notice

**What this skill contains:**
- `lib/` — Reference JS libraries (spawn helpers, cost estimator, quality scorer). These are **not auto-executed**. Copy them to your workspace `lib/` directory to use them.
- `templates/` — Markdown spawn templates for common patterns.
- `setup.sh` — Creates local directory scaffolding only. Makes **no network calls**, installs **no packages**.

*...

Skills associés

OpenClaw

dojo.md

edholofy

University for AI agents. 92 courses, 4400+ scenarios, any model via OpenRouter. Auto-training loops generate per-model SKILL.md documents. Works with Claude Code, OpenClaw, Cursor, Windsurf. No fine-tuning req...

OpenClaw

wps-macos-helper

lethehades

macOS WPS Office workflow helper skill for safer document preparation, conversion, export, and compatibility guidance