meeting-feedback
Post-meeting effectiveness feedback and continuous improvement
npx skills add majiayu000/claude-skill-registry --skill meeting-feedback --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Evaluates meeting effectiveness and identifies improvements. Provides both a quick feedback path and a full, step-by-step assessment for high-stakes or recurring meetings, including details on meeting outcomes, scoring across multiple dimensions, and concrete recommendations for future sessions.
How it works
- The agent asks for essential meeting details: Meeting name, Date, Duration, Attendees, Owner, and a yes/no/partially on whether the goal was achieved.
- It separates into two modes: Quick Feedback for post-meeting notes and Full Feedback for deeper analysis.
- Full Feedback proceeds through numbered steps:
- Gather Meeting Details (name, date, duration, attendees, owner).
- Assess Objectives (original purpose, whether the goal was achieved, blockers if not).
- Apply Effectiveness Scoring across five dimensions (Preparation, Time Management, Participation, Decisions, Action Items) with explicit anchors and prompts.
- Identify What Worked and What Didn’t, with structured sections and actionable fixes.
- Detect Meeting Smells from a checklist and suggest fixes.
- Provide Recommendations for Next Time with Must Change, Should Change, and Could Change sections.
- Decide on Meeting Continuation with options and potential changes to frequency, duration, attendees, and format.
- Optional Team Retrospective escalation if trends indicate systemic issues, including a dedicated format for a Team Meeting Retrospective.
- Output formats include a Markdown report template and an overall numeric score, with an “Overall Score” derived from the averages in the dimension scores.
- The Skill references integration with other skills (e.g., /meeting-agenda, /meeting-notes, /meeting-cleanup) for end-to-end meeting lifecycle support.
When to use it
- After high-stakes or recurring meetings to diagnose effectiveness.
- Immediately after important meetings (within 10 minutes) or during team retrospectives on meeting culture.
- When a meeting felt unproductive or for cadence improvement in recurring meetings.
What it can touch
- The skill uses the provided meeting details to populate a structured report and does not perform external actions unless those tools are invoked via the described prompts.
- It references attached templates and the option to include trend analysis by comparing against outputs stored in outputs/meeting-notes/.
Caveats
- The evaluation relies on the input data; inaccurate details yield correspondingly inaccurate assessments.
- For recurring meetings, trend analysis requires access to prior feedback files stored under outputs/meeting-notes/ and consistent naming conventions.
- The scope is constrained to post-meeting analysis and recommendations; it does not guarantee implementation of changes.
## Quick Start Tell me: 1. **Which meeting are you rating?** (name, date, and who ran it) 2. **Did it achieve its goal?** (yes/no/partially) 3. **What's the one thing you'd change?** I'll walk you through a structured evaluation, score the meeting across 5 dimensions, check for trends if this is a recurring meeting, and give you specific recommendations. **Shortcut:** `/meeting-feedback [meeting name] -- 3/5, pre-read was late` -- and I'll build the full assessment. --- # Meeting Feedback Skill Evaluate meeting effectiveness and identify improvements. Quick retrospective to make future meetings better. ## When to Use This Skill - Immediately after important meetings (within 10 minutes) - After recurring meetings (to improve cadence) - When a meeting felt unproductive (diagnose what went wrong) - For team retrospectives on meeting culture ## Quick Feedback Use after any meeting: ``` Meeting: [Meeting name] Date: [Date] ⭐ Rating: [1-5 stars] What worked: - [One thing that was effective] What didn't: - [One thing that was wasteful] One change for next time: - [Specific improvement] ``` ## Full Feedback Use after high-stakes or recurring meetings: ### Step 1: Meeting Details ``` Meetin
- Quick Start
- When to Use This Skill
- Quick Feedback
- Full Feedback
- Step 1: Meeting Details
- Step 2: Objectives Assessment
- Step 3: Effectiveness Scoring
- Step 4: What Worked
- Step 5: What Didn't Work
- Step 6: Meeting Smells
- Step 7: Recommendations
- Step 8: Meeting Continuation Decision
- Output Format
- When to Trigger a Team Retro
What does the meeting-feedback skill do?
Post-meeting effectiveness feedback and continuous improvement
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill meeting-feedback --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.