Secure Google Docs access for OpenClaw By PortEden

v1.0.0

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

0· 220·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for porteden/porteden-docs.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Secure Google Docs access for OpenClaw By PortEden" (porteden/porteden-docs) from ClawHub.
Skill page: https://clawhub.ai/porteden/porteden-docs
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Required env vars: PE_API_KEY
Required binaries: porteden
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install porteden-docs

ClawHub CLI

Package manager switcher

npx clawhub@latest install porteden-docs
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description describe Google Docs management and the skill only requires the 'porteden' CLI and a PE_API_KEY. Both are appropriate and expected for a CLI-based Google Drive/Docs integration.
Instruction Scope
SKILL.md instructs the agent to run porteden docs commands, use browser login or token stored in system keyring, and optionally pass a local ops-file (e.g., ./ops.json) for bulk edits. This is within scope, but be aware that using --ops-file means the CLI (and thus the agent when directed to use a file) can read local files you point it at — avoid referencing sensitive local files in ops-file paths.
Install Mechanism
Install spec uses a brew formula (porteden/tap/porteden) or go install for github.com/porteden/cli — both are standard package sources. No arbitrary URL downloads or extract-from-untrusted-host steps are present.
Credentials
Only PE_API_KEY (primary) and optional PE_PROFILE/PE_FORMAT/PE_COLOR/PE_VERBOSE are declared. These are proportional to a CLI that can use an API key and profile settings. No unrelated cloud credentials or broad secrets are requested.
Persistence & Privilege
Skill is not always-enabled and does not request system-wide config changes. It notes credentials persist in the system keyring (expected for CLI auth) and does not declare access to other skills' configs or elevated platform privileges.
Assessment
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.

Like a lobster shell, security has layers — review code before you run it.

Runtime requirements

📄 Clawdis
Binsporteden
EnvPE_API_KEY
Primary envPE_API_KEY

Install

Install porteden (brew)
Bins: porteden
brew install porteden/tap/porteden
Install porteden (go)
Bins: porteden
go install github.com/porteden/cli/cmd/porteden@latest
latestvk97bj87efjc817dy4r73b1f3ks8353yk
220downloads
0stars
1versions
Updated 4w ago
v1.0.0
MIT-0

porteden docs

Use porteden docs for Google Docs content operations and file management. Use -jc flags for AI-optimized output.

If porteden is not installed: brew install porteden/tap/porteden (or go install github.com/porteden/cli/cmd/porteden@latest).

Setup (once)

  • Browser login (recommended): porteden auth login — opens browser, credentials stored in system keyring
  • Direct token: porteden auth login --token <key> — stored in system keyring
  • Verify: porteden auth status
  • If PE_API_KEY is set in the environment, the CLI uses it automatically (no login needed).
  • Drive access requires a token with driveAccessEnabled: true and a connected Google account with Drive scopes.

Docs commands (porteden docs)

Content

  • Create new doc: porteden docs create --name "Meeting Notes"
  • Create in folder: porteden docs create --name "Brief" --folder google:0B7_FOLDER
  • Read content (plain text): porteden docs read google:DOCID
  • Read structured (full Google Docs API JSON): porteden docs read google:DOCID --format structured -j
  • Append text: porteden docs edit google:DOCID --append "New paragraph."
  • Insert at start: porteden docs edit google:DOCID --insert "Header text" --at 1
  • Find and replace: porteden docs edit google:DOCID --find "old text" --replace "new text"
  • Multiple replacements: porteden docs edit google:DOCID --find "foo" --replace "bar" --find "baz" --replace "qux"
  • Bulk ops from file: porteden docs edit google:DOCID --ops-file ./ops.json

File management

  • Get export links (pdf, docx, txt): porteden docs download google:DOCID -jc
  • Share: porteden docs share google:DOCID --type user --role writer --email user@example.com
  • Share publicly: porteden docs share google:DOCID --type anyone --role reader
  • List permissions: porteden docs permissions google:DOCID -jc
  • Rename: porteden docs rename google:DOCID --name "New Title"
  • Delete (trash): porteden docs delete google:DOCID -y

Ops file format

--ops-file accepts a JSON array of operations:

[
  {"type": "appendText", "text": "New paragraph at end."},
  {"type": "insertText", "text": "Header", "index": 1},
  {"type": "replaceText", "find": "old phrase", "replace": "new phrase", "matchCase": true}
]

Notes

  • Credentials persist in the system keyring after login. No repeated auth needed.
  • Set PE_PROFILE=work to avoid repeating --profile.
  • -jc is shorthand for --json --compact: strips noise, limits fields, reduces tokens for AI agents.
  • File IDs are always provider-prefixed (e.g., google:1BxiMVs0XRA5...). Pass them as-is.
  • porteden docs read returns plain text by default; use --format structured for full API JSON with headings and formatting.
  • --find and --replace are repeatable and must be used in matched pairs. --ops-file is mutually exclusive with inline edit flags.
  • porteden docs download returns URLs only — no binary content is streamed.
  • accessInfo in responses describes active token restrictions.
  • delete moves to trash (reversible). Files can be restored from Google Drive trash.
  • Confirm before sharing or deleting.
  • Environment variables: PE_API_KEY, PE_PROFILE, PE_FORMAT, PE_COLOR, PE_VERBOSE.

Comments

Loading comments...