How do I install the Reading Op Secrets skill?

Run npx skillmds@latest add tomevault-io/reading-op-secrets in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Reading Op Secrets safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Reading Op Secrets?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Reading Op Secrets free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Reading Op Secrets?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Reading Op Secrets by tomevault-io — Agent Skill

Name: Reading Op Secrets
Author: tomevault-io

Reading Op Secrets

Reads secrets from 1Password using the op CLI. Use when the user needs to retrieve passwords, API keys, credentials, documents, or one-time passwords stored in 1Password. Supports reading items by name or ID, extracting specific fields, listing vault contents, and reading secret references. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

Overview

This skill enables agents to read secrets from 1Password using the op CLI. It supports comprehensive read operations including full items, specific fields, documents, attachments, and one-time passwords.

The skill assumes the op CLI is installed and the user is already authenticated.

Overview
Table of Contents
Supported Operations
Workflow
- Phase 1: Context Assessment
- Phase 2: Secret Retrieval
Reference Documentation

Supported Operations

Operation	Use Case
Get Item	Retrieve complete item with all fields
Get Field	Extract specific field value(s)
List Items	Browse items in vault(s)
Get Document	Retrieve document content
Get OTP	Get current one-time password
Read Reference	Read using `op://` secret reference

Workflow

Phase 1: Context Assessment

Step 1: Understand the Request

Determine what the user needs:

Identify the secret type:
- Specific item (name or ID known)
- Specific field from an item
- List of items (browsing/searching)
- Document content
- One-time password
- Secret reference (op:// URI)
Identify scope:
- Specific vault or search all vaults
- Any filtering criteria (tags, categories)
Clarify if needed:
- If item name is ambiguous, ask for vault or use item ID
- If multiple fields could match, ask which specific field

Phase 2: Secret Retrieval

Step 2: Execute the Appropriate Command

Based on the context assessment, execute the appropriate op command.

See op CLI Read Command Reference for complete command syntax.

Get Complete Item:

op item get "<item-name>" --format json

Get Specific Field:

op item get "<item-name>" --fields "<field-name>" --format json

List Items:

op item list [--vault "<vault>"] [--categories <category>] --format json

Get Document:

op document get "<document-name>"

Get OTP:

op item get "<item-name>" --otp

Read Secret Reference:

op read "op://<vault>/<item>/<field>"

Step 3: Parse and Present Results

Parse JSON output (when using --format json)
Extract relevant information based on user's request
Present clearly:
- For single values: provide the value directly
- For items: summarize fields, highlight requested data
- For lists: present in table format with key metadata

See Output Schemas Reference for JSON structure details.

Step 4: Handle Errors

Common errors and resolutions:

Error	Resolution
`item not found`	Verify item name, try listing items in vault
`vault not found`	List available vaults with `op vault list`
`more than one item matches`	Use item ID instead of name, or specify vault
`field not found`	List item fields with full `op item get`

Reference Documentation

op CLI Read Command Reference - Complete command syntax for all read operations
Output Schemas Reference - JSON output structure examples

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: reading-op-secretsdescription: Reads secrets from 1Password using the op CLI. Use when the user needs to retrieve passwords, API keys, credentials, documents, or one-time passwords stored in 1Password. Supports reading items by name or ID, extracting specific fields, listing vault contents, and reading secret references. Use when this capability is needed.---# OverviewThis skill enables agents to read secrets from 1Password using the `op` CLI. It supports comprehensive read operations including full items, specific fields, documents, attachments, and one-time passwords.The skill assumes the `op` CLI is installed and the user is already authenticated.# Table of Contents- [Overview](#overview)- [Table of Contents](#table-of-contents)- [Supported Operations](#supported-operations)- [Workflow](#workflow) - [Phase 1: Context Assessment](#phase-1-context-assessment) - [Phase 2: Secret Retrieval](#phase-2-secret-retrieval)- [Reference Documentation](#reference-documentation)# Supported Operations| Operation | Use Case ||-----------|----------|| Get Item | Retrieve complete item with all fields || Get Field | Extract specific field value(s) || List Items | Browse items in vault(s) || Get Document | Retrieve document content || Get OTP | Get current one-time password || Read Reference | Read using `op://` secret reference |# Workflow## Phase 1: Context Assessment### Step 1: Understand the RequestDetermine what the user needs:1. **Identify the secret type**: - Specific item (name or ID known) - Specific field from an item - List of items (browsing/searching) - Document content - One-time password - Secret reference (`op://` URI)2. **Identify scope**: - Specific vault or search all vaults - Any filtering criteria (tags, categories)3. **Clarify if needed**: - If item name is ambiguous, ask for vault or use item ID - If multiple fields could match, ask which specific field## Phase 2: Secret Retrieval### Step 2: Execute the Appropriate CommandBased on the context assessment, execute the appropriate `op` command.See [op CLI Read Command Reference](references/op-read-commands.md) for complete command syntax.**Get Complete Item**:```bashop item get "<item-name>" --format json```**Get Specific Field**:```bashop item get "<item-name>" --fields "<field-name>" --format json```**List Items**:```bashop item list [--vault "<vault>"] [--categories <category>] --format json```**Get Document**:```bashop document get "<document-name>"```**Get OTP**:```bashop item get "<item-name>" --otp```**Read Secret Reference**:```bashop read "op://<vault>/<item>/<field>"```### Step 3: Parse and Present Results1. **Parse JSON output** (when using `--format json`)2. **Extract relevant information** based on user's request3. **Present clearly**: - For single values: provide the value directly - For items: summarize fields, highlight requested data - For lists: present in table format with key metadataSee [Output Schemas Reference](references/output-schemas.md) for JSON structure details.### Step 4: Handle ErrorsCommon errors and resolutions:| Error | Resolution ||-------|------------|| `item not found` | Verify item name, try listing items in vault || `vault not found` | List available vaults with `op vault list` || `more than one item matches` | Use item ID instead of name, or specify vault || `field not found` | List item fields with full `op item get` |# Reference Documentation- [op CLI Read Command Reference](references/op-read-commands.md) - Complete command syntax for all read operations- [Output Schemas Reference](references/output-schemas.md) - JSON output structure examples---> Converted and distributed by [TomeVault](https://tomevault.io/claim/leefowlercu) — claim your Tome and manage your conversions.

Frequently asked questions