standup-report

Generates a structured daily standup report from git history, task-queue status, and agent activity.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/SalesTeamToolbox/frood --skill standup-report
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: standup-report
Source: https://github.com/SalesTeamToolbox/frood/tree/main/skills/builtins/standup-report
Command: npx skills add https://github.com/SalesTeamToolbox/frood --skill standup-report

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns scattered signals from git, task queues, and agent runs into a consistent daily standup so teams can quickly see progress and blockers without manual digging.

Core Features & Use Cases

  • Git-backed updates: Summarizes commits and merged PRs from recent history to reflect what actually changed.
  • Task-queue awareness: Reports what moved forward, what’s still in progress, and what’s pending or failed.
  • Agent activity metrics: Highlights completions, iteration usage, and stalled agents/errors to support operational follow-through.
  • Blocker-first reporting: Surfaces dependencies and required actions explicitly to unblock the team fastest.
  • No fabrication guidance: Instructs the report generator to use actual data and clearly state when there are no blockers.

Quick Start

Ask the AI to produce the daily standup report for today using yesterday’s git activity, the current task queue status, and the last 24 hours of agent activity.

Frequently Asked Questions about standup-report

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

FAQPage Schema
How do I generate a daily standup report from git history and task queues?▼

A daily standup report combines git history, task-queue status, and recent agent activity into a single structured update. It summarizes PR and commit outcomes, tracks iteration usage versus budget, and explicitly lists any blockers.

What is the best way to track blockers and agent activity for daily reporting?▼

The best way to track blockers and agent activity is by using a blocker-first reporting method that surfaces dependencies, stalled agents, and iteration usage versus budget explicitly, ensuring required actions are communicated clearly to unblock the team fastest.

Does the daily standup report include actual command outputs or fabricated summaries?▼

The daily standup report includes actual command outputs and real data. It applies no fabrication guidance, instructing the generator to source data from real git activity, task queues, and agent runs, clearly stating when no blockers exist.

Can I use task tracking and git history for operational monitoring in team workflows?▼

Yes, you can use task tracking and git history for operational monitoring in team workflows. The Skill applies to software delivery, operational monitoring, and agent-assisted execution where progress and blockers must be clearly communicated.

How do I summarize PR and commit outcomes concisely for a standup update?▼

To summarize PR and commit outcomes concisely for a standup update, the Skill extracts recent git history and condenses merged PRs and commits into a structured update, reflecting what actually changed without requiring manual digging through scattered signals.