feat(prompt-library): add Smart Meeting Assistant advanced prompt (#4998)

[ARYPROGRAMMER]

Summary

Advanced prompt that orchestrates meeting workflow automation from preparation to follow-up through intelligent multi-extension integration. Features 4 extensions (Tavily, Google Drive, Developer, Memory), graceful fallback handling, and comprehensive meeting deliverables generation. Demonstrates seamless external MCP integration with optional configuration.

Extensions usage:

1. Tavily Web Search (External MCP)

• Type: external (npx)
• Command: npx -y tavily-mcp
• Environment: TAVILY_API_KEY (required)
• Purpose: Real-time web research for current best practices, industry trends, and technical recommendations
• Used for: Background research, gathering current dashboard implementation examples
• Fallback: Uses built-in knowledge if not configured

2. Google Drive (External MCP)

• Type: external (npx)
• Command: npx -y @modelcontextprotocol/server-gdrive
• Environment: GDRIVE_OAUTH_PATH, GDRIVE_CREDENTIALS_PATH (both required)
• Purpose: Automated document storage and organization in structured folders
• Used for: Saving meeting agendas, notes templates, action trackers to Drive
• Fallback: Generates documents inline if not configured

3. Developer (Builtin)

• Type: builtin
• Command: developer
• Purpose: File operations, document generation, template creation
• Used in: Creating structured meeting materials, formatting outputs
• Always available: No configuration required

4. Memory (Builtin)

• Type: builtin
• Command: memory
• Purpose: Storing meeting context and preferences across sessions
• Used in: Remembering meeting patterns, attendee details, project context
• Always available: No configuration required

Type of Change

• Feature
• Bug fix
• Refactor / Code quality
• Performance improvement
• Documentation
• Tests
• Security fix
• Build / Release
• Other (specify below)

Testing

Local Testing: Validated with multiple test scenarios - successfully demonstrated multi-extension orchestration, graceful fallback behavior, and comprehensive output generation.

Test Commands:

# Test 1: Builtin extensions only (no external APIs)
goose run -i test-meeting-builtin-only.txt

# Test 2: With explicit extension usage
goose run -i test-meeting-with-extensions.txt

Related Issues

Fixes #4998

ref: test-meeting-builtin-only.txt:

I have a project kickoff meeting scheduled for tomorrow at 2 PM with the development team. The meeting is about planning the new customer dashboard feature. Please:

1. Use your knowledge of customer dashboard best practices
2. Create a meeting agenda with time allocations
3. Draft a pre-meeting email with the agenda
4. Set up a notes template for capturing key points
5. Prepare a follow-up action item tracker

Attendees: John (Engineering Lead), Sarah (Product Manager), Mike (Designer)
Estimated Duration: 60 minutes

ref: test-meeting-with-extensions.txt:

I have a project kickoff meeting scheduled for tomorrow at 2 PM with the development team. The meeting is about planning the new customer dashboard feature. Please:

1. SEARCH THE WEB using Tavily to find the latest customer dashboard best practices, trends, and industry examples from 2024-2025. Look for recent articles about successful dashboard implementations.

2. Create a comprehensive meeting agenda with time allocations based on the research

3. Draft a pre-meeting email with the agenda and key research findings

4. Set up a notes template for capturing key points during the meeting

5. Prepare a follow-up action item tracker with status columns

6. SAVE ALL DOCUMENTS to my Google Drive in a folder called "Customer Dashboard Project - Kickoff Meeting"

Attendees: John (Engineering Lead), Sarah (Product Manager), Mike (Designer)
Estimated Duration: 60 minutes

Please use web search to ensure the best practices are current and relevant for 2025, and confirm when all documents are saved to Google Drive.

[EbonyLouis]

@ARYPROGRAMMER thank you so much for contributing!

[ARYPROGRAMMER]

Reminder to merge this,

Thanks @taniandjerry

[EbonyLouis]

Hey @ARYPROGRAMMER one of the test aren't being ran can you fetch and merge main?

Let me know if you need any help

[ARYPROGRAMMER]

Hey @ARYPROGRAMMER one of the test aren't being ran can you fetch and merge main?

Let me know if you need any help

i did that now, its just the dco signoff thats missing maybe the rebase didnt have that commit signed. check the rest

[ARYPROGRAMMER]

let me know if this is correct @EbonyLouis

[EbonyLouis]

that worked, thanks!! @ARYPROGRAMMER