Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub ยท Developer Tools
Secure Autofill
1Password-backed credential filling via vault_suggest/vault_fill (plugin tools).
skill openclawclawhub Free
1Password-backed credential filling via vault_suggest/vault_fill (plugin tools).
โฌ 0 downloads โ
0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- SKILL.md, config.env, scripts/onboard.sh
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
New install
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
Upgrade existing
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 0.1.0
Provenance
- Publisher
- moodykong
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
secure-autofill ๐
This skill documents how to use the secure-autofill plugin tools: vault_suggest โ find likely 1Password items vault_fill โ fill browser DOM fields with secrets (agent never sees credentials)
Architecture
Agent orchestrates; plugin handles secrets. The agent provides element refs from browser.snapshot; the plugin types secrets into the page.
Prerequisites
Tools available (if tool allowlists are in use): vault_suggest, vault_fill A working non-headless Chrome on WSL (many sites block headless) Gateway environment has required env vars Concrete checks: command -v google-chrome || command -v google-chrome-stable
Configuration (portable)
Machine-specific environment should NOT be hardcoded in this document. Example (do not edit): ~/.openclaw/skills/secure-autofill/config.env.example Real (machine-specific): ~/.openclaw/skills/secure-autofill/config.env Gateway env file (recommended destination): ~/.config/openclaw/env Typical keys: DISPLAY WAYLAND_DISPLAY OP_SERVICE_ACCOUNT_TOKEN (do not commit; do not paste into chat)
Preferred (chat-first)
Because the primary interface is chat (Telegram), the preferred onboarding flow is: Ask Boss which values to set (DISPLAY, WAYLAND_DISPLAY, whether to set OP_SERVICE_ACCOUNT_TOKEN). Write/update the real skill-local env file: config.env. Optionally update the gateway env file (~/.config/openclaw/env) with per-key confirmation. If applicable, detect whether openclaw-gateway is managed by systemctl --user and offer to restart.
Optional (terminal)
If you are running in a real terminal, you can use the interactive onboarding script: ~/.openclaw/skills/secure-autofill/scripts/onboard.sh
1) Install Google Chrome (.deb)
Ubuntu 22.04 moved Chromium to snap which doesn't work well in WSL. Install Chrome directly: # Add Google apt source wget -qO- https://dl.google.com/linux/linux_signing_key.pub \ | sudo gpg --dearmor -o /usr/share/keyrings/google-linux-signing-keyring.gpg echo "deb [arch=amd64 signed-by=/usr/share/keyrings/google-linux-signing-keyring.gpg] http://dl.google.com/linux/chrome/deb/ stable main" \ | sudo tee /etc/apt/sources.list.d/google-chrome.list # Install sudo apt update && sudo apt install -y google-chrome-stable
2) Configure gateway environment (non-headless + 1Password token)
Create/update ~/.config/openclaw/env. Run onboarding to generate the real env file (skill-local): ~/.openclaw/skills/secure-autofill/scripts/onboard.sh Copy the needed variables from the skill-local config.env into the gateway env file (~/.config/openclaw/env). Ensure the gateway service loads the env file: mkdir -p ~/.config/systemd/user/openclaw-gateway.service.d cat > ~/.config/systemd/user/openclaw-gateway.service.d/override.conf << 'EOF' [Service] EnvironmentFile=%h/.config/openclaw/env EOF systemctl --user daemon-reload systemctl --user restart openclaw-gateway
3) Tool allowlist (if configured)
In ~/.openclaw/openclaw.json, add: "tools": { "alsoAllow": ["vault_fill", "vault_suggest"] }
Tools
vault_suggest โ list 1Password items (to find available credentials) vault_fill โ fill DOM fields with secrets (agent provides refs, plugin types secrets)
vault_fill API
vault_fill({ item_title: "X", // 1Password item title fields: { username: { ref: "e3" }, // field type โ DOM ref password: { ref: "e5" }, otp: { ref: "e7" } // optional }, retry_mode: "simple", // "simple" | "next_candidate" | "reset" targetId: "..." // from browser snapshot }) // Returns: { ok: true, filled: ["username", "password"], item_title: "X", has_more_candidates: false }
Field types
username โ 1Password "username" field password โ 1Password "password" field email โ 1Password "email" field (falls back to username) otp โ 1Password TOTP (fresh code)
Retry modes
simple โ same credentials, same refs (use after dismissing a blocker) next_candidate โ try next matching 1Password item (wrong credentials) reset โ clear retry state and start fresh
Timing note
Always wait ~1 second after vault_fill before clicking submit. The plugin uses async CLI calls which take a moment to complete typing. vault_fill(...) // returns immediately wait 1000ms // let typing complete click submit
Login workflow (agent-driven)
1. Navigate to login page 2. Loop until logged in or max retries: a. snapshot โ identify page state b. If obstacle (cookie banner, popup, passkey error): - Dismiss it - Continue loop c. If credential field found: - Build field mapping from snapshot refs - Call vault_fill with mapping - Click submit button - Continue loop d. If logged in: - Done! e. If error: - Decide: retry_mode="simple" or "next_candidate" - Continue loop
X.com example
Agent: navigate to x.com/i/flow/login Agent: snapshot โ textbox "Phone, email, or username" [ref=e3] โ button "Next" [ref=e4] Agent: vault_fill({ item_title: "X", fields: { username: { ref: "e3" } }, targetId }) Agent: click e4 (Next button) Agent: wait, snapshot โ button "Next" [ref=e1] (passkey error dialog) Agent: click e1 (dismiss) Agent: wait, snapshot โ textbox "Password" [ref=e3] โ button "Log in" [ref=e6] Agent: vault_fill({ item_title: "X", fields: { password: { ref: "e3" } }, targetId }) Agent: click e6 (Log in) Agent: wait, snapshot โ textbox "Enter code" [ref=e4] โ button "Next" [ref=e7] Agent: vault_fill({ item_title: "X", fields: { otp: { ref: "e4" } }, targetId }) Agent: click e7 (Next) Agent: wait, snapshot โ home feed visible โ Done!
MFA handling
TOTP: use vault_fill(otp) SMS/Email: ask user for the code; type it; click Next Push: tell user to approve; wait; continue
Executables / bin placement
This skill is documentation for plugin tools; it does not ship a standalone executable. Helper scripts (like onboarding) live inside the skill folder under scripts/.
Category context
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
1 Docs1 Scripts1 Files
- SKILL.md
- scripts/onboard.sh
- config.env