db-status

Generate a status report for scheduled database cron batch scripts.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/sandsmichael/marketlab --skill db-status-sandsmichael
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: db-status
Source: https://github.com/sandsmichael/marketlab/tree/main/.openclaw/skills/db-status
Command: npx skills add https://github.com/sandsmichael/marketlab --skill db-status-sandsmichael

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a clear overview of the operational status of your data ingestion batch jobs, ensuring data freshness and identifying potential failures.

Core Features & Use Cases

  • Job Status Reporting: Displays the last run time, maximum data date, and update status for each scheduled script.
  • Error Identification: Highlights jobs that are stale or have encountered errors, facilitating prompt troubleshooting.
  • Use Case: A data engineer can quickly check if all daily data pipelines have successfully updated the database for the previous day, and if not, see the specific error messages.

Quick Start

Generate a status report for all database batch jobs.

Frequently Asked Questions about db-status

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

FAQPage Schema
How do I check the status of scheduled database batch jobs?

To check database batch jobs, this solution generates a status report detailing job names, last execution timestamps, the maximum date of data processed, and the operational status (Updated/Stale). This is crucial for maintaining data integrity and operational awareness in data pipelines.

What is the best way to monitor data pipeline freshness for cron scripts?

Monitoring data pipeline freshness involves generating a status report for scheduled cron batch scripts that populate a database. It provides a clear overview of the operational status of your data ingestion batch jobs, ensuring data freshness and identifying potential failures.

How do I identify stale data ingestion batch jobs in a database?

Identifying stale data ingestion batch jobs is done by generating a status report that highlights jobs that are stale or have encountered errors. This facilitates prompt troubleshooting and ensures your daily data pipelines have successfully updated the database.

Can I see error messages for failed cron batch scripts in a status report?

Yes, you can see error messages for failed cron batch scripts. The status report highlights jobs that are stale or have encountered errors, allowing a data engineer to quickly check if all daily data pipelines have successfully updated and see specific error messages if not.

Does this database batch job monitoring tool require any external dependencies?

No, this database batch job monitoring tool does not require any external dependencies. It operates using basic scripts to generate a status report for scheduled cron batch scripts, ensuring data freshness without complex setup requirements.