Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Query, insert, edit, and delete flomo memos through the flomo Web UI using Chrome MCP tools (no official API required). Use when a user wants CRUD operations...
Query, insert, edit, and delete flomo memos through the flomo Web UI using Chrome MCP tools (no official API required). Use when a user wants CRUD operations...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Use Chrome MCP tools to operate on live flomo memos at https://v.flomoapp.com/mine. This skill is for Web UI automation only. It does not depend on flomo official APIs. Default behavior (v1): Full CRUD (query/search, create/insert, edit, delete) Text search first, but lock a target by memo_id before write actions edit defaults to full content replacement (replace) delete always requires explicit second confirmation Auto deep scan for search with default cap of 50 memos Minimal logging (do not persist memo body text)
User is already logged in to flomo Web in Chrome Chrome MCP is available and working in this Codex session Prefer desktop layout (wide viewport). Mobile layout is best-effort only.
The user asks to search or find live flomo memos The user asks to insert/create a flomo memo in their real account The user asks to edit/update an existing flomo memo The user asks to delete a flomo memo and accepts confirmation steps
The user only wants to process exported flomo HTML/archives (use flomo-memo-to-markdown instead) The user asks for batch operations across many memos (not v1) The user asks for attachment upload/edit support (not v1)
Confirm Chrome MCP connectivity and switch to the flomo tab (or navigate to flomo). For query/edit/delete, run search workflow and build memo candidates from visible memo cards/links. If needed, deep-scan by scrolling and repeating reads up to the scan cap. For write operations, lock the target by memo_id and present a confirmation step. Execute UI actions with chrome_read_page refs first; refresh refs if they expire. Validate the result by re-reading the page and summarizing the outcome.
delete: Always require explicit second confirmation before actual deletion. edit via text search: Require candidate confirmation before writing. Do not persist memo body text to local files. If target UI controls cannot be located reliably, stop and report a recoverable failure instead of guessing.
Use mcp-chrome-global Chrome MCP tools in this order of preference: chrome_switch_tab / chrome_navigate chrome_read_page (structured refs) chrome_get_web_content (fast visible text read) chrome_click_element, chrome_fill_or_select, chrome_keyboard chrome_screenshot (debugging / visual confirmation) chrome_computer (coordinate fallback, minimal use) chrome_request_element_selection (human-in-the-loop fallback after repeated failures)
Return candidate memos with: memo_id visible timestamp text short snippet match reason
Insert a new memo through the top editor and report success with best-effort new memo_id detection.
Default mode is replace (replace full memo body). append/prepend are reserved optional modes and may be unsupported in v1 unless explicitly implemented during the run.
Delete a single target memo only after the user confirms the selected candidate.
Use these internal conventions in responses and reasoning (no code API required):
memo_id: string timestamp_text: string snippet: string match_reason: string score?: number
action: query | create | edit | delete target_query?: string target_memo_id?: string edit_mode?: replace | append | prepend scan_limit: number (default 50) requires_confirmation: boolean
success: boolean action: string memo_id?: string matched_count?: number message: string warnings?: string[]
Ask only if it changes the action materially: Multiple candidates match and a write action is requested The user did not provide new content for create or edit The user wants a scan cap larger than the default 50 The page layout is mobile or controls cannot be found reliably A destructive action (delete) reaches the final confirmation point
Workflow details: references/workflows.md UI locator strategy and fallback policy: references/ui-locators.md Safety and logging policy: references/safety.md Validation checklist: references/test-checklist.md
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.