Skip to main content
Use these to have a coding assistant build your EkaScribe integration. Each one hands it the same facts as these docs.
Check what the assistant writes against these docs, and test it in the sandbox before it reaches a patient.

Reference skill

Every operation, its hosts, auth and headers, in one install.

CLAUDE.md file

The four calls and their rules, in one file to drop into your project.

​
Before you start

Three things have to be in place before anything on this page works. Then work down this page in order: install the skill, connect the MCP server where there is one, and ask for one flow at a time in plain language. Read what the assistant writes before you run it.

​
Install the skill

The eka-scribe skill carries the hosts, auth and headers, and every Scribe operation, each with a link to its page here. It is built from these docs, so it changes when they do. In Claude Code:
In Cursor, Codex or another agent, copy the skill folder into the folder your agent loads skills from. Its map is SKILL.md.

​
Prompting an agent for Scribe

Tell the assistant these, and check its output against them. The CLAUDE.md file carries these rules and the four calls in one file you can drop into a project.

​
Read these docs as an agent

Every page here is also plain text an agent can read.
  • llms.txt is a map of every page.
  • llms-full.txt is every page’s text in one file.
  • The menu at the top of each page copies it as Markdown, or opens it in Claude or ChatGPT.