Results for “meeting notes”

Drafts one issue of an internal newsletter from the items the user provides (notes, messages, snippets, meeting outputs, contributor submissions): a running order with the reason for each position, a factual headline and one paragraph per item with its source line, one call to action per item with date and route, two subject-line options, an item register accounting for every item supplied, and a list of items that need an owner's confirmation before send. Use when the user asks to "draft this month's newsletter", "turn these items into the team update", "write the staff bulletin from these notes", "order and headline these items" or "prepare the internal digest". Do not use for one piece of news that needs its own send, use announcement-drafter instead; for a digest of external news, use news-monitor-digest; for a personal weekly status note, use weekly-status-update-writer. Drafts for human review; never approves, authorises or signs off.

The English summary is being prepared. Showing the original description.

Search personal knowledge bases, notes, docs, and meeting transcripts locally using qmd — a hybrid retrieval engine with BM25, vector search, and LLM reranking. Supports CLI and MCP integration.

The English summary is being prepared. Showing the original description.

Set up recurring work in Claude Code by combining persistent memory, scheduled prompts, task queues, and optional computer control. The skill explains how to connect these components, including external scheduling for work that continues after a session closes.

• Reviewing pull requests at regular intervals
• Collecting and summarizing research findings daily
• Preparing meeting notes from saved context

Search and update Notion pages and databases, read or write Markdown, and upload files through the API or ntn CLI. Also build Workers, programs hosted by Notion, for scheduled syncing, agent tools, and incoming events.

• Saving meeting notes as a Notion page
• Finding database items by status
• Uploading images and documents

Present clear choices when a task needs a human decision, then pause execution until the user replies. This reusable interaction pattern supports filing decisions, priority selection, and confirmation before destructive actions, with an option to decline.

• Clarifying requests with several possible meanings
• Confirming before bulk deletion or overwriting
• Choosing where to file meeting notes

Prepare a personal knowledge base for team sharing by removing compensation, performance assessments, personal details, and other sensitive content. The skill checks pages and searchable records, verifies the cleaned material, and addresses sensitive Git history with explicit confirmation.

• Creating a shared team knowledge base from personal notes
• Auditing an existing shared knowledge base
• Checking sensitive content before onboarding team members

Create and update person or company pages in gbrain using existing knowledge and external sources. Organize cited facts, dated events, and relationships, while adjusting research depth to importance and flagging contradictions without overwriting user assessments.

• Create a substantive page for a new business contact
• Update company records after funding or leadership changes
• Add people and company context from meeting notes

Review a sales opportunity using deal records, emails, and meeting notes. Get an evidence-based assessment of closing likelihood, missing information, risks, and prioritized next steps, with a comparison against the stage recorded in your sales system.

• Assess whether a deal is likely to close
• Check whether the recorded sales stage matches the evidence
• Identify missing information before a sales review

Build a single brief on an existing customer using available sales records, emails, documents, call notes, and internal chat. Understand the current situation, key contacts, recent discussions, and gaps that may need attention.

• Preparing for a meeting with an existing customer
• Catching up on an account during a handover
• Reviewing recent discussions and stalled opportunities

Organize Confluence documentation with clear page hierarchies, reusable templates, and access plans. Create and update pages, embed Jira reports, and audit existing content to identify outdated material and establish review responsibilities.

• Restructure a team's Confluence space
• Standardize meeting notes and decision logs
• Embed Jira issues and charts in documentation

Organize Confluence team wikis and project documentation with clear page hierarchies, labels, and templates. Use macros, built-in content tools, to assemble indexes and reports, with REST API guidance for creating and updating pages.

• Reorganizing a team wiki
• Building an index of decisions and runbooks
• Standardizing recurring meeting notes

Organize Notion workspaces with clear page structures, connected databases, and reusable templates. Build team wikis and task views, reduce duplicated content, and use the Notion API to automate page creation, database queries, and content updates.

• Organizing a team wiki so information is easier to find
• Creating templates for meeting notes and project briefs
• Connecting project databases with filtered views

Connect AI agents to Jira and Confluence through MCP, a protocol for accessing external tools. This skill guides issue searches and updates, page management, sprint workflows, authentication setup, and troubleshooting of Atlassian integrations.

• Find Jira issues by assignee or status
• Search and update Confluence pages
• Turn meeting notes into Jira ticket updates

Turn meeting notes, research, and business feedback into a one-page decision memo. Present a clear recommendation with confidence, supporting facts, option comparisons, risks, and next steps so decision-makers can assess the choice quickly.

• Preparing a product strategy decision
• Comparing options for budget approval
• Briefing leaders on an urgent risk

Convert Markdown into Word, PDF, and HTML using a workflow suited to the document. Simple files use direct delegation, while documents with special characters use separate conversion steps, character replacement, and output checks.

• Creating a simple Word document from meeting notes
• Exporting one document to several formats
• Converting documents containing special characters to PDF

Search the vault using QMD semantic search. Use PROACTIVELY before reading files. Preference order: (1) MCP tools — mcp__qmd__query, mcp__qmd__get, mcp__qmd__multi_get, mcp__qmd__status — if they appear in your tool menu, use them first; (2) CLI `qmd --index <name> ...` as fallback; (3) Grep/Glob only when QMD is not installed. Trigger proactively for past decisions, incidents, people, meetings, architecture, patterns, or any vault content — and after creating/editing notes to check for duplicates and related content.

The English summary is being prepared. Showing the original description.

Chinese-first academic Word and PowerPoint workflow for paper reading reports, thesis or group-meeting PPTs, editable DOCX/PPTX generation, Office file inspection, template matching, speaker notes, and layout quality checks. Use when the user asks to read papers into Word reports, create or polish PPT/PPTX, convert paper/thesis materials into slides, edit DOCX/PPTX, inspect Office files, or produce Chinese academic presentation/report deliverables. Preserve English paper titles, formulas, variable names, software commands, and references.

The English summary is being prepared. Showing the original description.

Pressure-tests a decision, plan, or idea before it is committed to — surfacing the assumption it rests on, the case against it, and what would have to be true for it to work. Use this when weighing options, when a plan needs challenging before commitment, when you have already decided and want a genuine gut check, when processing meeting notes into decisions, or when competing initiatives need ranking. Distinct from `chief-executive`, which owns direction; this one interrogates a specific decision.

The English summary is being prepared. Showing the original description.

Keeps the engagement record for client work. Use when they name a client or stakeholder. Use when they debrief a meeting or paste notes. Use when they ask what was agreed. Use when they run a POC, change the client's codebase, prove it on their staging, go live, or need evals before a model acts. Use when they prep a readout, when trust shifts, or they say @fde. Route and run the local fde CLI (or npx --yes fdeops). Never ask them to type commands. Not for ordinary code edits in an unbound repo.

The English summary is being prepared. Showing the original description.

Turn meeting notes or a transcript into sourced decisions, changes and next actions. Use after a customer conversation; review consequential record updates before saving.

The English summary is being prepared. Showing the original description.

RAID log methodology with decision extraction from emails and meeting notes. Use when asked to identify risks, log assumptions, track issues, extract decisions from correspondence, create or update a RAID log, escalate a risk to an issue, assess project risks, validate or challenge assumptions, or capture scope-relevant decisions. Also triggers when the user pastes email chains and asks what decisions were made, or needs to find buried decisions and untested assumptions in correspondence. Trigger on: 'risk report', 'RAID log', 'what are the risks', 'what decisions were made', 'update the risk register', 'what assumptions are we making', 'what could go wrong', 'flag any issues', 'extract decisions from these emails'.

The English summary is being prepared. Showing the original description.

When you paste raw human input — a call transcript (Grain, Zoom, Granola, Fathom), a text or email from a client/partner/friend, a voice-memo dump, or meeting notes — and want it converted into structured work. Extracts decisions, action items (yours vs theirs), bugs/feature requests, and facts worth keeping; files GitHub issues in the right repo, captures to the second-brain vault, and drafts (never sends) the reply. Triggers on "/ingest", "ingest this", "here's my call with X," "here's the transcript," "this is from [person]," "[person] asked me this," "from [person]:", a pasted transcript with speaker labels, or a forwarded client message that clearly expects processing. Person→project routing lives in a private config; unknown senders get asked about once, then remembered.

The English summary is being prepared. Showing the original description.

Generate templated stakeholder communications from project context. Use when someone asks to "write a go-live email", "create a status update", "onboard someone", "write an announcement", "steerco update", "incident summary", "change notification", or any stakeholder communication task. Reads project memory, stakeholder directory, PRD, and meeting notes to pre-fill real names, dates, and context. Produces ready-to-send Markdown.

The English summary is being prepared. Showing the original description.

Systematic framework for extracting actionable items from documents and organizing them into prioritized, trackable checklists. Use when converting reports, meeting notes, audits, or any document with embedded action items into structured TODO lists.

The English summary is being prepared. Showing the original description.