ocs-agent-setup

Automate OCS chatbot provisioning by cloning templates, uploading documents, and publishing versions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates end-to-end OCS chatbot provisioning for a given opportunity by cloning the ACE golden template, building a per-opp knowledge base, and exposing embed credentials.

Core Features & Use Cases

  • Clone the ACE golden template for a new opportunity to create an ACE chatbot instance.
  • Create a per-opp knowledge collection, upload PDD/training materials/app summaries, and index the data locally.
  • Patch the chatbot system prompt with opp-specific framing, publish a version, and retrieve embed credentials for Connect.

Quick Start

Run the OCS agent setup to configure a new ACE chatbot for the current opportunity and return the embed credentials.

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 OCS chatbot provisioning for a new opportunity?

Automate OCS chatbot provisioning by cloning a golden template, creating a per-opp knowledge collection, uploading PDD and training docs, patching the system prompt, and retrieving embed credentials.

What do I need to set up an ACE chatbot instance from a template?

Setting up an ACE chatbot instance requires environment variables for OCS endpoints, a golden template ID, and per-opp context like PDD, training, and app summaries accessible via the ACE workflow.

Can I upload PDD and training materials to a per-opportunity knowledge collection?

Yes, you can upload PDD, training materials, and app summaries to a per-opportunity knowledge collection, which indexes the data locally for the cloned chatbot instance.

How does the OCS setup process expose embed credentials for Connect?

The OCS setup exposes embed credentials for Connect by patching the chatbot system prompt with opportunity-specific framing, publishing a version, and retrieving the credentials upon completion.

What are the limitations of one-click OCS chatbot setup?

One-click OCS chatbot setup is limited by its dependency on predefined environment variables for OCS endpoints, a golden template ID, and per-opp context accessible via the ACE workflow for MCP atom calls.