skills.rest
JSdotNet
JSdotNetCOMMUNITY
Explore all skills by this author →
GitHub

schedule-run

Fires a repository schedule on demand and reports the resulting run.

Updated Sep 2, 2026
Search Tags:#automation#reporting#run#schedule#trigger#unattended#scheduler
One-click install
npx skills add https://github.com/JSdotNet/devbook --skill schedule-run-jsdotnet
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: schedule-run
Source: https://github.com/JSdotNet/devbook/tree/main/plugins/delivery-schedule/skills/schedule-run
Command: npx skills add https://github.com/JSdotNet/devbook --skill schedule-run-jsdotnet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Schedules normally run on their own cadence, so testing one after setup or re-running a failed one means waiting or digging through the host's scheduler page. This Skill fires a configured schedule immediately and reports the outcome. ## Core Features & Use Cases - On-Demand Execution: Resolves the host scheduler, finds the schedule by owner/repo and title, and fires it outside its cadence. - Safe Confirmation: Shows the schedule name, target skill, and what the run may open (a pull request or a schedule-report issue) before firing. - Run Reporting: Waits for the run to appear, retrieves its log, and reports the result the same way schedule-status does. - Use Case: Right after running delivery-schedule:init, fire the new schedule once to confirm it works end to end instead of waiting for its first cadence tick. ## Quick Start Run the schedule named nightly-review now and report what the run did.

Frequently Asked Questions about schedule-run

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

FAQPage Schema
How do I run a scheduled automation immediately instead of waiting?▼

Provide the schedule name and the skill resolves the host scheduler, finds the schedule by owner/repo and title, confirms with you, then fires it. It waits for the run to appear and reports the log.

How to test a schedule right after setting it up?▼

Fire it on demand immediately after running delivery-schedule:init or delivery-schedule:update. This runs the same unattended session the cadence would start, so you can verify behavior without waiting.

What happens if no scheduler tool is available in the host?▼

The skill checks the live tool list for a scheduler. If none resolves, it tells you the schedule must be fired from the host's own page, such as Routines in Claude Code or Automations in the Copilot app, and stops.

Why does a manually fired schedule stop without finishing?▼

A fired run is the same unattended session a cadence starts, so it cannot ask your session anything. Where a gate would require input, the run parks instead of completing.

What can a schedule run open when fired on demand?▼

Depending on the schedule, a run may open a pull request on a schedule/<name>/ branch or an issue labelled schedule-report. The skill shows these possibilities and waits for confirmation before firing.

Related Skills

Explore More Software Engineering Skills→
bish-xbish-x
2

cron-scheduler

Validate and register cron jobs with staggering and quiet hours.

Community
Advanced
yeaboi-aiyeaboi-ai
4

ceremonies

Inspect scheduled yeaboi ceremonies, their cadences, delivery channels, and run outcomes.

Official
Intermediate
shftwstshftwst
3

faffter-noon-concurrency-sequential

Executes the build pass sequentially, dispatching one graft build subagent at a time.

Official
Advanced
ArthTech-AIArthTech-AI

schedule-routine

Configure cloud-hosted Claude Code routines for cron, GitHub webhook, or API triggers.

Official
Advanced