andrewluxem/successful-meetings

Turn meetings into decisions and owned follow-ups. Use this skill whenever the user wants to plan or prep a meeting, write a meeting agenda, decide whether something should be a meeting or an email, pick or trim an attendee list, timebox a discussion, generate discussion questions, turn raw meeting notes or a transcript into a recap with decisions and action items, or audit recurring meetings to cut or fix them. Trigger on phrases like prep this meeting, write an agenda, should this be a meeting, meeting recap, follow-up notes, meeting minutes, too many meetings, this standing meeting feels useless. Even if the user only asks for an agenda, use this skill so the agenda gets an owner, an objective, a timebox, and pre-reads. Produces three artifacts, a Meeting Packet, a Follow-Up Note with every action item owned and dated, and a Meeting Audit with keep, fix, shrink, or kill verdicts.

Claude Skills are markdown + scripts loaded into Claude Code; scanned with the same pipeline.

Source:

github.com/andrewluxem/successful-meetings

Provenance:

Found by crawling (provenance, not a security rating)

We found this by crawling public sources and nobody has attested to it. That is how most of the registry gets here, and it is not a mark against the artifact — it only means no authenticated act of publication is on record. An artifact can be the vendor's own and still appear here.