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

Axone Proto Specification

by axone-protocol in axone-protocol/axoned

Design and evolve protobuf APIs for this repository. An agent skill from axone-protocol/axoned.

Apache-2.0Auto-check passedBackend & APIs

Install Axone Proto Specification

skills CLI
$ npx skills add axone-protocol/axoned --skill axone-proto-specification -a claude-code

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

GitHub CLI
$ gh skill install axone-protocol/axoned axone-proto-specification --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/axone-protocol/axoned.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/axone-proto-specification .claude/skills/axone-proto-specification && 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
axone-proto-specification
GitHub stars
176
Token cost
~828 tokens
SKILL.md length
403 words
Files
3 (incl. references)
Skills in repo
3
Repo updated
First seen
Licence
Apache-2.0

At a glance

Design and evolve protobuf APIs for this repository. An agent skill from axone-protocol/axoned.

  • Works in 3 steps: Read repo conventions. → Read external guidance if the change… → Then design the schema before editing…
  • Changing files under proto/
  • SKILL.md covers Read order, Design rules, What to change first and Compatibility rules, plus 2 more sections
  • Calls make

What it does

Axone Proto Specification is an agent skill from axone-protocol/axoned. Design and evolve protobuf APIs for this repository. Use when creating or changing files under proto/, or when shaping the Go implementation that follows from a proto contract. Focuses on API specification first, with repo-specific conventions plus Cosmos SDK, gRPC, and protobuf compatibility rules.

Its SKILL.md is about 830 tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/external-guidance.md` and `references/repo-conventions.md`). Compatibility notes: Requires go, make, docker, and local access to the repository. Read reference files in this skill when changing wire-visible schemas.

It sits in Backend & APIs, covering gRPC and Protobuf and OpenAPI specifications. It works with gRPC and Go. The repository describes itself as: ⛓️ Axone blockchain 💫. The licence is Apache-2.0.

When your agent uses it

  • Changing files under proto/
  • Shaping the Go implementation that follows from a proto contract

Example prompts

  • “/axone-proto-specification”

Requirements

  • Docker
  • Compatibility (from SKILL.md): Requires go, make, docker, and local access to the repository. Read reference files in this skill when changing wire-visible schemas.

Workflow steps

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

  1. Read repo conventions.
  2. Read external guidance if the change affects fields, service shape, compatibility, or error semantics.
  3. Then design the schema before editing code.

What it can do on your machine

Read from SKILL.md and the folder at commit 5570d4c. 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:

    • make

    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.

  • Compatibility

    Requires go, make, docker, and local access to the repository. Read reference files in this skill when changing wire-visible schemas.

    From compatibility in the SKILL.md frontmatter.

Context cost

Axone Proto Specification loads about 828 tokens when it runs, and up to ~2.2k if it reads all its reference files. Until then it costs about 82 tokens; SKILL.md has 403 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~82
When it runs · the whole SKILL.md, loaded when a task matches
~828
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 axone-protocol/axoned at commit 5570d4c, republished under its Apache-2.0 licence (© axone-protocol). 403 words, ~828 tokens.

Download SKILL.mdSave it as .claude/skills/axone-proto-specification/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
axone-proto-specification
description
Design and evolve protobuf APIs for this repository. Use when creating or changing files under proto/, or when shaping the Go implementation that follows from a proto contract. Focuses on API specification first, with repo-specific conventions plus Cosmos SDK, gRPC, and protobuf compatibility rules.
compatibility
Requires go, make, docker, and local access to the repository. Read reference files in this skill when changing wire-visible schemas.

Axone Proto Specification

Use this skill when changing protobuf schemas or designing module APIs that will be expressed in proto/.

This skill is about specification first. In this repo, the .proto contract is the source of truth; generated code, gateway routes, docs, and most implementation structure follow from it.

Read order

  1. Read repo conventions.
  2. Read external guidance if the change affects fields, service shape, compatibility, or error semantics.
  3. Then design the schema before editing code.

Design rules

  1. Start from the domain model and invariants, not from the current keeper or handler code.
  2. Treat every field number, field name, service name, and HTTP path as part of a long-lived public contract.
  3. Preserve the local convention of the touched module unless you are intentionally migrating the whole module. Do not normalize logic and mint styles accidentally.
  4. Prefer small, explicit RPCs with dedicated request and response messages.
  5. Use Cosmos-specific annotations only when they express real semantics such as signer identity, safe queries, or scalar meaning.
  6. Design pagination, field presence, and reserved slots deliberately. Do not leave them to later cleanup.
  7. Write comments as part of the spec, not as afterthoughts. In this repo, comments are linted and flow into generated docs.

What to change first

  • Edit proto/<module>/<version>/*.proto
  • Keep module docs aligned through proto/<module>/docs.yaml when the user-facing description changes
  • Let generation produce Go code and markdown docs
  • Then adapt the Go implementation to the contract rather than mutating the contract to match incidental implementation details
Show full SKILL.md (152 more words)Show less

Compatibility rules

  • Never reuse a field number.
  • When removing a field, reserve both its number and name.
  • Do not change wire-visible meaning casually: type, cardinality, field meaning, enum behavior, and path semantics all matter.
  • If a field needs presence semantics, decide that explicitly before choosing the representation.
  • If an RPC is side-effect free, keep it query-shaped and mark it accordingly.
  • If an RPC mutates state or is authority-gated, express signer and authority semantics explicitly in the schema.

Validation

  • Run make proto
  • If you changed Go implementation too, run make lint-go and make test-go
  • Inspect generated diffs instead of trusting generation blindly

Output expectation

When using this skill, the agent should be able to explain:

  • why the schema shape fits the module domain
  • why the chosen field numbers and names are safe to evolve
  • why the annotations and HTTP mapping match Cosmos and gRPC semantics
  • what generated and implementation files must change downstream

© axone-protocol, 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 2 other files (references) in .agents/skills/axone-proto-specification of axone-protocol/axoned.

  • SKILL.md
  • references/external-guidance.md
  • references/repo-conventions.md

Open the folder on GitHubat commit 5570d4c

Compare with similar skills

Axone Proto Specification 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.

Axone Proto Specification compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Axone Proto Specification this skillaxone-protocol/axoned176—~828Automated safety check: PassApache-2.0
Use Yaakmountain-loop/yaak19k—~1.9kAutomated safety check: PassMIT
Golang Proantoniopaya22/go-rest-template1723 repos~1.2kAutomated safety check: PassMIT
SpikardGoldziher/spikard123—~799Automated safety check: PassMIT
Golang Grpccontext-labs/whip1.1k1 repos~2.5kAutomated safety check: PassMIT
Capability GovernanceArtisanCloud/PowerX379—~3kAutomated safety check: PassApache-2.0

Similar skills

  • 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…

    19k GitHub stars~1.9k tokensUpdated 2 days ago
    Backend & APIsAuto-check passed

  • Golang Pro

    antoniopaya22/go-rest-template

    Implements concurrent Go patterns using goroutines and channels, designs and builds microservices with gRPC or REST, optimizes Go application performance with pprof, and enforces idiomatic Go with…

    172 GitHub starsUsed in 3 repos~1.2k tokens
    Backend & APIsAuto-check passed

  • Spikard

    Goldziher/spikard

    Scaffold Spikard projects and generate code from OpenAPI, AsyncAPI, OpenRPC, GraphQL, and Protobuf schemas using the Spikard CLI or its MCP server.

    123 GitHub stars~799 tokensUpdated 5 days ago
    Backend & APIsAuto-check passed

  • Golang Grpc

    context-labs/whip

    gRPC usage, protobuf organization, and production patterns for Go microservices.

    1.1k GitHub starsUsed in 1 repo~2.5k tokens
    Backend & APIsAuto-check passed

  • Capability Governance

    ArtisanCloud/PowerX

    PowerX 底座 Capability 治理与发布准入规则。用于审计 REST/OpenAPI/gRPC/Gin 生成的能力候选、正式 platformcapabilities 目录、Capability Registry 登记、agentusable/permissioncode/risklevel 元数据、ignore…

    379 GitHub stars~3k tokensUpdated today
    Backend & APIsAuto-check passed

  • Dotnet API

    novotnyllc/dotnet-artisan

    Builds ASP.NET Core APIs, EF Core data access, gRPC, SignalR, and backend services with middleware, security (OAuth, JWT, OWASP), resilience, messaging, OpenAPI, .NET Aspire, Semantic Kernel…

    233 GitHub stars~1.6k tokensUpdated yesterday
    Backend & APIsAuto-check passed

More from axone-protocol/axoned

  • Axone Contributor Workflow

    axone-protocol/axoned

    Contribute safely to the AXONE axoned repository. An agent skill from axone-protocol/axoned.

    176 GitHub stars~830 tokensUpdated today
    Auto-check passed

  • Axone Logic Predicate

    axone-protocol/axoned

    Add or change predicates in the AXONE logic module. An agent skill from axone-protocol/axoned.

    176 GitHub stars~1.9k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Axone Proto Specification

What does Axone Proto Specification do?

Design and evolve protobuf APIs for this repository. An agent skill from axone-protocol/axoned. Axone Proto Specification is an agent skill from axone-protocol/axoned. Design and evolve protobuf APIs for this repository.

When should I use Axone Proto Specification?

Axone Proto Specification fits situations like: changing files under proto/; shaping the Go implementation that follows from a proto contract.

How do I install Axone Proto Specification in Claude Code?

Run `npx skills add axone-protocol/axoned --skill axone-proto-specification -a claude-code`. Or copy the skill folder (.agents/skills/axone-proto-specification in axone-protocol/axoned) into .claude/skills/axone-proto-specification in your project. Claude Code loads it when a task matches its description.

How do I install Axone Proto Specification in Codex?

Run `npx skills add axone-protocol/axoned --skill axone-proto-specification -a codex`. Or copy the skill folder (.agents/skills/axone-proto-specification in axone-protocol/axoned) into .agents/skills/axone-proto-specification in your project. Codex loads it when a task matches its description.

Can I use Axone Proto Specification 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 axone-protocol/axoned --skill axone-proto-specification -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/axone-proto-specification, .gemini/skills/axone-proto-specification, .github/skills/axone-proto-specification and .opencode/skills/axone-proto-specification in your project.

What does Axone Proto Specification need to run?

Going by SKILL.md and its folder, Axone Proto Specification needs the command-line tools its instructions call (make). Our summary lists: Docker. Compatibility (from SKILL.md): Requires go, make, docker, and local access to the repository. Read reference files in this skill when changing wire-visible schemas..

Does Axone Proto Specification 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 Axone Proto Specification 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 Axone Proto Specification use?

Axone Proto Specification 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 Axone Proto Specification use?

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

What are the alternatives to Axone Proto Specification?

Skills that share tags, products or a category with Axone Proto Specification: Use Yaak (mountain-loop/yaak, 19k stars), Golang Pro (antoniopaya22/go-rest-template, 172 stars), Spikard (Goldziher/spikard, 123 stars) and Golang Grpc (context-labs/whip, 1.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Axone Proto Specification?

axone-protocol (a GitHub organization) maintains it in axone-protocol/axoned, which has 176 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 8, 2026.

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