taskr

Automate persistent cross-session task planning and execution for OpenClaw.

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/ISAQQSAI/SkillAttack --skill taskr-isaqqsai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: taskr
Source: https://github.com/ISAQQSAI/SkillAttack/tree/main/data/hot100skills/097_echo-of-machines_taskr
Command: npx skills add https://github.com/ISAQQSAI/SkillAttack --skill taskr-isaqqsai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Taskr solves the problem of maintaining persistent, cross-session task plans for OpenClaw, ensuring plans survive resets, are shareable across agents, and provide auditable trails.

Core Features & Use Cases

  • Hierarchical planning: break work into nested tasks before execution.
  • Persistent context: tasks, notes, and status survive session resets and context compaction.
  • Cross-agent continuity: any agent can pick up a task list from anywhere; task ownership and status travel with the task.
  • Audit trail via notes: notes attach to tasks to preserve cause, effect, and decisions across sessions.
  • Retroactive sync: task_sync records work done before Taskr activation, closing gaps in history.
  • Use Case: orchestrate multi-step workflows across agents with review before execution and a visible audit trail.

Quick Start

Initialize Taskr, create a full task list with an immediate CONTEXT note, then begin executing tasks across agents.

Frequently Asked Questions about taskr

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

FAQPage Schema
How do I maintain persistent task planning across multiple agent sessions in OpenClaw?

Persistent cross-session task planning in OpenClaw is maintained by using hierarchical task creation with context notes and status tracking, ensuring task lists and audit trails survive session resets and context compaction.

What is the best way to create an auditable trail for long-running multi-agent workflows?

An auditable trail for multi-agent workflows is created by attaching CONTEXT notes to hierarchical tasks, which preserves the cause, effect, and decisions across sessions for retroactive review.

Can I sync work completed before activating task management tools?

Yes, work completed before activation can be synced using retroactive task_sync integration, which records prior work to close gaps in history and ensure continuous cross-agent continuity.

How do I orchestrate multi-step workflows with review before execution?

Multi-step workflows are orchestrated by initializing a task plan, creating a full hierarchical task list with an immediate CONTEXT note, and then executing tasks across agents with status tracking.

Does cross-session task management work after context compaction?

Cross-session task management works after context compaction because persistent context notes, task ownership, and status travel with the task list, allowing any agent to pick up from anywhere.

Why do I need hierarchical task creation for agent orchestration?

Hierarchical task creation is needed for agent orchestration to break complex work into nested tasks before execution, enabling structured review, status tracking, and cross-agent collaboration.