daily-meeting-update

Gather GitHub, Jira, and Claude Code context to generate Markdown standup updates.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/albertms22/agent-toolkit --skill daily-meeting-update
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: daily-meeting-update
Source: https://github.com/albertms22/agent-toolkit/tree/main/skills/daily-meeting-update
Command: npx skills add https://github.com/albertms22/agent-toolkit --skill daily-meeting-update

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This tool automates the preparation of daily standups by gathering context from GitHub, Jira, and Claude Code history (with user consent), runs a focused interview, and outputs a clean Markdown update ready for sharing.

Core Features & Use Cases

  • Consent-based data discovery: detects integrations (Claude Code, GitHub, Jira) and prompts before pulling data.
  • Interview-first workflow: asks four questions (Yesterday, Today, Blockers, Topics) with contextual data shown during the interview.
  • Multi-repo and cross-tool support: aggregates activity across multiple repos and tools for a unified update.
  • Clean Markdown output: generates a concise, share-ready daily update with links and summaries.

Quick Start

Trigger the standup workflow by saying daily, standup, or scrum update to start the interview and generate a Markdown update.

Frequently Asked Questions about daily-meeting-update

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

FAQPage Schema
How do I automate daily standup updates from GitHub and Jira?

You can automate daily standup updates by triggering the workflow with keywords like daily or scrum update, which gathers context from GitHub, Jira, and Claude Code history to generate a concise Markdown update.

What is the best way to prepare a multi-repo standup update?

The best way to prepare a multi-repo standup update is to aggregate activity across multiple repositories and tools, run a contextual interview, and output a unified Markdown summary covering blockers and discussion topics.

Can I generate a Markdown daily update without manually copying Jira tickets?

Yes, you can generate a Markdown daily update without manual copying by using consent-based integration detection to automatically pull relevant Jira and GitHub data into an interview workflow.

Does the standup generation workflow require explicit consent to access GitHub data?

Yes, the standup generation workflow requires explicit consent before accessing GitHub data, utilizing consent-based data discovery to detect integrations and prompt the user before pulling any context.

How do I start the daily update interview workflow?

You start the daily update interview workflow by triggering the process with keywords like daily, standup, or scrum update, which initiates the contextual interview covering yesterday, today, blockers, and topics.

What limitations exist when aggregating cross-tool activity for a unified standup update?

A key limitation of aggregating cross-tool activity is that it requires consent-based data access, meaning the standup update generation depends entirely on explicit user permission to pull GitHub, Jira, and Claude Code history.