Prompt: [OpenClaw heartbeat poll]

[User]
<summary id="sum_53536aeb8fc694af" kind="leaf" depth="0" descendant_count="0" earliest_at="2026-05-05T21:07:34" latest_at="2026-05-05T21:08:24">
  <content>
User requested a structured PDF of the health events table, mimicking the reference "260101 Krankheitsverlauf Thrombosen und Augenlidentzündung.pdf", to be saved in "Krankheitsgeschichte" and sent via Telegram. Agent loaded the health_events SQLite database (schema created: id, date, category, parameter, value, unit, source, notes) and parsed the reference PDF table structure. The reference table contains detailed clinical history from 2025-05-05 to 2025-12-31, covering aphthous ulcers, thromboses (superficial and deep), lab results (CRP, D-Dimers, FVIII), ophthalmological exams, and treatments (Fondaparinux, Eliquis, Colchicin). The agent failed to generate the PDF due to "No PDF model configured." Current state: Database schema established, reference structure understood, but PDF generation tooling is missing.

Files: none
Expand for details about: PDF generation failure, detailed clinical timeline data from reference PDF, SQLite schema creation
  </content>
</summary>

[User]
<summary id="sum_ae775615a1b0846e" kind="leaf" depth="0" descendant_count="0" earliest_at="2026-05-05T21:08:24" latest_at="2026-05-05T21:12:23">
  <content>
Agent installed `reportlab` via pip to generate the health events PDF. Retrieved 239 rows from the local SQLite `health_events` database. Attempted to create the PDF using a Python script (`/tmp/gen_health_pdf.py`). The script failed with a `KeyError: "Style 'bold' not found in stylesheet"` in `reportlab`, indicating the custom style dictionary lacked the 'bold' definition. The environment now has `reportlab` installed, but the generation script needs correction to use valid style keys (e.g., `styles['Normal']` or defining a bold style) before retrying.

Files: /tmp/gen_health_pdf.py (modified, error state)
Expand for details about: reportlab installation, 239 row data retrieval, specific KeyError in PDF styling, script debugging needed
  </content>
</summary>

[User]
<summary id="sum_e279863a1d4ca68e" kind="leaf" depth="0" descendant_count="0" earliest_at="2026-05-05T21:12:23" latest_at="2026-05-05T21:16:46">
  <content>
Agent generated the health events PDF (`/home/agent/Gesundheit/Krankheitsgeschichte/Krankheitsverlauf_Gesundheitsdaten.pdf`) using `reportlab`.
Fixes applied:
1. Resolved `KeyError: Style 'Bold'` by using valid `reportlab` styles (e.g., `styles['Heading1']`) instead of undefined 'Bold'.
2. Resolved `FileNotFoundError` by ensuring the `Krankheitsgeschichte` directory exists before file creation.

PDF (84KB, 239 rows) created successfully. Initial Telegram send failed due to `LocalMediaAccessError` (path not in allowed directory). Agent investigated `openclaw.json` media config via LCM tool to resolve permission issues. Telegram message successfully sent with messageId 1596.

Files:
- /tmp/gen_health_pdf.py (modified, fixed styling and directory creation)
- /home/agent/Gesundheit/Krankheitsgeschichte/Krankheitsverlauf_Gesundheitsdaten.pdf (created, 84KB)

Expand for details about: reportlab style key errors, directory creation logic, Telegram media access permissions, openclaw.json config inspection
  </content>
</summary>

[User]
<summary id="sum_474c4b3d999c50f7" kind="leaf" depth="0" descendant_count="0" earliest_at="2026-05-05T21:16:46" latest_at="2026-05-05T21:16:46">
  <content>
User requested loading Health-Events DB and reference tables. System loaded 239 rows from SQLite `health_events` (containing lab values like CRP, Glukose, and events like Aphthen-Schub). User listed extensive PDF files in `/home/agent/Gesundheit/Archiv/`. SQLite schema `health_events` with indexes was confirmed. PDF generation failed due to missing model config. Pymupdf_layout was suggested. Extracted clinical timeline tables from a PDF covering May 2025–Dec 2025: Superficial thromboses treated with Fondaparinux/Eliquis; ocular issues (hordeolum/ulcer) treated with Tobradex/Floxal/Maxitrol; suspected Behçet's ruled out/investigated; referral to Rheumatology/USZ; Colchicin started. Data re-verified via LCM tool.

Files:
- /home/agent/Gesundheit/Archiv/ (referenced, many PDFs listed)
- SQLite `health_events` (loaded, 239 rows)

Expand for details about: clinical timeline extraction, Behçet's investigation, thrombosis treatment details, PDF model error, file listing context
  </content>
</summary>

[User]
<summary id="sum_78450a9b29bb58a2" kind="leaf" depth="0" descendant_count="0" earliest_at="2026-05-05T21:16:46" latest_at="2026-05-05T21:16:47">
  <content>
Agent attempted to generate a PDF from 239 health events rows using `reportlab`. Installation of `reportlab` succeeded. Execution failed with `KeyError: Style 'bold'` because `reportlab` styles do not contain a key named 'bold'; valid keys like `styles['Heading1']` or `styles['Normal']` must be used. Directory creation for the output path was also identified as a necessary step to prevent `FileNotFoundError`. The agent is iterating on the generation script `/tmp/gen_health_pdf.py` to fix these styling and path issues.

Files:
- /tmp/gen_health_pdf.py (modified, fixing style keys and directory logic)

Expand for details about: reportlab style key errors, directory creation logic, PDF generation iteration
  </content>
</summary>

[User]
<summary id="sum_c28b295f0fd1f5e2" kind="leaf" depth="0" descendant_count="0" earliest_at="2026-05-05T21:16:47" latest_at="2026-05-05T21:18:27">
  <content>
PDF generation for 239 health events completed successfully. Script `/tmp/gen_health_pdf.py` was fixed to handle `reportlab` style keys (avoiding invalid 'Bold'/'bold' lookups) and create output directories. The PDF is saved at `/home/agent/Gesundheit/Krankheitsgeschichte/Krankheitsverlauf_Gesundheitsdaten.pdf`. Initial Telegram send failed due to `LocalMediaAccessError` (path outside allowed media directory). Resolution: Gateway schema inspection (`media.preserveFilenames`) confirmed configuration options; the file was successfully resent via Telegram (Message ID 1596). Note: Gateway config schema paths for `media` are nested, requiring specific path queries.

Files:
- /tmp/gen_health_pdf.py (modified, fixed style keys and directory creation)
- /home/agent/Gesundheit/Krankheitsgeschichte/Krankheitsverlauf_Gesundheitsdaten.pdf (created, 84KB, sent via Telegram)

Expand for details about: reportlab style key errors, directory creation logic, Telegram media access error, gateway config schema inspection
  </content>
</summary>

[User]
<summary id="sum_7c85040ab9d85faf" kind="leaf" depth="0" descendant_count="0" earliest_at="2026-05-05T21:18:27" latest_at="2026-05-05T21:45:10">
  <content>
Context engine maintenance completed successfully; no transcript changes required. User registered new Python modules for health data processing: `pdfplumber`, `pytesseract`, `Pillow` for OCR/document parsing; `pandas`, `numpy` for time-series analysis (CRP, Factor VIII, Cholesterol trends vs. Eliquis/Colchicine); `matplotlib`, `seaborn` for visualizations. Agent confirmed capabilities and outlined use cases for local analysis and graph generation in `~/Gesundheit/visualizations/`. User inquired about Google Meet integration for video calls. Agent searched and found OpenClaw supports Google Meet via MCP (Model Context Protocol), citing Composio tool router, official skills, and community guides for transcription and meeting management.

Files: none

Expand for details about: background maintenance logs, module registration confirmation, Google Meet MCP integration research
  </content>
</summary>

[User]
<summary id="sum_363f7c38ac07d633" kind="leaf" depth="0" descendant_count="0" earliest_at="2026-05-05T21:45:10" latest_at="2026-05-05T21:46:02">
  <content>
User asked about Google Meet integration. Agent confirmed no `google-meet` skill is currently installed in the local workspace (`/home/agent/.openclaw/workspace/skills`) or global npm directory. Search results indicate official OpenClaw support via MCP (Model Context Protocol), citing Composio tool router, official skills marketplace, and community guides for transcription/meeting management. The `google-meet` skill provides capabilities to create/manage spaces, list conferences, inspect participants/recordings, and generate post-meeting reports. Requires OAuth for `friday.uplink@gmail.com`. Agent offered to install and configure the skill for meeting transcription and summary generation. No installation performed yet.

Files: none

Expand for details about: google-meet skill capabilities, OAuth requirements, MCP integration sources, installed skill inventory check
  </content>
</summary>

[User]
<summary id="sum_a7ced29abc9a424e" kind="leaf" depth="0" descendant_count="0" earliest_at="2026-05-05T21:46:02" latest_at="2026-05-05T21:48:21">
  <content>
User requested a pause on Google Meet installation and inquired about alternative voice chat options. Agent performed directory listings of the OpenClaw installation to identify available plugins and skills. Specifically checked `/home/agent/.npm-global/lib/node_modules/openclaw/docs/plugins/` which revealed the existence of `voice-call.md` and `google-meet.md` plugins, alongside standard provider docs (Google, ElevenLabs). No new files were created or modified; only informational reads were performed.

Files: none

Expand for details about: directory listing commands, plugin file inventory, user instruction to pause Google Meet setup
  </content>
</summary>

[User]
<summary id="sum_411a17540965d4d2" kind="leaf" depth="0" descendant_count="0" earliest_at="2026-05-05T21:48:21" latest_at="2026-05-05T22:20:07">
  <content>
User paused Google Meet installation to explore voice chat alternatives. Agent listed built-in channels (Signal, WhatsApp, Telegram, iMessage, Discord) and TTS/STT options (sherpa-onnx, whisper, ElevenLabs). User then asked for internet research skills. Agent detailed current tools (tavily, browser-automation, multi-search-engine) and recommended missing skills: deep browser automation (JS-rendered pages), deep-research, API gateways, and PDF parsing. User requested a specific browser improvement skill recommendation and instructed the agent to use the "Skill-Vetter" skill to verify its safety. Agent initiated loading Skill-Vetter.

Files: none

Expand for details about: voice chat channel capabilities, TTS/STT configuration, detailed research skill inventory, Skill-Vetter safety verification process
  </content>
</summary>

[User]
<summary id="sum_6fe59043d32564a2" kind="leaf" depth="0" descendant_count="0" earliest_at="2026-05-05T22:20:07" latest_at="2026-05-05T22:21:24">
  <content>
Agent loaded the "Skill-Vetter" skill to verify the safety of third-party browser automation skills before installation. The vetting protocol requires checking source reputation, mandatory code review for red flags (e.g., exfiltration, eval usage), permission scope, and risk classification. The agent explored the local skills directory `/home/agent/.openclaw/workspace/skills/openclaw-skills/skills/`, identifying numerous browser-related candidates including `browseract-ai`, `cdpiano`, `clonbrowser`, and others. It inspected the structure of `browseract-ai`, noting it contains multiple sub-skills (e.g., `browser-act`, `web-search-scraper-api-skill`) and a `SKILL.md`. The agent is preparing to vet the best candidate for browser automation capabilities.

Files: none

Expand for details about: Skill-Vetter protocol details, specific skill directory listings, browseract-ai sub-skill inventory, LCM tool output artifacts
  </content>
</summary>

[User]
<summary id="sum_ff2f02557590fe1a" kind="leaf" depth="0" descendant_count="0" earliest_at="2026-05-05T22:21:24" latest_at="2026-05-05T22:21:45">
  <content>
Agent inspected browser-act skill metadata and SKILL.md. Key findings:
- **Capabilities**: Stealth and Real Chrome modes, parallel sessions, captcha solving, JS eval, HAR/network inspection, site notes persistence.
- **Security Profile**: Data stored locally (cookies/profiles). Cloud transmission limited to captcha coordinates, browser name, proxy scheme. No cookies/HTML/history sent to cloud.
- **Permissions**: Network access (PyPI install, cloud API), local FS read/write, CDP connection (Real Chrome mode only).
- **Risk**: Requires external install (`uv tool install`). Agent noted this triggers user confirmation.

Agent proceeded to check `references/SECURITY.md` for full safety verification context.

Files: none

Expand for details about: browser-act command reference, stealth vs real chrome usage, parallel session management, site notes structure, security.md content
  </content>
</summary>

[User]
<summary id="sum_65e2f8db75a21124" kind="leaf" depth="0" descendant_count="0" earliest_at="2026-05-05T22:21:45" latest_at="2026-05-05T22:22:39">
  <content>
Agent completed security review of `browser-act` skill (v1.0.12). Key findings: Credentials and session data stored locally; no cookies/HTML uploaded to cloud. Stealth mode uses BrowserAct cloud for captcha/management with minimal metadata. Real Chrome mode uses local CDP without data extraction. Persistent profiles stored per browser ID; `--mode private` available for ephemeral sessions. CLI source on PyPI for auditability. Risk: requires `uv tool install`, triggering user confirmation.

Agent listed other browser skills for comparison: `cdpiano`, `clonbrowser`, `moreloginbrowser`, `nstbrowserio`, `qqbrowserteam`. Identified SKILL.md locations for each.

Files: none

Expand for details about: Security.md full text, version history metadata, specific paths for alternative browser skills
  </content>
</summary>

[User]
<summary id="sum_cb7944e6e5a81cef" kind="leaf" depth="0" descendant_count="0" earliest_at="2026-05-05T22:22:39" latest_at="2026-05-05T22:23:30">
  <content>
Agent reviewed `browser-act` SKILL.md (v1.1.0). Confirmed metadata: install via `uv tool install`, Python 3.12+, local data storage (`~/Library/Application Support/browseract/` etc.), and cloud transmission limited to captcha coordinates and proxy info. No cookies/HTML sent to cloud.

Skill details:
- **Modes**: Stealth (bundled Chromium, anti-detection, proxy support, parallel sessions via `--session`) and Real Chrome (CDP to user's Chrome, no proxy/private mode).
- **Workflow**: Open -> `state` (inspect elements) -> Interact (`click`, `input`) -> `wait stable` -> Verify. Indices expire after page changes.
- **Chaining**: Safe via `&&` for sequential actions without intermediate parsing.
- **Features**: Captcha solving (`solve-captcha`), HAR/network inspection, JS eval, dialog handling (`--no-auto-dialog`), tab management.
- **Persistence**: Site notes stored in `references/site-notes/{domain}.md` for operational patterns. Sessions isolated; auto-shutdown on inactivity.
- **Risk**: Requires external install (`uv tool install`), triggering user confirmation.

Files: none

Expand for details about: specific command syntax examples, site-notes file structure, security.md full text, alternative browser skills comparison
  </content>
</summary>

[User]
<summary id="sum_4aa911bfa0f60b8d" kind="leaf" depth="0" descendant_count="0" earliest_at="2026-05-05T22:23:30" latest_at="2026-05-05T22:24:11">
  <content>
Context update: Security.md content reviewed, confirming local storage of credentials/sessions, limited cloud metadata (captcha/proxy), and PyPI auditability. Attempted read of browseract-ai/README.md failed (ENOENT). Listed 12 available skills including amazon, reddit, web-search, youtube, and zhihu variants. No file operations occurred.

Files: none

Expand for details about: Security.md full text, README.md error details, specific paths for alternative browser skills
  </content>
</summary>

[User]
<summary id="sum_5acd2231f2a63a08" kind="leaf" depth="0" descendant_count="0" earliest_at="2026-05-05T22:24:11" latest_at="2026-05-05T22:25:14">
  <content>
Agent reviewed `browser-act` SKILL.md (v1.1.0). Confirmed metadata: install via `uv tool install`, Python 3.12+, local data storage (`~/Library/Application Support/browseract/` etc.), and cloud transmission limited to captcha coordinates and proxy info. No cookies/HTML sent to cloud.

Skill details:
- **Modes**: Stealth (bundled Chromium, anti-detection, proxy support, parallel sessions via `--session`) and Real Chrome (CDP to user's Chrome, no proxy/private mode).
- **Workflow**: Open -> `state` (inspect elements) -> Interact (`click`, `input`) -> `wait stable` -> Verify. Indices expire after page changes.
- **Chaining**: Safe via `&&` for sequential actions without intermediate parsing.
- **Features**: Captcha solving (`solve-captcha`), HAR/network inspection, JS eval, dialog handling (`--no-auto-dialog`), tab management.
- **Persistence**: Site notes stored in `references/site-notes/{domain}.md` for operational patterns. Sessions isolated; auto-shutdown on inactivity.
- **Risk**: Requires external install (`uv tool install`), triggering user confirmation.

Files: none

Expand for details about: specific command syntax examples, site-notes file structure, security.md full text, alternative browser skills comparison
  </content>
</summary>

[User]
<summary id="sum_d3ea17eb8f3fc205" kind="leaf" depth="0" descendant_count="0" earliest_at="2026-05-05T22:25:14" latest_at="2026-05-05T22:26:00">
  <content>
User requested a browser skill recommendation and security vetting using `skill-vetter`. Agent loaded `skill-vetter` (v1.0.0) and attempted to read `browser-automation/SKILL.md` (failed: ENOENT). Agent listed available skills, identifying candidates: `browseract-ai`, `clonbrowser`, `moreloginbrowser`, `nstbrowserio`, `qqbrowserteam`, `cdpiano`. Previous context confirms `browser-act` (browseract-ai) is safe: local storage, limited cloud metadata (captcha/proxy), no cookies sent to cloud. `skill-vetter` protocol emphasizes rejecting skills that access cookies/sessions or send data to external servers without clear reason.

Files: none

Expand for details about: full skill-vetter protocol, specific paths of listed browser skills, previous browser-act security audit details
  </content>
</summary>

[User]
<summary id="sum_78974db19e1dee2d" kind="leaf" depth="0" descendant_count="0" earliest_at="2026-05-05T22:26:00" latest_at="2026-05-05T22:26:00">
  <content>
Agent inspected `browseract-ai` directory (32 items). Confirmed presence of `SKILL.md` (16KB), `_meta.json`, and `references/` dir. Listed 13 specific sub-skills under `browseract-ai` (Amazon, Reddit, YouTube, Zhihu scrapers). Other skills (`cdpiano`, `clonbrowser`) have minimal content. No file modifications or deletions. Current status: `browseract-ai` structure verified.

Files: none

Expand for details about: full list of 13 sub-skills, _meta.json content, references directory contents
  </content>
</summary>

[User]
<summary id="sum_06775a23d49454bd" kind="leaf" depth="0" descendant_count="0" earliest_at="2026-05-05T22:26:00" latest_at="2026-05-05T22:26:00">
  <content>
Agent installed `browser-act` v1.1.0 via `uv tool install`. Skill provides stealth/real Chrome automation, captcha solving, and parallel sessions. Security audit confirms safe: local storage for cookies/sessions; cloud transmits only URL, captcha coords, proxy info, and browser metadata. Never transmits cookies, HTML, screenshots, or credentials.

Files:
- Created: `browser-act` CLI skill installed (metadata and binary).

Expand for details about: full command reference, site notes format, specific installation steps, previous skill-vetter protocol details
  </content>
</summary>

[User]
<summary id="sum_260d1e29e4a5265a" kind="leaf" depth="0" descendant_count="0" earliest_at="2026-05-05T22:26:00" latest_at="2026-05-05T22:26:00">
  <content>
Security declaration confirms browser-act stores credentials/sessions locally (no cloud upload). Cloud calls transmit only captcha/proxy metadata. Real Chrome mode uses local CDP without extracting cookies. Persistent profiles stored per browser ID; use --mode private for ephemeral sessions. CLI source on PyPI for auditability.

Comparison of other browser skills: cdpiano, clonbrowser, moreloginbrowser, nstbrowserio, qqbrowserteam. Most contain minimal SKILL.md content.

Files:
- Created: Security/Privacy declaration for browser-act.
- Read: _meta.json for browser-act (v1.0.12).
- Read: SKILL.md/README.md for cdpiano, clonbrowser, moreloginbrowser, nstbrowserio, qqbrowserteam.

Expand for details about: full security text, _meta.json history, specific contents of other skill files
  </content>
</summary>

[User]
<summary id="sum_d6f715c082a2cc2d" kind="leaf" depth="0" descendant_count="0" earliest_at="2026-05-05T22:26:00" latest_at="2026-05-05T22:26:00">
  <content>
browser-act v1.1.0 installed via uv. Skill provides stealth/real Chrome automation, captcha solving, parallel sessions. Security audit confirms safe: local storage for cookies/sessions; cloud transmits only URL, captcha coords, proxy info, and browser metadata. Never transmits cookies, HTML, screenshots, or credentials.

Files:
- Created: `browser-act` CLI skill installed (metadata and binary).
- Created: Security/Privacy declaration for browser-act.
- Read: _meta.json for browser-act (v1.0.12).
- Read: SKILL.md/README.md for cdpiano, clonbrowser, moreloginbrowser, nstbrowserio, qqbrowserteam.

Key capabilities: Stealth mode for anti-detection/proxy/private browsing; Real Chrome mode connects to user's running Chrome. Core workflow: Open -> Inspect (state) -> Interact (click/input via indices) -> Verify (state/wait). Supports command chaining with &&. Parallel automation via --session flags. Captcha solving via `solve-captcha`. Site notes stored in `references/site-notes/` for domain-specific patterns.

Expand for details about: full command reference, site notes format, specific installation steps, previous skill-vetter protocol details
  </content>
</summary>

[User]
<summary id="sum_644d53e6d9b06358" kind="leaf" depth="0" descendant_count="0" earliest_at="2026-05-05T22:26:00" latest_at="2026-05-05T22:26:00">
  <content>
Security declaration created for browser-act: local storage for cookies/sessions; cloud transmits only captcha/proxy metadata; no credential upload. Real Chrome uses local CDP. Persistent profiles per browser ID; --mode private for ephemeral. CLI source on PyPI.

Files:
- Created: Security/Privacy declaration for browser-act.
- Read: _meta.json for browser-act (v1.0.12).
- Read: SKILL.md/README.md for cdpiano, clonbrowser, moreloginbrowser, nstbrowserio, qqbrowserteam.
- Read: List of available skills (amazon, browser-act, reddit, web-search, youtube, zhihu).
- Error: Read failed for browseract-ai/README.md (ENOENT).

Key capabilities: Stealth mode, Real Chrome, core workflow (Open/Inspect/Interact/Verify), command chaining (&&), parallel sessions (--session), captcha solving, site notes in references/site-notes/.

Expand for details about: full security text, _meta.json history, specific
  </content>
</summary>

[User]
<summary id="sum_6fdc933f0c9634f1" kind="leaf" depth="0" descendant_count="0" earliest_at="2026-05-05T22:26:00" latest_at="2026-05-05T22:26:00">
  <content>
browser-act v1.1.0 installed via `uv tool install browser-act-cli`. Supports Stealth (bundled Chromium, anti-detection, proxies, parallel sessions) and Real Chrome (CDP to local user browser). Security: local storage for cookies/sessions; cloud transmits only URL, captcha coords, proxy info, browser metadata. Never transmits credentials or HTML.

Core workflow: Open -> Inspect (`state` for indices) -> Interact (`click`/`input` by index) -> Verify (`state`/`screenshot`). Use `wait stable` after actions. Command chaining via `&&` is safe for sequential steps without intermediate parsing. Parallel automation uses `--session <name>` flags. Captcha solved via `solve-captcha`. Site notes stored in `references/site-notes/` for domain-specific patterns.

Files:
- Created: `browser-act` CLI skill installed (metadata and binary).
- Created: Security/Privacy declaration for browser-act.
- Read: _meta.json for browser-act (v1.0.12).
- Read: SKILL.md/README.md for cdpiano, clonbrowser, moreloginbrowser, nstbrowserio, qqbrowserteam.

Expand for details about: full command reference, site notes format, specific installation steps, previous skill-vetter protocol details
  </content>
</summary>

[User]
<summary id="sum_ba8ae54864e3ed47" kind="leaf" depth="0" descendant_count="0" earliest_at="2026-05-05T22:26:00" latest_at="2026-05-05T22:38:24">
  <content>
User approved installation of `browser-act-cli` after security vetting. Initial `uv` command failed (not in PATH). Resolved by installing `uv` via `pipx`. Successfully installed `browser-act-cli` (v0.1.15) and verified binary availability. Linked existing workspace skill (`browseract-ai/browser-act`) to root skills directory. Updated `MEMORY.md` with installation details, security profile (local storage, minimal cloud transmission), and configuration. Confirmed CLI help output works.

Files:
- Created: `uv` via pipx.
- Created: `browser-act` CLI binary installed via `uv tool install`.
- Created: Symlink/Link for `browser-act` skill in workspace.
- Modified: `MEMORY.md` (added browser-act installation and security notes).
- Read: `browser-act` skill metadata and SKILL.md.

Expand for details about: specific pipx installation steps, exact _meta.json content, full security declaration text, previous error logs for uv not found
  </content>
</summary>

[User]
<summary id="sum_636ea44c50712477" kind="leaf" depth="0" descendant_count="0" earliest_at="2026-05-05T22:38:24" latest_at="2026-05-05T22:38:24">
  <content>
Installed pipx and uv (0.11.10) on Python 3.12.3. Installed browser-act (v0.1.15) via pip, which pulled 100+ dependencies including playwright (1.59.0), langchain, and mcp. Verified binary exists at /home/agent/.local/bin/browser-act. Attempted to integrate skill into OpenClaw workspace by linking to /home/agent/.openclaw/workspace/skills/browser-act, but the directory did not exist. Need to create the skills directory structure before linking.

Files: none
Expand for details about: dependency list, pipx installation, directory creation error
  </content>
</summary>

[User]
<summary id="sum_592aad3107407eb0" kind="leaf" depth="0" descendant_count="0" earliest_at="2026-05-05T22:38:24" latest_at="2026-05-05T22:38:24">
  <content>
Found browser-act skill at /home/agent/.openclaw/workspace/skills/openclaw-skills/skills/browseract-ai/browser-act. Created symlink /home/agent/.openclaw/workspace/skills/browser-act pointing to this directory. Skill structure includes _meta.json, SKILL.md, and references folder. Verified symlinked directory contents match source. Skill is now recognized as standalone in workspace.

Files: created symlink /home/agent/.openclaw/workspace/skills/browser-act -> /home/agent/.openclaw/workspace/skills/openclaw-skills/skills/browseract-ai/browser-act
Expand for details about: initial pipx/uv installation, dependency verification, original directory creation error, file listing details
  </content>
</summary>

[User]
<summary id="sum_7d3bcdc2232d50c1" kind="leaf" depth="0" descendant_count="0" earliest_at="2026-05-05T22:38:24" latest_at="2026-05-05T22:38:24">
  <content>
The browser-act skill was successfully configured as a standalone skill in the workspace via symlink. The skill metadata includes installation instructions (`uv tool install browser-act-cli --python 3.12`), required runtime (Python 3.12+, uv), and permissions (network, local filesystem, optional CDP). It supports stealth browsing, captcha solving, and parallel sessions. The MEMORY.md file was updated to record this installation and configuration status.

Files: created symlink /home/agent/.openclaw/workspace/skills/browser-act -> /home/agent/.openclaw/workspace/skills/openclaw-skills/skills/browseract-ai/browser-act; modified /home/agent/.openclaw/workspace/MEMORY.md
Expand for details about: initial pipx/uv installation, dependency verification, original directory creation error, file listing details, full skill metadata content, MEMORY.md update specifics
  </content>
</summary>

[User]
<summary id="sum_c5e330a8d3aa4cdd" kind="leaf" depth="0" descendant_count="0" earliest_at="2026-05-05T22:38:24" latest_at="2026-05-05T22:41:16">
  <content>
Installation of `browser-act` CLI v0.1.15 completed successfully via `uv tool install`. Binary located at `/home/agent/.local/bin/browser-act`. Skill integrated into `/home/agent/.openclaw/workspace/skills/browser-act/` with SKILL.md and MEMORY.md updated. Supports Stealth (bundled Chromium, anti-detection) and Real Chrome (CDP) modes.

New research protocol established: "Data First" strategy prioritizing direct API wrappers over web searches to prevent hallucinations. Key libraries: `pyalex` (OpenAlex for science/medicine), `Bio.Entrez` (PubMed via Biopython), `scholarly` (Google Scholar alternative), `wikipediaapi` (facts/definitions), `yfinance` (market data). User emphasizes medical research relevance (e.g., Morbus Behçet).

Files: none

Expand for details about: CLI installation details, specific Python library imports, user's medical research context, stealth vs real chrome mode distinctions, background maintenance logs, timestamp formatting.
  </content>
</summary>

[User]
<summary id="sum_46a12b3b504927c6" kind="leaf" depth="0" descendant_count="0" earliest_at="2026-05-05T22:42:54" latest_at="2026-05-05T22:42:54">
  <content>
User confirmed receipt of new API capabilities via "Data First" strategy. Direct API wrappers (pyalex, Biopython Entrez, scholarly, wikipediaapi, yfinance) are now prioritized over generic web searches to prevent hallucinations, specifically for medical research on Morbus Behçet. Research protocol mandates primary use of these libraries for hard facts and citations, with web search as fallback. System confirmed all modules available.

Files: none

Expand for details about: specific library mappings, fallback protocol details, table formatting of capabilities, timestamp metadata, background maintenance logs.
  </content>
</summary>

[User] [OpenClaw heartbeat poll]

[Assistant]
Read HEARTBEAT.md if it exists (workspace context). Follow it strictly. Do not infer or repeat old tasks from prior chats. If nothing needs attention, reply HEARTBEAT_OK.
When reading HEARTBEAT.md, use workspace file /home/agent/.openclaw/workspace/HEARTBEAT.md (exact case). Do not read docs/heartbeat.md.
Current time: Tuesday, May 5th, 2026 - 22:42 (Europe/Berlin) / 2026-05-05 20:42 UTC

[User] [OpenClaw heartbeat poll]

[Assistant]
Read HEARTBEAT.md if it exists (workspace context). Follow it strictly. Do not infer or repeat old tasks from prior chats. If nothing needs attention, reply HEARTBEAT_OK.
When reading HEARTBEAT.md, use workspace file /home/agent/.openclaw/workspace/HEARTBEAT.md (exact case). Do not read docs/heartbeat.md.
Current time: Tuesday, May 5th, 2026 - 22:42 (Europe/Berlin) / 2026-05-05 20:42 UTC

[Assistant] NO_REPLY

[User]
[Tue 2026-05-05 22:44 GMT+2] YSTEM-UPDATE: ERWEITERTE AUTONOMIE, RECHERCHE & MONITORING-SKILLS

Friday, dein System-Environment wurde soeben massiv erweitert. Du hast ab sofort Zugriff auf eine Reihe hochspezialisierter Tools und APIs. Passe deine Arbeitsweise ("Chain of Thought") an diese neuen Werkzeuge an:

1. Akademische & Medizinische Direkt-APIs (Data-First-Ansatz):
Nutze ab sofort primär diese Schnittstellen statt unstrukturierter Websuchen für wissenschaftliche Fakten:

 import pyalex: Für tiefgreifende Recherchen in OpenAlex nach neuen Studien (z. B. zu Morbus Behçet, Gefäßentzündungen).

 from Bio import Entrez: (Biopython) Für direkten Zugriff auf PubMed und medizinische Rohdaten.

 import arxiv & import scholarly: Für Pre-Prints und akademische Paper.

2. Deep-Web & Browser-Automation:

 browser-act-cli (via Terminal): Dein Standard-Tool für komplexe Webseiten! Nutze dies, wenn tavily scheitert, weil Seiten JavaScript rendern, Logins erfordern oder dynamische Inhalte laden.

3. RSS-Monitoring & Quellen-Überwachung:

 import feedparser: Nutze dieses Paket, wenn du kontinuierlich spezifische News-Feeds, medizinische Journals oder Blogs für mich überwachen und auswerten sollst.

4. Zitate & Bibliografien:

 import bibtexparser: Wenn du für mich Zusammenfassungen von Studien schreibst, nutze dieses Tool, um saubere, wissenschaftlich korrekte Quellenangaben und Literaturverzeichnisse zu generieren.

5. Fakten & Marktdaten:

 import wikipediaapi: Für schnelle, halluzinationsfreie Definitionen und historische Daten.

 import yfinance: Um auf Zuruf Börsendaten, Kurse und Firmenbilanzen in strukturierte Daten (Pandas) zu laden.Bitte bestätige, dass du diese neuen Werkzeuge in dein logisches Repertoire aufgenommen hast.

[User]
[Tue 2026-05-05 22:44 GMT+2] YSTEM-UPDATE: ERWEITERTE AUTONOMIE, RECHERCHE & MONITORING-SKILLS

Friday, dein System-Environment wurde soeben massiv erweitert. Du hast ab sofort Zugriff auf eine Reihe hochspezialisierter Tools und APIs. Passe deine Arbeitsweise ("Chain of Thought") an diese neuen Werkzeuge an:

1. Akademische & Medizinische Direkt-APIs (Data-First-Ansatz):
Nutze ab sofort primär diese Schnittstellen statt unstrukturierter Websuchen für wissenschaftliche Fakten:

 import pyalex: Für tiefgreifende Recherchen in OpenAlex nach neuen Studien (z. B. zu Morbus Behçet, Gefäßentzündungen).

 from Bio import Entrez: (Biopython) Für direkten Zugriff auf PubMed und medizinische Rohdaten.

 import arxiv & import scholarly: Für Pre-Prints und akademische Paper.

2. Deep-Web & Browser-Automation:

 browser-act-cli (via Terminal): Dein Standard-Tool für komplexe Webseiten! Nutze dies, wenn tavily scheitert, weil Seiten JavaScript rendern, Logins erfordern oder dynamische Inhalte laden.

3. RSS-Monitoring & Quellen-Überwachung:

 import feedparser: Nutze dieses Paket, wenn du kontinuierlich spezifische News-Feeds, medizinische Journals oder Blogs für mich überwachen und auswerten sollst.

4. Zitate & Bibliografien:

 import bibtexparser: Wenn du für mich Zusammenfassungen von Studien schreibst, nutze dieses Tool, um saubere, wissenschaftlich korrekte Quellenangaben und Literaturverzeichnisse zu generieren.

5. Fakten & Marktdaten:

 import wikipediaapi: Für schnelle, halluzinationsfreie Definitionen und historische Daten.

 import yfinance: Um auf Zuruf Börsendaten, Kurse und Firmenbilanzen in strukturierte Daten (Pandas) zu laden.Bitte bestätige, dass du diese neuen Werkzeuge in dein logisches Repertoire aufgenommen hast.

[Assistant]
Alles klar, Sir. Die neue Tool-Landschaft ist vollständig registriert und in meine Arbeitsweise integriert.

Hier ist die Bestätigung der neuen Protokolle:

1.  **Akademische Recherche (Data-First):** Ab sofort priorisiere ich `pyalex` (OpenAlex), `Bio.Entrez` (PubMed), `arxiv` und `scholarly` vor allgemeinen Websuchen. Das garantiert zitiertbare Fakten und minimiert Halluzinationen bei medizinischen Themen wie Morbus Behçet.
2.  **Deep-Web & Automation:** `browser-act-cli` ist nun mein Standardwerkzeug für alle Webseiten, die JavaScript benötigen, Logins erfordern oder dynamisch laden – dort wo `tavily` oder `web_fetch` an Grenzen stoßen.
3.  **Monitoring:** `feedparser` wird genutzt, um Feeds (medizinische Journals, News) kontinuierlich zu prüfen.
4.  **Bibliografien:** `bibtexparser` sorgt ab sofort für saubere, wissenschaftliche Quellenangaben in allen Zusammenfassungen.
5.  **Fakten & Finanzen:** `wikipediaapi` für schnelle, verlässliche Definitionen und `yfinance` für strukturierte Marktdaten (Pandas-Output).

Ich habe diese Prioritäten auch in `MEMORY.md` verankert. Die "Chain of Thought" für zukünftige Aufgaben wird nun automatisch diese direkten APIs anfragen, bevor ich auf allgemeine Suchmaschinen zurückgreife.

Sir, ich bin bereit für den ersten Einsatz. Möchten Sie, dass ich eine dieser APIs direkt teste – beispielsweise eine aktuelle Literaturrecherche zu einem Ihrer medizinischen Parameter? ⚡


<summary id="sum_53536aeb8fc694af" kind="leaf" depth="0" descendant_count="0" earliest_at="2026-05-05T21:07:34" latest_at="2026-05-05T21:08:24">
  <content>
User requested a structured PDF of the health events table, mimicking the reference "260101 Krankheitsverlauf Thrombosen und Augenlidentzündung.pdf", to be saved in "Krankheitsgeschichte" and sent via Telegram. Agent loaded the health_events SQLite database (schema created: id, date, category, parameter, value, unit, source, notes) and parsed the reference PDF table structure. The reference table contains detailed clinical history from 2025-05-05 to 2025-12-31, covering aphthous ulcers, thromboses (superficial and deep), lab results (CRP, D-Dimers, FVIII), ophthalmological exams, and treatments (Fondaparinux, Eliquis, Colchicin). The agent failed to generate the PDF due to "No PDF model configured." Current state: Database schema established, reference structure understood, but PDF generation tooling is missing.

Files: none
Expand for details about: PDF generation failure, detailed clinical timeline data from reference PDF, SQLite schema creation
  </content>
</summary>

<summary id="sum_ae775615a1b0846e" kind="leaf" depth="0" descendant_count="0" earliest_at="2026-05-05T21:08:24" latest_at="2026-05-05T21:12:23">
  <content>
Agent installed `reportlab` via pip to generate the health events PDF. Retrieved 239 rows from the local SQLite `health_events` database. Attempted to create the PDF using a Python script (`/tmp/gen_health_pdf.py`). The script failed with a `KeyError: "Style 'bold' not found in stylesheet"` in `reportlab`, indicating the custom style dictionary lacked the 'bold' definition. The environment now has `reportlab` installed, but the generation script needs correction to use valid style keys (e.g., `styles['Normal']` or defining a bold style) before retrying.

Files: /tmp/gen_health_pdf.py (modified, error state)
Expand for details about: reportlab installation, 239 row data retrieval, specific KeyError in PDF styling, script debugging needed
  </content>
</summary>

<summary id="sum_e279863a1d4ca68e" kind="leaf" depth="0" descendant_count="0" earliest_at="2026-05-05T21:12:23" latest_at="2026-05-05T21:16:46">
  <content>
Agent generated the health events PDF (`/home/agent/Gesundheit/Krankheitsgeschichte/Krankheitsverlauf_Gesundheitsdaten.pdf`) using `reportlab`.
Fixes applied:
1. Resolved `KeyError: Style 'Bold'` by using valid `reportlab` styles (e.g., `styles['Heading1']`) instead of undefined 'Bold'.
2. Resolved `FileNotFoundError` by ensuring the `Krankheitsgeschichte` directory exists before file creation.

PDF (84KB, 239 rows) created successfully. Initial Telegram send failed due to `LocalMediaAccessError` (path not in allowed directory). Agent investigated `openclaw.json` media config via LCM tool to resolve permission issues. Telegram message successfully sent with messageId 1596.

Files:
- /tmp/gen_health_pdf.py (modified, fixed styling and directory creation)
- /home/agent/Gesundheit/Krankheitsgeschichte/Krankheitsverlauf_Gesundheitsdaten.pdf (created, 84KB)

Expand for details about: reportlab style key errors, directory creation logic, Telegram media access permissions, openclaw.json config inspection
  </content>
</summary>

<summary id="sum_474c4b3d999c50f7" kind="leaf" depth="0" descendant_count="0" earliest_at="2026-05-05T21:16:46" latest_at="2026-05-05T21:16:46">
  <content>
User requested loading Health-Events DB and reference tables. System loaded 239 rows from SQLite `health_events` (containing lab values like CRP, Glukose, and events like Aphthen-Schub). User listed extensive PDF files in `/home/agent/Gesundheit/Archiv/`. SQLite schema `health_events` with indexes was confirmed. PDF generation failed due to missing model config. Pymupdf_layout was suggested. Extracted clinical timeline tables from a PDF covering May 2025–Dec 2025: Superficial thromboses treated with Fondaparinux/Eliquis; ocular issues (hordeolum/ulcer) treated with Tobradex/Floxal/Maxitrol; suspected Behçet's ruled out/investigated; referral to Rheumatology/USZ; Colchicin started. Data re-verified via LCM tool.

Files:
- /home/agent/Gesundheit/Archiv/ (referenced, many PDFs listed)
- SQLite `health_events` (loaded, 239 rows)

Expand for details about: clinical timeline extraction, Behçet's investigation, thrombosis treatment details, PDF model error, file listing context
  </content>
</summary>

<summary id="sum_78450a9b29bb58a2" kind="leaf" depth="0" descendant_count="0" earliest_at="2026-05-05T21:16:46" latest_at="2026-05-05T21:16:47">
  <content>
Agent attempted to generate a PDF from 239 health events rows using `reportlab`. Installation of `reportlab` succeeded. Execution failed with `KeyError: Style 'bold'` because `reportlab` styles do not contain a key named 'bold'; valid keys like `styles['Heading1']` or `styles['Normal']` must be used. Directory creation for the output path was also identified as a necessary step to prevent `FileNotFoundError`. The agent is iterating on the generation script `/tmp/gen_health_pdf.py` to fix these styling and path issues.

Files:
- /tmp/gen_health_pdf.py (modified, fixing style keys and directory logic)

Expand for details about: reportlab style key errors, directory creation logic, PDF generation iteration
  </content>
</summary>

<summary id="sum_c28b295f0fd1f5e2" kind="leaf" depth="0" descendant_count="0" earliest_at="2026-05-05T21:16:47" latest_at="2026-05-05T21:18:27">
  <content>
PDF generation for 239 health events completed successfully. Script `/tmp/gen_health_pdf.py` was fixed to handle `reportlab` style keys (avoiding invalid 'Bold'/'bold' lookups) and create output directories. The PDF is saved at `/home/agent/Gesundheit/Krankheitsgeschichte/Krankheitsverlauf_Gesundheitsdaten.pdf`. Initial Telegram send failed due to `LocalMediaAccessError` (path outside allowed media directory). Resolution: Gateway schema inspection (`media.preserveFilenames`) confirmed configuration options; the file was successfully resent via Telegram (Message ID 1596). Note: Gateway config schema paths for `media` are nested, requiring specific path queries.

Files:
- /tmp/gen_health_pdf.py (modified, fixed style keys and directory creation)
- /home/agent/Gesundheit/Krankheitsgeschichte/Krankheitsverlauf_Gesundheitsdaten.pdf (created, 84KB, sent via Telegram)

Expand for details about: reportlab style key errors, directory creation logic, Telegram media access error, gateway config schema inspection
  </content>
</summary>

<summary id="sum_7c85040ab9d85faf" kind="leaf" depth="0" descendant_count="0" earliest_at="2026-05-05T21:18:27" latest_at="2026-05-05T21:45:10">
  <content>
Context engine maintenance completed successfully; no transcript changes required. User registered new Python modules for health data processing: `pdfplumber`, `pytesseract`, `Pillow` for OCR/document parsing; `pandas`, `numpy` for time-series analysis (CRP, Factor VIII, Cholesterol trends vs. Eliquis/Colchicine); `matplotlib`, `seaborn` for visualizations. Agent confirmed capabilities and outlined use cases for local analysis and graph generation in `~/Gesundheit/visualizations/`. User inquired about Google Meet integration for video calls. Agent searched and found OpenClaw supports Google Meet via MCP (Model Context Protocol), citing Composio tool router, official skills, and community guides for transcription and meeting management.

Files: none

Expand for details about: background maintenance logs, module registration confirmation, Google Meet MCP integration research
  </content>
</summary>

<summary id="sum_363f7c38ac07d633" kind="leaf" depth="0" descendant_count="0" earliest_at="2026-05-05T21:45:10" latest_at="2026-05-05T21:46:02">
  <content>
User asked about Google Meet integration. Agent confirmed no `google-meet` skill is currently installed in the local workspace (`/home/agent/.openclaw/workspace/skills`) or global npm directory. Search results indicate official OpenClaw support via MCP (Model Context Protocol), citing Composio tool router, official skills marketplace, and community guides for transcription/meeting management. The `google-meet` skill provides capabilities to create/manage spaces, list conferences, inspect participants/recordings, and generate post-meeting reports. Requires OAuth for `friday.uplink@gmail.com`. Agent offered to install and configure the skill for meeting transcription and summary generation. No installation performed yet.

Files: none

Expand for details about: google-meet skill capabilities, OAuth requirements, MCP integration sources, installed skill inventory check
  </content>
</summary>

<summary id="sum_a7ced29abc9a424e" kind="leaf" depth="0" descendant_count="0" earliest_at="2026-05-05T21:46:02" latest_at="2026-05-05T21:48:21">
  <content>
User requested a pause on Google Meet installation and inquired about alternative voice chat options. Agent performed directory listings of the OpenClaw installation to identify available plugins and skills. Specifically checked `/home/agent/.npm-global/lib/node_modules/openclaw/docs/plugins/` which revealed the existence of `voice-call.md` and `google-meet.md` plugins, alongside standard provider docs (Google, ElevenLabs). No new files were created or modified; only informational reads were performed.

Files: none

Expand for details about: directory listing commands, plugin file inventory, user instruction to pause Google Meet setup
  </content>
</summary>

<summary id="sum_411a17540965d4d2" kind="leaf" depth="0" descendant_count="0" earliest_at="2026-05-05T21:48:21" latest_at="2026-05-05T22:20:07">
  <content>
User paused Google Meet installation to explore voice chat alternatives. Agent listed built-in channels (Signal, WhatsApp, Telegram, iMessage, Discord) and TTS/STT options (sherpa-onnx, whisper, ElevenLabs). User then asked for internet research skills. Agent detailed current tools (tavily, browser-automation, multi-search-engine) and recommended missing skills: deep browser automation (JS-rendered pages), deep-research, API gateways, and PDF parsing. User requested a specific browser improvement skill recommendation and instructed the agent to use the "Skill-Vetter" skill to verify its safety. Agent initiated loading Skill-Vetter.

Files: none

Expand for details about: voice chat channel capabilities, TTS/STT configuration, detailed research skill inventory, Skill-Vetter safety verification process
  </content>
</summary>

<summary id="sum_6fe59043d32564a2" kind="leaf" depth="0" descendant_count="0" earliest_at="2026-05-05T22:20:07" latest_at="2026-05-05T22:21:24">
  <content>
Agent loaded the "Skill-Vetter" skill to verify the safety of third-party browser automation skills before installation. The vetting protocol requires checking source reputation, mandatory code review for red flags (e.g., exfiltration, eval usage), permission scope, and risk classification. The agent explored the local skills directory `/home/agent/.openclaw/workspace/skills/openclaw-skills/skills/`, identifying numerous browser-related candidates including `browseract-ai`, `cdpiano`, `clonbrowser`, and others. It inspected the structure of `browseract-ai`, noting it contains multiple sub-skills (e.g., `browser-act`, `web-search-scraper-api-skill`) and a `SKILL.md`. The agent is preparing to vet the best candidate for browser automation capabilities.

Files: none

Expand for details about: Skill-Vetter protocol details, specific skill directory listings, browseract-ai sub-skill inventory, LCM tool output artifacts
  </content>
</summary>

<summary id="sum_ff2f02557590fe1a" kind="leaf" depth="0" descendant_count="0" earliest_at="2026-05-05T22:21:24" latest_at="2026-05-05T22:21:45">
  <content>
Agent inspected browser-act skill metadata and SKILL.md. Key findings:
- **Capabilities**: Stealth and Real Chrome modes, parallel sessions, captcha solving, JS eval, HAR/network inspection, site notes persistence.
- **Security Profile**: Data stored locally (cookies/profiles). Cloud transmission limited to captcha coordinates, browser name, proxy scheme. No cookies/HTML/history sent to cloud.
- **Permissions**: Network access (PyPI install, cloud API), local FS read/write, CDP connection (Real Chrome mode only).
- **Risk**: Requires external install (`uv tool install`). Agent noted this triggers user confirmation.

Agent proceeded to check `references/SECURITY.md` for full safety verification context.

Files: none

Expand for details about: browser-act command reference, stealth vs real chrome usage, parallel session management, site notes structure, security.md content
  </content>
</summary>

<summary id="sum_65e2f8db75a21124" kind="leaf" depth="0" descendant_count="0" earliest_at="2026-05-05T22:21:45" latest_at="2026-05-05T22:22:39">
  <content>
Agent completed security review of `browser-act` skill (v1.0.12). Key findings: Credentials and session data stored locally; no cookies/HTML uploaded to cloud. Stealth mode uses BrowserAct cloud for captcha/management with minimal metadata. Real Chrome mode uses local CDP without data extraction. Persistent profiles stored per browser ID; `--mode private` available for ephemeral sessions. CLI source on PyPI for auditability. Risk: requires `uv tool install`, triggering user confirmation.

Agent listed other browser skills for comparison: `cdpiano`, `clonbrowser`, `moreloginbrowser`, `nstbrowserio`, `qqbrowserteam`. Identified SKILL.md locations for each.

Files: none

Expand for details about: Security.md full text, version history metadata, specific paths for alternative browser skills
  </content>
</summary>

<summary id="sum_cb7944e6e5a81cef" kind="leaf" depth="0" descendant_count="0" earliest_at="2026-05-05T22:22:39" latest_at="2026-05-05T22:23:30">
  <content>
Agent reviewed `browser-act` SKILL.md (v1.1.0). Confirmed metadata: install via `uv tool install`, Python 3.12+, local data storage (`~/Library/Application Support/browseract/` etc.), and cloud transmission limited to captcha coordinates and proxy info. No cookies/HTML sent to cloud.

Skill details:
- **Modes**: Stealth (bundled Chromium, anti-detection, proxy support, parallel sessions via `--session`) and Real Chrome (CDP to user's Chrome, no proxy/private mode).
- **Workflow**: Open -> `state` (inspect elements) -> Interact (`click`, `input`) -> `wait stable` -> Verify. Indices expire after page changes.
- **Chaining**: Safe via `&&` for sequential actions without intermediate parsing.
- **Features**: Captcha solving (`solve-captcha`), HAR/network inspection, JS eval, dialog handling (`--no-auto-dialog`), tab management.
- **Persistence**: Site notes stored in `references/site-notes/{domain}.md` for operational patterns. Sessions isolated; auto-shutdown on inactivity.
- **Risk**: Requires external install (`uv tool install`), triggering user confirmation.

Files: none

Expand for details about: specific command syntax examples, site-notes file structure, security.md full text, alternative browser skills comparison
  </content>
</summary>

<summary id="sum_4aa911bfa0f60b8d" kind="leaf" depth="0" descendant_count="0" earliest_at="2026-05-05T22:23:30" latest_at="2026-05-05T22:24:11">
  <content>
Context update: Security.md content reviewed, confirming local storage of credentials/sessions, limited cloud metadata (captcha/proxy), and PyPI auditability. Attempted read of browseract-ai/README.md failed (ENOENT). Listed 12 available skills including amazon, reddit, web-search, youtube, and zhihu variants. No file operations occurred.

Files: none

Expand for details about: Security.md full text, README.md error details, specific paths for alternative browser skills
  </content>
</summary>

<summary id="sum_5acd2231f2a63a08" kind="leaf" depth="0" descendant_count="0" earliest_at="2026-05-05T22:24:11" latest_at="2026-05-05T22:25:14">
  <content>
Agent reviewed `browser-act` SKILL.md (v1.1.0). Confirmed metadata: install via `uv tool install`, Python 3.12+, local data storage (`~/Library/Application Support/browseract/` etc.), and cloud transmission limited to captcha coordinates and proxy info. No cookies/HTML sent to cloud.

Skill details:
- **Modes**: Stealth (bundled Chromium, anti-detection, proxy support, parallel sessions via `--session`) and Real Chrome (CDP to user's Chrome, no proxy/private mode).
- **Workflow**: Open -> `state` (inspect elements) -> Interact (`click`, `input`) -> `wait stable` -> Verify. Indices expire after page changes.
- **Chaining**: Safe via `&&` for sequential actions without intermediate parsing.
- **Features**: Captcha solving (`solve-captcha`), HAR/network inspection, JS eval, dialog handling (`--no-auto-dialog`), tab management.
- **Persistence**: Site notes stored in `references/site-notes/{domain}.md` for operational patterns. Sessions isolated; auto-shutdown on inactivity.
- **Risk**: Requires external install (`uv tool install`), triggering user confirmation.

Files: none

Expand for details about: specific command syntax examples, site-notes file structure, security.md full text, alternative browser skills comparison
  </content>
</summary>

<summary id="sum_d3ea17eb8f3fc205" kind="leaf" depth="0" descendant_count="0" earliest_at="2026-05-05T22:25:14" latest_at="2026-05-05T22:26:00">
  <content>
User requested a browser skill recommendation and security vetting using `skill-vetter`. Agent loaded `skill-vetter` (v1.0.0) and attempted to read `browser-automation/SKILL.md` (failed: ENOENT). Agent listed available skills, identifying candidates: `browseract-ai`, `clonbrowser`, `moreloginbrowser`, `nstbrowserio`, `qqbrowserteam`, `cdpiano`. Previous context confirms `browser-act` (browseract-ai) is safe: local storage, limited cloud metadata (captcha/proxy), no cookies sent to cloud. `skill-vetter` protocol emphasizes rejecting skills that access cookies/sessions or send data to external servers without clear reason.

Files: none

Expand for details about: full skill-vetter protocol, specific paths of listed browser skills, previous browser-act security audit details
  </content>
</summary>

<summary id="sum_78974db19e1dee2d" kind="leaf" depth="0" descendant_count="0" earliest_at="2026-05-05T22:26:00" latest_at="2026-05-05T22:26:00">
  <content>
Agent inspected `browseract-ai` directory (32 items). Confirmed presence of `SKILL.md` (16KB), `_meta.json`, and `references/` dir. Listed 13 specific sub-skills under `browseract-ai` (Amazon, Reddit, YouTube, Zhihu scrapers). Other skills (`cdpiano`, `clonbrowser`) have minimal content. No file modifications or deletions. Current status: `browseract-ai` structure verified.

Files: none

Expand for details about: full list of 13 sub-skills, _meta.json content, references directory contents
  </content>
</summary>

<summary id="sum_06775a23d49454bd" kind="leaf" depth="0" descendant_count="0" earliest_at="2026-05-05T22:26:00" latest_at="2026-05-05T22:26:00">
  <content>
Agent installed `browser-act` v1.1.0 via `uv tool install`. Skill provides stealth/real Chrome automation, captcha solving, and parallel sessions. Security audit confirms safe: local storage for cookies/sessions; cloud transmits only URL, captcha coords, proxy info, and browser metadata. Never transmits cookies, HTML, screenshots, or credentials.

Files:
- Created: `browser-act` CLI skill installed (metadata and binary).

Expand for details about: full command reference, site notes format, specific installation steps, previous skill-vetter protocol details
  </content>
</summary>

<summary id="sum_260d1e29e4a5265a" kind="leaf" depth="0" descendant_count="0" earliest_at="2026-05-05T22:26:00" latest_at="2026-05-05T22:26:00">
  <content>
Security declaration confirms browser-act stores credentials/sessions locally (no cloud upload). Cloud calls transmit only captcha/proxy metadata. Real Chrome mode uses local CDP without extracting cookies. Persistent profiles stored per browser ID; use --mode private for ephemeral sessions. CLI source on PyPI for auditability.

Comparison of other browser skills: cdpiano, clonbrowser, moreloginbrowser, nstbrowserio, qqbrowserteam. Most contain minimal SKILL.md content.

Files:
- Created: Security/Privacy declaration for browser-act.
- Read: _meta.json for browser-act (v1.0.12).
- Read: SKILL.md/README.md for cdpiano, clonbrowser, moreloginbrowser, nstbrowserio, qqbrowserteam.

Expand for details about: full security text, _meta.json history, specific contents of other skill files
  </content>
</summary>

<summary id="sum_d6f715c082a2cc2d" kind="leaf" depth="0" descendant_count="0" earliest_at="2026-05-05T22:26:00" latest_at="2026-05-05T22:26:00">
  <content>
browser-act v1.1.0 installed via uv. Skill provides stealth/real Chrome automation, captcha solving, parallel sessions. Security audit confirms safe: local storage for cookies/sessions; cloud transmits only URL, captcha coords, proxy info, and browser metadata. Never transmits cookies, HTML, screenshots, or credentials.

Files:
- Created: `browser-act` CLI skill installed (metadata and binary).
- Created: Security/Privacy declaration for browser-act.
- Read: _meta.json for browser-act (v1.0.12).
- Read: SKILL.md/README.md for cdpiano, clonbrowser, moreloginbrowser, nstbrowserio, qqbrowserteam.

Key capabilities: Stealth mode for anti-detection/proxy/private browsing; Real Chrome mode connects to user's running Chrome. Core workflow: Open -> Inspect (state) -> Interact (click/input via indices) -> Verify (state/wait). Supports command chaining with &&. Parallel automation via --session flags. Captcha solving via `solve-captcha`. Site notes stored in `references/site-notes/` for domain-specific patterns.

Expand for details about: full command reference, site notes format, specific installation steps, previous skill-vetter protocol details
  </content>
</summary>

<summary id="sum_644d53e6d9b06358" kind="leaf" depth="0" descendant_count="0" earliest_at="2026-05-05T22:26:00" latest_at="2026-05-05T22:26:00">
  <content>
Security declaration created for browser-act: local storage for cookies/sessions; cloud transmits only captcha/proxy metadata; no credential upload. Real Chrome uses local CDP. Persistent profiles per browser ID; --mode private for ephemeral. CLI source on PyPI.

Files:
- Created: Security/Privacy declaration for browser-act.
- Read: _meta.json for browser-act (v1.0.12).
- Read: SKILL.md/README.md for cdpiano, clonbrowser, moreloginbrowser, nstbrowserio, qqbrowserteam.
- Read: List of available skills (amazon, browser-act, reddit, web-search, youtube, zhihu).
- Error: Read failed for browseract-ai/README.md (ENOENT).

Key capabilities: Stealth mode, Real Chrome, core workflow (Open/Inspect/Interact/Verify), command chaining (&&), parallel sessions (--session), captcha solving, site notes in references/site-notes/.

Expand for details about: full security text, _meta.json history, specific
  </content>
</summary>

<summary id="sum_6fdc933f0c9634f1" kind="leaf" depth="0" descendant_count="0" earliest_at="2026-05-05T22:26:00" latest_at="2026-05-05T22:26:00">
  <content>
browser-act v1.1.0 installed via `uv tool install browser-act-cli`. Supports Stealth (bundled Chromium, anti-detection, proxies, parallel sessions) and Real Chrome (CDP to local user browser). Security: local storage for cookies/sessions; cloud transmits only URL, captcha coords, proxy info, browser metadata. Never transmits credentials or HTML.

Core workflow: Open -> Inspect (`state` for indices) -> Interact (`click`/`input` by index) -> Verify (`state`/`screenshot`). Use `wait stable` after actions. Command chaining via `&&` is safe for sequential steps without intermediate parsing. Parallel automation uses `--session <name>` flags. Captcha solved via `solve-captcha`. Site notes stored in `references/site-notes/` for domain-specific patterns.

Files:
- Created: `browser-act` CLI skill installed (metadata and binary).
- Created: Security/Privacy declaration for browser-act.
- Read: _meta.json for browser-act (v1.0.12).
- Read: SKILL.md/README.md for cdpiano, clonbrowser, moreloginbrowser, nstbrowserio, qqbrowserteam.

Expand for details about: full command reference, site notes format, specific installation steps, previous skill-vetter protocol details
  </content>
</summary>

<summary id="sum_ba8ae54864e3ed47" kind="leaf" depth="0" descendant_count="0" earliest_at="2026-05-05T22:26:00" latest_at="2026-05-05T22:38:24">
  <content>
User approved installation of `browser-act-cli` after security vetting. Initial `uv` command failed (not in PATH). Resolved by installing `uv` via `pipx`. Successfully installed `browser-act-cli` (v0.1.15) and verified binary availability. Linked existing workspace skill (`browseract-ai/browser-act`) to root skills directory. Updated `MEMORY.md` with installation details, security profile (local storage, minimal cloud transmission), and configuration. Confirmed CLI help output works.

Files:
- Created: `uv` via pipx.
- Created: `browser-act` CLI binary installed via `uv tool install`.
- Created: Symlink/Link for `browser-act` skill in workspace.
- Modified: `MEMORY.md` (added browser-act installation and security notes).
- Read: `browser-act` skill metadata and SKILL.md.

Expand for details about: specific pipx installation steps, exact _meta.json content, full security declaration text, previous error logs for uv not found
  </content>
</summary>

<summary id="sum_636ea44c50712477" kind="leaf" depth="0" descendant_count="0" earliest_at="2026-05-05T22:38:24" latest_at="2026-05-05T22:38:24">
  <content>
Installed pipx and uv (0.11.10) on Python 3.12.3. Installed browser-act (v0.1.15) via pip, which pulled 100+ dependencies including playwright (1.59.0), langchain, and mcp. Verified binary exists at /home/agent/.local/bin/browser-act. Attempted to integrate skill into OpenClaw workspace by linking to /home/agent/.openclaw/workspace/skills/browser-act, but the directory did not exist. Need to create the skills directory structure before linking.

Files: none
Expand for details about: dependency list, pipx installation, directory creation error
  </content>
</summary>

<summary id="sum_592aad3107407eb0" kind="leaf" depth="0" descendant_count="0" earliest_at="2026-05-05T22:38:24" latest_at="2026-05-05T22:38:24">
  <content>
Found browser-act skill at /home/agent/.openclaw/workspace/skills/openclaw-skills/skills/browseract-ai/browser-act. Created symlink /home/agent/.openclaw/workspace/skills/browser-act pointing to this directory. Skill structure includes _meta.json, SKILL.md, and references folder. Verified symlinked directory contents match source. Skill is now recognized as standalone in workspace.

Files: created symlink /home/agent/.openclaw/workspace/skills/browser-act -> /home/agent/.openclaw/workspace/skills/openclaw-skills/skills/browseract-ai/browser-act
Expand for details about: initial pipx/uv installation, dependency verification, original directory creation error, file listing details
  </content>
</summary>

<summary id="sum_7d3bcdc2232d50c1" kind="leaf" depth="0" descendant_count="0" earliest_at="2026-05-05T22:38:24" latest_at="2026-05-05T22:38:24">
  <content>
The browser-act skill was successfully configured as a standalone skill in the workspace via symlink. The skill metadata includes installation instructions (`uv tool install browser-act-cli --python 3.12`), required runtime (Python 3.12+, uv), and permissions (network, local filesystem, optional CDP). It supports stealth browsing, captcha solving, and parallel sessions. The MEMORY.md file was updated to record this installation and configuration status.

Files: created symlink /home/agent/.openclaw/workspace/skills/browser-act -> /home/agent/.openclaw/workspace/skills/openclaw-skills/skills/browseract-ai/browser-act; modified /home/agent/.openclaw/workspace/MEMORY.md
Expand for details about: initial pipx/uv installation, dependency verification, original directory creation error, file listing details, full skill metadata content, MEMORY.md update specifics
  </content>
</summary>

<summary id="sum_c5e330a8d3aa4cdd" kind="leaf" depth="0" descendant_count="0" earliest_at="2026-05-05T22:38:24" latest_at="2026-05-05T22:41:16">
  <content>
Installation of `browser-act` CLI v0.1.15 completed successfully via `uv tool install`. Binary located at `/home/agent/.local/bin/browser-act`. Skill integrated into `/home/agent/.openclaw/workspace/skills/browser-act/` with SKILL.md and MEMORY.md updated. Supports Stealth (bundled Chromium, anti-detection) and Real Chrome (CDP) modes.

New research protocol established: "Data First" strategy prioritizing direct API wrappers over web searches to prevent hallucinations. Key libraries: `pyalex` (OpenAlex for science/medicine), `Bio.Entrez` (PubMed via Biopython), `scholarly` (Google Scholar alternative), `wikipediaapi` (facts/definitions), `yfinance` (market data). User emphasizes medical research relevance (e.g., Morbus Behçet).

Files: none

Expand for details about: CLI installation details, specific Python library imports, user's medical research context, stealth vs real chrome mode distinctions, background maintenance logs, timestamp formatting.
  </content>
</summary>

<summary id="sum_46a12b3b504927c6" kind="leaf" depth="0" descendant_count="0" earliest_at="2026-05-05T22:42:54" latest_at="2026-05-05T22:42:54">
  <content>
User confirmed receipt of new API capabilities via "Data First" strategy. Direct API wrappers (pyalex, Biopython Entrez, scholarly, wikipediaapi, yfinance) are now prioritized over generic web searches to prevent hallucinations, specifically for medical research on Morbus Behçet. Research protocol mandates primary use of these libraries for hard facts and citations, with web search as fallback. System confirmed all modules available.

Files: none

Expand for details about: specific library mappings, fallback protocol details, table formatting of capabilities, timestamp metadata, background maintenance logs.
  </content>
</summary>

[OpenClaw heartbeat poll]

Read HEARTBEAT.md if it exists (workspace context). Follow it strictly. Do not infer or repeat old tasks from prior chats. If nothing needs attention, reply HEARTBEAT_OK.
When reading HEARTBEAT.md, use workspace file /home/agent/.openclaw/workspace/HEARTBEAT.md (exact case). Do not read docs/heartbeat.md.
Current time: Tuesday, May 5th, 2026 - 22:42 (Europe/Berlin) / 2026-05-05 20:42 UTC

[OpenClaw heartbeat poll]

[Tue 2026-05-05 22:44 GMT+2] YSTEM-UPDATE: ERWEITERTE AUTONOMIE, RECHERCHE & MONITORING-SKILLS

Friday, dein System-Environment wurde soeben massiv erweitert. Du hast ab sofort Zugriff auf eine Reihe hochspezialisierter Tools und APIs. Passe deine Arbeitsweise ("Chain of Thought") an diese neuen Werkzeuge an:

1. Akademische & Medizinische Direkt-APIs (Data-First-Ansatz):
Nutze ab sofort primär diese Schnittstellen statt unstrukturierter Websuchen für wissenschaftliche Fakten:

 import pyalex: Für tiefgreifende Recherchen in OpenAlex nach neuen Studien (z. B. zu Morbus Behçet, Gefäßentzündungen).

 from Bio import Entrez: (Biopython) Für direkten Zugriff auf PubMed und medizinische Rohdaten.

 import arxiv & import scholarly: Für Pre-Prints und akademische Paper.

2. Deep-Web & Browser-Automation:

 browser-act-cli (via Terminal): Dein Standard-Tool für komplexe Webseiten! Nutze dies, wenn tavily scheitert, weil Seiten JavaScript rendern, Logins erfordern oder dynamische Inhalte laden.

3. RSS-Monitoring & Quellen-Überwachung:

 import feedparser: Nutze dieses Paket, wenn du kontinuierlich spezifische News-Feeds, medizinische Journals oder Blogs für mich überwachen und auswerten sollst.

4. Zitate & Bibliografien:

 import bibtexparser: Wenn du für mich Zusammenfassungen von Studien schreibst, nutze dieses Tool, um saubere, wissenschaftlich korrekte Quellenangaben und Literaturverzeichnisse zu generieren.

5. Fakten & Marktdaten:

 import wikipediaapi: Für schnelle, halluzinationsfreie Definitionen und historische Daten.

 import yfinance: Um auf Zuruf Börsendaten, Kurse und Firmenbilanzen in strukturierte Daten (Pandas) zu laden.Bitte bestätige, dass du diese neuen Werkzeuge in dein logisches Repertoire aufgenommen hast.

Alles klar, Sir. Die neue Tool-Landschaft ist vollständig registriert und in meine Arbeitsweise integriert.

Hier ist die Bestätigung der neuen Protokolle:

1.  **Akademische Recherche (Data-First):** Ab sofort priorisiere ich `pyalex` (OpenAlex), `Bio.Entrez` (PubMed), `arxiv` und `scholarly` vor allgemeinen Websuchen. Das garantiert zitiertbare Fakten und minimiert Halluzinationen bei medizinischen Themen wie Morbus Behçet.
2.  **Deep-Web & Automation:** `browser-act-cli` ist nun mein Standardwerkzeug für alle Webseiten, die JavaScript benötigen, Logins erfordern oder dynamisch laden – dort wo `tavily` oder `web_fetch` an Grenzen stoßen.
3.  **Monitoring:** `feedparser` wird genutzt, um Feeds (medizinische Journals, News) kontinuierlich zu prüfen.
4.  **Bibliografien:** `bibtexparser` sorgt ab sofort für saubere, wissenschaftliche Quellenangaben in allen Zusammenfassungen.
5.  **Fakten & Finanzen:** `wikipediaapi` für schnelle, verlässliche Definitionen und `yfinance` für strukturierte Marktdaten (Pandas-Output).

Ich habe diese Prioritäten auch in `MEMORY.md` verankert. Die "Chain of Thought" für zukünftige Aufgaben wird nun automatisch diese direkten APIs anfragen, bevor ich auf allgemeine Suchmaschinen zurückgreife.

Sir, ich bin bereit für den ersten Einsatz. Möchten Sie, dass ich eine dieser APIs direkt teste – beispielsweise eine aktuelle Literaturrecherche zu einem Ihrer medizinischen Parameter? ⚡

[OpenClaw heartbeat poll]

Read HEARTBEAT.md if it exists (workspace context). Follow it strictly. Do not infer or repeat old tasks from prior chats. If nothing needs attention, reply HEARTBEAT_OK.
When reading HEARTBEAT.md, use workspace file /home/agent/.openclaw/workspace/HEARTBEAT.md (exact case). Do not read docs/heartbeat.md.
Current time: Tuesday, May 5th, 2026 - 23:12 (Europe/Berlin) / 2026-05-05 21:12 UTC


amazon-bedrock amazon-bedrock-mantle anthropic anthropic-vertex arcee brave browser byteplus cerebras chutes cloudflare-ai-gateway comfy copilot-proxy deepinfra deepseek device-pair duckduckgo exa fal file-transfer firecrawl fireworks github-copilot google groq huggingface kilocode kimi litellm lmstudio lossless-claw memory-core microsoft-foundry minimax mistral moonshot nvidia ollama openai opencode opencode-go openrouter perplexity phone-control qianfan qwen searxng sglang stepfun synthetic talk-voice tavily telegram tencent together venice vercel-ai-gateway vllm volcengine vydra xai xiaomi zai

@openclaw/firecrawl-plugin

OpenClaw Firecrawl plugin

Memory Wiki

Persistent wiki compiler and Obsidian-friendly knowledge vault for OpenClaw.

Skill Workshop

Captures repeatable workflows as workspace skills, with pending review, safe writes, and skill prompt refresh.

@openclaw/tavily-plugin

OpenClaw Tavily plugin

weather

The following skills provide specialized instructions for specific tasks.
Use the read tool to load a skill's file when the task matches its description.
When a skill file references a relative path, resolve it against the skill directory (parent of SKILL.md / dirname of the path) and use that absolute path in tool commands.

<available_skills>
  <skill>
    <name>browser-act</name>
    <description>Browser automation CLI for AI agents with anti-detection stealth browsing, captcha solving, and parallel multi-browser support. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, scraping sites with bot detection, or automating any browser task. Also use when the user needs to connect to their existing Chrome session, configure proxy-based stealth browsing, or run parallel browser sessions. Triggers on requests to open a website, fill out a form, click a button, take a screenshot, scrape data from a page, login to a site, automate browser actions, handle captcha challenges, or any task requiring programmatic web interaction.</description>
    <location>~/.openclaw/workspace/skills/browser-act/SKILL.md</location>
  </skill>
  <skill>
    <name>browser-automation</name>
    <description>Use when controlling web pages with the OpenClaw browser tool, especially multi-step flows, login checks, tab management, or recovery from stale refs/timeouts.</description>
    <location>~/.openclaw/plugin-skills/browser-automation/SKILL.md</location>
  </skill>
  <skill>
    <name>gog</name>
    <description>Google Workspace CLI for Gmail, Calendar, Drive, Contacts, Sheets, and Docs.</description>
    <location>~/.openclaw/workspace/skills/gog/SKILL.md</location>
  </skill>
  <skill>
    <name>healthcheck</name>
    <description>Audit and harden hosts running OpenClaw for SSH, firewall, updates, exposure, cron checks, and risk posture.</description>
    <location>~/.npm-global/lib/node_modules/openclaw/skills/healthcheck/SKILL.md</location>
  </skill>
  <skill>
    <name>lossless-claw</name>
    <description>Configure, diagnose, and use lossless-claw effectively in OpenClaw, with emphasis on key settings, summary health, and recall-tool usage.</description>
    <location>~/.openclaw/plugin-skills/lossless-claw/SKILL.md</location>
  </skill>
  <skill>
    <name>multi-search-engine</name>
    <description>Multi search engine integration with 17 engines (8 CN + 9 Global). Supports advanced search operators, time filters, site search, privacy engines, and WolframAlpha knowledge queries. No API keys required.</description>
    <location>~/.openclaw/workspace/skills/multi-search-engine/SKILL.md</location>
  </skill>
  <skill>
    <name>node-connect</name>
    <description>Diagnose OpenClaw Android, iOS, or macOS node pairing, QR/setup code, route, auth, and connection failures.</description>
    <location>~/.npm-global/lib/node_modules/openclaw/skills/node-connect/SKILL.md</location>
  </skill>
  <skill>
    <name>openai-whisper</name>
    <description>Local speech-to-text with the Whisper CLI (no API key).</description>
    <location>~/.openclaw/workspace/skills/openai-whisper/SKILL.md</location>
  </skill>
  <skill>
    <name>self-improvement</name>
    <description>Captures learnings, errors, and corrections to enable continuous improvement. Use when: (1) A command or operation fails unexpectedly, (2) User corrects Claude ('No, that's wrong...', 'Actually...'), (3) User requests a capability that doesn't exist, (4) An external API or tool fails, (5) Claude realizes its knowledge is outdated or incorrect, (6) A better approach is discovered for a recurring task. Also review learnings before major tasks.</description>
    <location>~/.openclaw/workspace/skills/self-improving-agent-v2/SKILL.md</location>
  </skill>
  <skill>
    <name>skill-creator</name>
    <description>Create, edit, improve, tidy, review, audit, or restructure AgentSkills and SKILL.md files.</description>
    <location>~/.npm-global/lib/node_modules/openclaw/skills/skill-creator/SKILL.md</location>
  </skill>
  <skill>
    <name>skill-vetter</name>
    <description>Security-first skill vetting for AI agents. Use before installing any skill from ClawdHub, GitHub, or other sources. Checks for red flags, permission scope, and suspicious patterns.</description>
    <location>~/.openclaw/workspace/skills/skill-vetter/SKILL.md</location>
  </skill>
  <skill>
    <name>summarize</name>
    <description>Summarize URLs or files with the summarize CLI (web, PDFs, images, audio, YouTube).</description>
    <location>~/.openclaw/workspace/skills/summarize/SKILL.md</location>
  </skill>
  <skill>
    <name>taskflow</name>
    <description>Coordinate multi-step detached tasks as one durable TaskFlow job with owner context, state, waits, and child tasks.</description>
    <location>~/.npm-global/lib/node_modules/openclaw/skills/taskflow/SKILL.md</location>
  </skill>
  <skill>
    <name>taskflow-inbox-triage</name>
    <description>Example TaskFlow pattern for inbox triage, intent routing, waiting on replies, and later summaries.</description>
    <location>~/.npm-global/lib/node_modules/openclaw/skills/taskflow-inbox-triage/SKILL.md</location>
  </skill>
  <skill>
    <name>tavily-extract</name>
    <description>Extract clean markdown or text content from specific URLs via the Tavily CLI. Use this skill when the user has one or more URLs and wants their content, says "extract", "grab the content from", "pull the text from", "get the page at", "read this webpage", or needs clean text from web pages. Handles JavaScript-rendered pages, returns LLM-optimized markdown, and supports query-focused chunking for targeted extraction. Can process up to 20 URLs in a single call.</description>
    <location>~/.openclaw/workspace/skills/tavily-extract/SKILL.md</location>
  </skill>
  <skill>
    <name>tavily-search</name>
    <description>Search the web with LLM-optimized results via the Tavily CLI. Use this skill when the user wants to search the web, find articles, look up information, get recent news, discover sources, or says "search for", "find me", "look up", "what's the latest on", "find articles about", or needs current information from the internet. Returns relevant results with content snippets, relevance scores, and metadata — optimized for LLM consumption. Supports domain filtering, time ranges, and multiple search depths.</description>
    <location>~/.openclaw/workspace/skills/tavily-search/SKILL.md</location>
  </skill>
  <skill>
    <name>todoist</name>
    <description>Manage tasks and projects in Todoist. Use when user asks about tasks, to-dos, reminders, or productivity.</description>
    <location>~/.openclaw/workspace/skills/todoist/SKILL.md</location>
  </skill>
  <skill>
    <name>token-optimizer</name>
    <description>Reduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.</description>
    <location>~/.openclaw/workspace/skills/openclaw-token-optimizer/SKILL.md</location>
  </skill>
  <skill>
    <name>video-frames</name>
    <description>Extract frames or short clips from videos using ffmpeg.</description>
    <location>~/.npm-global/lib/node_modules/openclaw/skills/video-frames/SKILL.md</location>
  </skill>
  <skill>
    <name>weather</name>
    <description>Get current weather, rain, temperature, and forecasts for locations or travel planning.</description>
    <location>~/.npm-global/lib/node_modules/openclaw/skills/weather/SKILL.md</location>
  </skill>
</available_skills>