steward

Maintains a commitments backlog by detecting overdue, stalled, and expired items via kb queries.

3|1|Updated Jul 17, 2026
One-click install
npx skills add https://github.com/AlmogBaku/aos --skill steward-almogbaku
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: steward
Source: https://github.com/AlmogBaku/aos/tree/main/capabilities/work-tracker/skills/steward
Command: npx skills add https://github.com/AlmogBaku/aos --skill steward-almogbaku

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Personal backlogs silently rot: commitments go overdue, waiting items stall, someday items go cold, and rescheduled blocks slip without anyone noticing. This Skill runs an unattended maintenance pass over an existing commitments knowledge base to keep it honest. ## Core Features & Use Cases - Five-signal detection: Queries the commitments base for overdue items, about-to-expire entries, stalled waiting items, passed blocks, and cold someday items, plus a backstop query for unscheduled next actions. - Silent vs. ask policy: Adjusts its own bookkeeping silently (extending expirations, rescheduling self-created blocks) while escalating user-facing decisions like dropping commitments, changing due dates, or nudging people. - Attributed writes and close-out: Runs as a named agent identity so every write is attributable, prunes completed pages, rebuilds the index, and emits a short report only when something needs attention. - Use Case: A nightly cron fires the steward, which finds a commitment rescheduled three times and asks the user whether to keep it or move it to someday, while silently extending an expiring reminder. ## Quick Start Ask your agent to run the steward pass to review your backlog and report anything overdue, stalled, or slipping.

Frequently Asked Questions about steward

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

FAQPage Schema
How do I review my backlog for overdue or stalled commitments?▼

Run the steward pass, which queries the commitments base for five signals: overdue items, about-to-expire entries, stalled waiting items, passed blocks, and cold someday items. It reschedules or extends silently where allowed and asks you about anything requiring your decision.

What changes can the steward make without asking the user?▼

It silently extends expiration dates, records stalls, and reschedules blocks it created itself. It must ask before dropping a commitment, changing a due date, or nudging a person on the user's behalf, since those affect promises the user made.

Why does the steward run as a separate agent identity?▼

Running as agent:steward makes every unattended write attributable to the steward rather than the user's interactive agent. The weekly grants audit checks the committer of each write, so attribution is the enforcement substrate.

Why does kb prune require an index rebuild afterward?▼

kb prune deletes the page but leaves its index.md entry behind, creating dead entries that surface as index drift. Running kb index rebuild after pruning is part of the close-out, not an optional tidy.

When does the steward escalate a slipping commitment?▼

It escalates on the pattern, not the event: one slip is normal, but when a commitment's slipped counter reaches the threshold (default 3), it asks whether to keep the commitment or move it to someday.