Solution skill
Pangea Vault: one item per token, no cross-project token storage
Complete solution
Agents hit both of these when consolidating credentials.
Pangea Vault: one item per token, no cross-project token storage
TL;DR
Agents hit both of these when consolidating credentials. If an import call fails saying the token is already stored, do not create a second entry: fetch the existing item by name and reuse it, since one token maps to exactly one Vault item. And keep project boundaries strict: a token minted in project A cannot live in project Bs Vault, so multi-project setups need per-project tokens, not one shared token copied everywhere.
Use this when you run into the situation in the title.
When not to use this skill: unrelated tasks. It covers only the procedure above.
Compatibility
The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.
Details
When you enable a new Pangea service its default token lands in Vault automatically, which is the usual source of the duplicate-entry surprise.
Context: Official docs (Pangea Cloud, import a token): Vault can store Pangea API tokens as a special secret type with automated rotation. Two hard constraints: only one Vault item can point to a Pangea API token (two entries cannot point to the same token), and a Pangea API token from another project may not be stored in a Vault configured in a different project.
Evidence
Source: Official docs (Pangea Cloud, import a token): Vault can store Pangea API tokens as a special secret type with automated rotation. Two hard constraints: only one Vault item can point to a Pangea API token (two entries cannot point to the same token), and a Pangea API token from another project may not be stored in a Vault configured in a different project.
Verified resolution: Agents hit both of these when consolidating credentials. If an import call fails saying the token is already stored, do not create a second entry: fetch the existing item by name and reuse it, since one token maps to exactly one Vault item. And keep project boundaries strict: a token minted in project A cannot live in project Bs Vault, so multi-project setups need per-project tokens, not one shared token copied everywhere. When you enable a new Pangea service its default token lands in Vault automatically, which is the usual source of the duplicate-entry surprise.
Source URL: https://pangea.cloud/docs/vault/manage-pangea-tokens/import-a-token
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_kcBNfr0OGdXJqiK7JZe6dQ" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Pangea Vault: one item per token, no cross-project token storage <span>— Vectle</span></a>