work-tracker

Answers questions about personal commitments by querying a knowledge base of tracked actions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? It gives you a single place to ask what you should be working on, what is overdue, and what you are waiting on, by querying a private commitments base instead of scattering tasks across chat history. ## Core Features & Use Cases - Status-based queries: Answers questions about commitments using four statuses (next, waiting, someday, done) via kb find queries over the commitments base. - Skill routing: Directs requests to the right narrower skill — capture for filing new commitments, schedule for finding time, update for progress reports, and the steward agent for backlog reviews. - Authority rules: Defines what the agent may change freely (estimates, blocks, status on progress reports), what requires asking (dropping commitments, changing due dates, nudging others), and what is never allowed (rewriting the original commitment text). - Use Case: You ask "what am I waiting on?" and the skill runs kb --base commitments find --where status=waiting to list every commitment blocked on another person. ## Quick Start Ask the agent what you should be working on this week or what commitments are currently overdue.

Frequently Asked Questions about work-tracker

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

FAQPage Schema
How do I check what tasks are overdue in my commitments base?▼

Run a kb find query filtering by status and due date, such as `kb --base commitments find --where status=next --where 'due<today+7d'`. Quote every comparison because a bare `<` is interpreted as shell redirection.

What is the difference between next, waiting, someday, and done statuses?▼

next means you will do it and it usually has an estimate or block; waiting means someone else owes an answer named in waiting_on; someday means maybe never, which is legitimate; done means finished or abandoned and carries an expires date for pruning.

When should a request be filed as a commitment versus just answered?▼

File it only when the user commits to something, like "I need to find time to write the CFP". A direct instruction like "write the CFP" is executed, not filed, and knowledge from others goes to the knowledge base, not the tracker.

Can the agent change a due date or drop a commitment on its own?▼

No. Dropping a commitment, changing a due date, or nudging another person always requires asking the user first. The agent may freely set estimates, blocks, projects, and update status on a progress report the user just gave.

What happens to completed commitments in the tracker?▼

Completed commitments get status done plus an expires date, and `kb prune` deletes pages whose expires has passed. Because action pages never hold the only copy of anything, pruning loses no knowledge.