Actionbook

This appears to be a coherent manual for a browser-automation CLI, not executable code — but there are important caveats: - Origin: the skill is instruction-only and references an external 'actionbook' CLI with no install provided. Verify the source and obtain the CLI from a trusted publisher before following commands. - Secrets: the docs show using environment variables for usernames, passwords, tokens, and cookies. Do not paste real credentials into example commands; prefer ephemeral credentials or test accounts. Confirm which env vars the agent or host will actually expose before running automation. - Persistence: profiles and cookies are stored on disk (e.g., ~/.config/actionbook/). If you use this, restrict directory permissions, delete profiles when finished, and avoid reusing profiles that contain unrelated account sessions. - Privileged operations: commands like browser eval and cookies set can access arbitrary page data and session tokens — run in an isolated environment or sandbox, especially for unfamiliar sites. - Metadata mismatch: the skill metadata declares no required binaries/credentials/config paths, but the instructions clearly use them. Treat that as a red flag: ask the publisher for clarification about expected local tooling, config locations, and what secrets (if any) you must supply. If you decide to use it: test against non-production/test accounts, run the CLI in a disposable container or VM, and wipe profiles/cookies after use.