> ## Documentation Index
> Fetch the complete documentation index at: https://docs.thinkplatform.ai/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Choose User guide for browser tasks, Developers for CLI, SDK and external agents, and Administration for organization management.
> Confirm identity and organization/project context before operations. Documentation access does not grant ThinkPlatform permissions.
> Review side effects, verify changes with a read, and do not blindly retry an operation with an uncertain outcome.
> Use documented UI steps for the web app and documented public CLI or SDK interfaces for automation. Follow each page’s prerequisites and authentication requirements.

# Connect a coding agent

> Connect an agent to ThinkPlatform documentation and install bundled CLI guidance.

Give your coding agent access to ThinkPlatform documentation and task-specific skills. It can read Markdown pages and LLM indexes, discover task skills, or use guidance bundled with the CLI. Access to documentation does not grant permission to operate on ThinkPlatform resources.

## Read Markdown and LLM indexes

The documentation is public. Fetch [the compact index](https://docs.thinkplatform.ai/llms.txt) to find relevant pages, or [the full documentation](https://docs.thinkplatform.ai/llms-full.txt) when your agent needs the complete content. Individual pages are available as Markdown using the page's `.md` route or a request with `Accept: text/markdown`.

For example, read [the CLI overview as Markdown](https://docs.thinkplatform.ai/cli/get-started/overview.md), then follow links to installation, authentication, and the commands for your task. Check that a fetch returned the expected text before using it.

## Discover task skills

Skills describe how to complete tasks such as preparing datasets, managing agents, or building Canvas dashboards. In **Developers**, browse the **Agent skills** group for command references, examples, and report templates. Read the instructions for your task, then follow their links to supporting pages as needed.

For clients that fetch skills directly, [the skill catalog](https://docs.thinkplatform.ai/skill.md) provides discovery. Machine-readable catalogs are available at [the skills index](https://docs.thinkplatform.ai/.well-known/skills/index.json) and [the agent skills index](https://docs.thinkplatform.ai/.well-known/agent-skills/index.json). Retrieve the instructions for your task and follow their links to supporting references and templates as needed.

If your client cannot retrieve the documentation or skill references, use the CLI's bundled guidance below.

## Use locally bundled CLI guidance

Install the [CLI](https://docs.thinkplatform.ai/cli/get-started/installation.md) to inspect and install the plugin and skills bundled with that CLI version. `tp plugins` operates on local bundled content and does not require a ThinkPlatform login. Installed guidance helps an agent choose commands; the agent still needs an authenticated CLI and access to the intended organization and project for platform operations.

## Find the right guidance

List the bundled plugin and its skills, then ask for guidance matching your task:

```bash theme={"system"}
tp plugins list
tp plugins recommend datalake upload-file
tp plugins recommend mlops jobs
```

Recommendations include a `skill_id` and a `show_command`. Read the recommended instructions before installing. For the bundled MLOps skill:

```bash theme={"system"}
tp plugins show thinkplatform
tp plugins show thinkplatform --file skills/thinkplatform-mlops/SKILL.md
```

Without `--file`, `show` displays the bundled plugin manifest. With global `--json`, it returns an object containing `id`, `file`, and `content`; without it, the file content is printed directly. Recommendation results depend on the guidance included in your installed CLI version.

## Install the full plugin

For Codex, inspect the proposed destination and files, then install:

```bash theme={"system"}
tp plugins install thinkplatform --target codex --dry-run
tp plugins install thinkplatform --target codex
tp plugins doctor --target codex
```

The install result reports `destination`, `files`, and `dry_run`, plus marketplace registration information where applicable. Review those paths. `doctor` checks local plugin and manifest paths and whether a marketplace file exists. It does not check platform authentication, prove the agent has loaded the instructions, or validate a skill's execution. Follow your agent's normal workflow to load newly installed guidance.

Other supported targets are `agents`, `claude`, and `dir`. The `agents` target uses the current repository as its root. The `claude` target installs bundled skill folders into the Claude-compatible skills location. For an explicit plugin directory, supply `--dest`:

```bash theme={"system"}
tp plugins install thinkplatform --target dir --dest ./agent-guidance --dry-run
tp plugins install thinkplatform --target dir --dest ./agent-guidance
tp plugins doctor --target dir --dest ./agent-guidance
```

This example writes a `thinkplatform` plugin folder below `./agent-guidance`. A directory export still needs to be loaded by the consuming agent.

## Install one skill instead

Choose a `skill_id` from `plugins list` or `plugins recommend`. To install only the MLOps skill into Codex's skill directory:

```bash theme={"system"}
tp plugins install-skill thinkplatform-mlops --target codex --dry-run
tp plugins install-skill thinkplatform-mlops --target codex
```

Check `destination` and `files` in the result. For Codex, `doctor` checks plugin installation paths, so it is not a verification command for a standalone skill install. Inspect the reported skill folder and confirm it is available in your agent.

Both install commands refuse an existing destination by default. If you intend to replace it, review the plan with `--force --dry-run`, then use `--force`; replacement creates a timestamped backup. Do not overwrite local customizations without reviewing them.

## Connect the agent to the correct project

Have a person run `tp profile setup` in the terminal environment where the agent invokes `tp`. It guides sign-in and organization/project selection, saving the profile after confirmation. The wizard requires an interactive terminal and rejects JSON output and root `--query`; agents should use the prepared profile rather than automate the wizard.

For unattended setup, use the [manual context commands](https://docs.thinkplatform.ai/cli/guides/context.md#manual-selection-for-scripts) and `configure --no-prompt` with explicit settings and discovered IDs. Authentication can still require a person to complete sign-in. Before a platform write, have the agent inspect:

```bash theme={"system"}
tp context show
```

Give the agent the intended profile or destination, task scope, and permitted changes. Ordinary commands such as `tp canvas pages list` reuse the saved context; root `--json` is optional for machine parsing. Use explicit global `--org-id` and `--project-id` overrides when a task must not depend on a saved default.

`tp skills` is a separate, remote platform skill registry scoped to an organization and project. Installing bundled guidance with `tp plugins` does not upload a platform skill, change an Agent's configuration, or register a remote skill. Use the [command reference](https://docs.thinkplatform.ai/cli/reference/commands.md) for those separate operations.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.