harperreed

Use when evaluating, designing, or pressure-testing the business model of an AI agent product. Triggers on "agent business model", "agent economics", "agent canvas", "evaluate agent product", "agent pricing", "agent unit economics", "agentic business", "AI agent company", "agent cost structure".

Use when someone wants to launch a content brand from scratch on any platform. Triggers on "launch a channel", "start a YouTube channel", "build a podcast", "start a newsletter", "content brand", "creator launchpad", "build my audience", "start creating content", "grow on TikTok", "start a blog".

Use when you have an existing pipeline DOT file that needs review, fixing, or validation. Use when validation produces warnings or errors, when a DOT file was hand-written or generated by another tool, or when you want to verify a pipeline covers 100% of a spec before running it.

Use when you want to build a project but don't have a spec yet and need to brainstorm the idea into a design doc structured for pipeline DOT generation. Use when starting from a vague idea, project concept, or feature request that needs to become a headless autonomous build pipeline.

Use when you have a spec, design doc, structured plan, or prompt_plan and need to generate a pipeline Graphviz DOT file for headless autonomous building. The agent reads the spec, extracts build pipeline phases, determines tech stack, asks about human gates and model preferences, generates a validated DOT digraph with rich self-contained prompts, and saves it to the project root. Handles any language or framework.

Use when a pipeline DOT file has passed structural validation but may still have flow inefficiencies, spec fidelity gaps, or information loss in prompts. Use after dotfile-audit or dotfile-from-spec when you want to deeply verify a pipeline captures everything from the original spec. Use when prompts might be missing critical domain rules, data models, or invariants.

Use when the user asks to check on agents, manage their fleet, babysit panes, see what needs attention, get a status report, or when they say "check on my agents", "what needs action", "fleet status", "babysit", "brief me". Requires the control MCP server to be registered and the daemon running.

Use when asked to import, sync, or add Granola meeting notes into the Obsidian vault. Triggers on "meeting notes", "Granola", "import meetings", "add notes from this week", or any request to move meeting content into Obsidian.

Manage calendar events, check conflicts, handle scheduling from emails. Use when adding events or coordinating meetings to ensure proper timezone handling and conflict detection.

Manage contacts, companies, deals, and relationships. Use when adding contacts, logging interactions, or working with CRM data to prevent duplicates and maintain data quality.

Handle email tasks (checking inbox, drafting replies, managing threads, adding events to calendar). Use when working with emails to prevent common mistakes like broken threading or missing recipients.

Set up your personal productivity style and preferences. Use when you first install office or want to customize your workflow patterns.

Browse and read blog posts on harper.blog

Subscribe to harper.blog via RSS for recent posts

Discover all URLs on harper.blog via XML sitemap

Search and retrieve Granola meeting transcripts using the muesli CLI. Use when the user asks about past meetings, wants to find what was discussed, look up meeting details, or reference meeting transcripts.

Task and todo management - add todos, manage projects, track completion. Use when the user wants to create, list, or manage tasks and todos.

Activity and accomplishment logging - track what was done and when. Use when the user completes something significant, wants to log an activity, or asks what they did recently.

Semantic memory and context - store and retrieve information with embeddings for similarity search. Use for long-term memory, context recall, and knowledge persistence.

Push notifications via Pushover - send and receive notifications. Use when the user wants to send alerts or check notification history.

Location tracking - log positions, view timelines, track entities. Use when the user mentions locations, coordinates, or wants to track where something/someone is.

RSS feed reader and article tracking - manage feeds, read articles, track reading progress. Use when the user discusses RSS feeds, articles, or reading lists.

Note-taking and knowledge capture - create, search, and manage notes with tags. Use when the user wants to save information, take notes, or recall saved content.

Bulletin board for threaded discussions - create topics, threads, and messages. Use for Q&A, discussions, or leaving notes for other agents/humans.