From clayworks-lite
Nudge the user with time-based reminders (stopping times, meetings, break suggestions). Surfaces via UserPromptSubmit hook -- requires human interaction to fire. NOT for process monitoring or job polling -- use `sleep` in Bash for that.
How this skill is triggered — by the user, by Claude, or both
Slash command
/clayworks-lite:clayworks-lite-nudgeThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Human-facing reminder system for managing focus and pacing. Nudges are stored in a local SQLite database and surface via a UserPromptSubmit hook on the next prompt the user sends after the nudge is due.
Human-facing reminder system for managing focus and pacing. Nudges are stored in a local SQLite database and surface via a UserPromptSubmit hook on the next prompt the user sends after the nudge is due.
Proactively set nudges when:
Do NOT use Nudge for:
~/.claude/projects/<project>/memory/MEMORY.md for facts)sleep <seconds> in Bash for inline blocking, or background tasks for non-blocking.python3 ~/.claude/skills/clayworks-lite-nudge/scripts/add_alert.py "<time>" "<message>"
Time formats:
| Format | Example | Meaning |
|---|---|---|
HH:MM | 17:00 | Today at 5 PM |
YYYY-MM-DD HH:MM | 2026-06-01 09:30 | Specific datetime |
+Nm | +30m | 30 minutes from now |
+Nh | +2h | 2 hours from now |
When a nudge has fired and been addressed, dismiss it so it doesn't repeat:
python3 ~/.claude/skills/clayworks-lite-nudge/scripts/ack_alert.py <id>
sqlite3 ~/.claude/skills/clayworks-lite-nudge/scripts/alerts.db \
"SELECT id, due_at, message FROM alerts WHERE acknowledged = 0 ORDER BY due_at"
Messages are notes-to-self for Claude. The format that's worked best:
<reason> - <action to take>
User asked to stop at 11 PM - wrap up current work, suggest breakStandup in 30m - remind user to prep notes2 hours on debugging session - check if stuck, suggest stepping awayDeployment window opens at 14:00 - remind user to run deploy scriptThe reason gives Claude context for why the nudge was set; the action tells Claude what to do when it fires. Without both, Claude has to reconstruct intent from a one-word message, which fails often.
Due nudges appear in a system-reminder on the next prompt submission after their due_at time has passed. When Claude sees an alert in the system-reminder:
ack_alert.py so it doesn't fire on every subsequent promptThis skill ships the SQL store and the helper scripts. For nudges to fire, you need a UserPromptSubmit hook configured in ~/.claude/settings.json:
{
"hooks": {
"UserPromptSubmit": [
{
"hooks": [
{
"type": "command",
"command": "python3 ~/.claude/skills/clayworks-lite-nudge/scripts/check_alerts.py",
"timeout": 5
}
]
}
]
}
}
The hook runs on every prompt submission, queries the SQLite for due+unacknowledged alerts, and prints them. Claude Code surfaces the printed text as a system-reminder.
For the broader UserPromptSubmit contract — full payload shape, exit behavior, common patterns beyond the Nudge use case — see hooks/examples/userpromptsubmit.sh in the LITE repo. The example is annotated and a good starting point for chaining multiple effects (Nudge + a freshness gate + context injection, etc.).
If you already have UserPromptSubmit hooks, add this entry to the existing hooks array — don't replace the block.
CREATE TABLE alerts (
id INTEGER PRIMARY KEY AUTOINCREMENT,
due_at TEXT NOT NULL, -- "YYYY-MM-DD HH:MM"
message TEXT NOT NULL, -- reason - action
created_at TEXT DEFAULT CURRENT_TIMESTAMP,
acknowledged INTEGER DEFAULT 0 -- 0 = pending, 1 = done
)
The DB file (alerts.db) is created in the scripts/ directory on first use. It's gitignored — your personal alert history never leaves your machine.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Applies a firm's KYC/AML rules grid to parsed onboarding records: assigns risk rating, checks required documents, outputs rule outcomes with citations, and routes for escalation.
Generates daily or weekly digests of activity from connected sources (chat, email, docs, tasks, CRM), highlighting action items, decisions, mentions, and project updates.
npx claudepluginhub clayboicardi/clayworks-lite --plugin clayworks-lite