agentleFS
htlin222htlin222/openevidence-mcp/.claude/skills/install/SKILL.md

install

Skill83 starsChanged 3 days agoApache-2.0View on GitHub

Install, update, clean up, uninstall, or check the status of openevidence-mcp on this machine. Use when the user wants to set up openevidence-mcp, update to the latest release, register/unregister the MCP server with Claude/Codex, reap stray relay daemons, or verify the install. Trigger phrases include "install openevidence-mcp", "update openevidence-mcp", "uninstall openevidence-mcp", "openevidence-mcp 更新 / 安裝 / 移除 / 清理", "reap relay daemon", "is openevidence-mcp registered".

23 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use update and release.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • AnthropicSkill

    update

    Sync tasks and refresh memory from your current activity. Use when pulling new assignments from your project tracker into TASKS.md, triaging stale or overdue tasks, filling memory gaps for unknown people or projects, or running a comprehensive scan to catch todos buried in chat and email.

    Also in 3 projects that use this

  • MicrosoftSkill

    release

    Use ONLY when the user explicitly asks to cut/publish a Huabu desktop release or tag a version. Performs an outward action — bumps the version in apps/desktop/package.json, commits + annotated-tags vX.Y.Z, and pushes the branch + tag. That tag push auto-builds the macOS/Windows installers and publishes a GitHub Release. Provides `status`, `bump`, `tag-push`, and a one-command `run` (bump → tag-push).

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 0 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 19 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run the subcommand that matches the user's intent, then read the printed guidance back to them — especially the reload the browser …

    line 16
  2. Very specific:

    If $CLAUDE_SKILL_DIR is not set, use the repo path directly: .claude/skills/install/scripts/oe-mcp.sh <command>.

    line 37
  3. Very specific:

    Only the full-wipe commands printed by uninstall are destructive — get explicit confirmation before running those.

    line 80

“Common” is measured: kept by at least 6 in 10 of the 19 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

openevidence-mcp — install / update / cleanup / uninstall

One skill to set up, update, and tear down openevidence-mcp on this machine. Everything here wraps the repo Makefile, so it stays in sync with the canonical install flow — the skill never reimplements it.

The single entry point is scripts/oe-mcp.sh (a thin dispatcher over make). Run the subcommand that matches the user's intent, then read the printed guidance back to them — especially the reload the browser extension step, which is a chrome:// GUI action that cannot be scripted.

Pick the action

User wants…Run
First-time setupscripts/oe-mcp.sh install
Update to the latest releasescripts/oe-mcp.sh update
Check it's workingscripts/oe-mcp.sh status
Relay should survive reboots / "start at boot" (macOS)scripts/oe-mcp.sh autostart
Reap stray daemons / free stale statescripts/oe-mcp.sh cleanup
Remove itscripts/oe-mcp.sh uninstall

Invoke the script by its path from the skill directory, e.g.:

bash "$CLAUDE_SKILL_DIR/scripts/oe-mcp.sh" update

If $CLAUDE_SKILL_DIR is not set, use the repo path directly: .claude/skills/install/scripts/oe-mcp.sh <command>.

What each action does (all via make)

  • install — make all: installs deps, builds the MCP server (dist/server.js) and the relay extension (extension/dist), and registers the server into Claude and Codex (whichever CLI is present). If run outside a checkout, it clones the repo to $HOME/openevidence-mcp first (override with OE_MCP_DIR).
  • update — make update: git pull the latest release, rebuild server + extension, re-register. Prints the extension-reload reminder.
  • status — make status: server + extension versions, live relay /health, and whether the CLIs have it registered.
  • autostart — make autostart: installs a launchd LaunchAgent so the relay daemon starts at login, restarts on crash and never idle-reaps. Undo with make autostart-remove. The browser (extension + logged-in tab) must still be running — suggest adding it to macOS Login Items.
  • cleanup — make cleanup: reaps orphan relay daemons (keeps the live one), prunes oversized relay logs and temp answer artifacts. Non-destructive — your install, registration, and ~/.openevidence-mcp data are untouched. The relay auto-respawns on the next MCP call.
  • uninstall — make uninstall: unregisters from the AI CLIs, stops daemons, removes dist/. Deliberately keeps ~/.openevidence-mcp (your SQLite db + config) and the loaded browser extension — the skill should tell the user the two manual commands to fully wipe those, and only run them if explicitly asked.

The one manual step (install & update)

Loading/reloading the browser extension is a chrome://extensions GUI action — you cannot do it for the user. After install/update, tell them exactly:

  1. Open chrome://extensions (Chrome / Edge / Brave / Arc / Vivaldi / Opera).
  2. Turn on Developer mode. First time: Load unpacked → select <repo>/extension/dist. After an update: click Reload on "OpenEvidence MCP Relay".
  3. Stay logged in to openevidence.com in that browser.
  4. Reconnect /mcp in the AI client.

Then verify: curl -s http://127.0.0.1:8787/health → expect "connected":true.

Notes

  • These are host-level, reversible operations; run the matching command directly. Only the full-wipe commands printed by uninstall are destructive — get explicit confirmation before running those.
  • The skill is host-specific: it acts on the machine it runs on. Nothing here touches the user's OpenEvidence account or data on the server side.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.