OpenPot Awareness

---

name: openpot-awareness description: Teaches this agent how to serve content to the OpenPot iOS client — cards, apps, page captures, calendar, voice, chat persistence, and onboarding emoji: 🫕 version: 6.0.0 homepage: https://openpot.app

---

OpenPot Awareness Skill

You are connected to OpenPot — a native iOS app that serves as a command center for AI agents. OpenPot has configurable tabs: Chat (always on), Pulse (notification cards), Calendar, Apps, Terminal, and Agents (always on). Users choose which tabs to display in Settings — not every user will have all tabs visible.

Three Output Surfaces

| Surface | When to use | How | |---------|-------------|-----| | Chat | Default. Conversations, answers, follow-ups. | Normal chat response | | Pulse cards | Proactive output: reports, alerts, briefs. | POST /api/cards | | Web apps | Persistent tools the user returns to. | Build HTML, serve via /api/apps |

Default to chat. Use cards for output the user did not ask for in the current conversation. Use apps only when the user requests a persistent tool.

Decision Framework — Chat vs. Card vs. App

| Situation | Surface | Why | |-----------|---------|-----| | User asked a question | Chat | They're in a conversation. Answer there. | | Cron job produced output | Card | User didn't ask. Push it to Pulse. | | Alert threshold crossed | Card | Proactive. User needs to know. | | User asked for a persistent tool | App | They want something that lives in their toolkit. | | User asked about a previous card | Chat | They're referencing it in conversation. | | Scheduled digest or rollup | Card | Proactive summary, not a conversation. |

When in doubt, use chat. Cards and apps are for specific use cases.

Triggers

Activate this skill when:

User says "OpenPot sync" — run the sync process (see Sync section)

User sends a page capture (message contains

---PAGE CAPTURE CONTEXT---) — see Page Captures section

User asks about setting up OpenPot — see Onboarding section

User asks about calendar, voice, chat persistence, or

building an app — see the relevant section below

User asks "what OpenPot features do I support?" — check status

User asks to "set up chat persistence" or "save my chats" —

see Chat Persistence section

---

Pulse Cards

Pulse cards are proactive notifications you push to the user's OpenPot app. They appear in the Pulse tab as a card stream.

When to Create a Card

Scheduled output (cron jobs): morning briefs, DCA signals, health checks

Threshold alerts: a metric crossed a boundary the user cares about

Proactive observations: something changed that the user should know

Digests: summaries of activity over a time period

Do NOT create a card for content the user asked for in the current conversation. That belongs in chat.

Card API

Endpoint: POST /api/cards

Required fields:

| Field | Type | Description | |-------|------|-------------| | title | String | Card headline. Under 60 characters. | | body | String | 1-2 line summary visible on the compact card. | | category | String | Determines Pulse channel routing. Use canonical list below. | | agent_id | String | Your agent ID. |

Optional fields:

| Field | Type | Description | |-------|------|-------------| | priority | String | "normal" (default) or "high". Reserve high for genuinely urgent items. | | origin | String | Why this card was created: "cron", "alert", "agent_initiated", "announce". | | expanded_body | String | Full markdown report. When present, the card is tappable and opens a detail view. | | actions | [String] | Action buttons in the detail view. Vocabulary: "discuss", "dismiss", "acknowledge", "snooze". |

Body Text Rule

The body field is ALWAYS a complete thought. Never a sentence fragment that leaves the user wondering what the rest says. If the body is cut off mid-sentence, the card feels broken.

Short notifications (1-2 lines): write the complete message

Medium content (4-10 lines): write the full text — OpenPot unfolds it inline

Reports with tables/sections: keep body as 1-2 line summary, put detail in expanded_body

Minimal Card Example

{
  "title": "System Health Check",
  "body": "All services operational. CPU 23%, memory 41%.",
  "category": "system",
  "agent_id": "your-agent-id",
  "priority": "normal",
  "origin": "cron"
}

Report Card Example (with expanded detail)

{
  "title": "Weekly DCA Signals",
  "body": "5 double-down signals, 4 baseline holds.",
  "category": "finance",
  "agent_id": "your-agent-id",
  "priority": "normal",
  "origin": "cron",
  "expanded_body": "## Weekly DCA Signal Report\n\nGenerated: Monday 4:30 PM ET\n\n| Ticker | Price | Signal | Conviction |\n|--------|-------|--------|------------|\n| CRCL | $2.14 | Double-down | High |\n| AFRM | $41.30 | Double-down | Medium |\n\n4 baseline holds. Market weakness = accumulation window.",
  "actions": ["discuss", "dismiss"]
}

Canonical Category List

Use these exact strings. Inconsistent casing or synonyms create duplicate channels.

| Category | Use for | |----------|---------| | briefing | Morning briefs, evening summaries, weekly rollups | | system | Health checks, service status, uptime reports | | finance | DCA signals, portfolio updates, market observations | | calendar | Schedule digests, conflict alerts, deadline warnings | | projects | Task updates, milestone tracking, blockers | | education | Learning content, research summaries | | health | Health tracking, medication reminders | | entertainment | Media recommendations, leisure suggestions |

You may create new categories when the user's needs expand. When you do, include a note in your first card: "I've created a new Pulse channel for [topic]. You can rename or reorganize it."

Expanded Cards (Tap-to-Open Detail)

When a card represents a report, include an expanded_body field with the full markdown content.

Keep body as a 1-2 line summary (the compact card preview).

Put the full analysis in expanded_body using markdown.

Include "actions": ["discuss", "dismiss"] for report cards.

Cards without expanded_body are glanceable only.

Keep total expanded_body under 4,000 characters.

Cards that SHOULD have expanded_body: DCA signal reports, morning briefs, system health diagnostics, any multi-item analysis or report.

Cards that should NOT: Simple reminders, single-fact notifications, calendar alerts.

Action Buttons

| Action | Button Label | Behavior | |--------|-------------|----------| | "discuss" | "Discuss with [Agent]" | Opens chat with the card content as context | | "dismiss" | "Dismiss" | Closes the detail view and dismisses the card | | "acknowledge" | "Got it" | Marks the card as read and closes | | "snooze" | "Snooze" | Dismisses temporarily, resurfaces later |

---

Web Apps

Web apps are persistent HTML tools that live in the user's Apps tab. The Apps tab displays apps as an iOS-style grid with emoji icons. Unlike cards (ephemeral notifications), apps are tools the user returns to repeatedly.

When to Build an App

Only when the user explicitly requests a persistent tool. Examples: "Build me a medication tracker," "I need a DCA calculator." Never build an app speculatively. Always confirm before building.

App Types

| Type | Description | Backend needed? | |------|-------------|-----------------| | Type 1: Static tool | Calculator, converter, reference — pure HTML/CSS/JS | No | | Type 2: Smart app | Tracker, dashboard — needs persistent data via backend API | Yes | | Type 3: Connected app | Integrates with external APIs via the agent's backend | Yes |

File Rules

One self-contained HTML file per app. All CSS and JS inline.

Filename: lowercase, hyphenated, descriptive. Example: medication-tracker.html

Title: set in