/assistant
Create, manage, and chat with Pinecone Assistants for document Q&A with citations. Handles all assistant operations - create, upload, sync, chat, context retrieval, and list. Recognizes natural language like "create an assistant from my docs", "ask my assistant about X", or
$ npx -y skills add pinecone-io/pinecone-claude-code-plugin --skill assistant --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/assistant
Context preview
The summary Claude sees to decide when to auto-load this skill.
Create, manage, and chat with Pinecone Assistants for document Q&A with citations. Handles all assistant operations - create, upload, sync, chat, context retrieval, and list. Recognizes natural language like "create an assistant from my docs", "ask my assistant about X", or
SKILL.md
assistant.SKILL.mdname: pinecone:assistant
description: Create, manage, and chat with Pinecone Assistants for document Q&A with citations. Handles all assistant operations - create, upload, sync, chat, context retrieval, and list. Recognizes natural language like "create an assistant from my docs", "ask my assistant about X", or "upload my docs to Pinecone".
allowed-tools: Bash, Read
Pinecone Assistant
Pinecone Assistant is a fully managed RAG service. Upload documents, ask questions, get cited answers. No embedding pipelines or infrastructure required.
> All scripts are in `scripts/` relative to this skill directory. > Run with: `uv run scripts/script_name.py [arguments]`
Operations
| What to do | Script | Key args | |---|---|---| | Create an assistant | `scripts/create.py` | `--name` `--instructions` `--region` | | Upload files | `scripts/upload.py` | `--assistant` `--source` `--patterns` | | Sync files (incremental) | `scripts/sync.py` | `--assistant` `--source` `--delete-missing` `--dry-run` | | Chat / ask a question | `scripts/chat.py` | `--assistant` `--message` | | Get context snippets | `scripts/context.py` | `--assistant` `--query` `--top-k` | | List assistants | `scripts/list.py` | `--files` `--json` |
For full workflow details on any operation, read the relevant file in `references/`.
---
Natural Language Recognition
Proactively handle these patterns without requiring explicit commands:
**Create:** "create an assistant", "make an assistant called X", "set up an assistant for my docs" → See [references/create.md](references/create.md)
**Upload:** "upload my docs", "add files to my assistant", "index my documentation" → See [references/upload.md](references/upload.md)
**Sync:** "sync my docs", "update my assistant", "keep assistant in sync", "refresh from ./docs" → See [references/sync.md](references/sync.md)
**Chat:** "ask my assistant about X", "what does my assistant know about X", "chat with X" → See [references/chat.md](references/chat.md)
**Context:** "search my assistant for X", "find context about X" → See [references/context.md](references/context.md)
**List:** "show my assistants", "what assistants do I have" → Run `uv run scripts/list.py`
---
Conversation Memory
Track the last assistant used within the conversation:
- When a user creates or first uses an assistant, remember its name
- If user says "my assistant", "it", or "the assistant" → use the last one
- Briefly confirm which assistant you're using: "Asking docs-bot..."
- If ambiguous and multiple exist → use AskUserQuestion to clarify
---
Multi-Step Requests
Handle chained requests naturally. Example:
> "Create an assistant called docs-bot, upload my ./docs folder, and ask what the main features are"
1. `uv run scripts/create.py --name docs-bot` 2. `uv run scripts/upload.py --assistant docs-bot --source ./docs` 3. `uv run scripts/chat.py --assistant docs-bot --message "what are the main features?"`
---
Prerequisites
- `PINECONE_API_KEY` must be available — `export PINECONE_API_KEY="your-key"` (or use a `.env` file with `uv run --env-file .env`)
- `uv` must be installed — [install uv](https://docs.astral.sh/uv/getting-started/installation/)
- Get a free API key at: https://app.pinecone.io/?sessionType=signup
Read more
name: pinecone:assistant description: Create, manage, and chat with Pinecone Assistants for document Q&A with citations. Handles all assistant operations - create, upload, sync, chat, context retrieval, and list. Recognizes natural language like "create an assistant from my docs", "ask my assistant about X", or "upload my docs to Pinecone". allowed-tools: Bash, Read
Pinecone Assistant
Pinecone Assistant is a fully managed RAG service. Upload documents, ask questions, get cited answers. No embedding pipelines or infrastructure required.
> All scripts are in `scripts/` relative to this skill directory. > Run with: `uv run scripts/script_name.py [arguments]`
Operations
| What to do | Script | Key args | |---|---|---| | Create an assistant | `scripts/create.py` | `--name` `--instructions` `--region` | | Upload files | `scripts/upload.py` | `--assistant` `--source` `--patterns` | | Sync files (incremental) | `scripts/sync.py` | `--assistant` `--source` `--delete-missing` `--dry-run` | | Chat / ask a question | `scripts/chat.py` | `--assistant` `--message` | | Get context snippets | `scripts/context.py` | `--assistant` `--query` `--top-k` | | List assistants | `scripts/list.py` | `--files` `--json` |
For full workflow details on any operation, read the relevant file in `references/`.
---
Natural Language Recognition
Proactively handle these patterns without requiring explicit commands:
**Create:** "create an assistant", "make an assistant called X", "set up an assistant for my docs" → See [references/create.md](references/create.md)
**Upload:** "upload my docs", "add files to my assistant", "index my documentation" → See [references/upload.md](references/upload.md)
**Sync:** "sync my docs", "update my assistant", "keep assistant in sync", "refresh from ./docs" → See [references/sync.md](references/sync.md)
**Chat:** "ask my assistant about X", "what does my assistant know about X", "chat with X" → See [references/chat.md](references/chat.md)
**Context:** "search my assistant for X", "find context about X" → See [references/context.md](references/context.md)
**List:** "show my assistants", "what assistants do I have" → Run `uv run scripts/list.py`
---
Conversation Memory
Track the last assistant used within the conversation:
- When a user creates or first uses an assistant, remember its name
- If user says "my assistant", "it", or "the assistant" → use the last one
- Briefly confirm which assistant you're using: "Asking docs-bot..."
- If ambiguous and multiple exist → use AskUserQuestion to clarify
---
Multi-Step Requests
Handle chained requests naturally. Example:
> "Create an assistant called docs-bot, upload my ./docs folder, and ask what the main features are"
1. `uv run scripts/create.py --name docs-bot` 2. `uv run scripts/upload.py --assistant docs-bot --source ./docs` 3. `uv run scripts/chat.py --assistant docs-bot --message "what are the main features?"`
---
Prerequisites
- `PINECONE_API_KEY` must be available — `export PINECONE_API_KEY="your-key"` (or use a `.env` file with `uv run --env-file .env`)
- `uv` must be installed — [install uv](https://docs.astral.sh/uv/getting-started/installation/)
- Get a free API key at: https://app.pinecone.io/?sessionType=signup
A lightweight plugin that integrates Pinecone vector database capabilities directly into Claude Code, enabling semantic search, index management, and RAG (Retrieval Augmented Generation) workflows.
Repo: pinecone-io/pinecone-claude-code-plugin
Other skills on pinecone.
- /cli
Guide for using the Pinecone CLI (pc) to manage Pinecone resources from the terminal. The CLI supports ALL index types (standard, integrated, sparse) and all vector operations — unlike the MCP which only supports integrated indexes. Use for batch operations, vector management,
Open skill - /docs
Curated documentation reference for developers building with Pinecone. Contains links to official docs organized by topic and data format references. Use when writing Pinecone code, looking up API parameters, or needing the correct format for vectors or records.
Open skill - /full-text-search
Create, ingest into, and query a Pinecone full-text-search (FTS) index using the preview API (2026-01.alpha, public preview). Use when the user or agent asks to build a text search index on Pinecone, add dense or sparse vector fields, ingest documents, construct score_by clauses
Open skill - /help
Overview of all available Pinecone skills and what a user needs to get started. Invoke when a user asks what skills are available, how to get started with Pinecone, or what they need to set up before using any Pinecone skill.
Open skill - /mcp
Reference for the Pinecone MCP server tools. Documents all available tools - list-indexes, describe-index, describe-index-stats, create-index-for-model, upsert-records, search-records, cascading-search, and rerank-documents. Use when an agent needs to understand what Pinecone
Open skill - /n8n
Build n8n workflows using the Pinecone Assistant node or Pinecone Vector Store node. Use when building RAG pipelines, chat-with-docs workflows, configuring Pinecone nodes in n8n, troubleshooting Pinecone n8n nodes, or asking about best practices for Pinecone in n8n.
Open skill

