Agent skill

Rudder Real Runtime Verifier Maintainer

by Undertone0809 in Undertone0809/rudder

A skill your agent uses when verifying Rudder agent runtime behavior in a real local environment, especially MCP/native Rudder tools across Codex, Claude, OpenCode, Pi, or user-named runtimes.

Apache-2.0Auto-check passedDevelopment

Install Rudder Real Runtime Verifier Maintainer

skills CLI
$ npx skills add Undertone0809/rudder --skill rudder-real-runtime-verifier-maintainer -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Undertone0809/rudder rudder-real-runtime-verifier-maintainer --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Undertone0809/rudder.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/maintainer/rudder-real-runtime-verifier-maintainer .claude/skills/rudder-real-runtime-verifier-maintainer && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
rudder-real-runtime-verifier-maintainer
GitHub stars
292
Token cost
~1.8k tokens
SKILL.md length
911 words
Files
8 (incl. references)
Skills in repo
30
Repo updated
First seen
Licence
Apache-2.0

At a glance

A skill your agent uses when verifying Rudder agent runtime behavior in a real local environment, especially MCP/native Rudder tools across Codex, Claude, OpenCode, Pi, or user-named runtimes.

  • Works in 7 steps: The local Rudder source of truth is… → A real local run was triggered for that… → The transcript shows the expected Rudder… → …
  • Verifying Rudder agent runtime behavior in a real local environment
  • SKILL.md covers Role Boundary, When This Skill Wins, Runtime Matrix and Acceptance Standard, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Rudder Real Runtime Verifier Maintainer is an agent skill from Undertone0809/rudder. Use when verifying Rudder agent runtime behavior in a real local environment, especially MCP/native Rudder tools across Codex, Claude, OpenCode, Pi, or user-named runtimes. Trigger for requests like 真是/真实环境跑过吗, 排查所有 rudder tools, transcript/fallback verification, runtime MCP availability, provider matrix proof, or checking whether agents used Rudder tools instead of rudder CLI/Bash/curl fallback.

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including reference files (for example `references/claude.md`, `references/codex.md` and `references/opencode.md`).

It sits in Development. It works with Model Context Protocol and Bash. The repository describes itself as: Open-source local Agent harness for self-improving agent teams: run agents, review work, and turn feedback into reusable skills. The licence is Apache-2.0.

When your agent uses it

  • Verifying Rudder agent runtime behavior in a real local environment
  • Especially MCP/native Rudder tools across Codex
  • User-named runtimes
  • Requests like 真是/真实环境跑过吗

Example prompts

  • “/rudder-real-runtime-verifier-maintainer”

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. The local Rudder source of truth is identified, usually
  2. A real local run was triggered for that runtime, or an existing real local
  3. The transcript shows the expected Rudder MCP/native tool calls.
  4. There is no model-visible fallback to shell, Bash, curl, or rudder CLI for
  5. Tool results are not internally failed (isError, structured error,
  6. The terminal product effect was read back: issue status, comments, run
  7. Provider/model blockers are separated from Rudder adapter/tool blockers.

What it can do on your machine

Read from SKILL.md and the folder at commit 2676a5c. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Rudder Real Runtime Verifier Maintainer loads about 1.8k tokens when it runs, and up to ~5.2k if it reads all its reference files. Until then it costs about 110 tokens; SKILL.md has 911 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~110
When it runs · the whole SKILL.md, loaded when a task matches
~1.8k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~5.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Undertone0809/rudder at commit 2676a5c, republished under its Apache-2.0 licence (© Undertone0809). 911 words, ~1,793 tokens.

Download SKILL.mdSave it as .claude/skills/rudder-real-runtime-verifier-maintainer/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.
name
rudder-real-runtime-verifier-maintainer
description
Use when verifying Rudder agent runtime behavior in a real local environment, especially MCP/native Rudder tools across Codex, Claude, OpenCode, Pi, or user-named runtimes. Trigger for requests like 真是/真实环境跑过吗, 排查所有 rudder tools, transcript/fallback verification, runtime MCP availability, provider matrix proof, or checking whether agents used Rudder tools instead of rudder CLI/Bash/curl fallback.

Rudder Real Runtime Verifier Maintainer

Verify Rudder agent runtime behavior on the user's real local Rudder instance. This is a black-box runtime acceptance workflow, not an implementation or code review workflow.

Default to Chinese when the user asks in Chinese. Put the current truth first: which runtimes passed, failed, or were blocked, and what transcript evidence proves it.

Role Boundary

Default to verification and diagnosis only:

  • Run real local runtime probes and inspect run transcripts, logs, API state, issue state, comments, and run metadata.
  • Create disposable orgs, agents, issues, and runs when needed for proof.
  • Separate provider/model failure from Rudder adapter failure.
  • Report exact blockers and smallest likely fixes.
  • As an independent verifier, do not edit source, configs, Git state, or product docs. Return findings to the implementer. The parent retains any existing fix authority; verification does not require that authority to be repeated.

If the user asks to fix the issue, hand back to the lifecycle implementation route or make the smallest explicit patch, then require this skill's real runtime proof again before claiming done.

When This Skill Wins

Use this skill when the core question is whether an agent runtime actually did the work through Rudder-managed tools in a real local run.

Typical prompts:

  • "你所有的 agent runtime 都本地测过跑过真实环境了吗?"
  • "OpenCode and Pi agent 你也测了吗?"
  • "看 transcript,别让它 fallback 用 rudder cli"
  • "排查所有 rudder tools,都试一遍"
  • "MCP tool 报 org id/auth 问题,正常 agent 调 tool 不该传 org"
  • "Codex/Claude/OpenCode/Pi 真实环境跑一下"

If the user asks for general product acceptance that is not runtime/tool-call specific, use product-acceptance-verifier-maintainer instead. If the user provides only one failed run id and wants root cause, use debug-run-transcript-maintainer first, then return here for rerun proof after a fix.

Runtime Matrix

Select the runtime matrix from the user's request and the changed integration. Test one runtime for a runtime-specific claim. Use the full supported matrix for an explicit all-runtime claim or a shared adapter/tool change that affects it:

  • Codex
  • Claude Code
  • Hermes
  • OpenCode
  • Pi
  • Cursor

Do not treat a Codex pass as proof for another runtime.

Read only the relevant reference files:

  • references/probe-workflow.md: real local setup, disposable data, probe script expectations, and proof levels.
  • references/transcript-evidence.md: how to prove tool use and reject CLI fallback from logs.
  • references/codex.md: Codex MCP transcript shape and known traps.
  • references/claude.md: Claude MCP transcript shape and strict config traps.
  • references/opencode.md: OpenCode MCP transcript shape, provider/model caveats, JSONL parser expectations, and final-text pitfalls.
  • references/pi.md: Pi native extension transcript shape, schema/error propagation traps, and 429/auth/provider separation.
  • references/reporting.md: verdict format, mutation ledger, and pass/fail language.

Acceptance Standard

A runtime passes only when all are true:

  1. The local Rudder source of truth is identified, usually GET /api/health on http://127.0.0.1:3100.
  2. A real local run was triggered for that runtime, or an existing real local run was inspected with enough raw transcript/log evidence.
  3. The transcript shows the expected Rudder MCP/native tool calls.
  4. There is no model-visible fallback to shell, Bash, curl, or rudder CLI for Rudder work.
  5. Tool results are not internally failed (isError, structured error, rudder_cli_command_failed, missing required argument, auth/org failure).
  6. The terminal product effect was read back: issue status, comments, run status, final text, API result, or another requested surface.
  7. Provider/model blockers are separated from Rudder adapter/tool blockers.

If the user requires "all tools", do not only run a happy-path issue workflow. Run or request a manifest-driven coverage plan: list every exposed tool, verify schemas load, check runtime-managed identity is not model-provided, and execute representative read/mutate/file/image/pagination/error cases. Mark unexecuted tools as not covered.

Show full SKILL.md (332 more words)Show less

Default Probe Ladder

Use the smallest probe that answers the question, then escalate only as needed:

  1. Tool availability probe: call rudder_agent_me, require final answer to say MCP/tool path and no fallback.
  2. Issue workflow probe: seed an issue, then require rudder_issue_context, rudder_issue_checkout, rudder_issue_comment, and rudder_issue_done; read back final issue status and comments.
  3. Representative matrix probe: add read/list/pagination/file/comment/image examples such as rudder_runs_errors, rudder_library_file_ref, inbox/context, review, chat, or automation.
  4. Full manifest audit: prove every exposed Rudder tool has a stable name, schema, description, and handler classification; execute safe read-only tools and representative mutating tools in disposable data.

Known Judgment Rules

  • A successful final answer is not enough. Inspect raw or parsed transcript.
  • A tool call name in prompt text is not evidence. Use structured tool-call events or parsed run-intelligence entries.
  • A run can fail after completing the product effect. Report that separately: tool/product effect passed; runtime finalization failed.
  • A provider 429/auth/model error before any tool call is not an MCP auth/org bug. Mark it blocked_provider.
  • If a tool result contains isError: true but the runtime marks the tool call completed, treat the runtime as failed or at least suspect until fixed.
  • Internal runtime-owned bridges may execute a server process. That is acceptable only if the model-visible action is a typed Rudder tool and runtime env owns identity. It is not acceptable if the model uses Bash/curl or runs rudder ... itself for Rudder work.

Output

Use references/reporting.md for the full shape. At minimum include:

  • overall verdict: PASS, FAIL, or QUESTION for the requested matrix; observed required behavior failure yields FAIL; otherwise missing required proof or provider access yields QUESTION; complete required proof yields PASS
  • verdict per runtime: PASS, FAIL, BLOCKED_PROVIDER, PARTIAL, or NOT_RUN
  • run IDs, issue IDs, org IDs when disposable data was created
  • observed tool names
  • whether CLI/Bash/curl fallback was observed
  • internal tool errors
  • terminal product effect
  • skipped coverage and why
  • mutation ledger

Do not say "all green" if any runtime is blocked, substituted, partial, or only covered by simple agent_me.

© Undertone0809, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 7 other files (references) in .agents/skills/maintainer/rudder-real-runtime-verifier-maintainer of Undertone0809/rudder.

  • SKILL.md
  • references/claude.md
  • references/codex.md
  • references/opencode.md
  • references/pi.md
  • references/probe-workflow.md
  • references/reporting.md
  • references/transcript-evidence.md

Open the folder on GitHubat commit 2676a5c

Compare with similar skills

Rudder Real Runtime Verifier Maintainer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Rudder Real Runtime Verifier Maintainer compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Rudder Real Runtime Verifier Maintainer this skillUndertone0809/rudder292—~1.8kAutomated safety check: PassApache-2.0
Ue Code AuthoringJasonMa0012/MooaToon750—~1.9kAutomated safety check: NotesCustom licence
Ue Live DebuggingJasonMa0012/MooaToon750—~2.9kAutomated safety check: NotesCustom licence
Restricted Tool Triagegithub/gh-aw5.4k—~1.2kAutomated safety check: PassMIT
Adr Indexruvnet/ruflo74k—~861Automated safety check: NotesMIT
Tapd Iteration InitTencentBlueKing/bk-bcs840—~1.3kAutomated safety check: PassCustom licence

Similar skills

  • Ue Code Authoring

    JasonMa0012/MooaToon

    A skill your agent uses when writing or modifying UE C++ (classes, actors, components, subsystems, interfaces, function libraries) with Rider MCP available.

    750 GitHub stars~1.9k tokensUpdated 22 days ago
    DevelopmentAuto-check: notes
  • Ue Live Debugging

    JasonMa0012/MooaToon

    A skill your agent uses when debugging UE C++ crashes, runtime bugs, or unexpected behavior with Rider MCP available.

    750 GitHub stars~2.9k tokensUpdated 22 days ago
    DevelopmentAuto-check: notes
  • Official

    Operate safely and efficiently inside a gh-aw workflow with a restricted tools/bash allowlist, and correctly triage tool-denial events before they exhaust the session's denial budget.

    5.4k GitHub stars~1.2k tokensUpdated today
    DevelopmentAuto-check passed
  • Adr Index

    ruvnet/ruflo

    Build or rebuild the ADR index + dependency graph by running scripts/import.mjs (handles v3-style and plugin-style ADR formats; one Bash call vs hundreds of MCP round-trips)

    74k GitHub stars~861 tokensUpdated today
    DevelopmentAuto-check: notes
  • Tapd Iteration Init

    TencentBlueKing/bk-bcs

    迭代执行流水线启动器。分三个阶段执行:信息检查(验证 git 环境、获取迭代信息、 解析迭代分支)→ 恢复检测(已有状态文件时判定恢复策略)→ 新流程初始化(创建分支、 迭代目录和 iteration-state.json)。

    840 GitHub stars~1.3k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Openspec Aware

    Chorus-AIDLC/Chorus

    OpenSpec-mode authoring for Chorus PM workflows on OpenClaw — the default whenever OpenSpec is usable.

    1.2k GitHub stars~7.6k tokensUpdated today
    DevelopmentAuto-check passed

More from Undertone0809/rudder

All 30 skills in this repo
  • Conversation To Skill

    Undertone0809/rudder

    Turn the current conversation's workflow into a reusable agent skill.

    292 GitHub stars~3.6k tokensUpdated today
    Auto-check passed
  • A skill your agent uses when starting the current Rudder checkout as a temporary managed local preview with a stable URL, readiness check, logs, stop command, and cleanup path for manual inspection…

    292 GitHub stars~2.1k tokensUpdated today
    Auto-check passed
  • Stop Rudder Dev Maintainer

    Undertone0809/rudder

    A skill your agent uses when the user explicitly asks to stop, restart, kill, or clean Rudder repo-local pnpm dev processes or local dev runtime residue, including “把 pnpm dev 停了”, “重启 dev”, or “清掉…

    292 GitHub stars~1.3k tokensUpdated today
    Auto-check passed
  • Deep Research

    Undertone0809/rudder

    Conducts enterprise-grade research with multi-source synthesis, citation tracking, and verification.

    292 GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • A skill your agent uses to audit or clean Rudder worktrees, generated artifacts, logs, caches, and repo-owned processes without deleting active work, user data, or unrelated machine state.

    292 GitHub stars~664 tokensUpdated today
    Auto-check passed
  • Visualize

    Undertone0809/rudder

    Create safe inline visual explanations in Rudder Chat. An agent skill from Undertone0809/rudder.

    292 GitHub stars~1.8k tokensUpdated today
    Auto-check passed

Categories

Questions about Rudder Real Runtime Verifier Maintainer

What does Rudder Real Runtime Verifier Maintainer do?

A skill your agent uses when verifying Rudder agent runtime behavior in a real local environment, especially MCP/native Rudder tools across Codex, Claude, OpenCode, Pi, or user-named runtimes. Rudder Real Runtime Verifier Maintainer is an agent skill from Undertone0809/rudder. Use when verifying Rudder agent runtime behavior in a real local environment, especially MCP/native Rudder tools across Codex, Claude, OpenCode, Pi, or user-named runtimes.

When should I use Rudder Real Runtime Verifier Maintainer?

Rudder Real Runtime Verifier Maintainer fits situations like: verifying Rudder agent runtime behavior in a real local environment; especially MCP/native Rudder tools across Codex; user-named runtimes; requests like 真是/真实环境跑过吗.

How do I install Rudder Real Runtime Verifier Maintainer in Claude Code?

Run `npx skills add Undertone0809/rudder --skill rudder-real-runtime-verifier-maintainer -a claude-code`. Or copy the skill folder (.agents/skills/maintainer/rudder-real-runtime-verifier-maintainer in Undertone0809/rudder) into .claude/skills/rudder-real-runtime-verifier-maintainer in your project. Claude Code loads it when a task matches its description.

How do I install Rudder Real Runtime Verifier Maintainer in Codex?

Run `npx skills add Undertone0809/rudder --skill rudder-real-runtime-verifier-maintainer -a codex`. Or copy the skill folder (.agents/skills/maintainer/rudder-real-runtime-verifier-maintainer in Undertone0809/rudder) into .agents/skills/rudder-real-runtime-verifier-maintainer in your project. Codex loads it when a task matches its description.

Can I use Rudder Real Runtime Verifier Maintainer in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Undertone0809/rudder --skill rudder-real-runtime-verifier-maintainer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/rudder-real-runtime-verifier-maintainer, .gemini/skills/rudder-real-runtime-verifier-maintainer, .github/skills/rudder-real-runtime-verifier-maintainer and .opencode/skills/rudder-real-runtime-verifier-maintainer in your project.

What does Rudder Real Runtime Verifier Maintainer need to run?

SKILL.md names no scripts, command-line tools or credentials: Rudder Real Runtime Verifier Maintainer is instructions for the agent only.

Does Rudder Real Runtime Verifier Maintainer access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Rudder Real Runtime Verifier Maintainer safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Rudder Real Runtime Verifier Maintainer use?

Rudder Real Runtime Verifier Maintainer is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Rudder Real Runtime Verifier Maintainer use?

About 1.8k tokens (SKILL.md is roughly 7.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.4k tokens, read only when the agent opens those files.

What are the alternatives to Rudder Real Runtime Verifier Maintainer?

Skills that share tags, products or a category with Rudder Real Runtime Verifier Maintainer: Ue Code Authoring (JasonMa0012/MooaToon, 750 stars), Ue Live Debugging (JasonMa0012/MooaToon, 750 stars), Restricted Tool Triage (github/gh-aw, 5.4k stars) and Adr Index (ruvnet/ruflo, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Rudder Real Runtime Verifier Maintainer?

Undertone0809 (a GitHub user) maintains it in Undertone0809/rudder, which has 292 GitHub stars. The repository holds 30 skills in this directory. The repository was last updated on October 10, 2026.

Source: Undertone0809/rudder on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.