example-holon

Execute holon-based tasks with bounded episodes, budgets, and tool permissions.

1|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/guardian-intelligence/apm2 --skill example-holon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: example-holon
Source: https://github.com/guardian-intelligence/apm2/tree/main/documents/skills/example-holon
Command: npx skills add https://github.com/guardian-intelligence/apm2 --skill example-holon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The holon-based task execution skill demonstrates bounded, episodic workflows by configuring stop conditions, budgets, and tool permissions to manage complex tasks.

Core Features & Use Cases

  • Bounded episodes: tasks progress through intake, execution, and state updates within defined limits.
  • Resource governance: budgets for tokens and tool calls enforce predictable usage.
  • Tool access control: per-episode tool permissions ensure safe automation.

Quick Start

Instantiate a holon with a defined config and invoke spawn_holon to begin episodic execution, providing intake data and observing TaskProgress updates until a stop condition triggers.

Frequently Asked Questions about example-holon

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce token budgets and tool permissions for complex task execution?

Bounded episodic workflows enforce token budgets and tool permissions by defining strict episode lifecycles. Tasks progress through intake, execution, and state updates while resource governance ensures predictable usage limits across iterations.

What are bounded episodes in state management and workflow orchestration?

Bounded episodes are structured task execution phases that progress through intake, execution, and state updates within defined limits. They manage complex workflows by enforcing stop conditions, budgets, and per-episode tool permissions.

How do I set up a holon task with stop conditions and execution budgets?

Instantiate a holon with a defined configuration and invoke spawn_holon to begin episodic execution. Provide intake data and observe TaskProgress updates until a stop condition triggers, enforcing budgets and tool-access governance throughout the lifecycle.

Can I control tool access permissions per episode in task execution workflows?

Per-episode tool permissions ensure safe automation by governing tool access control throughout bounded task execution. This resource governance mechanism restricts specific tool calls within each episodic lifecycle iteration.

What is the TaskRequest and TaskResult contract for bounded workflow execution?

The TaskRequest, TaskResult, and TaskProgress contract defines the structured data flow for bounded episodic workflows. It enforces stop conditions, budgets, and tool permissions while orchestrating complex task state updates across iterations.