meeting-prep

What This Skill Does

The meeting-prep skill is an advanced automation assistant designed specifically for engineering teams that rely on Google Calendar and GitHub. It functions as an automated standup secretary, silently monitoring your schedule to provide relevant development context exactly when you need it. By bridging the gap between your calendar and your repository commit history, it eliminates the manual labor of preparing status updates. The skill intelligently parses upcoming meetings, identifies those requiring virtual participation, and pre-fetches recent code changes to generate verbose, developer-friendly summaries. Additionally, it automates end-of-day reporting, aggregating commits from multiple repositories and developers into a cohesive, structured summary that highlights team velocity and individual contributions.

Installation

To integrate meeting-prep into your workflow, first ensure you have the OpenClaw environment properly configured. Use the command clawhub install openclaw/skills/skills/hougangdev/meeting-prep to fetch the source. Next, you must configure your credentials. Create an OAuth 2.0 Desktop application in the Google Cloud Console with the calendar scope enabled and save the client_secret.json into the credentials/ directory. You will also need to generate a classic GitHub Personal Access Token with repo scope permissions. Once these files are placed, the agent will handle the OAuth handshake and token persistence automatically.

Use Cases

• Automated Standups: Never scramble for status updates before a team sync; the agent provides a detailed digest of your recent commits as a meeting approaches.
• End-of-Day Reporting: Managers can use the daily summary feature to get an aggregated view of what the engineering team accomplished across disparate repositories without manually checking commit logs.
• Contextual Awareness: The agent ensures you are fully briefed on the work performed by your peers in the same subdirectories before you walk into a technical discussion.

Example Prompts

• "Can you check my calendar and prepare a summary of my recent commits for the 10 AM sprint planning meeting?"
• "Generate an end-of-day commit summary for all active projects in the organization and send it to the team channel."
• "What have the developers been working on in the core-engine repository since my last update?"

Tips & Limitations

• Token Management: Ensure your calendar_tokens.json files are kept secure, as they provide broad access to your schedule. For teams with multiple calendars, verify that you have mapped the correct token files to the corresponding account aliases in your agent configuration.
• Verbosity: The agent is designed for verbose output to capture technical nuance, but you can request shorter summaries if you find the output too detailed for quick reading.
• Network Dependency: Because this skill relies heavily on external API calls to Google and GitHub, ensure your agent environment has consistent network access to prevent skipped heartbeat checks.