backend-services-demos

Automate backend demo API flows and conversation management with tool isolation.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/freddomingues/think-tars --skill backend-services-demos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backend-services-demos
Source: https://github.com/freddomingues/think-tars/tree/main/.cursor/skills/backend-services-demos
Command: npx skills add https://github.com/freddomingues/think-tars --skill backend-services-demos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Esta Skill encapsula a lógica de negócio da API de demos do Think TARS, permitindo gerenciar assistentes, criar conversas, enviar mensagens com isolamento de ferramentas, fazer upload de PDFs para criar um vector store e limpar conversas.

Core Features & Use Cases

  • Listar assistentes a partir do AGENTS_REGISTRY.
  • Criar uma nova conversa com um assistente existente ou com um vetor de documentos (PDF) carregado.
  • Enviar mensagens com isolamento de ferramentas, respeitando as permissões de ferramentas permitidas.
  • Carregar PDFs para criar/vector store de busca e consultas.
  • Limpar/encerrar conversas, incluindo remoção de dados de contexto se necessário.

Quick Start

Exemplo de comandos:

  • Inicie uma conversa com um assistente da demos: create_conversation(agent_id)
  • Envie uma mensagem para uma conversa existente: send_message(conversation_id, content)
  • Faça upload de um PDF e crie o vector store: upload_pdf_and_create_vector_store(pdf_bytes, filename, conversation_id)
  • Limpe uma conversa: cleanup_conversation(conversation_id)

Frequently Asked Questions about backend-services-demos

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate backend API demo flows and conversation management?

To automate backend API demo flows and conversation management, you can use this Skill to list assistants, create conversations, send messages with tool isolation, upload PDFs to vector stores, and cleanup conversations.

How does tool isolation work when sending messages to a conversation?

Tool isolation restricts message sending capabilities by enforcing allowed tool names through the run_turn function, ensuring conversations only access explicitly permitted tools and preventing unauthorized tool execution.

Can I create a vector store from a PDF upload for backend API conversations?

Yes, you can create a vector store from a PDF upload by using the upload_pdf_and_create_vector_store function, which ingests PDF bytes and filenames to generate a searchable document vector for conversations.

What is the process to list available assistants for a backend demo?

Listing available assistants for a backend demo involves querying the AGENTS_REGISTRY, which serves as the central repository mapping agent identifiers to their corresponding assistant configurations.

How do I cleanup and remove conversation context data in API demos?

To cleanup and remove conversation context data in API demos, execute the cleanup_conversation function with the specific conversation_id, which terminates the session and purges associated context data.