Install
$ agentstack add skill-nyechiel-ai-augmented-workflow-meeting-prep ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Meeting Prep
Generate a meeting brief by discovering context across all available tools.
Use user_google_email: "{YOUR_EMAIL}" for all Google Workspace calls.
Workflow
1. Determine Meeting Target
- If the user provides a topic and/or attendees, use those directly.
- Otherwise, use
get_eventswithdetailed: trueto list upcoming meetings. Filter out declined and all-day events. Ask which one to prep for. - Check time to meeting via
get_current_time. If less than 15 minutes away, produce a fast brief (attendees + key context only).
2. Context Discovery (run in parallel)
A. Stakeholder Context
- Check
stakeholders/README.mdfor notes on each attendee. - For unknown attendees, look up via
search_directoryand add to stakeholder map. - Search recent emails and Slack messages with key attendees (last 7 days).
B. Meeting History
- Search
meetings/for previous meeting files with the same attendees or topic. - Extract unchecked action items and deferred topics from prior meetings.
C. Domain Knowledge
- Grep
*/knowledge.mdfiles for meeting topic keywords. - Check
/decisions/for prior decisions on the topic.
D. Task Board Context
- Search Crux for tasks related to the meeting topic or attendees.
3. Generate the Brief
Save to meetings/YYYY-MM-DD-.md using templates/meeting-brief.md:
# Meeting Brief: [Title]
**Date/Time:** [date and time]
**Attendees:** [names and titles]
## Quick Context
- [1-2 sentences: what this is about and why it matters]
## What They Expect from You
- [ ] [Commitments or deliverables they're waiting on]
## Suggested Follow-Up Questions
1. [Question that advances the discussion]
4. Present Summary
After saving, present: key context for this meeting, outstanding commitments, and top 3 talking points.
Graceful Degradation
| Tool | If unavailable | |------|---------------| | Calendar | Skip calendar lookup. User must provide topic and attendees. | | Gmail/Slack | Skip email/message search. Note gap. | | Crux | Skip task board search. Note gap. |
Key Principles
- "What do they expect from me?" is the most important section.
- Scannable in under 2 minutes. Bullet points, no filler.
- Link everything. Make it easy to jump to sources.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: nyechiel
- Source: nyechiel/ai-augmented-workflow
- License: MIT
- Homepage: https://nyechiel.com/blog/2026/06/14/build-your-own-ai-augmented-workflow/
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.