Mt daily standup
Skill MeisterLabs/meister-mcp-skills/skills/mt-daily-standup
Agent skills for the MeisterTask and MindMeister MCP servers
npx -y skills add MeisterLabs/meister-mcp-skills --skill mt-daily-standupAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Summarize what you worked on yesterday and what's planned for today from your MeisterTask activity.
SKILL.md
1.4 KB, as published. Nobody here has run it
Daily standup summary
Use the MeisterTask MCP to generate a standup-ready summary from your MeisterTask activity.
Workflow
- Identify the relevant projects:
- Use
mt_search(withtypes: ["TASKS", "PROJECTS"]) to surface recently active items, or ask the user directly which projects to include. - Ask the user to confirm which 1–3 projects to include rather than scanning all of them.
- Use
- Fetch recent activity:
- Use
mt_tasks_liston each confirmed project to find tasks updated or completed in the last 24 hours. - Note:
mt_tasks_listcan time out on projects with 200+ tasks — if this happens, usemt_searchfiltered by project ID instead.
- Use
- Fetch today's and upcoming tasks:
- From the task lists, filter for tasks due today or overdue. Alternatively, use
mt_tasks_searchfiltered by due date for large projects.
- From the task lists, filter for tasks due today or overdue. Alternatively, use
- Draft the standup summary:
- Yesterday: tasks completed or progressed (with task name and project context)
- Today: tasks due today or planned next
- Blockers: overdue tasks or open questions (only if found)
- Keep it concise — no more than 5 bullets per section. Offer to post it or copy it.
Important
If no recent activity is found, say so clearly rather than inventing items. Ask the user to confirm the summary before they send it.