ocs-agent-setup

Automate per-opportunity Open Chat Studio chatbot provisioning with RAG collections and prompt publishing.

1|2|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/dimagi-internal/ace --skill ocs-agent-setup-dimagi-internal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ocs-agent-setup
Source: https://github.com/dimagi-internal/ace/tree/main/skills/ocs-agent-setup
Command: npx skills add https://github.com/dimagi-internal/ace --skill ocs-agent-setup-dimagi-internal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the manual, error-prone work of configuring per-opportunity Open Chat Studio (OCS) chatbots for the ACE Connect lifecycle, removing the need to manually navigate the OCS dashboard, track API identifiers, and assemble RAG knowledge bases from scattered project documents.

Core Features & Use Cases

  • End-to-end Chatbot Provisioning: Automatically clones the golden OCS template, creates per-opportunity RAG collections populated with project design documents, training materials, and CommCare app summaries, composes archetype-aware system prompts, publishes a configured chatbot version, and retrieves embed credentials.
  • Idempotent Re-runs and Fast Iteration: Skips redundant OCS calls if a local state file exists, and supports a --prompt-patch mode that updates only the system prompt and republishes without re-uploading or re-indexing RAG content for quick iterations after quality evaluations.
  • Use Case: For a new ACE Connect opportunity, run this Skill to deploy a fully configured support chatbot in minutes, with knowledge grounded in the project's design documents, training guides, and app structure, ready for facilitator use.

Quick Start

Use the ocs-agent-setup skill to deploy a fully configured OCS support chatbot for your current ACE opportunity, with RAG knowledge sourced from project design documents, training materials, and CommCare app summaries.

Frequently Asked Questions about ocs-agent-setup

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

FAQPage Schema
How do I automate Open Chat Studio chatbot deployment for ACE opportunities?

Automate OCS chatbot deployment by cloning a golden template, creating RAG collections from project documents, composing system prompts, and publishing a configured version with embed credentials retrieved automatically.

Can I update an OCS chatbot system prompt without re-uploading RAG content?

Yes, you can update the system prompt without re-uploading RAG content by using the fast prompt-patch mode, which applies the prompt update and republishes the chatbot version while skipping redundant file indexing.

What documents do I need to build a RAG knowledge base for an ACE Connect chatbot?

To build the RAG knowledge base for an ACE Connect chatbot, you need project design documents, training materials, and CommCare app summaries, which are automatically assembled into the per-opportunity RAG collection.

How do re-runs work when provisioning OCS chatbots for ACE opportunities?

Re-runs are idempotent, meaning the process checks for an existing local state file and short-circuits redundant OCS API calls to prevent duplicate configurations, while validating live round-trip identifiers to avoid fabricated state corruption.

Does the OCS chatbot provisioning process validate API identifiers automatically?

Yes, the OCS chatbot provisioning process validates live round-trip API identifiers to prevent fabricated state corruption, enforcing strict serial execution of dependent OCS API calls throughout the template cloning and publishing lifecycle.