Skip to content
Raw Markdown

For agents

Use MCP to inspect and ask, the CLI to verify, and a repository checkout to change git-managed context. Default to leaving a pull request for review.

Use the right interface

MCP
Ask data questions, record the user’s rating of a conversation, inspect project and schema state, and triage issues. MCP does not return or edit context files.
Repository
Read and edit the context, then open a pull request. Follow cassis/AGENTS.md in the checkout.
CLI
Pull, format, validate, test, run evals, and confirm publication. Use the CLI reference for exact behavior.
Web app
Inspect evidence and versions. Edit only when the project is app-managed.

The capability matrix distinguishes what is technically possible from the supported workflow.

Authenticate safely

Any compatible interactive MCP client can use browser OAuth. Headless agents, the CLI, and CI use an API key that acts as the person who created it. When the MCP server’s instructions say the key is scoped to one project, omit project_id and skip list_projects.

Read CASSIS_API_KEY from the environment. Never print it or put it in a prompt, file, commit, issue, or pull request. If it is missing, stop and report that instead of asking someone to paste it into chat.

Read in this order

  1. How the curation loop works.
  2. Curate a git-managed project.
  3. Capability matrix.
  4. The relevant MCP, CLI, or context file format reference.

Machine-readable navigation is at /llms.txt. Every page also has /raw/<path>.md; for example, /curate/agent is available at /raw/curate/agent.md.

Stop at the authorized boundary

Default to a pull request. Merge only when the repository owner explicitly authorizes it after required checks pass. Write Resolves <issue id> in the pull request description so the merge closes the issue the work started from: closing the loop is the last step of the work, not an optional extra. A merge is not proof of publication, so confirm the live version with get_project_status or cassis status.

Never publish from the app or run context upload against a repository the GitHub App already syncs.

Start a session

Prompt for an agent Orient before acting

Use before assigning context work.

Goal: work on this Cassis project without guessing at capabilities or authority. Read: - https://docs.getcassis.com/raw/for-agents.md - https://docs.getcassis.com/raw/curate/agent.md - https://docs.getcassis.com/raw/reference/capabilities.md - cassis/AGENTS.md if this is a repository checkout Before changing anything, state: 1. Whether the project is app-managed or git-managed and how you checked. 2. Which interface you will use for each step. 3. The artifact you will produce and the verification commands you will run. 4. Whether you must stop at the pull request or are explicitly authorized to merge and confirm publication. Read CASSIS_API_KEY from the environment if needed. Never reveal it. Do not resolve an issue until the published version contains the landed fix. When it does, propose resolving it and name the id.