openpond-cli
Use the OpenPond CLI to create repos, watch deployments, and run tools without the web UI.
Setup & Installation
Install command
clawhub install glucrypto/openpond-cliIf the CLI is not installed:
Install command
npx clawhub@latest install glucrypto/openpond-cliOr install with OpenClaw CLI:
Install command
openclaw skills install glucrypto/openpond-clior paste the repo link into your assistant's chat
Install command
https://github.com/openclaw/skills/tree/main/skills/glucrypto/openpond-cliWhat This Skill Does
Command-line interface for managing OpenPond apps, repos, and tools without the web UI. Supports non-interactive authentication, deployment monitoring, and tool execution via shell commands.
Enables fully scriptable, headless OpenPond workflows that can run in CI or automated agents without browser access.
When to Use It
- Pushing code to an OpenPond repo from a CI pipeline
- Watching a deployment status without opening a browser
- Running a deployed tool with a JSON payload from the terminal
- Creating a new OpenPond app with an agent prompt from a script
- Listing all tools available on a given handle/repo
View original SKILL.md file
# OpenPond CLI
Use this skill when an agent needs to create or manage OpenPond apps via the CLI, without MCP.
## Quick setup
- Install: `npm i -g openpond-code` (or `npx --package openpond-code openpond <cmd>`)
- Auth: run `openpond login` or set `OPENPOND_API_KEY`
- Non-interactive login: `openpond login --api-key opk_...`
## Common workflows
- Create internal repo and attach remote:
- `openpond repo create --name my-repo --path .`
- Non-interactive push (tokenized remote):
- `openpond repo create --name my-repo --path . --token`
- `git add . && git commit -m "init"`
- `openpond repo push --path . --branch main`
- `openpond repo push` reads `.git/config`, temporarily tokenizes `origin`, and restores it after push.
- Watch deployments:
- `openpond deploy watch handle/repo --branch main`
- List and run tools:
- `openpond tool list handle/repo`
- `openpond tool run handle/repo myTool --body '{"foo":"bar"}'`
- Account-level APIs:
- `openpond apps list [--handle <handle>] [--refresh]`
- `openpond apps tools`
- `openpond apps performance --app-id app_123`
- `openpond apps agent create --prompt "Build a daily digest agent"`
## OpenTool passthrough
Use the CLI to run OpenTool commands via `npx`:
- `openpond opentool init --dir .`
- `openpond opentool validate --input tools`
- `openpond opentool build --input tools --output dist`
## Config and URLs
- Optional env vars: `OPENPOND_BASE_URL`, `OPENPOND_API_URL`, `OPENPOND_TOOL_URL`, `OPENPOND_API_KEY`
- Cache file: `~/.openpond/cache.json` (auto-refreshes on next use)
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: Pushing code to an OpenPond repo from a CI pipeline
- 1Pushing code to an OpenPond repo from a CI pipeline
- 2Watching a deployment status without opening a browser
- 3Running a deployed tool with a JSON payload from the terminal
- 4Creating a new OpenPond app with an agent prompt from a script
- 5Listing all tools available on a given handle/repo
Use the OpenPond CLI to create repos, watch deployments, and run tools without the web UI.
Security Audits
These signals reflect official OpenClaw status values. A Suspicious status means the skill should be used with extra caution.