Proactivity (Proactive Agent)

Maintain durable memory and session state for proactive task management.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/EvezArt/evez666-advancement --skill proactivity-proactive-agent-evezart
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Proactivity (Proactive Agent)
Source: https://github.com/EvezArt/evez666-advancement/tree/main/skills/proactivity
Command: npx skills add https://github.com/EvezArt/evez666-advancement --skill proactivity-proactive-agent-evezart

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Proactivity automates proactive task management by maintaining durable memory, session state, and follow-through loops to keep work moving and reduce context drift.

Core Features & Use Cases

  • Durable local memory at ~/proactivity/ to persist boundaries and activation preferences.
  • Session-state tracking to capture current objective, blockers, and next useful move.
  • Heartbeat checks to surface stale blockers and promised follow-ups with minimal noise.
  • Recoverable task flow that can reconstruct recent work after interruptions and long-running tasks.
  • Safe, user-driven tool use with explicit approval required for external actions.
  • Use cases span ongoing personal productivity and team workflows requiring proactive follow-through.

Quick Start

Initialize local proactive state in ~/proactivity (memory, session-state, and heartbeat) and begin each interaction by leaving a concrete next move.

Frequently Asked Questions about Proactivity (Proactive Agent)

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

FAQPage Schema
How do I maintain task context and recover work after interruptions in a long-running workflow?

Proactive task management maintains durable memory and session state tracking to reconstruct recent work after interruptions, capturing current objectives and blockers to keep long-running workflows moving.

What is a heartbeat check for task management and how does it surface blockers?

A heartbeat check for task management periodically surfaces stale blockers and promised follow-ups with minimal noise, ensuring stalled items in long-running workflows are flagged for review and recovery.

How do I set up durable memory for an agent to persist boundaries and activation preferences?

Initialize local proactive state in ~/proactivity/ to create durable memory that persists boundaries and activation preferences, allowing the agent to maintain consistent behavior across sessions.

Can I automate proactive follow-through without the agent executing external actions automatically?

Yes, proactive follow-through supports safe, user-driven tool use where explicit approval is required for external actions, ensuring boundary-aware decisions are enforced during automated task management.

What is the best way to prevent context drift in context-rich, long-running automation tasks?

Preventing context drift in long-running automation requires session-state tracking and follow-through loops that capture the next useful move, ensuring the workflow maintains its original objective.

When should I not use a proactive agent for task management?

You should avoid proactive task management for short, single-step tasks that do not require context-rich workflows, as the overhead of durable memory and heartbeat checks provides no recovery value for trivial operations.