New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Workflow Runtime Abi

by Consensys in Consensys/c0

Guidance for safely changing the c0 Workflow runtime ABI, manifest ABI, runtime kernels, manifest migrations, workflow artifact compatibility, and audit/backfill tooling.

LGPL-3.0Auto-check passed

Install Workflow Runtime Abi

skills CLI
$ npx skills add Consensys/c0 --skill workflow-runtime-abi -a claude-code

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

GitHub CLI
$ gh skill install Consensys/c0 workflow-runtime-abi --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/Consensys/c0.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/workflow-runtime-abi .claude/skills/workflow-runtime-abi && 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
workflow-runtime-abi
GitHub stars
105
Token cost
~1.8k tokens
SKILL.md length
884 words
Files
3 (incl. references)
Skills in repo
11
Repo updated
First seen
Licence
LGPL-3.0

At a glance

Guidance for safely changing the c0 Workflow runtime ABI, manifest ABI, runtime kernels, manifest migrations, workflow artifact compatibility, and audit/backfill tooling.

  • Works in 8 steps: Read the current ABI files and tests… → Identify the precise contract delta:… → Add the next version beside the old one.… → …
  • Modifying workflow runtime contracts
  • SKILL.md covers Core Model, Early Trigger Check, Version Decision and Implementation Flow, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Workflow Runtime Abi is an agent skill from Consensys/c0. Guidance for safely changing the c0 Workflow runtime ABI, manifest ABI, runtime kernels, manifest migrations, workflow artifact compatibility, and audit/backfill tooling. Use when modifying workflow runtime contracts, compiled workflow imports, kernel modules, manifest versions, node handle semantics, template context such as nodes. or trigger., workflow artifact loading, in-flight workflow run resume behavior, or any workflow node catalog/default/validation/adapter change where persisted node options, ports…

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `agents/openai.yaml` and `references/upgrade-checklist.md`).

The repository describes itself as: c0 is an open-source AI platform built for organizational work, tools, and context. A single deployment to Cloudflare to get started. The licence is LGPL-3.0.

When your agent uses it

  • Modifying workflow runtime contracts
  • Compiled workflow imports
  • Manifest versions
  • Node handle semantics

Example prompts

  • “/workflow-runtime-abi”

Workflow steps

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

  1. Read the current ABI files and tests before editing.
  2. Identify the precise contract delta: source version, target version, migrated fields, runtime behavior, and incompatible old references.
  3. Add the next version beside the old one. Keep previous kernel source and manifest migrations immutable except for tests or comments that…
  4. Chain migrations one version at a time. Prefer v1 -> v2 -> v3 over a direct v1 -> v3 jump so each upgrade is auditable.
  5. Compile only new saves against the current ABI. Keep the loader able to serve every supported kernel module needed by old compiled…
  6. Keep run resume paths bound to workflow_runs.workflow_version; never silently switch a live run to the latest workflow version.
  7. Extend the dry-run audit/backfill path for the exact changed handles, templates, node types, or runtime contracts. Default to audit-only…
  8. Surface migration summaries through save/update responses and UI only when the change is user-visible.

What it can do on your machine

Read from SKILL.md and the folder at commit e7a1810. 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 (its code samples are bash).

    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

Workflow Runtime Abi loads about 1.8k tokens when it runs, and up to ~3.1k if it reads all its reference files. Until then it costs about 154 tokens; SKILL.md has 884 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~154
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
~3.1k

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 Consensys/c0 at commit e7a1810, republished under its LGPL-3.0 licence (© Consensys). 884 words, ~1,829 tokens.

Download SKILL.mdSave it as .claude/skills/workflow-runtime-abi/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
workflow-runtime-abi
description
Guidance for safely changing the c0 Workflow runtime ABI, manifest ABI, runtime kernels, manifest migrations, workflow artifact compatibility, and audit/backfill tooling. Use when modifying workflow runtime contracts, compiled workflow imports, kernel modules, manifest versions, node handle semantics, template context such as nodes.* or trigger.*, workflow artifact loading, in-flight workflow run resume behavior, or any workflow node catalog/default/validation/adapter change where persisted node options, ports, outputs, trigger payloads, or old workflow artifacts could execute differently.

Workflow Runtime ABI

Core Model

Treat the Workflow runtime ABI as a versioned contract between saved workflow artifacts, generated workflow code, manifest shape, node handles, template context, and runtime kernel behavior.

Preserve old contracts. Add new contracts. Migrate editable manifests explicitly on save or audit. Let in-flight runs continue on the workflow_runs.workflow_version and compiled artifact they started with.

For repository-specific file maps and checklists, read references/upgrade-checklist.md before editing.

Early Trigger Check

Use this skill alongside node-implementation guidance when changing workflow node catalog entries, defaults, option validation, inspector options, ports, outputs, or adapter behavior. Treat the change as ABI-relevant until proven otherwise if any of these are true:

  • the value is stored under WorkflowManifestNode.options
  • an existing manifest could already contain the field, handle, node type, or output name as inert or user-authored data
  • the runtime starts interpreting a previously ignored option or changes how an existing option is interpreted
  • compiled workflow code, action adapter inputs, run event redaction, or saved artifact loading needs an additional field
  • a workflow saved before the change would produce different action outputs, side effects, events, or stored artifacts after the change

Version Decision

Create a new runtime or manifest ABI version when a change affects any saved or compiled workflow artifact behavior:

  • generated workflow code imports or calls a runtime kernel differently
  • runtime kernel inputs, outputs, trigger payloads, redaction, action result normalization, branch gating, or CEL scope changes
  • manifest version, node option shape, default option meaning, edge handle names, node type names, port/output names, template expressions, or validation semantics change
  • adapter behavior begins honoring a persisted option, rejects a value that used to be accepted, or changes the side effect for an existing option value
  • old nodes.* or trigger.* templates need translation, warning, or rejection
  • old artifacts would execute differently if loaded with the new implementation

Do not create a new ABI version for internal refactors that preserve the behavior of every existing artifact and manifest contract.

Implementation Flow

  1. Read the current ABI files and tests before editing.
  2. Identify the precise contract delta: source version, target version, migrated fields, runtime behavior, and incompatible old references.
  3. Add the next version beside the old one. Keep previous kernel source and manifest migrations immutable except for tests or comments that do not change behavior.
  4. Chain migrations one version at a time. Prefer v1 -> v2 -> v3 over a direct v1 -> v3 jump so each upgrade is auditable.
  5. Compile only new saves against the current ABI. Keep the loader able to serve every supported kernel module needed by old compiled artifacts.
  6. Keep run resume paths bound to workflow_runs.workflow_version; never silently switch a live run to the latest workflow version.
  7. Extend the dry-run audit/backfill path for the exact changed handles, templates, node types, or runtime contracts. Default to audit-only; require an explicit write flag for mutation.
  8. Surface migration summaries through save/update responses and UI only when the change is user-visible.

Multiple Kernels

Support multiple kernels by registering each immutable kernel module and advancing CURRENT_WORKFLOW_RUNTIME_ABI_VERSION only for newly compiled workflow code.

The upgrade path between kernels is a manifest migration plus compiler/runtime registry change:

  • old compiled artifact imports workflow-runtime-kernel.vN.js
  • new compiled artifact imports workflow-runtime-kernel.vN+1.js
  • dynamic loader includes both modules
  • manifest migration rewrites old editable manifests into the new current manifest contract
  • in-flight runs continue resolving their original workflow artifact version

Do not make the current kernel emulate every old contract unless the old compiled artifacts actually import that kernel.

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

Migration Rules

Implement migrations as small, deterministic transforms. Each migration should:

  • accept exactly one source version and produce exactly the next version
  • document what changed in the step description
  • preserve user-authored data when possible
  • report ambiguous or unsafe changes through audit findings instead of guessing
  • normalize and validate the migrated manifest before saving
  • reject unsupported future versions

When renaming handles, node types, options, or template paths, update both the save migration and the audit scanner. The audit should identify the path and node where manual review is needed.

Test Requirements

Write focused tests around the changed contract, not broad snapshots.

At minimum, add or update tests that prove:

  • the registry exposes all supported kernels and selects the new current ABI
  • old kernel module names remain available for old compiled artifacts
  • a previous-version manifest migrates to the new manifest with only the intended deltas
  • current manifests remain unchanged when saved
  • unsupported future manifest versions fail clearly
  • audit catches old templates, renamed handles, or runtime contract references affected by the change
  • old workflow runs and approval/reconcile paths use run.workflow_version instead of latest workflow version

If runtime behavior changes, add paired kernel tests: one fixture for old behavior on the old kernel and one fixture for new behavior on the new kernel.

Validation

Run the smallest relevant set first, then broaden if shared behavior changed:

bash
nub exec vitest run tests/workflows/runtime-abi.test.ts tests/workflows/runtime-kernel.test.ts tests/workflows/runner.test.ts tests/workflows/lifecycle.test.ts
nub run workflow:runtime:audit <fixture-or-export.json>
nub run lint

If the change touches HTTP workflow APIs, UI save flows, or dynamic workflow loading, also run the matching integration or route tests.

Review Checklist

Before finishing, verify:

  • old workflow artifacts and kernel source strings are not rewritten in place
  • WORKFLOW_RUNTIME_ABI_VERSIONS includes every supported kernel
  • loader cache keys include all runtime kernel source fingerprints
  • save/update paths migrate manifests explicitly before writing new artifacts
  • artifact keys stay versioned and immutable
  • dry-run audit output is actionable and safe by default
  • tests describe the changed ABI contract in fixture names and assertions

© Consensys, LGPL-3.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 2 other files (references) in .agents/skills/workflow-runtime-abi of Consensys/c0.

  • SKILL.md
  • agents/openai.yaml
  • references/upgrade-checklist.md

Open the folder on GitHubat commit e7a1810

Compare with similar skills

Workflow Runtime Abi 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.

Workflow Runtime Abi compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Workflow Runtime Abi this skillConsensys/c0105—~1.8kAutomated safety check: PassLGPL-3.0
Make Changesremix-run/remix33k—~2.4kAutomated safety check: PassMIT
Safe PushJetBrains/intellij-community21k—~1.1kAutomated safety check: PassCustom licence
Orch Change Featureaffaan-m/ECC275k1 repos~420Automated safety check: PassMIT
Generate .NET Release changes.jsondotnet/core22k—~1.7kAutomated safety check: PassMIT
Change Managementsickn33/agentic-awesome-skills47k2 repos~3.5kAutomated safety check: PassMIT

Similar skills

  • Make Changes

    remix-run/remix

    Create or update Remix repo change files under packages//.changes.

    33k GitHub stars~2.4k tokensUpdated today
    DevelopmentAuto-check passed

  • Safe Push

    JetBrains/intellij-community

    Official

    Push IntelliJ repository changes through the Safe Push workflow.

    21k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Orch Change Feature

    affaan-m/ECC

    Orchestrate altering an existing, working feature to new desired behavior — update its tests to the new spec, change the implementation to match, review, and gated commit.

    275k GitHub starsUsed in 1 repo~420 tokens
    Auto-check passed

  • Generate .NET Release changes.json

    dotnet/core

    Official

    Produces the changes.json manifest for a .NET preview, RC or GA milestone by choosing the right VMR base and head refs and running release-notes generate changes.

    22k GitHub stars~1.7k tokensUpdated today
    DevelopmentAuto-check passed

  • Change Management

    sickn33/agentic-awesome-skills

    Implement change management processes. An agent skill from sickn33/agentic-awesome-skills.

    47k GitHub starsUsed in 2 repos~3.5k tokens
    DevOps & CloudAuto-check passed

  • Implement Change

    pnpm/pnpm

    Implement a pnpm feature, bug fix, or refactor by checking existing capabilities, prioritizing code reuse and deduplication, assessing architecture impact, and validating the final change.

    37k GitHub stars~1.1k tokensUpdated today
    DevelopmentAuto-check passed

More from Consensys/c0

All 11 skills in this repo

  • Debug Cloudflare Workers Observability

    Consensys/c0

    Debug deployed Cloudflare Workers using the cfobservability MCP, Wrangler, D1/R2 state, repo evidence, and safe live reproduction.

    105 GitHub stars~1.2k tokensUpdated 1 mo ago
    Auto-check: notes

  • Deslop Typescript

    Consensys/c0

    Run a final de-slopping pass on nearly finished JavaScript or TypeScript work before commit or PR.

    105 GitHub stars~1.6k tokensUpdated 1 mo ago
    Auto-check passed

  • Implement Workflow Node

    Consensys/c0

    A skill your agent uses when adding, changing, or reviewing Workflow Nodes in the c0 agent repo, including shared node catalog metadata, Workflow Node options and ports, runtime node Adapters…

    105 GitHub stars~943 tokensUpdated 1 mo ago
    Auto-check passed

  • Agent Eval Loop

    Consensys/c0

    Run and improve the c0 agent evaluation loop using the local and remote Cloudflare MCP harness, versioned history notes, and current Cloudflare product updates.

    105 GitHub stars~1.2k tokensUpdated 1 mo ago
    Auto-check passed

  • Alchemy Env Types

    Consensys/c0

    Derive Cloudflare worker env types from Alchemy resource Env types instead of hand-writing env shapes.

    105 GitHub stars~707 tokensUpdated 1 mo ago
    Auto-check passed

  • C0 Config

    Consensys/c0

    A skill your agent uses when changing c0 deployment configuration, runtime-editable global settings, auth providers, AI providers, MCP Context Forge, discovered registries, secret references, or…

    105 GitHub stars~2.1k tokensUpdated 1 mo ago
    Auto-check: notes

Questions about Workflow Runtime Abi

What does Workflow Runtime Abi do?

Guidance for safely changing the c0 Workflow runtime ABI, manifest ABI, runtime kernels, manifest migrations, workflow artifact compatibility, and audit/backfill tooling. Workflow Runtime Abi is an agent skill from Consensys/c0. Guidance for safely changing the c0 Workflow runtime ABI, manifest ABI, runtime kernels, manifest migrations, workflow artifact compatibility, and audit/backfill tooling.

When should I use Workflow Runtime Abi?

Workflow Runtime Abi fits situations like: modifying workflow runtime contracts; compiled workflow imports; manifest versions; Node handle semantics.

How do I install Workflow Runtime Abi in Claude Code?

Run `npx skills add Consensys/c0 --skill workflow-runtime-abi -a claude-code`. Or copy the skill folder (.agents/skills/workflow-runtime-abi in Consensys/c0) into .claude/skills/workflow-runtime-abi in your project. Claude Code loads it when a task matches its description.

How do I install Workflow Runtime Abi in Codex?

Run `npx skills add Consensys/c0 --skill workflow-runtime-abi -a codex`. Or copy the skill folder (.agents/skills/workflow-runtime-abi in Consensys/c0) into .agents/skills/workflow-runtime-abi in your project. Codex loads it when a task matches its description.

Can I use Workflow Runtime Abi 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 Consensys/c0 --skill workflow-runtime-abi -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/workflow-runtime-abi, .gemini/skills/workflow-runtime-abi, .github/skills/workflow-runtime-abi and .opencode/skills/workflow-runtime-abi in your project.

What does Workflow Runtime Abi need to run?

SKILL.md names no scripts, command-line tools or credentials: Workflow Runtime Abi is instructions for the agent only.

Does Workflow Runtime Abi 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 Workflow Runtime Abi 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 Workflow Runtime Abi use?

Workflow Runtime Abi is published under the LGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Workflow Runtime Abi use?

About 1.8k tokens (SKILL.md is roughly 7.3k 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 1.2k tokens, read only when the agent opens those files.

What are the alternatives to Workflow Runtime Abi?

Skills that share tags, products or a category with Workflow Runtime Abi: Make Changes (remix-run/remix, 33k stars), Safe Push (JetBrains/intellij-community, 21k stars), Orch Change Feature (affaan-m/ECC, 275k stars) and Generate .NET Release changes.json (dotnet/core, 22k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Workflow Runtime Abi?

Consensys (a GitHub organization) maintains it in Consensys/c0, which has 105 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on August 18, 2026.

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