Log Automation — Append log entries to Google Sheet
v1.0.0Log Automation — Append log entries, record audit trails, and automate event logging to a pre-configured Google Sheet by PortEden Secure access.
⭐ 0· 171·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The skill name/description describe appending logs to a Google Sheet and the SKILL.md exclusively invokes the 'porteden' CLI and the PE_API_KEY / PE_SHEET_ID env vars. Asking for the porteden binary and an API key + sheet ID is consistent with that purpose.
Instruction Scope
Runtime instructions remain focused on finding the sheet ID, reading header rows, and appending rows via the CLI. The doc suggests persisting PE_SHEET_ID/PE_PROFILE into shell profiles or a .env file and supports reading a local CSV file for bulk import — both are expected for this workflow but are user-visible actions that persist credentials or read local files, so users should be aware they may expose the token if stored insecurely.
Install Mechanism
Install options are brew (porteden/tap/porteden) and go install from github.com/porteden/cli. Both are standard installers; the brew entry is a third-party tap (porteden/tap) rather than an official core formula — reasonable but the user should review the tap/formula and the GitHub repo before installing.
Credentials
Only PE_API_KEY (primary) and PE_SHEET_ID are required. These are appropriate for a CLI that authenticates to PortEden and targets a specific spreadsheet. The documentation correctly notes token scope requirements (Drive access).
Persistence & Privilege
The skill does not request always:true and does not attempt to modify other skills or system-wide agent settings. It recommends storing credentials in the system keyring or shell profiles (user actions), which is normal for a CLI but should be done carefully by the user.
Assessment
This skill appears to do what it says, but before installing: 1) Verify the porteden CLI source (review the GitHub repo and the brew tap/formula) to ensure you trust the publisher; 2) Restrict the PE_API_KEY token to the minimum Drive scopes needed (prefer a dedicated logging/service token or account); 3) Prefer storing credentials in the system keyring (recommended by the docs) rather than putting PE_API_KEY into ~/.bashrc/.zshrc/.env if you are worried about other processes or users reading your shell files; 4) Test against a non-production spreadsheet to confirm behavior; and 5) Be aware that using --csv-file will read local files you point it at — avoid pointing it at sensitive files unless intended.Like a lobster shell, security has layers — review code before you run it.
latestvk975d5agtg0qttz0sk1va8ybrd834dx3
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
📋 Clawdis
Binsporteden
EnvPE_API_KEY, PE_SHEET_ID
Primary envPE_API_KEY
Install
Install porteden (brew)
Bins: porteden
brew install porteden/tap/portedenInstall porteden (go)
Bins: porteden
go install github.com/porteden/cli/cmd/porteden@latest