From slim-rebranding
Generates meeting agendas by gathering context from previous summaries, external services (GitHub, Slack via TECH.md), and custom templates. Suggests generating missing summaries for upcoming meetings.
npx claudepluginhub nasa-ammos/slim --plugin slim-rebrandingThis skill uses the workspace's default tool permissions.
Writes meeting agendas by orchestrating context from multiple sources: previous meeting summaries, external services (via TECH.md), and custom templates. Supports natural language date inputs and flexible template formats.
Implements structured self-debugging workflow for AI agent failures: capture errors, diagnose patterns like loops or context overflow, apply contained recoveries, and generate introspection reports.
Monitors deployed URLs for regressions in HTTP status, console errors, performance metrics, content, network, and APIs after deploys, merges, or upgrades.
Provides React and Next.js patterns for component composition, compound components, state management, data fetching, performance optimization, forms, routing, and accessible UIs.
Writes meeting agendas by orchestrating context from multiple sources: previous meeting summaries, external services (via TECH.md), and custom templates. Supports natural language date inputs and flexible template formats.
Required Skills:
slim-project-aware-workspace: Provides AGENTS.md and static files (PROJECT.md, TEAM.md, PRODUCTS.md, MEETINGS.md, TECH.md)Related Skills:
slim-meeting-summary: Used to generate missing summaries when neededExternal Tools (discovered dynamically from TECH.md):
To generate a meeting agenda, follow WORKFLOW.md.
The workflow guides you through gathering user inputs, discovering meeting metadata, checking for previous summaries, querying external services, and generating the final agenda.
All files for one agenda go in ONE folder:
dynamic/[agenda-date]/meeting-agendas/[meeting-name]/
├── meeting-agenda-[meeting-name].[ext] ← Final agenda at ROOT
└── prep/ ← Prep work in SUBFOLDER
├── context/
├── previous-summaries/
├── external-context/
└── template/
Do NOT create separate folders for prep work and final agenda.
The generated agenda MUST match the template in:
Analyze the template carefully before generation. Default template: assets/meeting-agenda-template.md
Do NOT create intermediate summary files (e.g., context-summary.md). Use prep files directly during generation to save tokens.
Calculate expected meeting dates based on MEETINGS.md frequency field (e.g., "Weekly", "Biweekly") to identify which summaries should exist.
When summaries are missing, guide user to invoke slim-meeting-summary (skills cannot invoke each other programmatically). Provide clear instructions and wait for confirmation. Suggest the user execute the slim-meeting-summary skill in a separate AI instance for all needed meetings to maintain proper context within the current skill.
Issue: Cannot find AGENTS.md
Issue: Meeting not in MEETINGS.md
Issue: No previous summaries found
Issue: Multiple meetings match search
For detailed step-by-step execution, see WORKFLOW.md.