toolbox-browser-api-integration

Estrelas12

Forks9

Atualizado7 de julho de 2026 às 14:51

Implementation patterns for the Vault Toolbox Browser Extension (Manifest V3).

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Fonte

veeva

veeva/Vault-Toolbox

Abrir repositório GitHub Ver repositórios do creator

Download

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

Explorador de arquivos

3 arquivos

SKILL.md

readonly

name	toolbox-browser-api-integration
description	Implementation patterns for the Vault Toolbox Browser Extension (Manifest V3).
applicable_apps	["toolbox-browser"]

Skill: toolbox-browser-api-integration

This skill provides the procedural knowledge for integrating Vault APIs within a Manifest V3 Chrome Extension.

1. Authentication Flow (Manifest V3)

Storage: Session ID is stored in an HTTP-only Chrome cookie (vaultToolboxSessionId) scoped to the vaultDNS.
Authorization: The request wrapper intercepts calls to query the cookie API (chrome.cookies.get) and inject the Authorization header.
Keep-Alive: Use useVaultSessionKeepAlive.ts to periodically ping the /keep-alive endpoint.

2. API Architecture

Facade Pattern: Centralized in src/app/services/ApiService.js.
VAPIL Entry (Default): Reusable APIs (Metadata, Query) MUST be added to src/app/services/vapil/.
Direct Fetch Forbidden: Never use window.fetch directly; use the request wrapper in VaultRequest.js.
Credentials: Always set credentials: 'omit' in the request wrapper.

3. Telemetry & Normalization

ApiService.js MUST normalize all errors and include telemetry:

{ 
  responseStatus: 'FAILURE', 
  errors: [{ type: 'ErrorType', message: 'Readable message' }],
  responseTelemetry: { responseSizeInKB, executionTimeInMS }
}

Mais deste repositório

mesmo repositório

toolbox-browser-brainstormer

veeva/Vault-Toolbox

Specialized design challenges for the Vault Toolbox Browser Extension, focusing on VQL prototyping.

2026-07-0712

toolbox-browser-code-reviewer

veeva/Vault-Toolbox

Specialized audit for the Vault Toolbox Browser Extension, focusing on Island Architecture and UI visibility.

2026-07-0712

toolbox-browser-data-grid

veeva/Vault-Toolbox

Specialized data grid implementation for the Vault Toolbox Browser Extension using TanStack Table/Virtual.

2026-07-0712

toolbox-browser-feature-designer

veeva/Vault-Toolbox

Specialized design requirements for the Vault Toolbox Browser Extension, focusing on UI visibility.

2026-07-0712

toolbox-browser-testing

veeva/Vault-Toolbox

Specialized testing and dev-server protocol for the Vault Toolbox Browser Extension.

2026-07-0712

toolbox-browser-tool-builder

veeva/Vault-Toolbox

Specialized scaffolding and shell integration for the Vault Toolbox Browser Extension.

2026-07-0712

name	toolbox-browser-api-integration
description	Implementation patterns for the Vault Toolbox Browser Extension (Manifest V3).
applicable_apps	["toolbox-browser"]

Skill: toolbox-browser-api-integration

This skill provides the procedural knowledge for integrating Vault APIs within a Manifest V3 Chrome Extension.

1. Authentication Flow (Manifest V3)

Storage: Session ID is stored in an HTTP-only Chrome cookie (vaultToolboxSessionId) scoped to the vaultDNS.
Authorization: The request wrapper intercepts calls to query the cookie API (chrome.cookies.get) and inject the Authorization header.
Keep-Alive: Use useVaultSessionKeepAlive.ts to periodically ping the /keep-alive endpoint.

2. API Architecture

Facade Pattern: Centralized in src/app/services/ApiService.js.
VAPIL Entry (Default): Reusable APIs (Metadata, Query) MUST be added to src/app/services/vapil/.
Direct Fetch Forbidden: Never use window.fetch directly; use the request wrapper in VaultRequest.js.
Credentials: Always set credentials: 'omit' in the request wrapper.

3. Telemetry & Normalization

ApiService.js MUST normalize all errors and include telemetry:

{ 
  responseStatus: 'FAILURE', 
  errors: [{ type: 'ErrorType', message: 'Readable message' }],
  responseTelemetry: { responseSizeInKB, executionTimeInMS }
}