Pinecone Full-Text Search Agent Skill

Name: Pinecone Full-Text Search
Author: pinecone-io

Create, ingest into, and query a Pinecone full-text-search (FTS) document index using the graduated document-schema API (Python SDK…

Install this skill Read the source first Free Written by pinecone-io

Context cost: 26.4k tokensestimated from the bundle, loaded when it triggers
Bundle: 6 files · 115.7 kB1 script among them — read before you run
Licence: MITthe author’s own terms
Last change: —no release on file
Servers it uses: Noneruns standalone

What it does

Create, ingest into, and query a Pinecone full-text-search (FTS) document index using the graduated document-schema API (Python SDK 10.0.0, API version 2026-07). 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 (text / query_string / dense_vector / sparse_vector), or compose with text-match filters ($match_phrase / $match_all / $match_any).

What this skill changes about the agent has not been set out here as a list. Its SKILL.md, shown below, says it in the author’s own words.

databasepython

Filed under

Databases

The skill itself

A skill is instructions the model reads, so you can see what you are getting: below is the start of its SKILL.md. The front matter loads with every session, the body loads when the skill triggers, and the whole file comes with the install.

SKILL.md41.4 kB · preview

--- name: pinecone:full-text-search allowed-tools: Bash, Read ---

7# Pinecone Full-Text Search

9> **Requires pinecone Python SDK ≥ 10.0.0** (pip install pinecone>=10.0.0). The document-schema API graduated out of pinecone.preview in 10.0.0 — it is now a first-class, SemVer-covered part of the SDK, reachable directly off pc (pc.indexes, pc.index(...)). If you land on this skill from an older habit of importing pinecone.preview, stop: that package is deleted outright in 10.0.0 (ModuleNotFoundError, no shim). The packaged helper script pins pinecone==10.0.0 via PEP 723 inline metadata; if you're writing your own code against this skill, pin at least that version. The wire API version is 2026-07.

11> **Authoritative reference (last resort).** If you hit a question this skill and its references/*.md files don't answer, the official Pinecone FTS docs are at <https://docs.pinecone.io/guides/search/full-text-search>. Prefer this skill's content for anything covered here — the docs may describe surfaces (e.g. classic vector API, or the older pinecone.preview shape) that don't apply to the graduated document-schema path. Consult the link only when you're genuinely stuck.

13> **Tell the user up front:** "This skill ships a helper at scripts/ingest.py that handles bulk ingestion safely (batched upsert, error inspection, readiness polling). When we get to the ingest step, I'll use it." Surface this at the start of the conversation so the user knows the helper exists. Query construction is hand-written documents.search(...) per the **Querying** section below — there is no query helper.

15A workflow skill for building a Pinecone full-text-search index with the graduated document-schema API (pc.indexes, pc.index(name), API version 2026-07). Covers schema design (text, dense vector, sparse vector, filterable metadata), ingestion (including async indexing and polling), and query construction (text / query_string / dense_vector / sparse_vector scoring; $match_phrase / $match_all / $match_any text-match filters; $eq / $in / $gte / $exists / $and / $or / $not metadata filters).

17## Scope — this skill is for the document-schema FTS API only

19This skill covers pc.indexes.create(..., schema=...), pc.index(name), idx.documents.upsert(...) / idx.documents.batch_upsert(...) / idx.documents.search(...). If you find yourself reaching for any of the following, **stop** — those are different Pinecone APIs and this skill's guidance and helpers won't apply:

21- **Classic vector / records API**: pc.Index(name), index.upsert(vectors=[...]), index.query(vector=..., sparse_vector=...), pc.create_index(dimension=..., metric=..., spec=ServerlessSpec(...)). This is the *deprecated sugar* path in 10.0.0 — it still runs, but it creates a schemaless index served by the vector data plane, addressing the vector by the reserved _values field. It cannot hold full_text_search fields.

22- **Integrated-embedding / records indexes**: pc.create_index_for_model(...) / pc.indexes.create_for_model(...) with embed={...}. Pinecone vectorizes text server-side, and the resulting semantic_text field is served by the **records** API (upsert_records / search_records), not the documents API. Different upsert/search shapes. A semantic_text field cannot be combined with full_text_search fields in the same index.

24If the user already has a non-document-schema index, they can stand up a separate document-schema index alongside it — the two are independent — but you can't add FTS fields to a classic or integrated-embedding index after the fact, and a document-schema index only ever serves reads and writes through index.documents.* — never index.upsert / index.query / index.upsert_records (those calls are refused with "This index has a document schema, so writes must go through the documents API").

This is a preview of SKILL.md. Download or install the skill to get the whole thing.

In the file

SKILL.md5,707 words

Files6

LicenceMIT

Why you can read it

Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.

What it costs in context

Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.

≈200

always loaded

The name and description, so the model knows the skill exists and when to reach for it.

26,225

on trigger

The instruction body and 5 supporting files, read only when the skill fires.

13.2%

of a 200k window

Ten skills this size would not fit in the window together.

050k100k150k200k context window

26.4k tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Heavy. Teams tend to install this one per project rather than globally, and load it only when the job comes up.

Servers bill, skills cost

A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.

Before and after

The same question, put to the same model twice: once as it comes, and once with these instructions loaded.

No worked example has been published for this skill yet.

The procedure it runs

The procedure has not been set out here step by step. It is in the body of its SKILL.md: the start of it is shown above, and the whole file comes with the install.

Prose, not code

These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.

Servers it uses

None. This skill calls no MCP servers at all.

Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.

Its SKILL.md asks for Bash, which can write files and reach the network alike, so what it touches is whatever the instructions themselves ask for — read them before you install it.

What it asks for

Writes filesnot declared

Network accessnot declared

The allowed-tools line of this skill’s own SKILL.md asks for Bash, which could do either, so neither is ruled out. A skill grants no permissions of its own — it can only ask for tools your client already has.

What it will not do

Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.

What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.

If this is not it

2114 other skills in Databases

What is in the bundle

6 files, 115.7 kB on disk. Mostly text — the instructions the model reads — with 1 script in it that your client would run only if the instructions tell it to.

SKILL.md41.4 kB
references/ingestion.md15.9 kB
references/onboarding-walkthrough.md12.8 kB
references/querying.md19.4 kB
references/schema-design.md16.2 kB
scripts/ingest.py10.0 kB

What is not in it

A skill installs nothing and depends on nothing: it is a folder your client reads. This one carries 1 script beside the text, so the bundle is 6 files you can review in full before installing. The MIT licence covers the templates and examples as well as the instructions.

Install

Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.

# Pinecone Full-Text Search · 26.4k tokens when loaded · macOS, Linux
mkdir -p .claude/skills && t=$(mktemp -d) &&
  curl -fsSL -o "$t/bundle.tar.gz" https://mcprush.com/api/skills/pinecone-full-text-search/bundle.tar.gz &&
  tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/pinecone-full-text-search" ] &&
  { [ ! -e .claude/skills/pinecone-full-text-search ] || { mv .claude/skills/pinecone-full-text-search "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } &&
  mv "$t/pinecone-full-text-search" .claude/skills/ && echo "Installed .claude/skills/pinecone-full-text-search"

On Windows, or any OS with Node 20+

npx mcprush@latest skill add pinecone-io/pinecone-full-text-search

Windows PowerShell says 'running scripts is disabled on this system'? Run Set-ExecutionPolicy -Scope CurrentUser RemoteSigned once, or type npx.cmd instead of npx (codex.cmd, gemini.cmd, grok.cmd likewise). PowerShell 7 needs neither. Writes to .claude/skills/pinecone-full-text-search/ in the current project. For every project instead, run mkdir -p ~/.claude/skills && t=$(mktemp -d) && curl -fsSL -o "$t/bundle.tar.gz" https://mcprush.com/api/skills/pinecone-full-text-search/bundle.tar.gz && tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/pinecone-full-text-search" ] && { [ ! -e ~/.claude/skills/pinecone-full-text-search ] || { mv ~/.claude/skills/pinecone-full-text-search "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } && mv "$t/pinecone-full-text-search" ~/.claude/skills/ && echo "Installed ~/.claude/skills/pinecone-full-text-search" (macOS, Linux) — or add --global to the npx line. The curl line replaces .claude/skills/pinecone-full-text-search/ only after the download succeeds, so files left there by another skill of the same name, or by an older release, do not mix in. A copy already there is moved aside, not deleted, and the line prints where. It appears as pinecone:full-text-search in Gemini CLI, Codex, Copilot and Grok (its own name); Claude Code lists it by the folder name, pinecone-full-text-search.

Which clients pick it up on their own

A skill is a folder of text. Most of these read a skills folder and pick it up without being told; the rest take the same folder another way — an upload in the app, a parameter on an API call — and then choose it by its description just the same.

Claude Code.claude/skills/

Claude DesktopCustomize › Skills

ChatGPTSkills › Create › Upload

Cursor.cursor/skills/

VS Code.github/skills/

Codex CLI.agents/skills/

Gemini CLI.gemini/skills/

Grok Build.grok/skills/

Microsoft CopilotSkills › Upload a skill

PerplexityComputer › Skills › Upload a skill

DeepSeek Harness.dsh/skills/

Zed.agents/skills/

Devin Desktop.devin/skills/

Windsurf (legacy).windsurf/skills/

OpenAI Agents SDKInstructions or sandbox Skills

HTTP / APIa request parameter

This release

Versionnot versioned

Publishedno release date on file

PriceFree

Referencepinecone-io/pinecone-full-text-search

Versions

Its author publishes no version number, so there is nothing here to pin to: what you install is the folder as it stands today. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.

Pinning

Nothing to pin to: this skill carries no version number of its own. What you install is what the folder holds on the day you install it.

Reviews

—no reviews yet

Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.

Sign in to review it

A review is tied to an account so it can be answered, edited and taken down by the person who wrote it.

Who can post

Anybody with an account, one review each. It carries the version that was current when you wrote it, and the publisher may reply once.

Who wrote it

pinecone-io

Publishes on mcprush.

1 server listed8 skills listednot claimed

Profile

Publisher

Servers1

Claim this skill