1password
using 1Password cli to manage secrets via op cli.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 2
- Forks
- 0
01 前言 Front Matter
- name
- 1password
- homepage
- https://developer.1password.com/docs/cli/get-started/
- description
- using 1Password cli to manage secrets via op cli.
02 资源文件 3
- 参考文档agents/openai.yaml153 B
- 参考文档references/cli-examples.md720 B
- 参考文档references/get-started.md994 B
03 SKILL.md 正文
1Password CLI
Follow official CLI get-started steps. Don't guess install commands.
References
references/get-started.md(install + app integration + sign-in flow)references/cli-examples.md(realopexamples)
Workflow
- Check OS + shell
- Verify CLI:
op --version - Confirm desktop app integration enabled (per get-started) and app unlocked
- REQUIRED: create fresh tmux session for all
opcommands (no directopcalls outside tmux) - Sign in/authorize inside tmux:
op signin(expect app prompt) - Verify access inside tmux:
op whoami(must succeed before any secret read) - Multiple accounts → use
--accountorOP_ACCOUNT
REQUIRED tmux session (T-Max)
Shell tool uses fresh TTY per command. Run op inside dedicated tmux session with fresh socket/session name to avoid re-prompts.
SOCKET_DIR="${CLAWDBOT_TMUX_SOCKET_DIR:-${TMPDIR:-/tmp}/clawdbot-tmux-sockets}"
mkdir -p "$SOCKET_DIR"
SOCKET="$SOCKET_DIR/clawdbot-op.sock"
SESSION="op-auth-$(date +%Y%m%d-%H%M%S)"
tmux -S "$SOCKET" new -d -s "$SESSION" -n shell
tmux -S "$SOCKET" send-keys -t "$SESSION":0.0 -- "op signin --account my.1password.com" Enter
tmux -S "$SOCKET" send-keys -t "$SESSION":0.0 -- "op whoami" Enter
tmux -S "$SOCKET" send-keys -t "$SESSION":0.0 -- "op vault list" Enter
tmux -S "$SOCKET" capture-pane -p -J -t "$SESSION":0.0 -S -200
tmux -S "$SOCKET" kill-session -t "$SESSION"
See tmux skill for socket conventions; don't reuse old session names.
Guardrails
- Never paste secrets into logs, chat, or code
- Prefer
op run/op injectover writing secrets to disk - Sign-in without app integration → use
op account add - "account is not signed in" → re-run
op signininside tmux, authorize in app - Don't run
opoutside tmux; stop + ask if tmux unavailable
04 同仓库更多 Skills
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
workflow-from-chats
Extract preferences from agent chats → skills, rules, workflow docs. For learning preferences, mining feedback, personalizing workflows.
winui3-csharp-app
WinUI 3 / Windows App SDK desktop apps in C#/XAML. MVVM, bindings, navigation, Mica/Acrylic, windowing, packaging, performance.
why
Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.
what-did-i-get-done
Summarize authored commits over a user-specified time period into a concise status update.
weekly-review
Produce a short weekly synthesis of authored commits with highlights by bugfix, tech debt, and net-new work.