tavus-cli 0.2.0__tar.gz → 0.3.0__tar.gz

{tavus_cli-0.2.0 → tavus_cli-0.3.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: tavus-cli
-Version: 0.2.0
+Version: 0.3.0
 Summary: Tavus CLI and MCP server for agentic PAL creation and editing.
 Requires-Python: >=3.11
 Requires-Dist: fastmcp>=2.0.0
@@ -94,8 +94,29 @@ uv run tavus doctor
 uv run tavus pal list
 uv run tavus pal options <pal_id>
 uv run tavus pal patch <pal_id> --op replace --path /pal_name --value '"New Name"'
+uv run tavus pal capabilities list <pal_id>
+uv run tavus pal capabilities attach <pal_id> web_search
+uv run tavus pal capabilities attach <pal_id> slide_presenter --document-id <document_id> --slides-trigger walk_the_deck
+uv run tavus document create --url https://example.com/handbook.pdf --tag onboarding
+TAVUS_PORTAL_BEARER_TOKEN=<firebase-id-token> uv run tavus document upload ./handbook.pdf --tag onboarding
+uv run tavus pal knowledge add <pal_id> --document-id <document_id>
+TAVUS_PORTAL_BEARER_TOKEN=<firebase-id-token> uv run tavus pal knowledge upload <pal_id> ./handbook.pdf
 ```
 
+`pal capabilities` mirrors PAL Maker's built-in capability surface:
+Magic Canvas (`magic_canvas`), Slide Presenter (`slide_presenter`), Web Search
+(`web_search`), Perception (`perception`), and Memory (`memory`). The first,
+second, third, and fifth map to RQH PAL skills; Perception maps to
+`layers.perception`.
+
+`document` and `pal knowledge` mirror PAL Maker's Knowledge section. With a
+normal Tavus API key, create Knowledge documents from an already reachable URL
+via RQH `/v2/documents`. Local file upload uses the same portal-only flow as
+PAL Maker (local file -> tavus-api upload/S3 URL -> RQH document record), so it
+requires `TAVUS_PORTAL_BEARER_TOKEN`. PAL Knowledge attachment uses
+`document_ids` and `document_tags`; RAG tuning lives under
+`layers.knowledge_base`.
+
 ## MCP
 
 ```json

{tavus_cli-0.2.0 → tavus_cli-0.3.0}/README.md

@@ -74,8 +74,29 @@ uv run tavus doctor
 uv run tavus pal list
 uv run tavus pal options <pal_id>
 uv run tavus pal patch <pal_id> --op replace --path /pal_name --value '"New Name"'
+uv run tavus pal capabilities list <pal_id>
+uv run tavus pal capabilities attach <pal_id> web_search
+uv run tavus pal capabilities attach <pal_id> slide_presenter --document-id <document_id> --slides-trigger walk_the_deck
+uv run tavus document create --url https://example.com/handbook.pdf --tag onboarding
+TAVUS_PORTAL_BEARER_TOKEN=<firebase-id-token> uv run tavus document upload ./handbook.pdf --tag onboarding
+uv run tavus pal knowledge add <pal_id> --document-id <document_id>
+TAVUS_PORTAL_BEARER_TOKEN=<firebase-id-token> uv run tavus pal knowledge upload <pal_id> ./handbook.pdf
 ```
 
+`pal capabilities` mirrors PAL Maker's built-in capability surface:
+Magic Canvas (`magic_canvas`), Slide Presenter (`slide_presenter`), Web Search
+(`web_search`), Perception (`perception`), and Memory (`memory`). The first,
+second, third, and fifth map to RQH PAL skills; Perception maps to
+`layers.perception`.
+
+`document` and `pal knowledge` mirror PAL Maker's Knowledge section. With a
+normal Tavus API key, create Knowledge documents from an already reachable URL
+via RQH `/v2/documents`. Local file upload uses the same portal-only flow as
+PAL Maker (local file -> tavus-api upload/S3 URL -> RQH document record), so it
+requires `TAVUS_PORTAL_BEARER_TOKEN`. PAL Knowledge attachment uses
+`document_ids` and `document_tags`; RAG tuning lives under
+`layers.knowledge_base`.
+
 ## MCP
 
 ```json

{tavus_cli-0.2.0 → tavus_cli-0.3.0}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "tavus-cli"
-version = "0.2.0"
+version = "0.3.0"
 description = "Tavus CLI and MCP server for agentic PAL creation and editing."
 readme = "README.md"
 requires-python = ">=3.11"

{tavus_cli-0.2.0 → tavus_cli-0.3.0}/skills/tavus-agentic-pals/SKILL.md

@@ -100,6 +100,26 @@ PAL tools:
 - `tavus_patch_pal(pal_id, ops)`
 - `tavus_describe_pal_options(pal_id)`
 - `tavus_pal_from_template(template, pal_name, business_context, default_face_id, layers)`
+- `tavus_skill_list()`
+- `tavus_pal_skills_list(pal_id)`
+- `tavus_pal_skill_attach|patch|detach(pal_id, skill_id, config?)`
+- `tavus_pal_capability_catalog()`
+- `tavus_pal_capabilities_list(pal_id)`
+- `tavus_pal_capability_attach|patch|detach(pal_id, capability_id, ...)`
+
+Knowledge document tools:
+
+- `tavus_document_list(limit?, page?, status?, tags?, participant_tags?, name_or_uuid?, verbose?)`
+- `tavus_document_get(document_id, verbose?)`
+- `tavus_document_create(document_url, document_name?, tags?, participant_tags?, crawl?, custom_description?, is_customer_support_document?, font_size_aware_extraction?)`
+- `tavus_document_upload(local_path, document_name?, tags?, participant_tags?, custom_description?, is_customer_support_document?, font_size_aware_extraction?, bucket_name?, region?, sign_duration?)` — requires `TAVUS_PORTAL_BEARER_TOKEN`; with only a Tavus API key, use `tavus_document_create` with a public/presigned URL
+- `tavus_document_tags(search?, page?, limit?)`
+- `tavus_document_chunks(document_id, collection?, limit?, offset?)`
+- `tavus_document_recrawl(document_id, crawl?)`
+- `tavus_pal_knowledge_list(pal_id)`
+- `tavus_pal_knowledge_add|remove|replace(pal_id, document_ids?, document_tags?)`
+- `tavus_pal_knowledge_settings_patch(pal_id, rag_score_threshold?, rag_n_chunks?, rag_surrounding_chunk_radius?, enable_rag_observability_app_messages?, use_procedure_goalchain?)`
+- `tavus_pal_knowledge_upload(pal_id, local_path, ...)` — upload a local file and attach it to the PAL by default; requires `TAVUS_PORTAL_BEARER_TOKEN`
 
 Conversation and resource tools:
 
@@ -107,7 +127,7 @@ Conversation and resource tools:
 - `tavus_conversation_create(pal_id, face_id, conversation_name)`
 - `tavus_conversation_end(conversation_id)`
 - `tavus_quickstart(system_prompt, pal_name, face_id)`
-- `tavus_resource_list(resource, limit)` for `guardrails`, `objectives`, `documents`, `voices`, or `tools`
+- `tavus_resource_list(resource, limit)` for `guardrails`, `objectives`, `documents`, `voices`, `skills`, or `tools`
 - `tavus_scaffold_embed(conversation_url, target, component_name)`
 
 `tavus_scaffold_embed` returns a file manifest. The MCP host agent writes files if the user wants files created.
@@ -138,6 +158,23 @@ Autonomous build + verify (one call drives the full loop):
 
 Before patching an existing pal, call `tavus_describe_pal_options` or `tavus pal options`. Use its `available` resources and `schemas.patchable_paths` output to choose valid IDs and patch paths.
 
+For PAL Maker capabilities, prefer `tavus_pal_capability_*` or
+`uv run tavus pal capabilities ...` over raw JSON Patch. Supported capability
+ids are `magic_canvas`, `slide_presenter`, `web_search`, `perception`, and
+`memory` (also accepts the portal ids `builtin:magic_canvas`,
+`builtin:slide_presenter`, `builtin:web_search`, and `skill:memory`). Magic
+Canvas, Slide Presenter, Web Search, and Memory persist through
+`/pals/{id}/skills`; Perception persists through `/layers/perception`.
+
+For PAL Knowledge, prefer `tavus_pal_knowledge_*` or
+`uv run tavus pal knowledge ...` over raw JSON Patch. The Knowledge section is
+`document_ids` plus `document_tags`, and RAG tuning lives under
+`layers.knowledge_base`. Use `tavus_document_chunks` before making content
+claims about an uploaded document; it reads the text RQH actually indexed.
+The Tavus API-key path creates documents from an already reachable URL. Local
+file upload goes through the developer-portal upload endpoint and needs a
+Firebase portal bearer token in `TAVUS_PORTAL_BEARER_TOKEN`.
+
 Prefer focused patches over full rebuilds:
 
 ```json