Secure Google Docs access for OpenClaw By PortEden

Secure Google Docs Management - permission-based create, read, and edit doc content; manage sharing, permissions, rename and delete.

This skill appears coherent with its purpose, but before installing: - Verify the upstream sources: confirm porteden.com, the brew tap (porteden/tap), and the GitHub module (github.com/porteden/cli) are the legitimate project repos. - Understand auth: the CLI can use a PE_API_KEY or browser OAuth stored in your system keyring; prefer least-privilege API keys and check what scopes the key grants (Drive read/write). - Be cautious with --ops-file: the CLI will read any file you point it at. Do not pass paths that contain secrets or unrelated sensitive data. - Confirm sharing/deletion prompts: the tool can share or move docs to trash; follow the advice to confirm before using share or delete commands. - Installing adds a new binary to your system; inspect the package or source if you require stronger assurance (review the brew formula and the GitHub repo). - Monitor Google account audit logs and rotate credentials if you stop using the CLI. If you want more assurance, provide the brew formula URL or the GitHub repo so I can highlight exact files/commands to inspect.

Type: OpenClaw Skill Name: porteden-docs Version: 1.0.0 The skill bundle provides a standard interface for an AI agent to manage Google Docs via the 'porteden' CLI tool. It includes well-documented instructions for authentication, document CRUD operations, and permission management without any evidence of malicious intent, data exfiltration, or prompt injection. The installation procedures (Homebrew and Go) and the use of system keyrings for credential storage are standard practices for CLI-based integrations.