Skip to main content
The overcut-api skill connects an AI coding agent to the Overcut GraphQL API. Once it is available, you can explore and manage your Overcut account in plain language: build a workflow, inspect an agent’s skills, check why a run failed, or review token usage, without opening the web app. This is the main Overcut skill, and the place to start. For the full list of skills and the general install path, see the Overcut Skills overview.

​
What the skill does

Everything you can see in the Overcut web app is also reachable through a single GraphQL endpoint, and the skill teaches your agent how to reach it. With a personal API token, it can:
  • Explore your account: workspaces, projects, workflows, agents, skills, MCP servers, secrets, repositories, and playbooks.
  • Build and manage: create and update workflows, agents, and orchestrations, assign skills and MCP servers, add workflows from playbooks, and trigger a workflow run.
  • Monitor and analyze executions: track workflow runs and orchestration instances, inspect execution history, and review token-usage analytics.
  • Debug runs: walk a failed run down through its steps, logs, and threads to find the root cause.
  • Script your setup: audit or report on your configuration from outside the UI.
The skill defaults to read-only. It asks for confirmation before any create, update, delete, commit, or trigger action, and it never reads or prints secret values.

​
Add the skill

You add this skill the same way you add any skill to your agent. The exact steps vary by agent, so check your agent’s documentation. There are two common paths:

Install from the plugin marketplace

If your agent supports plugin marketplaces, add the marketplace repository overcut-ai/overcut-skills and install the overcut plugin.

Or copy the skill folder

Otherwise, clone the overcut-ai/overcut-skills repository and copy the overcut-api skill folder (at plugins/overcut/skills/overcut-api/, including its references/ and scripts/) into the directory your agent loads SKILL.md skills from.
For example, in Claude Code:
Once installed, your agent uses the skill automatically when you ask it to work with your Overcut account.

​
Authenticate

The skill needs a personal API token so it can call the API as you.

Generate a token

In the Overcut web app, go to Workspace Settings → Security → API Tokens and select New API Token. Copy the token when it is shown. You will not be able to see it again.

Export the token

Set the token as an environment variable before you start your agent:
The token carries the same permissions as the user who created it and expires after about 30 days of inactivity. Treat it like a password: never commit it or paste it into chat. For safety, create a dedicated, least-privilege user and generate the token as that user, so a leaked token has a limited blast radius.

​
Use it

Once the skill is available and the token is set, ask your agent in plain language. The skill translates your request into the right API calls. Example prompts:
  • “List my Overcut workflows and show which ones are active.”
  • “Create a workflow from the code-review playbook in this project.”
  • “Show the skills and MCP servers assigned to the code-review agent.”
  • “Why did the last run of the release workflow fail?”
  • “Summarize token usage for this project over the last week.”
The skill starts from your workspace, drills into a project, and then into individual entities, asking for confirmation before it changes anything.
Workflows run on a draft plus committed model: edits change the draft, and production keeps running the last committed version until you commit. The skill never commits, discards, or triggers without your explicit confirmation.

​
What it doesn’t cover

The skill is about reaching the API: connecting, exploring, and running CRUD operations. It does not cover deeper product-design questions, such as how to write good step instructions, choose a base agent, or design triggers. For those, use the built-in Overcut assistant in the web app, which has current knowledge of the whole product.
  • Convert to Overcut: migrate an existing framework, then import it with this skill.
  • Skills: add SKILL.md-based skills to your Overcut agents.
  • Workflows: how workflows, steps, and triggers work.