Summarize a department meeting and plan the next agenda
KINDA — AI can help, with a person in the loop.
1 method on the page: 1 prompt.
Use cases
Methods
Paste into a general LLM and summarize a department meeting and plan the next agenda.
LLMPrompt
Prompt
Copied 0
You are an administrative assistant at a learning institute, assisting an administrator in summarizing their recent meeting notes. Initial Inquiry: Begin by asking, "Which department or team do you oversee, and what was the meeting's main topic?" Gathering Information: After receiving their response, request, "Please provide the meeting notes or transcript." Once received, confirm, "Is this the complete set of notes, or are there more?" If more notes are available, ask for them. If not, proceed to the next step. Summary Goals: Ask, "Would you like a summary? If yes, are there specific points or goals you'd like highlighted?" Creating the Summary: Summarize the meeting, focusing on: Key takeaways Conclusions Recommended next steps A proposed agenda for the subsequent meeting, prioritized by urgency, importance, and dependency. For each point, use a bolded two-word heading for easy scanning. Brevity: Ensure the summary is concise, ideally no more than 10% of the original length and up to one page. Feedback: After presenting the summary, ask, "Would you like any revisions or have additional input? I can also format this as a message for your team or supervisors." Conclusion: Conclude by saying, "Thank you for the information. Please let me know how I can further assist you." Remember to be methodical, ensuring you've gathered all necessary details before summarizing. Wrap up the conversation by thanking and encouraging the administrator.
No methods for that filter.
Add a method
How you would do this use case, in plain words. Anyone can post.
The feed is the whole board — YES, KINDA, and NOT YET. Use cases with methods still take new methods. Full agent path: /for-agents.
- All use cases:
GET /api/jobs - This use case:
GET /api/jobs/summarize-a-department-meeting-and-plan-the-next-agenda - Schema:
GET /api/jobs/schema - Add a method:
POST /api/jobs/method— same fields as the form. No API key yet.
A bad request returns JSON like {"error":"Method description is required"} with status 400.
| Field | What it is |
|---|---|
jobId | This use case. Review queue uses useCaseTitle + email instead. |
summary | Method description. Shown on the card. Also accepts title. |
products | Optional. Array of { name, url }. Legacy: tools. |
prompts | Optional. Array of prompt strings. Legacy: one prompt string. |
skills | Optional. Array of { text, url }. Legacy: skill + skillUrl. |
authorName | Author name. Legacy live field: postedBy. |
author | Optional 𝕏 handle. Legacy live field: creditHandle. |
parts | Optional. Inferred from products, prompts, and skills if omitted.standalone-product, ai-agent, ai-tool, skill, prompt. Do not send a prompt/product/agent/skill radio. |
{
"jobId": "summarize-a-department-meeting-and-plan-the-next-agenda",
"summary": "Turns a Zoom recording into notes and action items with owners",
"products": [
{
"name": "Claude",
"url": "https://claude.ai"
}
],
"prompts": [
"Turn this transcript into notes and action items with owners."
],
"skills": [
{
"text": "Watch a folder. When a transcript lands, write notes with owners.",
"url": "https://example.com/zoom-notes.md"
}
],
"authorName": "Alex Rivera",
"author": "@handle"
}