--- name: memoriesweave description: Creates and manages photo memory collections on MemoriesWeave via its REST API. Use when the user mentions MemoriesWeave, memory collections, photo wallpapers, photo books, or wants to create/edit digital memories or print products using the MemoriesWeave API. Do not use for general photo editing, image generation, or non-MemoriesWeave tasks. --- # MemoriesWeave API Provides programmatic access to MemoriesWeave — a platform for creating photo memory collections with custom HTML layouts. The agent designs HTML layouts and pushes them to memories. The API provides photos, conversations, workspace context, and people data. ## How to call the API **ALWAYS use `curl` via the Bash tool.** Do not use WebFetch, fetch(), or any other HTTP client — they fail due to redirects and auth header stripping. ```bash API="https://grandiose-loris-729.eu-west-1.convex.site/api/v1" KEY="" curl -s "$API/ENDPOINT" -H "Authorization: Bearer $KEY" ``` The user provides their API key (format: `mw_sk_<32hex>`) when requesting this skill. ## Workflow: Creating or editing a memory Follow these steps in order. Do not skip steps. ### Step 1: Lock the memory FIRST The VERY FIRST API call must be locking the memory. Do this before gathering context, before reading HTML, before anything else. This shows a loading animation on the user's screen immediately. ```bash curl -s -X POST "$API/memories/{memoryId}/lock" -H "Authorization: Bearer $KEY" ``` If creating a new memory (no memory ID yet), lock it immediately after creation. ### Step 2: Gather context ```bash # Get workspace list curl -s "$API/workspaces" -H "Authorization: Bearer $KEY" # Get workspace context (who the people are, relationship info, instructions) curl -s "$API/workspaces/{wsId}/context" -H "Authorization: Bearer $KEY" # Get registered people (names, roles, descriptions) curl -s "$API/workspaces/{wsId}/persons" -H "Authorization: Bearer $KEY" ``` ### Step 3: Save a "before" snapshot ```bash curl -s -X POST "$API/memories/{memoryId}/snapshots" \ -H "Authorization: Bearer $KEY" \ -H "Content-Type: application/json" \ -d '{"label": "Before edit — description of planned change"}' ``` ### Step 4: Select photos Use tag filtering as a starting point, then verify with conversation context. **IMPORTANT: dateFrom and dateTo must be Unix timestamps in milliseconds, NOT date strings.** Example: July 1, 2025 = `1751328000000`, not `2025-07-01`. Calculate with: `new Date("2025-07-01").getTime()` ```bash # Filter by tag (e.g. couple, selfie, portrait, traveling) curl -s "$API/workspaces/{wsId}/photos?tag=couple&limit=50" -H "Authorization: Bearer $KEY" # Filter by date range (Unix ms timestamps) curl -s "$API/workspaces/{wsId}/photos?dateFrom=1751328000000&dateTo=1754006400000&limit=50" -H "Authorization: Bearer $KEY" # If user provides a photo ID, fetch it directly curl -s "$API/photos/{photoId}" -H "Authorization: Bearer $KEY" # Get conversation context around a photo (what was happening when it was shared) curl -s "$API/workspaces/{wsId}/conversations/by-photo/{photoId}" -H "Authorization: Bearer $KEY" ``` **Tags are AI-generated and may be inaccurate.** Use them as a first filter, then verify with conversation context. Do not rely on tags alone. **Pagination:** If a search doesn't return enough results, check `meta.hasMore` in the response. If `true`, use the `cursor` value to fetch the next batch: ```bash # First request curl -s "$API/workspaces/{wsId}/photos?tag=couple&limit=50" -H "Authorization: Bearer $KEY" # Response includes: "meta": { "cursor": "abc123", "hasMore": true } # Get next batch using cursor curl -s "$API/workspaces/{wsId}/photos?tag=couple&limit=50&cursor=abc123" -H "Authorization: Bearer $KEY" ``` Keep paginating until you find what you need or `hasMore` is `false`. ### Step 5: Choose the correct format ```bash curl -s "$API/digital-formats" -H "Authorization: Bearer $KEY" ``` Common formats: Phone Wallpaper (1170x2532 iPhone 13, 1320x2868 iPhone 16 Pro Max), Desktop (3840x2160), Social Post (1080x1080). ### Step 5b: VERIFY every photo before using it Before including ANY photo in your design, you MUST verify it exists and get its actual data by calling: ```bash curl -s "$API/photos/{photoId}" -H "Authorization: Bearer $KEY" ``` **NEVER fabricate, guess, or construct photo URLs.** Every photo URL must come from an actual API response (`urls.original`, `urls.medium`, or `urls.thumbnail`). If a photo search returns no results for a month, report that to the user — do not invent URLs. **Verification checklist for every photo:** 1. You received the photo ID from the API (not made up) 2. You called `GET /photos/{photoId}` and got a valid response 3. The `dateTaken` field matches the month you're placing it on 4. The `tags` or photo content matches what you expect (couple/selfie/andrea etc.) 5. The `urls.original` URL is what you're putting in the HTML If the API returns empty results for a time period, try different search strategies: - Search by `tag=couple`, `tag=selfie`, `tag=andrea` without date range - Then filter results by `dateTaken` in your code - Try broader date ranges - If truly no photos exist for a month, tell the user ### Step 6: Design HTML and push **Note:** Custom HTML is rendered inside a sandboxed iframe with DOMPurify sanitization. All `

memoriesweave

Installation

SKILL.md