From workiq-productivity
Extract action items with owners, deadlines, and priorities from meeting content
How this skill is triggered — by the user, by Claude, or both
Slash command
/workiq-productivity:action-item-extractorThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Parses Teams meeting chat messages for action-oriented language — commitments, assignments, and deadlines. Cross-references owners against the attendee list and assigns priority levels. Outputs a structured table ready for downstream recipes.
Parses Teams meeting chat messages for action-oriented language — commitments, assignments, and deadlines. Cross-references owners against the attendee list and assigns priority levels. Outputs a structured table ready for downstream recipes.
| Requirement | Details |
|---|---|
| WorkIQ CLI | User profile, meeting details, chat messages (read queries via ask_work_iq) |
| Input | Type | Description |
|---|---|---|
| meeting_identifier | string | Meeting title, keyword, or "latest" |
| date | string (optional) | Target date (defaults to today) |
workiq-ask_work_iq (
question: "What is my profile including display name and time zone? Also find the meeting matching '<meeting_identifier>' on <date> and list all attendees with their names and email addresses."
)
Extract: displayName, time zone, attendee list with names and emails.
workiq-ask_work_iq (
question: "Get all chat messages from the Teams meeting '<meeting subject>' held on <date>, including sender names and timestamps."
)
Scan messages for:
Match extracted owner names to attendees[] from Step 1. Flag any unresolved names.
| # | Description | Owner | Due Date | Priority |
|---|---|---|---|---|
| 1 | ... | ... | ... | P1/P2/P3 |
Return action items as structured data, plus inline display for the user.
| Error | Solution |
|---|---|
| No chat messages | Report "No meeting content found" |
| Unresolved owner names | List as "[Unresolved: partial name]" for user clarification |
| No deadlines mentioned | Mark all due dates as "TBD" |
Returns: structured action item list with owners, due dates, and priorities. Usable as input for downstream recipes.
This skill is invoked by recipes or orchestration agents — not directly by end users. To invoke it, supply the required inputs and ensure authentication is configured.
"sprint planning"), a partial title, or "latest" to target the most recent meeting."2026-03-03") to scope the calendar lookup. Omit to default to today.meeting_identifier (and optionally date) as inputs. The skill will execute Steps 1–7 automatically.{
"meeting_identifier": "sprint planning",
"date": "2026-03-03"
}
Output (sample):
| # | Description | Owner | Due Date | Priority |
|---|---|---|---|---|
| 1 | Update API docs with new endpoint schema | Firstname1 Lastname1 | 2026-03-07 | P2 |
| 2 | Fix login blocker bug before release | Firstname2 Lastname2 | 2026-03-04 | P1 |
| 3 | Review UX mocks when you get a chance | [Unresolved: Firstname3] | TBD | P3 |
{
"meeting_identifier": "latest"
}
The skill resolves today's date from the user profile time zone, finds the most recently concluded meeting, and parses its chat transcript for action items.
{
"meeting_identifier": "Q1 budget review",
"date": "2026-02-28"
}
The skill searches calendar events on February 28 for a meeting matching "Q1 budget review", fetches its Teams chat, and returns all commitments made — including any flagged with "ASAP" or "before end of quarter" language as P1 items.
npx claudepluginhub miyake-san/work-iq --plugin workiq-productivityCreates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
4plugins reuse this skill
First indexed Jul 17, 2026