| name | 1password |
| description | Set up and use 1Password CLI (op). Use when installing the CLI, enabling desktop app integration, signing in, and reading/injecting secrets for commands. |
1password
Purpose
Set up and use 1Password CLI (op). Use when installing the CLI, enabling desktop app integration, signing in, and reading/injecting secrets for commands.
Use When
- The user request matches
1password, security or the skill description.
- Set up and use 1Password CLI (op). Use when installing the CLI, enabling desktop app integration, signing in, and reading/injecting secrets for commands.
- The task benefits from domain-specific workflow, checks, output structure, or safe fallback behavior.
Workflow
- Confirm authorization, scope, assets, and objective.
- Use read-only or local test methods first.
- Report risks with evidence, impact, likelihood, and remediation.
- Require confirmation before active scans, external testing, or changes.
Codex Runtime Rules
- Use only tools, plugins, MCP servers, files, commands, and credentials that are actually available in the current Codex session.
- If an external write, install, publish, deploy, paid action, credential use, account operation, physical-device action, or production action is needed, ask for explicit confirmation first.
- If the required tool is unavailable, return a portable fallback such as Markdown, CSV, prompt pack, implementation plan, config sketch, or verification checklist.
- Do not claim files, media, issues, API calls, payments, deployments, transactions, messages, or integrations were created unless there is concrete local or tool evidence.
- Treat source repository runtime details as historical source context, not active Codex capabilities.
Avoid
- Do not enable unauthorized access, credential theft, evasion, malware, or real-world harm.
Output
Return the useful artifact first, then evidence and verification status.
For non-trivial work, include:
Result: ...
Evidence: ...
Verification: PASS/FAIL/NOT RUN
Risks / Next Steps: ...
