Update to Runzumi

Snapshot Nov 4, 2026 · 00:11 UTC · version 0.1.10

Collection source: downloaded plugin package.

WHAT CHANGED

Payment or plan references changed

Skill instructions — Now says: For a new user, offer [Create your Runzumi account](https://app.runzumi.com/api/auth/sign-in?screen=sign-up&returnPathname=%2Fonboarding) before trying...

Observed in published text. Live prices and checkout terms have not been verified by this change.

Save Runzumi and check future changes in Following.

Up to 10 plugins free · no card required.

All fields and original values.

Skill instructions

Before

Oct 24, 2026 · 13:52 UTC

If the tools are not available or the sign-in expired, use the reconnect flow of the host. Do not ask the user for passwords or tokens. If the connection fails, tell the user why and give the link https://runzumi.com. 1. Use `list_worksp...

After

Nov 4, 2026 · 00:11 UTC

For a new user, offer [Create your Runzumi account](https://app.runzumi.com/api/auth/sign-in?screen=sign-up&returnPathname=%2Fonboarding) before trying tools. If tools are unavailable or sign-in expired, use the host's connection or reco...

Compare saved observations

Download comparison JSON

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -3,12 +3,14 @@
 description: Use when the user wants to connect Runzumi or open their GitHub Actions runner performance, compute usage and failed jobs.
 ---
 
-Use the Runzumi MCP connection in `agents/openai.yaml`. If the tools are not available or the sign-in expired, use the reconnect flow of the host. Do not ask the user for passwords or tokens. If the connection fails, tell the user why and give the link https://runzumi.com.
+Use the Runzumi MCP connection in `agents/openai.yaml`. For a new user, offer [Create your Runzumi account](https://app.runzumi.com/api/auth/sign-in?screen=sign-up&returnPathname=%2Fonboarding) before trying tools. If tools are unavailable or sign-in expired, use the host's connection or reconnect flow. Do not ask for passwords or tokens.
 
-1. Use `list_workspaces` to get the workspaces of the user. If the workspace is not on the first page, follow the cursor.
-2. If there is no workspace, tell the user to set up the account and GitHub on the Runzumi website. Use the link that the tools return.
+Use the environment-specific links returned by tools or server instructions whenever available. Only use the public `https://app.runzumi.com` links here when no connection environment is known.
+
+1. Use `list_workspaces` to find an accessible workspace. Follow the cursor until `isDone` is true; an empty intermediate page does not mean there are no workspaces.
+2. For missing workspace consent or no accessible workspaces, offer Create account for new users and [Finish setup](https://app.runzumi.com/onboarding) for existing users. On the website, create or join a workspace and connect GitHub. If the workspace needs billing, someone with billing access can [Set up billing](https://app.runzumi.com/billing). Then reconnect the Runzumi MCP connection in the host to grant workspace access and retry `list_workspaces`. Missing permission alone does not mean payment is required; use the account with workspace access or ask its owner for access.
 3. Use `open_dashboard` with the workspace. You can also give a repository or a job.
 
-Hosts without a panel can use the same tools and the Runzumi link. For setup, billing, repository settings and CI operations, send the user to the Runzumi website.
+Hosts without a panel use the same website links and reconnect sequence. Keep account creation, billing changes, repository settings and CI operations on the Runzumi website.
 
 For slow CI, use the [CI slowness guide](../explain-ci-slowness/SKILL.md). For usage and cost, use the [compute cost guide](../explain-compute-costs/SKILL.md). For a failed job, use the [failure investigation guide](../investigate-failure/SKILL.md).

Full technical diff · 1 changed fields

changed `/skill_md_contents`

BEFORE

"---\nname: connect-runzumi\ndescription: Use when the user wants to connect Runzumi or open their GitHub Actions runner performance, compute usage and failed jobs.\n---\n\nUse the Runzumi MCP connection in `agents/openai.yaml`. If the tools are not available or the sign-in expired, use the reconnect flow of the host. Do not ask the user for passwords or tokens. If the connection fails, tell the user why and give the link https://runzumi.com.\n\n1. Use `list_workspaces` to get the workspaces of the user. If the workspace is not on the first page, follow the cursor.\n2. If there is no workspace, tell the user to set up the account and GitHub on the Runzumi website. Use the link that the tools return.\n3. Use `open_dashboard` with the workspace. You can also give a repository or a job.\n\nHosts without a panel can use the same tools and the Runzumi link. For setup, billing, repository settings and CI operations, send the user to the Runzumi website.\n\nFor slow CI, use the [CI slowness guide](../explain-ci-slowness/SKILL.md). For usage and cost, use the [compute cost guide](../explain-compute-costs/SKILL.md). For a failed job, use the [failure investigation guide](../investigate-failure/SKILL.md).\n"

AFTER

"---\nname: connect-runzumi\ndescription: Use when the user wants to connect Runzumi or open their GitHub Actions runner performance, compute usage and failed jobs.\n---\n\nUse the Runzumi MCP connection in `agents/openai.yaml`. For a new user, offer [Create your Runzumi account](https://app.runzumi.com/api/auth/sign-in?screen=sign-up&returnPathname=%2Fonboarding) before trying tools. If tools are unavailable or sign-in expired, use the host's connection or reconnect flow. Do not ask for passwords or tokens.\n\nUse the environment-specific links returned by tools or server instructions whenever available. Only use the public `https://app.runzumi.com` links here when no connection environment is known.\n\n1. Use `list_workspaces` to find an accessible workspace. Follow the cursor until `isDone` is true; an empty intermediate page does not mean there are no workspaces.\n2. For missing workspace consent or no accessible workspaces, offer Create account for new users and [Finish setup](https://app.runzumi.com/onboarding) for existing users. On the website, create or join a workspace and connect GitHub. If the workspace needs billing, someone with billing access can [Set up billing](https://app.runzumi.com/billing). Then reconnect the Runzumi MCP connection in the host to grant workspace access and retry `list_workspaces`. Missing permission alone does not mean payment is required; use the account with workspace access or ask its owner for access.\n3. Use `open_dashboard` with the workspace. You can also give a repository or a job.\n\nHosts without a panel use the same website links and reconnect sequence. Keep account creation, billing changes, repository settings and CI operations on the Runzumi website.\n\nFor slow CI, use the [CI slowness guide](../explain-ci-slowness/SKILL.md). For usage and cost, use the [compute cost guide](../explain-compute-costs/SKILL.md). For a failed job, use the [failure investigation guide](../investigate-failure/SKILL.md).\n"

Full snapshot data

{
  "description": "Use when the user wants to connect Runzumi or open their GitHub Actions runner performance, compute usage and failed jobs.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 569
    },
    {
      "relative_path": "assets/icon.svg",
      "size_in_bytes": 1053
    }
  ],
  "name": "connect-runzumi",
  "skill_md_contents": "---\nname: connect-runzumi\ndescription: Use when the user wants to connect Runzumi or open their GitHub Actions runner performance, compute usage and failed jobs.\n---\n\nUse the Runzumi MCP connection in `agents/openai.yaml`. For a new user, offer [Create your Runzumi account](https://app.runzumi.com/api/auth/sign-in?screen=sign-up&returnPathname=%2Fonboarding) before trying tools. If tools are unavailable or sign-in expired, use the host's connection or reconnect flow. Do not ask for passwords or tokens.\n\nUse the environment-specific links returned by tools or server instructions whenever available. Only use the public `https://app.runzumi.com` links here when no connection environment is known.\n\n1. Use `list_workspaces` to find an accessible workspace. Follow the cursor until `isDone` is true; an empty intermediate page does not mean there are no workspaces.\n2. For missing workspace consent or no accessible workspaces, offer Create account for new users and [Finish setup](https://app.runzumi.com/onboarding) for existing users. On the website, create or join a workspace and connect GitHub. If the workspace needs billing, someone with billing access can [Set up billing](https://app.runzumi.com/billing). Then reconnect the Runzumi MCP connection in the host to grant workspace access and retry `list_workspaces`. Missing permission alone does not mean payment is required; use the account with workspace access or ask its owner for access.\n3. Use `open_dashboard` with the workspace. You can also give a repository or a job.\n\nHosts without a panel use the same website links and reconnect sequence. Keep account creation, billing changes, repository settings and CI operations on the Runzumi website.\n\nFor slow CI, use the [CI slowness guide](../explain-ci-slowness/SKILL.md). For usage and cost, use the [compute cost guide](../explain-compute-costs/SKILL.md). For a failed job, use the [failure investigation guide](../investigate-failure/SKILL.md).\n"
}

SHA-256 of public snapshot: 6b3c8ba170aaab45511153a3875d48f3b51640ee7e87a52281e39e976483ed83