How do I install the Meeting Studio skill?

Run npx skillmds@latest add navinspire-ia/meeting-studio in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Meeting Studio safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Meeting Studio?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Meeting Studio free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Meeting Studio?

Navinspire-ia (@navinspire-ia) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Meeting Studio by navinspire-ia — Agent Skill

Name: Meeting Studio
Rating: 4.2 (5 reviews)
Author: Navinspire-ia

File contents

Meeting studio

Privacy-first meeting desk inside Navin Studio (#/meeting, command /meeting). Transcription uses the user's configured Navin STT provider (prefer the highest-accuracy managed/local model available). Summaries use their chat models and optional custom templates from the Meeting workbench. Nothing is sent to a third-party meeting brand.

Inputs

Live or pasted transcript from the Meeting workbench
Speaker map (Speaker 1… or real names only when explicit in transcript)
Selected summary template instructions
Optional calendar event metadata (ICS import is local-only)
Chat-with-meeting questions (answer only from this meeting's evidence)
Raw notes / CRM context

Outputs (workspace)

meetings/<slug>/
  transcript.md
  speakers.md
  summary.md
  minutes.md
  follow-up.md
  actions.md
  discovery.md
  chat.md
  audit.md
  export.docx   # when /studio document export is requested
meeting-report-YYYYMMDD-HHMMSS.html

Workflow

Confirm language, template instructions, attendees/speakers if known.
High-accuracy cleanup of ASR when asked - never invent words or speakers.
If speaker identification is requested: label turns; use Speaker N when names are unknown.
Extract: decisions ≠ discussion ≠ actions (owner + deadline required).
Apply the selected template for summary/minutes.
For chat-with-meeting: answer only from transcript/notes; append Q&A to chat.md.
Draft follow-up email (human sends) and log CRM activity with the crm tool (log_activity) plus crm-update-agent.
Ship meeting-report-*.html (PDF via File Preview export), open preview, critic-review gate.
When DOCX is requested, use document studio tools / /studio patterns under meetings/<slug>/.

Rules

Never invent quotes, attendees, speaker identities, or commitments.
Ambiguous actions become clarifying questions in the follow-up draft.
Prefer facts from the transcript; mark hypotheses explicitly.
Keep external email shorter and warmer than internal minutes.
Respect privacy: do not upload meeting content outside configured Navin providers.
Reuse meeting-followup and discovery-call-assistant when relevant.

---name: meeting-studiodescription: Run the Navin Meeting studio desk - capture notes/transcripts, custom summary templates, speaker labels, calendar-linked meetings, chat-with-meeting Q&A, exports, and local audit-aware reports. Use when the user opens---# Meeting studioPrivacy-first meeting desk inside Navin Studio (`#/meeting`, command `/meeting`).Transcription uses the user's configured Navin STT provider (prefer the highest-accuracymanaged/local model available). Summaries use their chat models and optional **customtemplates** from the Meeting workbench. Nothing is sent to a third-party meeting brand.## Inputs- Live or pasted transcript from the Meeting workbench- Speaker map (Speaker 1… or real names only when explicit in transcript)- Selected summary template instructions- Optional calendar event metadata (ICS import is local-only)- Chat-with-meeting questions (answer only from this meeting's evidence)- Raw notes / CRM context## Outputs (workspace)```textmeetings/<slug>/ transcript.md speakers.md summary.md minutes.md follow-up.md actions.md discovery.md chat.md audit.md export.docx # when /studio document export is requestedmeeting-report-YYYYMMDD-HHMMSS.html```## Workflow1. Confirm language, template instructions, attendees/speakers if known.2. High-accuracy cleanup of ASR when asked - never invent words or speakers.3. If speaker identification is requested: label turns; use Speaker N when names are unknown.4. Extract: decisions ≠ discussion ≠ actions (owner + deadline required).5. Apply the selected template for summary/minutes.6. For chat-with-meeting: answer only from transcript/notes; append Q&A to `chat.md`.7. Draft follow-up email (human sends) and log CRM activity with the `crm` tool (`log_activity`) plus `crm-update-agent`.8. Ship `meeting-report-*.html` (PDF via File Preview export), open preview, critic-review gate.9. When DOCX is requested, use document studio tools / `/studio` patterns under `meetings/<slug>/`.## Rules- Never invent quotes, attendees, speaker identities, or commitments.- Ambiguous actions become clarifying questions in the follow-up draft.- Prefer facts from the transcript; mark hypotheses explicitly.- Keep external email shorter and warmer than internal minutes.- Respect privacy: do not upload meeting content outside configured Navin providers.- Reuse `meeting-followup` and `discovery-call-assistant` when relevant.

Frequently asked questions

Meeting Studio