protonmail-claw_skill

This skill helps you automate ProtonMail tasks like login, read, and send emails using Playwright, saving time and eliminating repetitive inbox chores.
  • Python

2.6k

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill protonmail-claw

  • _meta.json291 B
  • SKILL.md7.6 KB

Overview

This skill automates ProtonMail using Playwright browser automation to log in, read, compose, send, and manage encrypted emails through the web UI. It avoids IMAP/SMTP and works by controlling a real browser session so you can script mailbox tasks without official APIs. It includes bot-detection evasion techniques and guidance for saving sessions to reduce repeated logins.

How this skill works

The skill launches Chromium via Playwright, injects small scripts and launch flags to reduce headless detection, and navigates ProtonMail pages to perform actions. It automates form fills, clicks, keyboard navigation, and DOM queries to list messages, open content, and send mail. You can persist context/cookies to reuse authenticated sessions and avoid 2FA barriers.

When to use it

  • Automate routine inbox tasks like triage, backups, or bulk sends from a ProtonMail account
  • Integrate ProtonMail actions into agents, bots, or scheduled jobs without using ProtonMail APIs
  • Run headless mailbox checks and trigger workflows based on new messages
  • Create archived backups or exports of messages using a scripted browser session
  • Prototype workflows that require interaction with ProtonMail’s web UI when APIs are unavailable

Best practices

  • Store credentials in environment variables and never hardcode passwords
  • Save and reuse browser context/cookies after a manual 2FA login to avoid repeating 2FA in automation
  • Prefer text or ARIA selectors over fragile class names; update selectors if the UI changes
  • Throttle actions and add waits to mimic human timing and avoid rate limiting
  • Test in headed mode first and adjust stealth settings if login fails

Example use cases

  • Scheduled script that checks inbox and forwards important messages to a team channel
  • Automated backup job that scrapes subjects and message bodies into a local archive
  • Agent that reads incoming requests and triggers downstream automation based on content
  • Batch send of templated responses via the compose flow when no SMTP is available
  • Session-saving helper that reuses cookies to keep long-running automation authenticated

FAQ

No. The recommended approach is to perform an initial manual login with 2FA, save the browser context/cookies, and reuse that session in automation.

Is headless detection fully solved?

No. The skill includes common evasion flags and scripts that reduce detection, but ProtonMail may still detect automation occasionally. Use headed mode for debugging and adjust waits and user agent strings.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
protonmail-claw skill by openclaw/skills | VeilStrat