everruns-agent-authoring SKILL.md skillA
everruns-agent-authoring from everruns/everruns is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add everruns/everruns/everruns-agent-authoring@v1.0Pins v1.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-agent-authoring/SKILL.md- Versions recorded
- 4
- Latest version
- v1.0, committed Nov 8, 2026
- First version recorded
- Oct 12, 2026
- Size
- 5,840 bytes
- Repository stars
- 67
- License
- MIT
Create or revise Everruns platform agents through MCP, including instructions, harnesses, capabilities, model selection, portable packages, and behavioral verification. Use when changing an agent definition; use everruns-mcp for running an existing agent or inspecting sessions.
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
# Author an Everruns agent Use the connected MCP server's `discover`, `query`, and `execute` tools. Their `everruns` commands execute on the server; do not require a local CLI or send REST requests with the MCP OAuth token. Select the user's organization and pass `organization_id` consistently. ## Establish the behavior and dependencies Translate the user's request into instructions, permitted actions, expected outputs, and conditions that require human input. Resolve only missing details that materially affect behavior. For an existing agent, read its current definition and manager context before editing; preserve unrelated configuration. Inspect available harnesses, capabilities, models, skills, and MCP catalog entries through resources or discovered list/get commands. A harness supplies the base environment; an agent overlays behavior and configuration. Reuse a suitable harness and add capabilities only for required actions. Conversation is plain chat with no files; an agent that researches, keeps notes, runs on a schedule, or holds one long session belongs on Worker, which already includes files, saved tool output, compaction and web search. Do not re-add a capability …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_pic4zdkesvbdkbmc/bbaa56fac16a81184d6383d97e34e68b795714c35671cfd4ee374a6d1aa8b98b.json
Then /plugin install everruns-agent-authoring@markdownregistry-pic4zdkesvbdkbmc in Claude Code. It installs v1.0, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add everruns/everruns/everruns-agent-authoring@sha256:bbaa56fac16a8118The line at the top of this page pins the label v1.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.
[](https://markdownregistry.com/a/art_pic4zdkesvbdkbmc)
1 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in everruns/everruns/everruns-agent-authoring 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-agent-authoring from somewhere else? Ask it: where did my everruns-agent-authoring 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 4 versions of this file, between Oct 12, 2026 and Nov 8, 2026, about one every 9 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0 latest | 2026-11-08 | ad7b3dc | 5,840 B | A | view · diff |
| v1.0 | 2026-11-08 | 2d59f76 | 4,795 B | A | view · diff |
| v1.0 | 2026-10-12 | 386d3ce | 4,405 B | A | view · diff |
| v1.0 | 2026-10-12 | 35aa5eb | 4,405 B | A | view |
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.
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.
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.
Installed this file, say at .claude/skills/everruns-agent-authoring/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
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
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (5840 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
everruns/everruns · 67 stars · license MIT · pushed 2026-11-16 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_pic4zdkesvbdkbmc GET https://markdownregistry.com/api/v1/resolve?ref=everruns/everruns/everruns-agent-authoring GET https://markdownregistry.com/api/v1/blob/bbaa56fac16a81184d6383d97e34e68b795714c35671cfd4ee374a6d1aa8b98b
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.