Contracko

View saved version →

---
name: contracko
description: 'Manage contracts in Contracko: import or upload documents, set renewal and notice reminders, review AI analysis and reports, organise folders and types, draft new agreements.'
---

Upstream: none (homegrown).

# Contracko

Use this skill for connecting and onboarding a workspace, importing or uploading contracts, syncing records from other systems, notifications and reminders, notice and end dates, reviewing AI analysis and portfolio reports, comparing contracts, organising folders, types and parties, creating or drafting agreements from templates, signature handoffs and filing signed agreements.

## Say this once

In the first response of a session where Contracko is connected to an AI product that is not Contracko's own:

> Contract data will be sent to the AI provider running this session. Contracko cannot control what that provider does with it. Turn off model training in the provider's settings before working with real contracts.

## Connect and discover

For client setup and user-owned consent, follow [onboarding](references/onboarding.md) and the [README connection steps](https://github.com/contracko/contracko-skills#install).

Use `auth_validate` to confirm workspace, access and scopes match the requested work. `status: "ok"` confirms a credential, not Contract Management access: inspect the returned access refusals.

| Scope | Available work |
|---|---|
| any valid credential | connection validation and tool search |
| `contract:read` | contracts, folders, access overviews, types, parties, comments, events, document search and reads, document re-read results |
| `contract:write` | contract and folder changes, import and ingest, documents, comments, events, notifications, types, and parties |

Read scopes do not guarantee read-only effects. Follow live annotations and get approval before saved-state changes; the [tool index](references/tool-index.md) records those effects.

## Workspace availability

If an action is not available on the workspace's current plan, say so plainly and do not retry.

For partial imports, keep accepted items, continue checking accepted unfinished work, and do not resubmit the batch.

## Find the right tool

Use `clm_search_tools` when unsure which tool fits, before a multi-step job, or for a first contract in an empty workspace. It searches only this connection's listed tools; a missing result does not establish unavailability.

```json mcp:clm_search_tools
{ "query": "Add my first contract", "toolset": "imports" }
```

Use discovered tools, arguments and returned identifiers, never invented tools, signatures or source ids. For unavailable operations, offer the nearest supported step and hand off to the app.

## Read tool results once

Check `isError` first. On success, prefer `structuredContent`; otherwise parse the legacy JSON text. Use one representation, once.

A completed Task can carry a refusal inside its nested `result`. Inspect that result, relay its current audience-safe message, and never retry the refused work. Apply [workspace availability](#workspace-availability) when relevant.

Missing or malformed required `outputSchema` fields mean a response mismatch, not empty data. Report it; never retry a mutation solely for output validation failure.

`OUTCOME_UNKNOWN` means a write may have completed. Re-read affected state and reconcile before retrying or reporting success or failure.

## Write safely

Confirm every bulk change. For intake confirmation, follow [imports](references/importing-contracts.md#confirm-before-writing); for field sets and destination confirmation before moves, follow [workspace organisation](references/organising-the-workspace.md). Explain email effects before notification changes. Read returned per-item outcomes and read back changed state before claiming completion.

## Route the work

Load only the references needed for the job.

| The user wants | Read |
|---|---|
| connecting, consent, a first contract, import before mod

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 8 — file references are metadata, not package contents.