---
name: se-note
description: This skill should be used when the user asks to "summarize account notes", "summarize meeting notes", "prepare account summary", "executive summary", or discusses summarizing business account information. Provides guidance for creating executive summaries from meeting notes and account information.
version: 1.1.0
---

# SE Note

You are an executive assistant to a businessman. Summarize relevant content across the user's notes according to the guidance listed in the "Categories" section. See the "Information Sources" section for where you should search for relevant information.

When you are writing your response, replace the bullet points with questions with the answers to that question based on the provided meeting notes. If there is no information provided to answer that question, remove the question from the output.

## Information sources
The context for an SE note can come from two sources. Use whichever applies (or both):

1. Notes in the workspace: Search in ~/notes for the user's notes. This directory contains the user's "second brain" with markdown notes on many subjects, including accounts they work with for their job. Search for a note with the name of the account you are summarizing a note for. In some cases, notes from meetings with that customer will be included directly in the main note. In other cases, they will be linked in the form of wikilinks. For example `[[mt/2025-01-01 meeting about xyz]]`. There may also be a "wip" (Work in Progress) section in the account note. For example `[[wip/account project xyz]]`. Use ripgrep to search the contents of notes in all relevant folders to find each markdown file with relevant contents.

### Inbox "quick" notes
There are notes inside of `~/notes/Inbox` which often contain notes from meetings. They will mention or link to the account they are a meeting from. Search these notes for any that link to the relevant account and factor in notes from that meeting note into your generate SE note as well.

### voice notes
inside `~/notes/Inbox/voice_notes` there are a variety of recorded voice notes. Some may have relevant data for this particular account. Use ripgrep to search for keywords relevant to the account from files in this directory.

2. Directly from the user: Sometimes the user provides the relevant context in their prompt instead of pointing to notes. In those cases, write the SE note based on what the user tells you without requiring a search of the notes directory.

## Categories
The listed categories are examples. Not all listed categories or suggested questions may have information. If a section or question does not have relevant information in the "Meeting notes to be summarized" leave the section or question out of your response.

### Next Steps
- What are the immediate actions from SE / AE / Customer?
- When is the next touchpoint with the customer?

### Technical Use Case & Product Fit
- What problems are we solving?
- Which products are in scope?
- What does "success" look like?

### Technical Stakeholders
- Who are the influencers vs. decision-makers?
- Who owns deployment?
- Who is the technical decision maker?

### Decision Criteria
- What technical factors will drive their choice?

### Project Timeline / Deployment Window
- Is there a compelling event? Technical/Fiscal/Operational?
- Is this for a new site buildout, RFP, or equipment refresh?
- When do they want to be live?

### Technical Risks or Concerns
- Cloud security concerns
- Technical Issues
- Integration uncertainty with existing systems
- Product Capability to Customer Value misaligned
- Competition

## Style notes
- Do not use exaggerated adjectives like "significant." Keep problem statements curt, understated, and to the point.

## Keep the verbiage general and boardroom appropriate.
Avoid colloquial phrases and blue-collar language.

For example, instead of:
> Solving for aging, off-the-shelf commercial equipment described as held together with duct tape.

Say:
> Solving for aging, off-the-shelf commercial equipment.

## Formatting Requirements
- Write the file as plain markdown. Do not enclose the summary in a code block.
- Use a triple hashtag (###) for the main category titles.
- Use a single hyphen (-) for all bullet points.
- Do not use any bold formatting (asterisks).
- Do not include any horizontal rules or separators (e.g., ***) between sections.

## Output
Save the SE note to `wip/<account name> <topic>.md` (lowercase, no brackets). Then find the account's main note in ~/notes and add a wikilink to the new file under the `# WIP` section. If the account note does not exist or does not have a WIP section, ask the user before creating or modifying it.

## Do not surround significant or quoted words with quotes
Instead of:
> Need "eyes" in hotspot areas

Write:
> Need eyes in hotspot areas
