openmates:daily-meeting

Orchestrate an interactive daily standup by aggregating repository, test, health, and Linear data.

43|2|Updated Jan 25, 2024
One-click install
npx skills add https://github.com/glowingkitty/OpenMates --skill openmates-daily-meeting
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openmates:daily-meeting
Source: https://github.com/glowingkitty/OpenMates/tree/main/.claude/skills/daily-meeting
Command: npx skills add https://github.com/glowingkitty/OpenMates --skill openmates-daily-meeting

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps you run a consistent daily standup by automatically collecting recent engineering, test, system health, inspirations, compliance, and Linear task context—so you can decide priorities without manually hunting for information.

Core Features & Use Cases

  • Step-by-step daily standup flow: Prompts for interactive decisions (not a report dump), guiding you through yesterday’s review, health checks, inspirations, legal/compliance findings, and priority selection.
  • Operational data gathering with resilience: Pulls from multiple local services and repositories (Git logs, test results, OpenObserve logs, server stats, issue lists, coverage, smoke tests, inspiration audit, prior meeting summaries) while recording unavailable sources instead of failing the whole meeting.
  • Actionable updates and tracking: Applies status cleanup, updates Linear labels for daily priorities, adjusts milestone planning via Linear, and writes a persistent state and meeting summary for continuity.

Quick Start

Run the openmates:daily-meeting Skill with no arguments to conduct the full interactive standup and then confirm the priorities it proposes.

Frequently Asked Questions about openmates:daily-meeting

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

FAQPage Schema
How do I run a daily standup with automated engineering workflow and test results context?

To run a daily standup with engineering workflow context, you can initiate an interactive flow that aggregates Git logs, test results, and Linear tasks. This guides you step-by-step through health checks and priority selection instead of manually gathering data.

What is the best way to track Linear tasks and system health during a daily standup?

Tracking Linear tasks and system health during a daily standup involves aggregating repository activity, OpenObserve logs, and issue lists into a single flow. This allows you to apply status cleanup and update Linear labels for daily priorities directly.

Can I conduct a daily standup if some local services or repository data sources are unavailable?

You can conduct a daily standup even when local services are unavailable because the system uses safe parallel data collection with graceful degradation. It records unavailable sources instead of failing the entire meeting flow.

How do I include compliance scanning and prior meeting summaries in my daily operational planning?

Including compliance scanning and prior meeting summaries in daily operational planning requires aggregating legal scans and previous artifacts alongside system health data. This evidence-backed approach ensures consistent momentum tracking and informed priority setting.

Does the daily standup flow support updating Linear milestones and persisting meeting summaries?

The daily standup flow supports updating Linear milestones and persisting meeting summaries by applying optional label adjustments and writing a persistent state. This ensures continuity and actionable tracking across your engineering workflow.