One-click install
npx skills add https://github.com/ankitjh4/skill-builder --skill midday-checkin-ankitjh4
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: midday-checkin
Source: https://github.com/ankitjh4/skill-builder/tree/main/midday-checkin
Command: npx skills add https://github.com/ankitjh4/skill-builder --skill midday-checkin-ankitjh4

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires duckdb, and includes scripts (resource) components.

What problem does it solve?

It prevents afternoon from starting cold by detecting task drift and stale work, checking meeting records for gaps, and pre-loading relevant context so the user only gets nudged when something truly matters.

Core Features & Use Cases

  • Pattern detection with delta state: Scans DuckDB task data and recent meeting records, using a persisted state file to surface only new or changed findings.
  • Context warming for upcoming meetings: Pulls today’s remaining Google Calendar events and correlates external participants with prior meeting records and open threads.
  • AI continuity checkpoint: Creates a lightweight midday memory breadcrumb (when Supermemory is available) to keep the afternoon aligned with earlier activity.
  • Threshold-based delivery: Texts only for high-severity issues (e.g., 7+ days overdue), time-sensitive upcoming meetings, or genuinely new, important changes—otherwise stays silent.

Quick Start

Ask your scheduled agent to run midday-checkin at noon in the user’s timezone to deliver any urgent drift updates and pre-warm context for the afternoon.

Frequently Asked Questions about midday-checkin

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

FAQPage Schema
How do I detect task drift in a DuckDB database for a midday check-in?

Detect task drift by running a scheduled patterns script that scans your DuckDB tasks database and uses persisted delta state to surface only new or changed findings. This midday check-in identifies stale work before your afternoon starts.

How does context warming work for upcoming Google Calendar meetings?

Context warming pulls your remaining Google Calendar events and correlates external participants with prior meeting markdown records and open threads. This pre-loads relevant context for a proactive afternoon briefing.

What is the best way to stop starting my afternoon cold without getting too many notifications?

Use threshold-based delivery to stop starting cold. The midday check-in texts you only for high-severity issues like 7+ days overdue tasks or time-sensitive meetings, otherwise staying completely silent.

Can I use meeting record markdown files to check for gaps in my workflow?

Yes, you can use meeting record markdown files to check for gaps. The Skill reads recent meeting markdown files alongside DuckDB task data to detect drift and stale work during your midday review.

Do I need Supermemory to create an AI continuity checkpoint for my tasks?

No, Supermemory is optional. When available, it creates a lightweight midday memory breadcrumb to keep your afternoon aligned with earlier activity, but the core task monitoring works without it.

What are the limitations of using scheduled automation for midday task monitoring?

Limitations include requiring a root SKILL.md file and a DuckDB tasks database to function. The scheduled automation also depends on conditional severity thresholds, meaning it stays silent if no high-severity drift is detected.