EverOS Tools

Official EverOS developer tools for AI coding assistants.

Available Plugins

everos-sdk-upgrade

Migrate an EverOS Cloud integration between API/SDK versions.

• Python SDK (everos-cloud / evermemos) — full rule coverage
• Raw HTTP callers in any language — endpoint, payload and response rules
• Detects the current version and chains rules to the target
• Flags capabilities that have no equivalent in the target version instead of silently dropping or approximating them
• --scan mode produces an impact report without editing anything

Install and run

The tool needs a git repository: it refuses to edit a tree it cannot restore. Start with --scan in every case; it reads your code and prints a report without changing anything.

Claude Code

Inside a Claude Code session:

/plugin marketplace add EverMind-AI/everos-tools      # one-time
/plugin install everos-sdk-upgrade@everos-tools

/everos-sdk-upgrade --scan     # report only, nothing edited
/everos-sdk-upgrade            # migrate; stops to ask if anything has no v2 equivalent
/everos-sdk-upgrade --yes      # migrate and proceed with those call sites flagged (CI, or a second run)

/plugin marketplace update     # pick up new rules later

The same two install steps from a terminal, if you prefer:

claude plugin marketplace add EverMind-AI/everos-tools
claude plugin install everos-sdk-upgrade@everos-tools

Codex, Cursor, and other tools that follow the Agent Skills standard

This skill follows the Agent Skills open standard. From your project directory:

npx skills add https://github.com/EverMind-AI/everos-tools

This places the skill at .agents/skills/everos-sdk-upgrade/ and writes skills-lock.json; Codex and Cursor read that directory directly, and a symlink is added for any other detected tool. Commit both, or add them to .gitignore, as you prefer.

Then ask your assistant, in its own chat:

Run the everos-sdk-upgrade skill in --scan mode on this repository.

and later, to migrate, the same sentence without --scan (add “proceed with every blocker flagged” for the --yes behaviour).

What has been verified where

The tool names in SKILL.md (Grep, Glob, Read) are Claude Code’s; Codex and Cursor mapped them to their own tools without help.

What the report looks like

The first lines of a real --scan on a small v1 script:

VERDICT