Aggregate GitHub tasks, emails, SLA records, and vault content into a status briefing.
npx skills add https://github.com/sonthanh/brain-os-plugin --skill status-sonthanh
Please help me install this Agent Skill. Skill: status Source: https://github.com/sonthanh/brain-os-plugin/tree/main/skills/status Command: npx skills add https://github.com/sonthanh/brain-os-plugin --skill status-sonthanh
People struggle to keep track of ongoing work across tasks, emails, handovers, and priorities; this Skill assembles a concise, up-to-date briefing from a cached data source to save time and reduce context-switching.
Ask /status to view today's briefing; it will read from the cache and regenerate only when the data is stale.
High-intent search queries and answers about installing and using this skill.
A consolidated status briefing aggregates GitHub tasks, emails, SLA records, and vault content into a single prioritized snapshot. It surfaces pending handovers, blocked tasks, and critical breaches to reduce context-switching and enable quick daily planning.
The cache-first workflow uses lazy regeneration and a staleness gate to keep briefings current. It reads from a cached data source and only triggers updates to pull fresh data when the cache age or underlying inputs indicate staleness.
Yes, you can track pending handovers and blocked tasks in a single daily work status snapshot. The briefing presents structured sections for tasks, handovers, email status, and SLA ledgers, enabling quick daily planning.
Monitoring SLA breaches and research signals across platforms is best handled by a cache-driven status briefing. It consolidates GitHub tasks, emails, SLA data, and vault content into a concise snapshot of what needs attention now.
No, you do not need to manually trigger cache updates for recent GitHub tasks and email status. The briefing enforces lazy regeneration, automatically checking for staleness and updating the cache only when inputs or cache age require it.
A status briefing might show stale data if the staleness gate has not detected sufficient input changes to trigger lazy regeneration. The cache-first workflow prioritizes efficiency by only pulling fresh data when the cache age indicates staleness.
gnektScan email inboxes, score priority, classify, and save relevant emails to Obsidian.
nirholasMonitor system health, track errors, and trigger alerts across distributed services.
aggelosChatziioannouMonitor sub-agent activity and announce task lifecycle status updates.
Happy-Technologies-LLCAggregate ITSM incident work notes, state changes, assignments, and SLA data into a narrative.
