For us, the bottleneck wasn’t the meetings — it was everything after. Transcribing notes, cleaning them up, posting to the Asana project, and manually creating follow-up tasks was taking 30–60 minutes per session. With at least six cross-functional meetings a week, that’s up to six hours of overhead that often didn’t happen at all, leaving Asana out of date and action items untracked. We built a custom skill in Claude Cowork to fix it, and now the whole workflow takes five minutes.
What the skill does
After a meeting ends, Claude pulls the transcript directly from Teams via the calendar event and runs through a set workflow:
- Identifies speakers by cross-referencing our team roster — our Teams transcripts come through with anonymous tags, not names.
- Drafts a structured summary with topic sections, decisions, owners, and dates.
- Shows us the draft for review and approval before anything is posted.
- Posts the approved meeting notes as a project status update in Asana, with a status color, so the project reflects what happened without anyone having to write it up manually.
- Creates individual tasks in the project for each action item — no copy-pasting from notes, no manual entry.
Why this matters for Asana specifically
The skill knows our Asana setup — project structure, section conventions, and task format — so nothing lands in the wrong place or needs cleaning up after the fact. Action items go in as subtasks under the meeting notes task, which keeps the project tidy and makes it easy to see what came out of any given meeting. The status update means the project health is always current, not just when someone remembers to post one. Before this, manual task creation was the step that got skipped most often. Now it’s automatic, and Asana actually reflects what’s happening — which is the whole point.
Why we built it as a custom skill
A generic summarizer doesn’t know our internal terminology, product lines, or team structure. Our skill is backed by a CLAUDE.md knowledge base with our people, acronyms, and active projects baked in. That context is what makes speaker identification accurate and Asana task routing reliable. It also improves with each meeting as it refines what it knows.