API Designer
Jeffallan/claude-skills
Designs REST and GraphQL APIs from resource modeling to an OpenAPI 3.1 contract, with versioning, pagination and RFC 7807 error handling.
Read the status of a Hyperledger Cello deployment through its REST API.
Install Cello
$ npx skills add hyperledger-cello/cello --skill cello -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install hyperledger-cello/cello cello --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/hyperledger-cello/cello.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/cello .claude/skills/cello && rm -rf skills-srcUse ~/.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/
Install the "cello" agent skill from https://github.com/hyperledger-cello/cello/tree/main/.claude/skills/cello into .claude/skills/cello/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cello", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/hyperledger-cello/cello/tree/main/.claude/skills/celloType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add hyperledger-cello/cello --skill cello -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install hyperledger-cello/cello cello --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hyperledger-cello/cello.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/cello .agents/skills/cello && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "cello" agent skill from https://github.com/hyperledger-cello/cello/tree/main/.claude/skills/cello into .agents/skills/cello/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cello", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add hyperledger-cello/cello --skill cello -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install hyperledger-cello/cello cello --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hyperledger-cello/cello.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/cello .cursor/skills/cello && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "cello" agent skill from https://github.com/hyperledger-cello/cello/tree/main/.claude/skills/cello into .cursor/skills/cello/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cello", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/hyperledger-cello/cello.git --path .claude/skills/cello--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add hyperledger-cello/cello --skill cello -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install hyperledger-cello/cello cello --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hyperledger-cello/cello.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/cello .gemini/skills/cello && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "cello" agent skill from https://github.com/hyperledger-cello/cello/tree/main/.claude/skills/cello into .gemini/skills/cello/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cello", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install hyperledger-cello/cello celloInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add hyperledger-cello/cello --skill cello -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/hyperledger-cello/cello.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/cello .github/skills/cello && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "cello" agent skill from https://github.com/hyperledger-cello/cello/tree/main/.claude/skills/cello into .github/skills/cello/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cello", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add hyperledger-cello/cello --skill cello -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install hyperledger-cello/cello cello --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hyperledger-cello/cello.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/cello .opencode/skills/cello && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "cello" agent skill from https://github.com/hyperledger-cello/cello/tree/main/.claude/skills/cello into .opencode/skills/cello/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cello", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
cello- GitHub stars
- 918
- Token cost
- ~443 tokens
- SKILL.md length
- 157 words
- Files
- 5
- Skills in repo
- 1
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Read the status of a Hyperledger Cello deployment through its REST API.
- The user asks to inspect Cello
- SKILL.md covers Setup and Topics — load the matching…
- Calls curl and jq; needs CELLO_PASSWORD
- Fabric networks
What it does
Cello is an agent skill from hyperledger-cello/cello. Read the status of a Hyperledger Cello deployment through its REST API. Use when the user asks to inspect Cello, Fabric networks, nodes, peers, orderers, channels, chaincodes, or organizations.
Its SKILL.md is about 440 tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files (for example `chaincodes.md`, `channels.md` and `nodes.md`).
It sits in Backend & APIs, covering REST APIs. The repository describes itself as: Operating System for Enterprise Blockchain. The licence is Apache-2.0.
When your agent uses it
- The user asks to inspect Cello
- Fabric networks
Example prompts
- “/cello”
What it can do on your machine
Read from SKILL.md and the folder at commit cd208b2. 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
Shell commands in SKILL.md call:
curljq
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use curl, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
CELLO_PASSWORD
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Cello loads about 443 tokens when it runs. Until then it costs about 50 tokens; SKILL.md has 157 words of instructions outside code blocks.
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 hyperledger-cello/cello at commit cd208b2, republished under its Apache-2.0 licence (© hyperledger-cello). 157 words, ~443 tokens.
Download SKILL.mdSave it as
.claude/skills/cello/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- cello
- description
- Read the status of a Hyperledger Cello deployment through its REST API. Use when the user asks to inspect Cello, Fabric networks, nodes, peers, orderers, channels, chaincodes, or organizations.
Cello API
Read-only inspection of a running Cello API Engine.
Setup
- Base URL:
http://localhost:8080/api/v1 - Credentials: read from
~/.cello/credentials, an env-style file withCELLO_EMAIL=...andCELLO_PASSWORD=...(create it once,chmod 600). - Auth: send the JWT from
~/.cello/tokenas theAuthorization: JWT <token>header. If~/.cello/tokenis missing, run the login helper below first. Tokens expire after ~1 hour, so on any401re-run the helper and retry the request.
Login helper:
mkdir -p ~/.cello
set -a; . ~/.cello/credentials; set +a
curl -s -X POST http://localhost:8080/api/v1/login \
-H "Content-Type: application/json" \
-d "{\"email\":\"$CELLO_EMAIL\",\"password\":\"$CELLO_PASSWORD\"}" \
| jq -r '.data.token' > ~/.cello/token
chmod 600 ~/.cello/tokenIf login fails or the token is empty or null, ask the user to verify
~/.cello/credentials and API availability. Do not guess credentials.
Successful responses use {status, msg, data}; error responses may not.
List endpoints default to per_page=10; use per_page=100 for
inspection and page further only when .data.total > 100.
Topics — load the matching file as needed
| User mentions… | Read this file |
|---|---|
| nodes, peers, orderers | nodes.md |
| channels | channels.md |
| chaincodes, smart contracts | chaincodes.md |
| organizations, members | organizations.md |
Load only the file relevant to the user's question, not all of them.
© hyperledger-cello, 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 4 other files in .claude/skills/cello of hyperledger-cello/cello.
- SKILL.md
- chaincodes.md
- channels.md
- nodes.md
- organizations.md
Open the folder on GitHubat commit cd208b2
Compare with similar skills
Cello 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Cello this skillhyperledger-cello/cello | 918 | — | ~443 | Automated safety check: Pass | Apache-2.0 | |
| API DesignerJeffallan/claude-skills | 12k | 2 repos | ~2k | Automated safety check: Pass | MIT | |
| Paperclippaperclipai/paperclip | 99k | — | ~9.6k | Automated safety check: Pass | MIT | |
| Nodejs Backend Patternsever-works/ever-works | 158 | 18 repos | ~4k | Automated safety check: Pass | AGPL-3.0 | |
| OpenAPI to MCP Servermcp-use/mcp-use | 11k | — | ~5.2k | Automated safety check: Pass | Apache-2.0 | |
| Use Yaakmountain-loop/yaak | 19k | — | ~1.9k | Automated safety check: Pass | MIT |
Similar skills
Paperclip
paperclipai/paperclip
Interact with the Paperclip control plane API for task coordination and governance.
Nodejs Backend Patterns
ever-works/ever-works
Build production-ready Node.js backend services with Express/Fastify, implementing middleware patterns, error handling, authentication, database integration, and API design best practices.
OpenAPI to MCP Server
mcp-use/mcp-use
Turns an OpenAPI or Swagger spec into an MCP server with the mcp-use TypeScript SDK, mapping each operation to a tool, wiring auth, testing and deploying.
Use Yaak
mountain-loop/yaak
A skill your agent uses when the user mentions Yaak, a Yaak workspace, or the yaak command, or asks to call, hit, or smoke test HTTP/REST endpoints, save or organize API requests for reuse or manual…
RuView CLI, API and WASM
ruvnet/RuView
Covers the RuView `wifi-densepose` command line binary, its Axum REST API and the WebAssembly builds for browsers and ESP32, for embedding or scripting RuView.
Related
Categories
Questions about Cello
What does Cello do?
Read the status of a Hyperledger Cello deployment through its REST API. Cello is an agent skill from hyperledger-cello/cello. Read the status of a Hyperledger Cello deployment through its REST API.
When should I use Cello?
Cello fits situations like: the user asks to inspect Cello; fabric networks.
How do I install Cello in Claude Code?
Run `npx skills add hyperledger-cello/cello --skill cello -a claude-code`. Or copy the skill folder (.claude/skills/cello in hyperledger-cello/cello) into .claude/skills/cello in your project. Claude Code loads it when a task matches its description.
How do I install Cello in Codex?
Run `npx skills add hyperledger-cello/cello --skill cello -a codex`. Or copy the skill folder (.claude/skills/cello in hyperledger-cello/cello) into .agents/skills/cello in your project. Codex loads it when a task matches its description.
Can I use Cello 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 hyperledger-cello/cello --skill cello -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cello, .gemini/skills/cello, .github/skills/cello and .opencode/skills/cello in your project.
What does Cello need to run?
Going by SKILL.md and its folder, Cello needs the command-line tools its instructions call (curl and jq) and credentials named CELLO_PASSWORD.
Does Cello access the network?
SKILL.md contains no URLs. Its commands use curl, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Cello 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 Cello use?
Cello 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 Cello use?
About 443 tokens (SKILL.md is roughly 1.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Cello?
Skills that share tags, products or a category with Cello: API Designer (Jeffallan/claude-skills, 12k stars), Paperclip (paperclipai/paperclip, 99k stars), Nodejs Backend Patterns (ever-works/ever-works, 158 stars) and OpenAPI to MCP Server (mcp-use/mcp-use, 11k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Cello?
hyperledger-cello (a GitHub organization) maintains it in hyperledger-cello/cello, which has 918 GitHub stars. The repository was last updated on October 7, 2026.
Source: hyperledger-cello/cello on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.