network-ai_skill

This skill coordinates multi-agent workflows by decomposing tasks, delegating work, validating results on a shared blackboard, and synthesizing final outputs
  • Python

2.5k

GitHub Stars

11

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill network-ai

  • _meta.json3.4 KB
  • ADOPTERS.md1.3 KB
  • ARCHITECTURE.md10.9 KB
  • AUDIT_LOG_SCHEMA.md6.6 KB
  • AWESOME_LISTS.md4.7 KB
  • BENCHMARKS.md6.7 KB
  • ENTERPRISE.md6.3 KB
  • INTEGRATION_GUIDE.md20.0 KB
  • requirements.txt483 B
  • SHOW_HN.md3.9 KB
  • SKILL.md21.5 KB

Overview

This skill implements a local, sandboxed multi-agent swarm orchestrator for complex workflows. It decomposes tasks into three specialized agents, manages a shared blackboard for state, and enforces permission walls and budget checks before sensitive operations. All execution is local and audit-logged for compliance.

How this skill works

On receipt of a complex request, the orchestrator decomposes it into exactly three sub-tasks (DATA, VERIFY, RECOMMEND) and delegates each to a specialized agent using a budget-aware handoff interceptor. Every sessions_send is gated by a handoff check and permission scripts; agents write results to a local blackboard file. Before committing results, the orchestrator runs validation, supervisor review, and only writes a final approved state to the blackboard and audit log.

When to use it

  • Coordinating parallel analysis, risk checks, and strategic recommendations for a single business problem
  • Delegating work to specialized agent sessions (data_analyst, risk_assessor, strategy_advisor)
  • Accessing sensitive systems (SAP_API, FINANCIAL_API) where permission checks and tokens are required
  • Maintaining a persistent shared state among agents via a local blackboard
  • Running budgeted workflows where token and cost limits must be enforced

Best practices

  • Always initialize a task budget before delegation and check remaining budget before each handoff
  • Run the handoff interceptor script before every sessions_send and abort if blocked
  • Limit permission scopes and include clear justifications when requesting resource access
  • Use the blackboard for explicit read/write coordination and clean up TTL entries regularly
  • Validate agent results and run supervisor-review before committing final outputs to the blackboard
  • Log every sensitive action to the audit_log.jsonl to preserve an audit trail

Example use cases

  • Q4 financial analysis: extract metrics, run compliance checks, and produce board-ready recommendations
  • Data export gating: request permission, anonymize PII, and write approved export to a local file
  • Parallel risk assessment: run data processing, compliance verification, and strategy synthesis concurrently
  • Incident investigation: coordinate a data pull, verify integrity, and recommend remediation steps

FAQ

The orchestrator always decomposes a complex request into exactly three sub-tasks: DATA (data_analyst), VERIFY (risk_assessor), and RECOMMEND (strategy_advisor).

What happens if the handoff interceptor denies a sessions_send?

If the interceptor denies the handoff, the orchestrator stops, reports the blocked reason, and suggests reducing scope or aborting the task. No sessions_send is performed.

Where is shared state stored?

Shared state and intermediate outputs are stored in a local markdown blackboard file (swarm-blackboard.md) and managed via read/write scripts with TTL support.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
network-ai skill by openclaw/skills | VeilStrat