Skip to content
TrustedSkillsbeta
Back to all skills

Meeting Insights Analyzer

Checked
prorise-cool·vlatest·productivity

This skill analyzes meeting transcripts to extract key decisions, action items, and sentiment, boosting productivity & clarity.

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add prorise-cool/claude-code-multi-agent --skill meeting-insights-analyzer -a claude-code
  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

prorise-cool

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned prorise-cool/claude-code-multi-agent at 0dc13057c1.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Scanned
1 file, 314 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The Meeting Insights Analyzer skill extracts key information and insights from meeting transcripts. It can identify action items, summarize discussions, and highlight important decisions made during the meeting. This allows users to quickly understand the outcomes of meetings without having to review lengthy recordings or transcripts.

When to use it

  • Post-Meeting Summarization: Quickly generate a summary for team members who missed the meeting or need a refresher.
  • Action Item Tracking: Automatically identify and list action items assigned during the meeting, ensuring accountability.
  • Decision Documentation: Capture key decisions made in meetings for future reference and alignment.
  • Meeting Analysis: Gain insights into recurring themes, bottlenecks, or areas needing improvement based on multiple meeting transcripts.

Key capabilities

  • Action item extraction
  • Discussion summarization
  • Decision highlighting
  • Transcript analysis

Example prompts

  • "Analyze this meeting transcript and list all action items."
  • "Summarize the key decisions made in this meeting."
  • “What were the main topics discussed in this meeting?”

Tips & gotchas

The quality of the output depends heavily on the clarity and completeness of the meeting transcript. Ensure the transcript is accurate and includes speaker identification for best results.