run-once

Dispatch ad-hoc debugging tasks to aweek agents with per-agent locks and execution logs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually dispatch an ad-hoc debugging task to aweek agents. The task follows the exact same execution path as a heartbeat tick, including per-agent lock handling, per-agent .env loading, and a full activity/execution log, but does not affect the weekly plan.

Core Features & Use Cases

  • Deterministic ad-hoc runs that validate agent behavior without altering the weekly schedule.
  • End-to-end execution trace including per-agent environment, lock status, and comprehensive activity logs for debugging.

Quick Start

Invoke this skill to dispatch a single ad-hoc task to a chosen agent, providing a prompt, and review the resulting execution log.

Frequently Asked Questions about run-once

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

FAQPage Schema
How do I run an ad-hoc debugging task on an agent without affecting the scheduled workflow?▼

To run an ad-hoc debugging task without altering the weekly plan, dispatch a single task to a chosen agent with an explicit prompt. The execution follows the exact heartbeat tick path, including per-agent lock handling and environment loading, keeping the schedule untouched.

Can I trace execution logs for a specific agent to validate its behavior?▼

Yes, you can trace execution logs for a specific agent to validate its behavior. Dispatching an ad-hoc task generates comprehensive activity logs, per-agent lock status, and environment details, returning structured results including finalStatus and duration.

What is the best way to probe an agent dispatch workflow without modifying the weekly plan?▼

The best way to probe a dispatch workflow without modifying the weekly plan is to execute a deterministic ad-hoc run. This dispatches a single task following the heartbeat execution path, ensuring the weekly schedule remains completely unaffected.

Does dispatching ad-hoc tasks require explicit confirmation for destructive operations?▼

Yes, dispatching ad-hoc tasks requires explicit confirmation for destructive operations. The execution enforces a destructive-operation confirmation gate and requires explicit prompt and agent selection before returning structured results and optional dashboard links.

Why do I need per-agent environment loading when debugging an automated workflow?▼

Per-agent environment loading is needed when debugging an automated workflow to ensure the ad-hoc task executes under the exact same conditions as a heartbeat tick. This includes per-agent locks and .env files, producing accurate end-to-end execution traces.