update

Updates existing commitments in a knowledge base when users report progress, stalls, or abandonment.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping a personal commitment tracker accurate requires translating casual progress reports ("I did that", "push it to next week") into precise, schema-valid updates β€” and doing so without losing the knowledge those reports carry or letting completed items linger forever. ## Core Features & Use Cases - Commitment Matching: Finds the open action the user means by querying the commitments base, asking for clarification when genuinely ambiguous rather than guessing. - Status Transitions: Applies completion, start, waiting, rescheduling, and abandonment updates via kb set, including expires on completion so done items do not live forever. - Knowledge Routing: Captures facts reported alongside progress (e.g., "they want a pilot in Q4") into the user's knowledge base with an explicit --base, so the information outlives the action. - Use Case: A user says "finished the CFP talk, and the organizers want a workshop version too" β€” the skill marks the action done with an expiry date and captures the workshop request into the knowledge base. ## Quick Start Tell your agent "I finished writing the CFP, and they asked for a Q4 pilot" and it will update the matching commitment and route the new fact to your knowledge base.

Frequently Asked Questions about update

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

FAQPage Schema
How do I update a commitment when I report progress to my agent?β–Ό

Report progress naturally, such as "I did that" or "push that to next week". The skill finds the matching open action with kb find, then applies the change with kb set, which validates against the base schema and commits with attribution.

How does the skill handle ambiguous commitment matches?β–Ό

When a report genuinely matches two open actions, the skill asks which one you meant rather than guessing. Guessing would write the wrong page, which is worse than one short clarifying question.

Why does completing an action also set an expires date?β–Ό

The expires field is the only lifetime rule kb has, so a done action without one lives forever. Setting expires to today plus the retention window keeps the commitment list from becoming a graveyard of finished items.

What happens to facts mentioned alongside a progress report?β–Ό

Facts like "they want a pilot in Q4" are captured to the knowledge base with kb capture and an explicit --base flag. This ensures the knowledge outlives the action page after its expires date fires.

When should I not use this skill?β–Ό

Do not use it to file a new commitment β€” that is handled by the capture skill β€” or to find time for a commitment, which belongs to scheduling. If no open action matches the report, the skill hands off to capture instead of inventing a page.