ClawHub

Google Sheets File Automation

v1.0.0

Automated Google Sheets Data Writer — Append rows, update cells, and automate spreadsheet data pipelines with a pre-configured target sheet.

⭐ 0· 142·0 current·0 all-time
by@porteden
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
The name/description (Google Sheets writer) match the declared requirements: a porteden CLI binary, PE_API_KEY (primary credential) and PE_SHEET_ID. These are exactly what a CLI-based Sheets automation tool would need.
✓
Instruction Scope
SKILL.md contains direct CLI instructions for authenticating, locating a spreadsheet, reading, writing, and appending ranges. It does not instruct the agent to read unrelated system files or other secrets. It does recommend persisting PE_SHEET_ID in shell profiles or using system keyring for tokens — standard for a CLI tool but user-visible and explicit.
✓
Install Mechanism
Install options are a Homebrew formula (porteden/tap/porteden) or a Go 'go install' module matching github.com/porteden/cli. Both are typical installation methods for a CLI and are proportionate to the skill's stated needs. No arbitrary downloads or unknown short URLs are used.
✓
Credentials
Requested environment variables (PE_API_KEY as primary, PE_SHEET_ID and optional PE_PROFILE/PE_FORMAT/etc.) align with the functionality. The skill requires Drive access scopes for Google tokens (documented). It does not request unrelated credentials or system secrets.
✓
Persistence & Privilege
The skill is not always-enabled and does not request elevated platform privileges. It stores tokens in the system keyring (per SKILL.md), which is a normal behavior for CLIs. Model invocation remains allowed (default), which is expected for an invocable skill.
Assessment
This skill appears coherent, but before installing: 1) Verify you trust the 'porteden' project and the Homebrew tap or GitHub module (confirm the repo and release integrity). 2) Limit the API key's permissions (grant only what the CLI needs; ensure Drive/Sheets scopes are narrow). 3) Prefer browser-based auth (system keyring) over placing PE_API_KEY in shell profiles or .env if you want less secret exposure. 4) If you must store PE_SHEET_ID in shell startup files, be aware those files are readable by processes that can read your environment. 5) After testing, rotate or revoke the token if you no longer use the skill. If you want a deeper check, provide the Homebrew formula URL or the GitHub repo contents so they can be audited for unexpected behavior.

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

latestvk97075d5qmqkm2e4x77kx3mdys8358cf

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Runtime requirements

🤖 Clawdis
Binsporteden
EnvPE_API_KEY, PE_SHEET_ID
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

Comments