andara-meeting-minutes
Capture meeting summaries and action items from voice or text
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/atiati82/andara-meeting-minutesMeeting Minutes Skill
When ATTi or a team member sends a meeting summary (voice or text), save it as a structured record.
Trigger
When user says something like "Meeting Notes:", "Besprechungsnotizen:", or "save meeting" — parse the content and store it.
Steps
-
Extract the meeting topic, attendees, decisions, and action items from the message.
-
Save to PostgreSQL using bash + psql:
psql "$DATABASE_URL" -c "
INSERT INTO team_meetings (title, summary, attendees, meeting_date, created_at)
VALUES ('TOPIC', 'SUMMARY', ARRAY['ATTENDEE1','ATTENDEE2'], NOW(), NOW())
RETURNING id;"
- For each action item, insert into meeting_action_items:
psql "$DATABASE_URL" -c "
INSERT INTO meeting_action_items (meeting_id, assignee, description, due_date, status, created_at)
VALUES (MEETING_ID, 'ASSIGNEE', 'TASK DESCRIPTION', 'DUE_DATE', 'pending', NOW());"
- Confirm to the user: "Meeting gespeichert ✅ — [X] Action Items erstellt."
Output Format
Reply in German with a structured summary:
- 📋 Meeting: [Title]
- 👥 Teilnehmer: [Names]
- ✅ Action Items: [List with assignees]
- 📅 Nächstes Treffen: [if mentioned]
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-atiati82-andara-meeting-minutes": {
"enabled": true,
"auto_update": true
}
}
}Related Skills
openclaw-admin
Manage and inspect the OpenClaw multi-agent gateway — list agents, check model health, view routing rules, manage crons, inspect context budgets, and run system diagnostics.
andara-rag-search
Search the Andara Ionic RAG knowledge base (3,800+ records) for business intel, research, products, team, meetings, and any indexed content.
andara-self-improvement
Captures learnings, errors, and corrections to enable continuous improvement. Use when: (1) A command or operation fails unexpectedly, (2) User corrects Claude ('No, that's wrong...', 'Actually...'), (3) User requests a capability that doesn't exist, (4) An external API or tool fails, (5) Claude realizes its knowledge is outdated or incorrect, (6) A better approach is discovered for a recurring task. Also review learnings before major tasks.
knowledge-gaps
Track questions Hans failed to answer and flag missing knowledge