10-of-my-most-popular-text-to-image-series-prompts-78b0897e
generate a bunch of images, then you curate the results to handpick the best ones
A 5-phase framework for reliable AI-to-AI task delegation, inspired by Google DeepMind's "Intelligent AI Delegation" paper (arXiv 2602.11865). Includes task tracking, sub-agent performance logging, automated verification, fallback chains, and multi-axis task scoring.
Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.
SkillHub CLI
skillhub install hogpile/intelligent-delegationInspect the source and compatibility requirements, then follow its installation steps.
Give your agent the source link and ask it to inspect instructions and dependencies before explaining the installation steps.
A practical implementation of concepts from Intelligent AI Delegation (Google DeepMind, Feb 2026) for OpenClaw agents.
When AI agents delegate tasks to sub-agents, common failure modes include:
Problem: "I'll ping you when it's done" → never happens.
Solution:
TASKS.md file to log all background workHEARTBEAT.md to check TASKS.md firstTASKS.md template:
# Active Tasks
### [TASK-ID] Description
- **Status:** RUNNING | COMPLETED | FAILED
- **Started:** ISO timestamp
- **Type:** subagent | background_exec
- **Session/Process:** identifier
- **Expected Done:** timestamp or duration
- **Check Cron:** cron job ID
- **Result:** (filled on completion)
Key rule: Never promise to follow up without scheduling a mechanism to wake yourself up.
Problem: No memory of which agents succeed or fail at which tasks.
Solution: Create memory/agent-performance.md to track:
After every delegation:
Before every delegation:
Example entry:
#### 2026-...
These signals come from indexed source analysis and may lag behind changes. Check the current source files.
# Intelligent Delegation Framework A practical implementation of concepts from [Intelligent AI Delegation](https://arxiv.org/abs/2602.11865) (Google DeepMind, Feb 2026) for OpenClaw agents. ## The Problem When AI agents delegate tasks to sub-agents, common failure modes include: - **Lost tasks** — background work completes silently, no follow-up - **Blind trust** — passing through sub-agent output without verification - **No learning** — repeating the same delegation mistakes - **Brittle failure** — one error kills the whole workflow - **Gut-feel routing** — no systematic way to choose which agent handles what ## The Solution: 5 Phases ### Phase 1: Task Tracking & Scheduled Checks **Problem:** "I'll ping you when it's done" → never happens. **Solution:** 1. Create a `TASKS.md` file to log all background work 2. For every background task, schedule a one-shot cron job to check on completion 3. Update your `HEARTBEAT.md` to check `TASKS.md` first **TASKS.md template:** ```markdown # Active Tasks ### [TASK-ID] Description - **Status:** RUNNING | COMPLETED | FAILED - **Started:** ISO timestamp - **Type:** subagent | background_exec - **Session/Process:** identifier - **Expected Done:** timestamp or duration - **Check Cron:** cron job ID - **Result:** (filled on completion) ``` **Key rule:** Never promise to follow up without scheduling a mechanism to wake yourself up. --- ### Phase 2: Sub-Agent Performance Tracking **Problem:** No memory of which agents succeed or fail at which tasks. **Solution:** Create `memory/agent-performance.md` to track: - Success rate per agent - Quality scores (1-5) per task - Known failure modes - "Best for" / "Avoid for" heuristics **After every delegation:** 1. Log the outcome (success/partial/failed/crashed) 2. Note runtime and token cost 3. Record lessons learned **Before every delegation:** 1. Check if this agent has failed on similar tasks 2. Consult the "decision heuristics" section Example entry: ```markdown #### 2026-...
generate a bunch of images, then you curate the results to handpick the best ones
generate a bunch of images, then you curate the results to handpick the best ones
Productivity system based on Maya calendar with 13 natural tones for project management and personal development
Set up and use 1Password CLI (op). Use when installing the CLI, enabling desktop app integration, signing in (single or multi-account), or reading/injecting/running secrets via op.