everruns-api SKILL.md skillA

everruns-api from everruns/everruns is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add everruns/everruns/everruns-api@v2.0

Pins v2.0 in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
everruns/everruns
Path
skills/everruns-api/SKILL.md
Versions recorded
1
Latest version
v2.0, committed Nov 10, 2026
Size
2,741 bytes
Repository stars
67
License
MIT

Create agents, open sessions, and stream events over the Everruns REST API with a personal access token. Use for server-to-server automation where no browser or MCP client is available; use everruns-cli for shell work and everruns-mcp for MCP clients.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# Drive Everruns over the REST API

Everruns is API-first: everything the UI does is available over HTTP, with
server-sent events for streaming. Use the person's own Everruns unless they
name another one.

## Base URL

Set `EVERRUNS_URL` to the deployment's origin and use `$EVERRUNS_URL/api`:

- On their machine (`everruns docker up`, `everruns k8s port-forward`):
  `http://localhost:9300`
- On their server or cluster: the public URL they chose, such as
  `https://everruns.example.com`
- The demo instance, only when the person asks for it: `https://app.everruns.com`.
  It is a demo, not a hosted service.

Check it first: `curl -fsS "$EVERRUNS_URL/health"`. The deployment's own
`$EVERRUNS_URL/auth.md` says which credentials it needs; a local install with
`--auth none` needs none.

## Credential

The person issues a personal access token in the UI under **Settings →
Personal access tokens** and puts it in their environment as
`EVERRUNS_TOKEN`. Tokens start with `evr_pat_` and carry the full authority of
the account. Never ask for the token in the conversation, print it, or commit
it. Send it as `Authorization: Bearer $EVERRUNS_TOKEN`.

## Create an agent

```bash
…

Read the whole file at its exact version.

How to install

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_uvcw4xxsgn2mcedv/6bb115c6ecd1d1e4c7728f1d930d324df1a61f9aa750a4ed971e1cb064649fa9.json

Then /plugin install everruns-api@markdownregistry-uvcw4xxsgn2mcedv in Claude Code. It installs v2.0, the one graded A here, pinned to the commit it was graded at, and leaves it there.

The exact contents, by fingerprint
mdr add everruns/everruns/everruns-api@sha256:6bb115c6ecd1d1e4

The line at the top of this page pins the label v2.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_uvcw4xxsgn2mcedv.svg)](https://markdownregistry.com/a/art_uvcw4xxsgn2mcedv)

1 badge image fetches in 30 days. What the badge shows.

Ask from your agent
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry

Then ask it: what changed in everruns/everruns/everruns-api since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.

Got a copy of everruns-api from somewhere else? Ask it: where did my everruns-api come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.

Versions

The registry has recorded 1 version of this file, committed on Nov 10, 2026.

Watch this file (sign in, one email per new version)

versioncommittedcommitsizeaudit
v2.0 latest2026-11-10 0bc77b5 2,741 BA view
Keep it current by itself, install once

Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

Install on GitHub

It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.

Keep it current by itself

Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml

It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.

Check a whole project

From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies

In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies

No sha256sum on your machine? shasum -a 256 prints the same lines.

Audit of the latest version

A  17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (2741 bytes)
  • pass: No zero-width or bidi control characters
  • pass: No instruction hidden inside an HTML comment
  • pass: No link to an exfiltration or paste host
  • pass: No credential-shaped string
  • pass: No instruction to send local credentials anywhere
  • pass: No text hidden with inline styles
  • pass: No prompt-injection phrasing
  • pass: No curl or wget piped into a shell
  • pass: No recursive delete of root, home or parent
  • pass: No instruction to read or print local credentials
  • pass: No base64 blob over 200 characters
  • pass: No link to a raw IP address
  • pass: No script tag

Source

GitHub

everruns/everruns · 67 stars · license MIT · pushed 2026-11-16 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_uvcw4xxsgn2mcedv
GET https://markdownregistry.com/api/v1/resolve?ref=everruns/everruns/everruns-api
GET https://markdownregistry.com/api/v1/blob/6bb115c6ecd1d1e4c7728f1d930d324df1a61f9aa750a4ed971e1cb064649fa9

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from everruns/everruns

facet-icons SKILL.md skill
everruns/everruns · .agents/skills/facet-icons/SKILL.md · Extend or refine Everruns' custom Facet domain icon family while preserving the approved Intent Agent mark and Slate's…
git:20261009.a5a3c69 · audit A · 67 stars
maintenance SKILL.md skill
everruns/everruns · .agents/skills/maintenance/SKILL.md · Goal-oriented repository maintenance and release-readiness work. Use when the user asks for maintenance, release prep…
git:20261012.386d3ce · audit A · 67 stars
manual-ui-testing SKILL.md skill
everruns/everruns · .agents/skills/manual-ui-testing/SKILL.md · Run manual UI test cases using agent-browser against a running stack. Use when the user asks to run UI tests, test the…
git:20260914.2afcf40 · audit A · 67 stars
process-issues SKILL.md skill
everruns/everruns · .agents/skills/process-issues/SKILL.md · Process Linear issues — pick up, fix, and ship one PR per issue. Use when the user asks to process one issue, a…
git:20260912.cec03d4 · audit A · 67 stars
ship SKILL.md skill
everruns/everruns · .agents/skills/ship/SKILL.md · Goal-oriented workflow for landing a requested change safely. Use when the user asks to ship, fix and ship, take a…
git:20261017.31cb0a8 · audit A · 67 stars
tune-cli-help SKILL.md skill
everruns/everruns · .agents/skills/tune-cli-help/SKILL.md · Tune `everruns` command help (descriptions, examples, group summaries) against the platform-capability eval's friction…
git:20261010.a4989f0 · audit A · 67 stars
ui-screenshots SKILL.md skill
everruns/everruns · .agents/skills/ui-screenshots/SKILL.md · Take UI screenshots using agent-browser. Use this skill to capture visual state of UI components for code review…
git:20260917.8119041 · audit A · 67 stars
AGENTS.md@.deepsec AGENTS.md file
everruns/everruns · .deepsec/AGENTS.md
git:20261003.aaf3bb0 · audit A · 67 stars
AGENTS.md AGENTS.md file
everruns/everruns · AGENTS.md
git:20261110.0bc77b5 · audit A · 67 stars
CLAUDE.md CLAUDE.md file
everruns/everruns · CLAUDE.md
git:20251214.1f0f793 · audit B · 67 stars
AGENTS.md@apps/chat-ui AGENTS.md file
everruns/everruns · apps/chat-ui/AGENTS.md
git:20261024.8e062e0 · audit A · 67 stars
AGENTS.md@apps/ui AGENTS.md file
everruns/everruns · apps/ui/AGENTS.md
git:20261028.f751048 · audit A · 67 stars

Every file in everruns/everruns

Browse by kind, by grade A, or by owner.