manage

Manage aweek agents through lifecycle actions with schema validation.

11|1|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/runbear-io/aweek --skill manage-runbear-io
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: manage
Source: https://github.com/runbear-io/aweek/tree/main/skills/manage
Command: npx skills add https://github.com/runbear-io/aweek --skill manage-runbear-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

aweek's lifecycle management for agents is complex and error-prone without a unified control surface. This skill consolidates resume, top-up, pause, and delete operations into a single, validated workflow, enforcing safety gates and consistent identity handling.

Core Features & Use Cases

  • Resume a budget-paused agent to continue operation.
  • Top-up a paused agent by resetting usage and optionally adjusting the weekly budget with explicit confirmation for destructive changes.
  • Pause or stop an active agent to temporarily halt heartbeat-driven execution.
  • Delete or archive an agent with guided prompts to confirm destructive actions and to decide whether to keep or remove the subagent identity file.
  • Identity management is handled through .claude/agents/<slug>.md and should not be edited directly to avoid schema drift.

Quick Start

At invocation, choose an operation (resume, top-up, pause, delete) and select the target agent; then confirm any destructive actions when prompted.

Frequently Asked Questions about manage

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

FAQPage Schema
How do I resume a paused agent and continue its execution?

To resume a paused agent, select the resume operation from the lifecycle management workflow and choose the target agent stored under .aweek/agents or .claude/agents to restart heartbeat-driven execution.

How do I safely delete an agent without breaking subagent identity files?

Deleting an agent uses guided prompts to confirm the destructive action and lets you decide whether to keep or remove the subagent identity file in .claude/agents, preventing schema drift and accidental data loss.

Can I top up an agent budget and adjust weekly limits at the same time?

Yes, top-up operations reset agent usage and optionally adjust the weekly budget, applying explicit confirmation for destructive changes before updating the agent state through validated Node modules.

What happens if I edit agent JSON files directly outside the management module?

Direct edits to agent JSON files bypass schema validation and timestamp integrity enforced by src/skills/manage.js, risking data corruption and schema drift across the agent lifecycle state.

How do I pause an active agent to temporarily halt its scheduled operations?

Pausing an active agent temporarily halts heartbeat-driven execution by applying the pause lifecycle action, which updates the agent state safely through the centralized Node management module.

When should I archive an agent instead of deleting it completely?

Archive an agent instead of deleting when you need to retain the subagent identity file for future reference while stopping active execution, guided by confirmation prompts during the lifecycle operation.