Menu
1Password UI tab for OpenClaw dashboard. Manage secrets, credential mappings, and auth state from the Control UI.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
| name | 1password-ui |
| description | 1Password UI tab for OpenClaw dashboard. Manage secrets, credential mappings, and auth state from the Control UI. |
| version | 1.1.0 |
| author | OpenClaw Community |
| metadata | {"clawdbot":{"emoji":"🔐","requires":{"clawdbot":">=2026.1.0"},"category":"tools"}} |
Adds a 1Password tab to the OpenClaw Control dashboard under the Tools group. Browse vaults, manage credential mappings for skills, and handle authentication — all from the web UI.
| Feature | Description |
|---|---|
| Dashboard Tab | "1Password" under Tools in sidebar |
| Connection Status | See signed-in account, CLI/Connect mode |
| Sign In Flow | Authenticate directly from the UI |
| Docker Support | Works with 1Password Connect for containers |
| Credential Mappings | Map 1Password items to skill configs |
To install this skill, give your agent this prompt:
Install the 1password-ui skill from ClawHub.
The skill is at: ~/clawd/skills/1password-ui/
Follow INSTALL_INSTRUCTIONS.md step by step.
Summary of changes needed:
1. Copy 1password-backend.ts to src/gateway/server-methods/1password.ts
2. Register handlers in server-methods.ts
3. Add "1password" tab to navigation.ts (TAB_GROUPS, Tab type, TAB_PATHS, icon, title, subtitle)
4. Add state variables to app.ts
5. Copy 1password-views.ts to ui/src/ui/views/1password.ts
6. Add view rendering to app-render.ts
7. Add tab loading to app-settings.ts
8. Build and restart: pnpm build && pnpm ui:build && clawdbot gateway restart
1Password CLI (op):
# macOS/Linux
brew install 1password-cli
# Or from https://1password.com/downloads/command-line/
CLI Integration enabled in 1Password app:
See Docker Setup below.
op signin in terminal)Once signed in, you can map 1Password items to skills:
~/clawd/config/1password-mappings.json{ "skillId": { "item": "Item Name", "vault": "Private", "fields": {...} } }# Store Pipedream credentials in 1Password
op item create --category="API Credential" --title="Pipedream Connect" \
--vault="Private" \
"client_id[text]=your_client_id" \
"client_secret[password]=your_client_secret" \
"project_id[text]=proj_xxxxx"
# Use in token refresh
PIPEDREAM_1PASSWORD_ITEM="Pipedream Connect" python3 ~/clawd/scripts/pipedream-token-refresh.py
| Method | Description |
|---|---|
1password.status | Get CLI/Connect status, signed-in account |
1password.signin | Trigger sign-in flow |
1password.signout | Sign out of current session |
1password.vaults | List available vaults |
1password.items | List items in a vault |
1password.getItem | Get item field structure (not values) |
1password.readSecret | Read a secret (backend only) |
1password.mappings.list | Get skill → 1Password mappings |
1password.mappings.set | Create/update a mapping |
1password.mappings.delete | Remove a mapping |
1password.mappings.test | Test if a mapping works |
For Docker-based OpenClaw installations, use 1Password Connect instead of the CLI.
# docker-compose.yml
services:
op-connect-api:
image: 1password/connect-api:latest
ports:
- "8080:8080"
volumes:
- ./1password-credentials.json:/home/opuser/.op/1password-credentials.json:ro
- op-data:/home/opuser/.op/data
op-connect-sync:
image: 1password/connect-sync:latest
volumes:
- ./1password-credentials.json:/home/opuser/.op/1password-credentials.json:ro
- op-data:/home/opuser/.op/data
volumes:
op-data:
1password-credentials.jsonservices:
clawdbot:
environment:
- OP_CONNECT_HOST=http://op-connect-api:8080
- OP_CONNECT_TOKEN=your-access-token
The UI automatically detects Connect mode.
1password-ui/
├── SKILL.md # This file
├── INSTALL_INSTRUCTIONS.md # Step-by-step installation
├── CHANGELOG.md # Version history
├── package.json # Skill metadata
├── reference/
│ ├── 1password-backend.ts # Gateway RPC handlers
│ ├── 1password-views.ts # UI view (Lit template)
│ ├── 1password-settings.ts # Tab loading logic
│ └── 1password-plugin.ts # Plugin registration (optional)
└── scripts/
└── op-helper.py # CLI/Connect bridge for skills
| Aspect | Implementation |
|---|---|
| Secrets not in UI | getItem and items return field names only, never values |
| No network installers | No curl | sh or remote scripts — all code is local |
| Manual installation | Requires explicit code edits, no automated patching |
| Mapping file perms | 1password-mappings.json should be 0600 (contains references, not secrets) |
| CLI auth | Uses 1Password app integration for biometric auth when available |
| Risk | Mitigation |
|---|---|
readSecret RPC available | The 1password.readSecret method IS exposed via gateway RPC. This is intentional — skills need to read secrets. Security relies on: (1) 1Password requiring user auth, (2) gateway access control (loopback-only by default). |
| Gateway exposure | All 1password.* methods are RPC calls. If you expose your gateway to the network, protect it with authentication. |
| Connect token | In Docker mode, OP_CONNECT_TOKEN grants vault access. Keep it secure like any API key. |
# Recommended permissions for mapping file
chmod 600 ~/clawd/config/1password-mappings.json
brew install 1password-cli
# or download from 1password.com/downloads/command-line/
op signin
op whoami # verify
docker ps | grep op-connect # check containers running
OP_CONNECT_TOKEN is set correctlyBloom Mission Discovery — find missions matched to your taste, submit content, and track rewards. Powered by Bloom Protocol.
DESCRIPTION of what this skill does. Include specific trigger keywords and scenarios. Use when: scenario1, scenario2, scenario3.
First-time setup for the Durable Agents stack (Mastra + Trigger.dev). Run once before using the main skill.
Read/search Gmail via gog CLI. Inbox check, email search, content retrieval.
One-sentence description. Use when [trigger scenarios].
Use cheap, TEE-verified AI models from the 0G Compute Network as OpenClaw providers. Discover available models and compare pricing vs OpenRouter, verify provider integrity via hardware attestation (Intel TDX), manage your 0G wallet and sub-accounts, and configure models in OpenClaw with one workflow. Supports DeepSeek, GLM-5, Qwen, and other models available on the 0G marketplace.