How do I install the Meeting Master skill?

Run npx skillmds@latest add garphengate/meeting-master 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 Master safe to use?

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

Which AI agents work with Meeting Master?

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 Master free to use?

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

Who published Meeting Master?

GarphenGate (@garphengate) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Meeting Master by garphengate — Agent Skill

Name: Meeting Master
Author: GarphenGate

File contents

Meeting Cost Counter

Free gateway skill from the Meeting Master bundle by GarphenGate.

Put a price tag on the recurring meeting and then ask the only question that matters: would you buy this outcome at this price?

Procedure

Collect the inputs: attendee count, duration, frequency, and (optionally) a rough average hourly cost. If the user declines to estimate cost, use attendee-hours alone; never insist on salary data.
Compute the bill: attendee-hours per occurrence, per month, per year; multiply by hourly cost if provided. Show the arithmetic in one line so it is checkable.
Audit the return. Ask what the meeting produced in its last three occurrences: decisions, unblocked work, or coordination that prevented a concrete problem. "Alignment" without an example counts as nothing.
Render a verdict: EARNS IT (keep as is), RESTRUCTURE (halve duration, halve frequency, or cut the attendee list; state which and why), or KILL (recommend cancellation with a one-line replacement, usually a doc or an async update).
Draft the change note if the verdict is RESTRUCTURE or KILL: two sentences the user can send to attendees, framed on respect for their time.

Output

MEETING COST — <meeting>
BILL: <n> people x <m> min x <freq> = <hours>/yr (~$<x>/yr if cost given)
RETURN (last 3): <what it produced, or "nothing concrete">
VERDICT: EARNS IT | RESTRUCTURE (<change>) | KILL (replace with <alternative>)
DRAFT NOTE: "<two sentences>"

Rules

Never inflate or guess salary figures; without user-provided cost, report attendee-hours only.
Never verdict KILL on a meeting the user does not own without framing the draft as a proposal to the owner.
"It's always been on the calendar" is not a return; verdicts rest on produced outcomes only.

Degradation

If the user cannot recall what the last three occurrences produced, that fact is itself the finding: verdict RESTRUCTURE at minimum, and suggest attending the next occurrence with a one-line log to settle the question.

Like this? This is the free gateway skill for Meeting Master by Moltline Studio. The paid listing: https://www.agensi.io/skills/meeting-master-persona

---name: meeting-masterdescription: Estimate what a recurring meeting really costs in attendee-hours and money, and judge whether it earns it; use before accepting or renewing any recurring invite.---# Meeting Cost Counter*Free gateway skill from the Meeting Master bundle by GarphenGate.*Put a price tag on the recurring meeting and then ask the only question that matters: would you buy this outcome at this price?## Procedure1. **Collect the inputs:** attendee count, duration, frequency, and (optionally) a rough average hourly cost. If the user declines to estimate cost, use attendee-hours alone; never insist on salary data.2. **Compute the bill:** attendee-hours per occurrence, per month, per year; multiply by hourly cost if provided. Show the arithmetic in one line so it is checkable.3. **Audit the return.** Ask what the meeting produced in its last three occurrences: decisions, unblocked work, or coordination that prevented a concrete problem. "Alignment" without an example counts as nothing.4. **Render a verdict:** EARNS IT (keep as is), RESTRUCTURE (halve duration, halve frequency, or cut the attendee list; state which and why), or KILL (recommend cancellation with a one-line replacement, usually a doc or an async update).5. **Draft the change note** if the verdict is RESTRUCTURE or KILL: two sentences the user can send to attendees, framed on respect for their time.## Output```MEETING COST — <meeting>BILL: <n> people x <m> min x <freq> = <hours>/yr (~$<x>/yr if cost given)RETURN (last 3): <what it produced, or "nothing concrete">VERDICT: EARNS IT | RESTRUCTURE (<change>) | KILL (replace with <alternative>)DRAFT NOTE: "<two sentences>"```## Rules- Never inflate or guess salary figures; without user-provided cost, report attendee-hours only.- Never verdict KILL on a meeting the user does not own without framing the draft as a proposal to the owner.- "It's always been on the calendar" is not a return; verdicts rest on produced outcomes only.## DegradationIf the user cannot recall what the last three occurrences produced, that fact is itself the finding: verdict RESTRUCTURE at minimum, and suggest attending the next occurrence with a one-line log to settle the question.---*Like this? This is the free gateway skill for **Meeting Master** by Moltline Studio. The paid listing: https://www.agensi.io/skills/meeting-master-persona*

Frequently asked questions

Meeting Master