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

Implement Workflow Node

by Consensys in 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…

LGPL-3.0Auto-check passed

Install Implement Workflow Node

skills CLI
$ npx skills add Consensys/c0 --skill implement-workflow-node -a claude-code

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

GitHub CLI
$ gh skill install Consensys/c0 implement-workflow-node --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/implement-workflow-node .claude/skills/implement-workflow-node && 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
implement-workflow-node
GitHub stars
105
Token cost
~943 tokens
SKILL.md length
379 words
Files
3 (incl. references)
Skills in repo
11
Repo updated
First seen
Licence
LGPL-3.0

At a glance

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…

  • Works in 3 steps: Read CONTEXT.md for domain terms,… → Read references/node-architecture.md for… → Inspect the closest existing node…
  • Reviewing Workflow Nodes in the c0 agent repo
  • SKILL.md covers Start Here, Choose The Node Kind, Implementation Workflow and Runtime Rules, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Implement Workflow Node is an agent skill from Consensys/c0. Use 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, adapter registry routing, compiler inline logic nodes, workflow validation, and tests for Workflow Node execution.

Its SKILL.md is about 940 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/node-architecture.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

  • Reviewing Workflow Nodes in the c0 agent repo
  • Including shared node catalog metadata
  • Workflow Node options and ports
  • Runtime node Adapters

Example prompts

  • “/implement-workflow-node”

Workflow steps

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

  1. Read CONTEXT.md for domain terms, especially Workflow, Workflow Node, and Workflow Run.
  2. Read references/node-architecture.md for the current file map and Adapter pattern.
  3. Inspect the closest existing node category before editing

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

Implement Workflow Node loads about 943 tokens when it runs, and up to ~2.2k if it reads all its reference files. Until then it costs about 78 tokens; SKILL.md has 379 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~78
When it runs · the whole SKILL.md, loaded when a task matches
~943
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.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 Consensys/c0 at commit e7a1810, republished under its LGPL-3.0 licence (© Consensys). 379 words, ~943 tokens.

Download SKILL.mdSave it as .claude/skills/implement-workflow-node/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
implement-workflow-node
description
Use 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, adapter registry routing, compiler inline logic nodes, workflow validation, and tests for Workflow Node execution.

Implement Workflow Node

Use this skill when implementing or reviewing a new Workflow Node in this repo. Keep authored metadata, runtime execution, validation, and tests aligned.

Start Here

  1. Read CONTEXT.md for domain terms, especially Workflow, Workflow Node, and Workflow Run.
  2. Read references/node-architecture.md for the current file map and Adapter pattern.
  3. Inspect the closest existing node category before editing:
    • Runtime action Adapter: packages/api/src/server/background/workflows/nodes/*.ts
    • Shared catalog/options: packages/shared/src/workflow-nodes.ts
    • Inline logic execution: packages/api/src/server/background/workflows/compiler.ts
    • Tests: tests/workflows/*

Choose The Node Kind

  • Trigger nodes start Workflow Runs. Add scheduling/webhook lifecycle behavior only when the node actually starts runs.
  • Logic nodes execute inside compiled workflow code. Implement them in compiler.ts; do not route them through WorkflowActionExecutor.
  • Action nodes execute through WorkflowActionExecutor and the node Adapter registry. Add runtime behavior behind the appropriate Adapter Module.
  • Provider variants should live inside an existing category Adapter unless behavior divergence justifies a new concrete Adapter Seam.

Implementation Workflow

  1. Add the node type to WORKFLOW_NODE_TYPES and WORKFLOW_NODE_CATALOG in packages/shared/src/workflow-nodes.ts.
  2. Add default options in getWorkflowNodeDefaultOptions(...).
  3. Add option/template validation only for real invariants. Keep validation in shared code when it affects authoring or portability.
  4. If it is an action node, add execution to a category Adapter under packages/api/src/server/background/workflows/nodes/.
  5. If it needs a new action category, add the category to shared metadata and register a category Adapter in nodes/registry.ts.
  6. Keep actions.ts as a thin WorkflowActionExecutor; it should delegate through executeWorkflowNodeWithAdapters(...).
  7. Add focused direct Adapter tests and keep executor regression tests only for end-to-end dispatch behavior.
Show full SKILL.md (130 more words)Show less

Runtime Rules

  • Require userId; do not reintroduce userNamespace terminology.
  • Use createNodeContext(...) and renderTemplate(...) from nodes/common.ts for runtime templating.
  • Use recordWorkflowNodeRunEvent(...) from nodes/events.ts for node action run events.
  • Keep nodes/common.ts small. Move helpers there only after at least two Adapters need the same Interface.
  • Keep provider calls and binding knowledge inside Adapter Modules, not in actions.ts or shared authoring code.
  • Redact secret values in compiler/run-event paths if the node can expose secrets or derived secret values.

Tests And Validation

Add or update focused tests based on the node kind:

  • Shared catalog/defaults/validation: tests/workflows/nodes.test.ts and tests/workflows/authoring.test.ts
  • Runtime Adapter: a direct tests/workflows/<category-or-node>-nodes.test.ts
  • Registry routing: tests/workflows/node-registry.test.ts
  • Compiler/logic behavior: tests/workflows/compiler.test.ts
  • Executor regression, only when dispatch behavior changes: tests/workflows/actions.test.ts

Run the narrowest relevant Vitest command while iterating, then run the repo-root checks required by AGENTS.md before handoff:

bash
nub run typecheck
nub run lint
nub run format

© 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/implement-workflow-node of Consensys/c0.

  • SKILL.md
  • agents/openai.yaml
  • references/node-architecture.md

Open the folder on GitHubat commit e7a1810

Compare with similar skills

Implement Workflow Node 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.

Implement Workflow Node compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Implement Workflow Node this skillConsensys/c0105—~943Automated safety check: PassLGPL-3.0
Implement Changepnpm/pnpm37k—~1.1kAutomated safety check: PassMIT
Verdaccio Change Implementationverdaccio/verdaccio18k—~1.3kAutomated safety check: PassMIT
Implementsickn33/agentic-awesome-skills47k5 repos~306Automated safety check: PassMIT
Implementcodewhale-hq/Codewhale41k—~190Automated safety check: PassMIT
Incremental Implementationaddyosmani/agent-skills103k1 repos~2.3kAutomated safety check: PassMIT

Similar skills

  • 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

  • Verdaccio Change Implementation

    verdaccio/verdaccio

    A workflow for implementing a Verdaccio bug fix, feature or refactor: pick the release lines, check existing options, edit the owning layer, test and add a changeset.

    18k GitHub stars~1.3k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Implement

    sickn33/agentic-awesome-skills

    Implement a piece of work based on a PRD or set of issues. An agent skill from sickn33/agentic-awesome-skills.

    47k GitHub starsUsed in 5 repos~306 tokens
    Product & Project ManagementAuto-check passed

  • Implement

    codewhale-hq/Codewhale

    Carry an authorized, defined request or approved plan through scoped edits and proportionate verification.

    41k GitHub stars~190 tokensUpdated today
    Auto-check passed

  • Incremental Implementation

    addyosmani/agent-skills

    Delivers a change in thin vertical slices, each implemented, tested, verified and committed before the next, using vertical, contract-first or risk-first slicing.

    103k GitHub starsUsed in 1 repo~2.3k tokens
    Agent WorkflowsAuto-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

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

  • Workflow Runtime Abi

    Consensys/c0

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

    105 GitHub stars~1.8k 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 Implement Workflow Node

What does Implement Workflow Node do?

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…. Implement Workflow Node is an agent skill from Consensys/c0. Use 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, adapter registry routing, compiler inline logic nodes, workflow validation, and tests for Workflow Node execution.

When should I use Implement Workflow Node?

Implement Workflow Node fits situations like: reviewing Workflow Nodes in the c0 agent repo; including shared node catalog metadata; workflow Node options and ports; runtime node Adapters.

How do I install Implement Workflow Node in Claude Code?

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

How do I install Implement Workflow Node in Codex?

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

Can I use Implement Workflow Node 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 implement-workflow-node -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/implement-workflow-node, .gemini/skills/implement-workflow-node, .github/skills/implement-workflow-node and .opencode/skills/implement-workflow-node in your project.

What does Implement Workflow Node need to run?

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

Does Implement Workflow Node 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 Implement Workflow Node 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 Implement Workflow Node use?

Implement Workflow Node 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 Implement Workflow Node use?

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

What are the alternatives to Implement Workflow Node?

Skills that share tags, products or a category with Implement Workflow Node: Implement Change (pnpm/pnpm, 37k stars), Verdaccio Change Implementation (verdaccio/verdaccio, 18k stars), Implement (sickn33/agentic-awesome-skills, 47k stars) and Implement (codewhale-hq/Codewhale, 41k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Implement Workflow Node?

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.