Run any Skill in Manus with one click

1password

Stars0

Forks0

UpdatedJuly 18, 2026 at 13:49

Set up and use 1Password CLI (op). Use when installing the CLI, enabling desktop app integration, signing in, and reading/injecting secrets for commands.

Installation

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.

Run Skill in Manus

Source

PAISHU-AI

PAISHU-AI/PAI-zong-NB-v5.8

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Information Security AnalystsComputer and Mathematical Occupations·SOC 15-1212

SKILL.md

readonly

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: ...

More from this repository

same repository

router

PAISHU-AI/PAI-zong-NB-v5.8

Route user requests to the right Codex role, output mode, and minimal skill set. Use for every task before deciding whether the answer is simple consultation, architecture, project assistance, coding, debugging, review, documentation, or rule maintenance.

2026-07-180

project-context

PAISHU-AI/PAI-zong-NB-v5.8

Inspect and summarize project context before coding. Use when Codex needs to modify a repository, understand structure, follow existing conventions, locate scripts, read AGENTS.md, README, package manifests, or project documentation.

2026-07-180

ui-design

PAISHU-AI/PAI-zong-NB-v5.8

Design practical user interfaces, flows, information architecture, layout systems, component states, and design tokens. Use for page design, UX redesign, dashboards, tools, mobile/web UI, interaction design, and before frontend implementation when visual or workflow decisions matter.

2026-07-180

frontend

PAISHU-AI/PAI-zong-NB-v5.8

Build and modify frontend pages, components, state logic, styling, forms, client-side interactions, and UI behavior in React, Vue, Svelte, vanilla HTML/CSS/JS, or similar frameworks. Use for frontend implementation and frontend bug fixes.

2026-07-180

backend

PAISHU-AI/PAI-zong-NB-v5.8

Implement backend services, business logic, API handlers, jobs, integrations, file processing, authentication flows, and server-side fixes. Use for backend coding and debugging in Node, Python, Go, Java, Rust, PHP, or similar stacks.

2026-07-180

api-design

PAISHU-AI/PAI-zong-NB-v5.8

Design REST, GraphQL, RPC, webhook, and internal service APIs. Use for routes, status codes, request/response schemas, error models, pagination, filtering, versioning, idempotency, and OpenAPI or contract documentation.

2026-07-180

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: ...