Skip to main content

AI & Agents

TI Admin Claude Plugin

Connect Claude to Thought Industries in a few steps. Browse your course catalog, generate outlines, write lessons, and update content without switching tools.

BetaClaude DesktopDrafts only

Now in beta. Head over to your instance and look for "Your Thought Industries Academy, inside Claude" and follow the prompts.

Overview

The TI Admin Plugin lets you administer Thought Industries platforms directly from the Claude desktop application. Browse course catalogs, author new courses with AI assistance, rewrite lesson content, and manage learning experiences — all without leaving Claude.

The plugin is built on the Thought Industries REST API. All write operations are configured as drafts only — publishing from Claude is not supported. Final review and publishing always stays with the human author in the Thought Industries admin UI.

Skill tiers

The plugin is organized into three tiers of increasing autonomy.

TypeDescription
ActionsSingle-purpose tasks — one API call, deterministic, narrowly scoped
RoutinesFixed sequences of Actions for repeatable multi-step workflows
PlaybooksStrategic, flexible workflows that string Routines and Actions together

Prerequisites

  • Claude desktop application (latest version) — the browser version does not support this setup flow
  • A Thought Industries instance with API access enabled
  • A Thought Industries API key (see Get your API key below)
1

Install the plugin

In the Claude desktop app, go to Customize → Plugins → Personal → Add marketplace and enter thoughtindustries/ti-admin-plugin. This uses the personal plugin setup flow — not the standard connector flow. You can also use the CLI:

Claude Code CLI
# From the Claude Code CLI — add the Thought Industries marketplace
/plugin marketplace add thoughtindustries/ti-admin-plugin

# Then install the plugin
/plugin install ti-admin-plugin@ti-plugins

Once added, the plugin appears in Claude as the TI Admin Plugin.

2

Get your API key

  1. 1.Log in to your Thought Industries instance as an admin.
  2. 2.Navigate to {your-instance-url}/learn/manager/security-settings.
  3. 3.Under the API section, create a new Ancillary API key — name it “Claude Key” and copy it.
  4. 4.Store it securely — you will provide it to the plugin on first use.
3

Configure access

The plugin needs two values to make API calls: your Thought Industries instance base URL and your API key. For CI or scripting, set them as environment values.

Environment values
export TI_BASE_URL="https://your-instance.thoughtindustries.com"
export TI_API_KEY="your-api-key-here"
ValueDescription
TI_BASE_URLYour Thought Industries instance, e.g. acme.thoughtindustries.com
TI_API_KEYThe Ancillary “Claude Key” from Security Settings

Your first experience

Once installed and configured, just talk to Claude naturally — browse your catalog, inspect a course, read lesson content, author a new course, or rewrite existing content.

Conversation
You: "Show me my courses"
Claude: (runs the list-course-groups Action)
→ Returns your catalog with titles, IDs, and content types.

You: "Help me build a course on API security best practices"
Claude: (runs the author-course Playbook)
→ Discovery → Outline → Content → Refinement → Summary
→ Everything created as a DRAFT for you to publish manually.

Safety guardrails

Every skill enforces hard gates — non-negotiable constraints baked into the skill definitions that cannot be overridden by prompting.

GuaranteeDetail
All content stays as draftThe plugin never calls releaseContent. Publishing happens manually in the Thought Industries admin UI only.
Approval required before writesRoutines and Playbooks show what they will create or update and wait for explicit confirmation.
No fabricated IDsThe agent always reads IDs from the API first — it never invents or guesses UUIDs.
No content destructionExisting content is never discarded or overwritten without your explicit permission.
No assessment auto-creationThe Playbook may suggest quiz placement but never creates assessment content.

Use a dedicated, scoped Ancillary key and never paste production API keys into shared or public conversations.

Related