schedule-status

Reports repository schedules, recent run outcomes, and published artifacts from the host scheduler.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When unattended scheduled work runs overnight, it is hard to know whether a routine fired, why one failed, or what it published. This Skill inspects the repository's configured schedules and their recent runs so you can answer those questions without digging through the host's scheduler pages. ## Core Features & Use Cases - Schedule inventory: Lists the schedules selected in .devbook/config.json alongside what the live scheduler actually knows, flagging entries that are not scheduled or unmanaged. - Run diagnostics: Retrieves run history and the log of a failed or parked run, quoting the line where things went wrong. - Publication cross-check: Verifies what a run published via gh — an open pull request on schedule/<name>/ or an issue labelled schedule-report. - Use Case: You arrive Monday morning and ask why the nightly review routine produced nothing; the Skill shows the schedule's enabled state, its last failed run, and the failing log line. ## Quick Start Ask the assistant to show this repository's schedules and how their recent runs went, including why the last failed run stopped.

Frequently Asked Questions about schedule-status

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

FAQPage Schema
How do I check whether a scheduled run fired in my repository?▼

Ask for the schedule status: the Skill lists each schedule with its cron, enabled state, and last run outcome. Note that an empty run list is not proof a schedule never fired, since a fire refused before a session existed leaves no run behind.

How to find out why a scheduled automation failed?▼

The Skill retrieves the log of the most recent failed or parked run and reports one line from the log at the point the run went wrong, alongside the schedule's cadence and enabled state.

What does a scheduled run publish when it completes?▼

A run typically publishes an open pull request on a schedule/<name>/ branch or an open issue labelled schedule-report. The Skill cross-checks these with the GitHub CLI and reports them as links in its summary table.

Why does a schedule in my config not appear in the scheduler?▼

An entry in the .devbook/config.json stamp that the scheduler does not know is reported as not scheduled, meaning you should run delivery-schedule:update. A scheduled entry missing from the stamp is reported as unmanaged.

Can this Skill modify or trigger schedules?▼

No, it is strictly read-only. It resolves the repository, reads the schedule selection, lists runs, and fetches logs, but never creates, updates, or triggers schedules.