Runbear
Official@runbear-io
Offers lifecycle management and configuration governance for distributed agentic task environments through structured manifest orchestration and project initialization.
Agent Skills by Runbear
Showing 12 vetted skills indexed across 1 GitHub repositories.
calendar
Render an agent's weekly plan into a markdown calendar grid with numbered tasks.
run-once
Dispatch ad-hoc debugging tasks to aweek agents with per-agent locks and execution logs.
config
Inspect and update aweek configuration in .aweek/config.json with validation.
plan
Edit agent plan.md files and manage weekly task approvals.
slack-init
Provision a Slack app and persist credentials to project config.
teardown
Remove aweek heartbeat and .aweek/ data directory with confirmations.
delegate-task
Delegate tasks between agents through an asynchronous inbox queue.
setup
Automate aweek project initialization with filesystem layout and heartbeat scheduling.
manage
Manage aweek agents through lifecycle actions with schema validation.
hire
Create aweek subagent manifests and plan.md files via guided interview.
query
Filter the aweek agent roster by role, keyword, status, and budget to return matching agent slugs.
summary
Render a read-only dashboard of aweek agents with goals, tasks, budget, and status.
Frequently Asked Questions About Runbear
FAQPage SchemaWhat specific tasks can be managed using Runbear?▼
Runbear enables the creation, configuration, and lifecycle management of subagent manifests. Users can delegate tasks between agents, render weekly task grids in markdown, manage budget allocations, and monitor agent status through read-only dashboards and heartbeat scheduling.
Which personas benefit most from Runbear?▼
Runbear is designed for systems engineers and technical leads managing distributed agentic architectures. It is ideal for those requiring strict schema validation, project-level configuration governance, and structured task delegation across complex, multi-agent environments.
What are the prerequisites for initializing a Runbear project?▼
Initialization requires a local filesystem environment capable of hosting a .aweek directory. Users must have the ability to provision Slack applications for credential persistence and maintain write access to project configuration files for heartbeat and schema validation.