القائمة
Manage and run background schedule triggers. Run `bunx smithers-orchestrator cron --help` for usage details.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | smithers-cron |
| description | Manage and run background schedule triggers. Run `bunx smithers-orchestrator cron --help` for usage details. |
| requires_bin | bunx |
| command | bunx smithers-orchestrator cron |
Register a new workflow cron schedule.
| Name | Type | Required | Description |
|---|---|---|---|
pattern | string | yes | Cron execution pattern (e.g. '0 * * * *') |
workflowPath | string | yes | Path or ID of the workflow to schedule |
List all registered background cron schedules.
Delete an existing cron schedule by ID.
| Name | Type | Required | Description |
|---|---|---|---|
cronId | string | yes | Cron ID to delete |
Start the background scheduler loop in the current terminal.
Create structured plans for multi-step tasks -- software features, research workflows, events, study plans, or any goal that benefits from breakdown. Also deepens existing plans with interactive sub-agent review. Use when the user says 'plan this', 'create a plan', 'how should we build', 'break this down', or when a brainstorm doc is ready for planning. Use 'deepen the plan' or 'deepening pass' for the deepening flow. For exploratory requests, prefer ce-brainstorm first.
Select the right Bead to work on using Beads robot-mode CLI evidence. Use when asked what Bead to pick next, which local issue is highest leverage, which blocker to clear, or how to choose work from a Beads graph. Produces a validator-checked .laguna/bead-selection.json artifact grounded in bv/br robot output, never the interactive bv TUI.
Inventory the top level of a workspace and write .laguna/workspace-inventory.json. Use when an agent or user needs a quick orientation snapshot: what top-level entries exist, which are files vs directories, and how many files each directory contains. Triggers on requests like "what's at the top of this workspace", "give me a lay of the land", "list the top-level structure", "how many files are in each directory", or any task whose first step is understanding what is present without doing deep analysis. Every claim (entry names, kinds, file counts, total) is mechanically checkable against the real filesystem tree.
Inspect and register subscriptions and api keys. Run `bunx smithers-orchestrator agents --help` for usage details.
List and manage durable alert instances. Run `bunx smithers-orchestrator alerts --help` for usage details.
Approve a paused approval gate. Auto-detects the pending node if only one exists. Run `bunx smithers-orchestrator approve --help` for usage details.
