corthos-corthography

client.corthography.ai

TypeScript SDK, CLI, and Claude plugin for invoking Corthography Press workflows.

This is the partner-facing surface of the multi-tenant Press service (SPEC-00018). Engineers in partner repos install this client to start template-query / template-render / template-publish runs from their own Claude Code sessions, terminals, or CI without ever touching Press core.

[ Partner engineer ]
    ↓ /corthography-press-render dms/.../colleges/overview+computer-science-degree
[ Claude plugin (this repo) ]
    ↓ corthography render ...
[ @corthos/corthography-cli ]
    ↓ PressClient.startRun(...)
[ @corthos/corthography-sdk ]
    ↓ HTTPS + Bearer token
[ api.corthography.ai ]
    ↓ AssumeRole + StartExecution
[ press.corthography.ai engine ]

The SDK and CLI are public; the API and engine are private. Security is enforced by the partner token and the API's authorization registry — not by hiding the client.

Three deliverables, one repo

Package	What it is	Who uses it
@corthos/corthography-sdk	Typed SDK wrapping the REST API	Custom integrations, CI scripts
@corthos/corthography-cli	corthography binary built on the SDK	Engineers in terminals, CI pipelines
Claude plugin	Slash commands (/corthography-press-render, etc.) wrapping the CLI, four template-authoring standards skills, and five bundled FABER workflows for end-to-end pipeline runs and guided template hotfixes	Partner engineers in Claude Code

All three are versioned together. The plugin's bundled FABER workflows (template-query, template-render, template-publish, the composite template-query-render-publish, and template-hotfix) can be invoked directly or extended in a partner repo with custom pre/post steps — see docs/client/extending-workflows.md. The template-authoring standards skills back the hotfix workflow's edit step and are also readable on their own — see docs/client/template-authoring.md.

Install

Claude plugin (recommended for partners)

In a Claude Code session, add this repo as a marketplace and install the plugin:

/plugin marketplace add corthosai/client.corthography.ai
/plugin install corthography-press-client@corthography-client

The legacy direct install (/plugin install corthosai/client.corthography.ai) also still works.

Other agentic harnesses

The same skills/ tree is exposed to other harnesses via parallel manifests, so the slash commands are available regardless of which agent the partner uses:

• Codex — .codex-plugin/plugin.json
• Cursor — .cursor-plugin/plugin.json

Each harness's manifest points at ./skills/, so there is one source of truth for the corthography-press-* skill content.

Then add your token to your shell:

export CORTHOGRAPHY_TOKEN=...
export CORTHOGRAPHY_API=https://api.corthography.ai/v1

CLI (standalone)

npm install -g @corthos/corthography-cli
corthography --help

SDK (programmatic)

npm install @corthos/corthography-sdk

import { PressClient } from "@corthos/corthography-sdk";

const client = new PressClient({
  token: process.env.CORTHOGRAPHY_TOKEN!,
  baseUrl: "https://api.corthography.ai/v1",
});

const run = await client.startRun({
  workflow: "template-render",
  target: "dms/education-niche/colleges/overview+computer-science-degree",
  environment: "test",
});
console.log(run.runId);

Slash commands

Pipeline action skills (corthography-press-*)

Command	What it does
/corthography-press-query {target}	Stage 1: collect Corthodex API data into S3 chunks (supports --wait)
/corthography-press-render {target}	Stage 2: render Markdown from staged data (supports --wait)
/corthography-press-publish {target}	Stage 3: distribute rendered content to destination (test); use --env prod for production (requires approval); supports --wait
/corthography-press-status {run_id}	Check run status; pass --wait to block until terminal
/corthography-press-logs {run_id}	Get the CloudWatch log group for a run
/corthography-press-approve {run_id}	Approve a run paused at the prod release gate
/corthography-press-list-projects	Show projects you're authorized for
/corthography-press-list-templates	Show templates you're authorized for

Template-authoring standards skills (corthography-template-*)

These don't drive any runs — they're partner-facing documentation, loadable as context (by the template-hotfix workflow) or readable directly.