New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Daily Meeting Update

by davila7 in davila7/claude-code-templates

Interactive daily standup/meeting update generator. An agent skill from davila7/claude-code-templates.

MITAuto-check passedProduct & Project Management

Install Daily Meeting Update

skills CLI
$ npx skills add davila7/claude-code-templates --skill daily-meeting-update -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install davila7/claude-code-templates daily-meeting-update --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/davila7/claude-code-templates.git skills-src && mkdir -p .claude/skills && cp -r skills-src/cli-tool/components/skills/enterprise-communication/daily-meeting-update .claude/skills/daily-meeting-update && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
daily-meeting-update
GitHub stars
33k
Used in
2 other repos
Token cost
~3k tokens
SKILL.md length
703 words
Files
3 (incl. scripts)
Skills in repo
479
Repo updated
First seen
Licence
MIT

At a glance

Interactive daily standup/meeting update generator. An agent skill from davila7/claude-code-templates.

  • Works in 3 steps: Detect & Offer Integrations → Interview (with insights) → Generate Update
  • User says daily
  • SKILL.md covers Workflow, Phase 1: Detect & Offer…, Phase 2: Interview (with… and Phase 3: Generate Update, plus 6 more sections
  • Runs Python scripts from its folder; calls python3 and gh; reaches github.com

What it does

Daily Meeting Update is an agent skill from davila7/claude-code-templates. Interactive daily standup/meeting update generator. Use when user says 'daily', 'standup', 'scrum update', 'status update', 'what did I do yesterday', 'prepare for meeting', 'morning update', or 'team sync'. Pulls activity from GitHub, Jira, and Claude Code session history. Conducts 4-question interview (yesterday, today, blockers, discussion topics) and generates formatted Markdown update.

Its SKILL.md is about 3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including scripts (for example `README.md` and `scripts/claude_digest.py`).

It sits in Product & Project Management, covering Meeting notes and agendas and Sprint planning and agile. It works with Jira, GitHub, Git and Model Context Protocol. The repository describes itself as: CLI tool for configuring and monitoring Claude Code. The licence is MIT.

When your agent uses it

  • User says daily
  • What did I do yesterday
  • Prepare for meeting

Example prompts

  • “standup”
  • “scrum update”
  • “status update”
  • “/daily-meeting-update”

Requirements

  • Python 3

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Detect & Offer Integrations
  2. Interview (with insights)
  3. Generate Update

What it can do on your machine

Read from SKILL.md and the folder at commit 79182c5. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • python3
    • gh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • github.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Daily Meeting Update loads about 3k tokens when it runs. Until then it costs about 104 tokens; SKILL.md has 703 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~104
When it runs · the whole SKILL.md, loaded when a task matches
~3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from davila7/claude-code-templates at commit 79182c5, republished under its MIT licence (© davila7). 703 words, ~3,003 tokens.

Download SKILL.mdSave it as .claude/skills/daily-meeting-update/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
daily-meeting-update
description
Interactive daily standup/meeting update generator. Use when user says 'daily', 'standup', 'scrum update', 'status update', 'what did I do yesterday', 'prepare for meeting', 'morning update', or 'team sync'. Pulls activity from GitHub, Jira, and Claude Code session history. Conducts 4-question interview (yesterday, today, blockers, discussion topics) and generates formatted Markdown update.
user-invocable
true

Daily Meeting Update

Generate a daily standup/meeting update through an interactive interview. Never assume tools are configured—ask first.

Workflow

START
  │
  ▼
┌─────────────────────────────────────────────────────┐
│ Phase 1: DETECT & OFFER INTEGRATIONS                │
│ • Check: Claude Code history? gh CLI? jira CLI?     │
│ • Claude Code → Pull yesterday's session digest     │
│   → User selects relevant items via multiSelect     │
│ • GitHub/Jira → Ask user, pull if approved          │
│ • Pull data NOW (before interview)                  │
├─────────────────────────────────────────────────────┤
│ Phase 2: INTERVIEW (with insights)                  │
│ • Show pulled data as context                       │
│ • Yesterday: "I see you merged PR #123, what else?" │
│ • Today: What will you work on?                     │
│ • Blockers: Anything blocking you?                  │
│ • Topics: Anything to discuss at end of meeting?    │
├─────────────────────────────────────────────────────┤
│ Phase 3: GENERATE UPDATE                            │
│ • Combine interview answers + tool data             │
│ • Format as clean Markdown                          │
│ • Present to user                                   │
└─────────────────────────────────────────────────────┘

Phase 1: Detect & Offer Integrations

Step 1: Silent Detection

Check for available integrations silently (suppress errors, don't show to user):

IntegrationDetection
Claude Code History~/.claude/projects directory exists with .jsonl files
GitHub CLIgh auth status succeeds
Jira CLIjira command exists
Atlassian MCPmcp__atlassian__* tools available
GitInside a git repository
Step 2: Offer GitHub/Jira Integrations (if available)

Claude Code users: Use AskUserQuestionTool tool for all questions in this phase.

GitHub/Git:

If HAS_GH or HAS_GIT:

"I detected you have GitHub/Git configured. Want me to pull your recent activity (commits, PRs, reviews)?"

Options:
- "Yes, pull the info"
- "No, I'll provide everything manually"

If yes:

"Which repositories/projects should I check?"

Options:
- "Just the current directory" (if in a git repo)
- "I'll list the repos" → user provides list

Jira:

If HAS_JIRA_CLI or HAS_ATLASSIAN_MCP:

"I detected you have Jira configured. Want me to pull your tickets?"

Options:
- "Yes, pull my tickets"
- "No, I'll provide everything manually"
Step 3: Pull GitHub/Jira Data (if approved)

GitHub/Git — For each approved repo:

  • Commits by user since yesterday
  • PRs opened/merged by user
  • Reviews done by user

Jira — Tickets assigned to user, updated in last 24h

Key insight: Store results to use as context in Phase 2 interview.

Step 4: Offer Claude Code History

This integration captures everything you worked on with Claude Code — useful for recalling work that isn't in git or Jira.

Detection:

bash
ls ~/.claude/projects/*/*.jsonl 2>/dev/null | head -1

If Claude Code history exists, ask:

"I can also pull your Claude Code session history from yesterday. This can help recall work that isn't in git/Jira (research, debugging, planning). Want me to check?"

Options:
- "Yes, pull my Claude Code sessions"
- "No, I have everything I need"

If yes, run the digest script:

bash
python3 ~/.claude/skills/daily-meeting-update/scripts/claude_digest.py --format json

Then present sessions with multiSelect:

Use AskUserQuestionTool with multiSelect: true to let user pick relevant items:

"Here are your Claude Code sessions from yesterday. Select the ones relevant to your standup:"

Options (multiSelect):
- "Fix authentication bug (backend-api)"
- "Implement OAuth flow (backend-api)"
- "Update homepage styles (frontend-app)"
- "Research payment providers (docs)"

Key insight: User selects which sessions are work-related. Personal projects or experiments can be excluded.

Do NOT run digest script when:

  • User explicitly says "No" to Claude Code history
  • User says they'll provide everything manually
  • ~/.claude/projects directory doesn't exist

If digest script fails:

  • Fallback: Skip Claude Code integration silently, proceed with interview
  • Common issues: Python not installed, no sessions from yesterday, permission errors
  • Do NOT block the standup flow — the script is supplemental, not required

Phase 2: Interview (with insights)

Claude Code users: Use AskUserQuestionTool tool to conduct the interview. This provides a better UX with structured options.

Use pulled data as context to make questions smarter.

Question 1: Yesterday

If data was pulled, show it first:

"Here's what I found from your activity:
- Merged PR #123: fix login timeout
- 3 commits in backend-api
- Reviewed PR #456 (approved)

Anything else you worked on yesterday that I missed?"

If no data pulled:

"What did you work on yesterday/since the last standup?"

If user response is vague, ask follow-up:

  • "Can you give more details about X?"
  • "Did you complete anything specific?"
Question 2: Today
"What will you work on today?"

Options:
- [Text input - user types freely]

If Jira data was pulled, you can suggest:

"I see you have these tickets assigned:
- PROJ-123: Implement OAuth flow (In Progress)
- PROJ-456: Fix payment bug (To Do)

Will you work on any of these today?"
Question 3: Blockers
"Do you have any blockers or impediments?"

Options:
- "No blockers"
- "Yes, I have blockers" → follow-up for details
Question 4: Topics for Discussion
"Any topic you want to bring up at the end of the daily?"

Options:
- "No, nothing to discuss"
- "Yes" → follow-up for details

Examples of topics:
- Technical decision that needs input
- Alignment with another team
- Question about prioritization
- Announcement or info for the team

Phase 3: Generate Update

Combine all information into clean Markdown:

markdown
# Daily Update - [DATE]

## Yesterday
- [Items from interview]
- [Items from GitHub/Jira if pulled]

## Today
- [Items from interview]

## Blockers
- [Blockers or "No blockers"]

## PRs & Reviews (if pulled from GitHub)
- [PRs opened]
- [PRs merged]
- [Reviews done]

## Jira (if pulled from Jira)
- [Tickets updated]

## Topics for Discussion
- [Topics or "None"]

---
*Links:*
- [PR links]
- [Ticket links]

Core Principles

  1. Interview is primary — Tools supplement, they don't replace human context
  2. Consent before access — Always ask before pulling from any integration
  3. Context-aware questions — Show pulled data during interview to trigger memory ("I see you merged PR #123...")
Show full SKILL.md (290 more words)Show less

Quick Reference

PhaseActionTool
1. Detect & OfferCheck gh/jira/claude history, ask user, pull dataBash (silent), AskUserQuestionTool*
2. InterviewAsk 4 questions with insightsAskUserQuestionTool*
3. GenerateFormat MarkdownOutput text

*Claude Code only: Use AskUserQuestionTool tool for structured questions.

Claude Code Digest Script
bash
# Get yesterday's sessions as JSON
python3 ~/.claude/skills/daily-meeting-update/scripts/claude_digest.py --format json

# Get today's sessions
python3 ~/.claude/skills/daily-meeting-update/scripts/claude_digest.py --date today --format json

# Filter to specific project
python3 ~/.claude/skills/daily-meeting-update/scripts/claude_digest.py --project ~/my-app --format json

Example Session

Claude: "Let's prepare your daily! I detected GitHub configured. Want me to pull your recent activity?"
User: "Yes"

Claude: "Which repos should I check?"
User: "backend-api and frontend-app"

[Claude pulls GitHub data silently]

Claude: "I can also pull your Claude Code session history from yesterday. Want me to check?"
User: "Yes"

[Claude runs digest script, gets 5 sessions]

Claude: "Here are your Claude Code sessions from yesterday. Select the ones relevant to your standup:"
  ☑ Fix authentication timeout bug (backend-api)
  ☑ Implement OAuth flow (backend-api)
  ☐ Update personal blog (blog) - [user unchecks personal project]
  ☑ Research payment providers (docs)
  ☐ Debugging test failures (experiments)

User: [selects 3 relevant items]

Claude: "Here's what I found from your activity:
- Merged PR #120: fix login timeout
- Opened PR #125: feat: add OAuth flow
- Reviewed PR #123 (approved), PR #456 (changes requested)
- 5 commits in backend-api
- [From Claude Code] Fix authentication timeout bug
- [From Claude Code] Implement OAuth flow
- [From Claude Code] Research payment providers

Anything else you worked on yesterday that I missed?"
User: "No, that covers it"

Claude: "What will you work on today?"
User: "Continue the OAuth feature and deploy to staging"

Claude: "Any blockers?"
User: "No"

Claude: "Any topic to bring up at the end of the daily?"
User: "Yes, I want to discuss the architecture of the new payments module"

[Claude generates update]

Output Example

markdown
# Daily Update - 2026-01-22

## Yesterday
- Worked on authentication feature
- Research on payment providers
- Merged PR #120 (fix: login timeout)
- Opened PR #125 (feat: add OAuth flow)

## Today
- Continue OAuth feature
- Deploy to staging

## Blockers
- No blockers

## PRs & Reviews
- **Opened:** PR #125 - feat: add OAuth flow
- **Merged:** PR #120 - fix: login timeout
- **Reviews:** PR #123 (approved), PR #456 (changes requested)

## Topics for Discussion
- Architecture of the new payments module

---
*Links:*
- https://github.com/org/repo/pull/125
- https://github.com/org/repo/pull/120

Anti-Patterns

AvoidWhy (Expert Knowledge)Instead
Run gh/jira without askingUsers may have personal repos visible, or be in a sensitive project context they don't want exposedAlways ask first, let user choose repos
Assume current directory is the only projectDevelopers often work on 2-5 repos simultaneously (frontend, backend, infra)Ask "Which projects are you working on?"
Skip interview even with tool dataTools capture WHAT happened but miss WHY and context (research, meetings, planning)Interview is primary, tools supplement
Generate update before all 4 questionsUser might have critical blocker or discussion topic that changes the narrativeComplete interview, then generate
Include raw commit messagesCommit messages are often cryptic ("fix", "wip") and don't tell the storySummarize into human-readable outcomes
Ask for data after interviewShowing insights during interview makes questions smarter ("I see you merged PR #123, anything else?")Pull data first, then interview with context

NEVER

  • NEVER assume tools are configured — Many devs have gh installed but not authenticated, or jira CLI pointing to wrong instance
  • NEVER skip the "Topics for Discussion" question — This is often the most valuable part of standup that tools can't capture
  • NEVER generate more than 15 bullets — Standup should be <2 minutes to read; long updates lose the audience
  • NEVER include ticket/PR numbers without context — "PROJ-123" means nothing; always include title or summary
  • NEVER pull data from repos user didn't explicitly approve — Even if you can see other repos, respect boundaries

© davila7, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (scripts) in cli-tool/components/skills/enterprise-communication/daily-meeting-update of davila7/claude-code-templates.

  • SKILL.md
  • README.md
  • scripts/claude_digest.py

Open the folder on GitHubat commit 79182c5

Used in 2 other repositories

We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in davila7/claude-code-templates, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Daily Meeting Update next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Daily Meeting Update compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Daily Meeting Update this skilldavila7/claude-code-templates33k2 repos~3kAutomated safety check: PassMIT
Vibe Kanbanaiskillstore/marketplace433—~4.4kAutomated safety check: NotesNone
JiraVixenLights/Vixen114—~3.4kAutomated safety check: PassCustom licence
Retrokoolamusic/claudefiles130—~2.8kAutomated safety check: PassMIT
Scrum Masteralirezarezvani/claude-skills28k1 repos~2.4kAutomated safety check: PassMIT
Piv Slice Epiccoleam00/skills676—~1.5kAutomated safety check: PassMIT

Similar skills

  • Vibe Kanban

    aiskillstore/marketplace

    Manage AI coding agents on a visual Kanban board. An agent skill from aiskillstore/marketplace.

    433 GitHub stars~4.4k tokensUpdated yesterday
    Agent WorkflowsAuto-check: notes

  • Jira

    VixenLights/Vixen

    Manages JIRA issues, projects, and workflows using Atlassian MCP.

    114 GitHub stars~3.4k tokensUpdated yesterday
    Product & Project ManagementAuto-check passed

  • Retro

    koolamusic/claudefiles

    A skill your agent uses when a user completes a phase, sprint, milestone, or meaningful unit of work and needs a retrospective.

    130 GitHub stars~2.8k tokensUpdated yesterday
    Product & Project ManagementAuto-check passed

  • Scrum Master

    alirezarezvani/claude-skills

    Advanced Scrum Master skill for data-driven agile team analysis and coaching.

    28k GitHub starsUsed in 1 repo~2.4k tokens
    Product & Project ManagementAuto-check passed

  • Piv Slice Epic

    coleam00/skills

    Slice an epic (with its architecture decisions) into PIV-sized tickets with a dependency graph, then create them in your tracker (Jira via the Atlassian MCP, or GitHub/Linear/local).

    676 GitHub stars~1.5k tokensUpdated 4 days ago
    Product & Project ManagementAuto-check passed

  • Project Management

    seb1n/awesome-ai-agent-skills

    Manages software projects end-to-end — decomposing work into tasks, tracking progress across sprints, generating status reports, and integrating with tools like Jira, Linear, GitHub Issues, and…

    206 GitHub stars~2.7k tokensUpdated 2 mo ago
    Product & Project ManagementAuto-check passed

More from davila7/claude-code-templates

All 479 skills in this repo

  • Perplexity Web Search

    davila7/claude-code-templates

    Runs web-grounded searches through Perplexity's Sonar models over OpenRouter for current events, recent literature and cited facts beyond the model's training cutoff.

    33k GitHub starsUsed in 11 repos~3.5k tokens
    Auto-check: notes

  • Neuropixels Data Analysis

    davila7/claude-code-templates

    Analyzes Neuropixels recordings from SpikeGLX or Open Ephys through preprocessing, drift correction, Kilosort4 spike sorting, quality metrics and curation.

    33k GitHub starsUsed in 9 repos~2.8k tokens
    Auto-check passed

  • Scientific Venue Templates

    davila7/claude-code-templates

    Supplies LaTeX templates and formatting rules for journals, conferences, posters, and grant proposals, then can check a draft against them.

    33k GitHub starsUsed in 9 repos~5.1k tokens
    Auto-check: notes

  • Brand Voice Content Creator

    davila7/claude-code-templates

    Analyzes a brand's existing writing to lock in a consistent voice, then builds SEO blog posts and platform-specific social content around it.

    33k GitHub starsUsed in 3 repos~1.9k tokens
    Auto-check passed

  • CAPA Officer

    davila7/claude-code-templates

    Guides corrective and preventive action (CAPA) work in a quality management system, from initiation and root cause analysis through effectiveness verification.

    33k GitHub starsUsed in 1 repo~2k tokens
    Auto-check passed

  • Fda Consultant Specialist

    davila7/claude-code-templates

    Senior FDA consultant and specialist for medical device companies including HIPAA compliance and requirement management.

    33k GitHub starsUsed in 1 repo~2.7k tokens
    Auto-check passed

Works with

Categories

Questions about Daily Meeting Update

What does Daily Meeting Update do?

Interactive daily standup/meeting update generator. An agent skill from davila7/claude-code-templates. Daily Meeting Update is an agent skill from davila7/claude-code-templates. Interactive daily standup/meeting update generator.

When should I use Daily Meeting Update?

Daily Meeting Update fits situations like: user says daily; what did I do yesterday; prepare for meeting.

How do I install Daily Meeting Update in Claude Code?

Run `npx skills add davila7/claude-code-templates --skill daily-meeting-update -a claude-code`. Or copy the skill folder (cli-tool/components/skills/enterprise-communication/daily-meeting-update in davila7/claude-code-templates) into .claude/skills/daily-meeting-update in your project. Claude Code loads it when a task matches its description.

How do I install Daily Meeting Update in Codex?

Run `npx skills add davila7/claude-code-templates --skill daily-meeting-update -a codex`. Or copy the skill folder (cli-tool/components/skills/enterprise-communication/daily-meeting-update in davila7/claude-code-templates) into .agents/skills/daily-meeting-update in your project. Codex loads it when a task matches its description.

Can I use Daily Meeting Update in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add davila7/claude-code-templates --skill daily-meeting-update -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/daily-meeting-update, .gemini/skills/daily-meeting-update, .github/skills/daily-meeting-update and .opencode/skills/daily-meeting-update in your project.

What does Daily Meeting Update need to run?

Going by SKILL.md and its folder, Daily Meeting Update needs Python for the scripts in its folder and the command-line tools its instructions call (python3 and gh). Our summary lists: Python 3.

Does Daily Meeting Update access the network?

SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Daily Meeting Update safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Daily Meeting Update use?

Daily Meeting Update is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Daily Meeting Update use?

About 3k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Daily Meeting Update?

Skills that share tags, products or a category with Daily Meeting Update: Vibe Kanban (aiskillstore/marketplace, 433 stars), Jira (VixenLights/Vixen, 114 stars), Retro (koolamusic/claudefiles, 130 stars) and Scrum Master (alirezarezvani/claude-skills, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Daily Meeting Update?

davila7 (a GitHub user) maintains it in davila7/claude-code-templates, which has 32,552 GitHub stars. The repository holds 479 skills in this directory. The repository was last updated on October 11, 2026.

Source: davila7/claude-code-templates on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.