meetings

Evaluate meetings from transcripts or descriptions and recommend improvements.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/imsus/cto --skill meetings-imsus
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: meetings
Source: https://github.com/imsus/cto/tree/main/.agents/skills/meetings
Command: npx skills add https://github.com/imsus/cto --skill meetings-imsus

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The meetings skill helps engineering managers stop wasting team focus on unnecessary or poorly run meetings by deciding what to keep, kill, shorten, or redesign—and by diagnosing what went wrong in a specific meeting.

Core Features & Use Cases

  • Meeting decision support: Determine whether a request should be a meeting, an async doc, a shortened session, or a redesign based on meeting type (decision, problem-solving, buy-in, or information sharing) and whether the decision-maker is present.
  • Practical facilitation guidance: Create a written agenda, ensure preparation happens ahead of time, keep discussion on track, drive toward an actual decision, and end with clear follow-through.
  • Focus-time protection: Reduce calendar fragmentation by batching, shortening by default, and scheduling outside high-productivity windows to minimize maker-block disruption.
  • Recurring meeting cleanup: Identify and remove rituals that have outlived their purpose, including a quarterly “Why are we still doing this?” review habit.
  • Meeting review from transcript or description: Evaluate the meeting across purpose, attendance, preparation, facilitation, and follow-through, then recommend one or two concrete improvements.

Quick Start

Tell the AI: “I’m drowning in meetings and engineers can’t focus—help me reduce them and redesign my recurring syncs.”

Frequently Asked Questions about meetings

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I reduce unnecessary meetings and protect engineering focus time?▼

To reduce unnecessary meetings and protect engineering focus time, evaluate each request to decide if it should be a meeting, an async doc, a shortened session, or a redesign. Batch calendars and schedule outside high-productivity windows to minimize maker-block disruption.

How do I decide if a meeting should be async communication instead?▼

Decide if a meeting should be async communication by identifying the meeting type, such as decision, problem-solving, buy-in, or information sharing, and verifying whether the decision-maker is present. If not, convert the request into an async document alternative.

What is the best way to clean up recurring engineering manager syncs?▼

The best way to clean up recurring engineering manager syncs is to perform a quarterly meeting review asking why the ritual still exists. Identify and remove meetings that have outlived their purpose to shrink and batch calendars effectively.

How do I evaluate a meeting from a transcript to improve facilitation?▼

Evaluate a meeting from a transcript by diagnosing its purpose, attendance, preparation, facilitation, and follow-through. Recommend one or two concrete improvements to create a written agenda and ensure actual decisions are reached with clear follow-up mechanisms.

Can I get a specific operating plan for meeting management decisions?▼

Yes, you can get a specific operating plan for meeting management decisions. The output covers the meeting decision, purpose, agenda or async alternative, required participants, and the follow-up mechanism to drive toward an actual decision.