New: 97,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

Conversion Method Naming

by 0xMiden in 0xMiden/protocol

A skill your agent uses when naming a conversion or accessor method in Rust — follow the Rust API naming conventions for the method's cost and ownership.

MITAuto-check passedDevelopment

Install Conversion Method Naming

skills CLI
$ npx skills add 0xMiden/protocol --skill conversion-method-naming -a claude-code

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

GitHub CLI
$ gh skill install 0xMiden/protocol conversion-method-naming --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/0xMiden/protocol.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/conversion-method-naming .claude/skills/conversion-method-naming && 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
conversion-method-naming
GitHub stars
133
Token cost
~450 tokens
SKILL.md length
142 words
Files
1
Skills in repo
34
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when naming a conversion or accessor method in Rust — follow the Rust API naming conventions for the method's cost and ownership.

  • Naming a conversion
  • SKILL.md covers Rule, Why and Examples
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Accessor method in Rust — follow the Rust API naming conventions for the methods cost and ownership

What it does

Conversion Method Naming is an agent skill from 0xMiden/protocol. Use when naming a conversion or accessor method in Rust — follow the Rust API naming conventions for the method's cost and ownership.

Its SKILL.md is about 450 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development. It works with Rust. The repository describes itself as: Core components of the Miden protocol. The licence is MIT.

When your agent uses it

  • Naming a conversion
  • Accessor method in Rust — follow the Rust API naming conventions for the methods cost and ownership

Example prompts

  • “/conversion-method-naming”

What it can do on your machine

Read from SKILL.md and the folder at commit 3a8215e. 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 rust).

    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

Conversion Method Naming loads about 450 tokens when it runs. Until then it costs about 40 tokens; SKILL.md has 142 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~40
When it runs · the whole SKILL.md, loaded when a task matches
~450

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 0xMiden/protocol at commit 3a8215e, republished under its MIT licence (© 0xMiden). 142 words, ~450 tokens.

Download SKILL.mdSave it as .claude/skills/conversion-method-naming/SKILL.md (or your agent's skills folder).
name
conversion-method-naming
description
Use when naming a conversion or accessor method in Rust — follow the Rust API naming conventions for the method's cost and ownership.

Rust Conversion Method Naming

Rule

Pick the prefix that matches the cost and ownership of the conversion:

  • as_<type> — free or near-free, returns a borrow (e.g. as_bytes() -> &[u8]).
  • to_<type> — non-trivial cost, returns an owned value, leaves self intact (e.g. to_string() -> String).
  • into_<type> — consumes self, returns the inner/converted value.
  • from_<type> — associated function on the target type that constructs it.
  • with_<field> — only for builder-style methods that take and return Self with a field set.

Do not name a non-borrowing method as_*. Do not name a non-builder method with_*. Do not use to_* for a free borrow.

Why

The prefixes come from the Rust API guidelines and are baked into the standard library: readers expect as_ to be cheap, to_ to allocate, into_ to consume, and with_ to return Self. Violating that costs every reader a moment of confusion and erodes trust in the API.

Examples

rust
// Good
impl Header {
    pub fn as_bytes(&self) -> &[u8] { ... }              // cheap borrow
    pub fn to_vec(&self) -> Vec<u8> { ... }              // allocates
    pub fn into_payload(self) -> Payload { self.payload } // consumes
}

impl HeaderBuilder {
    pub fn with_version(mut self, v: u8) -> Self { self.version = v; self }
}

// Bad
impl Header {
    pub fn as_vec(&self) -> Vec<u8> { ... }  // allocates, should be to_vec
    pub fn to_bytes(&self) -> &[u8] { ... }  // borrow, should be as_bytes
}

// Bad: with_* on a non-builder method
fn with_seed(rng: &mut Rng, seed: u64) { ... }   // not returning Self

© 0xMiden, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/conversion-method-naming of 0xMiden/protocol.

Open the folder on GitHubat commit 3a8215e

Compare with similar skills

Conversion Method Naming 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.

Conversion Method Naming compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Conversion Method Naming this skill0xMiden/protocol133—~450Automated safety check: PassMIT
Migrate Core Code to Submodulestinyhumansai/openhuman41k—~2.6kAutomated safety check: PassGPL-3.0
Rust Best Practicesfarm-fe/farm5.6k3 repos~1.1kAutomated safety check: PassMIT
OpenLogi macOS Permissions TriageAprilNEA/OpenLogi23k—~2.5kAutomated safety check: NotesApache-2.0
RTK Rust Design Patternsrtk-ai/rtk83k—~1.9kAutomated safety check: PassApache-2.0
Release Skillsnexmoe/eve4213 repos~3.3kAutomated safety check: PassNone

Similar skills

  • Migrate Core Code to Submodules

    tinyhumansai/openhuman

    Plans and carries out moving non-host-specific code and its tests from the OpenHuman core into vendored tiny submodule libraries, then releases the submodule and re-pins the host.

    41k GitHub stars~2.6k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Rust Best Practices

    farm-fe/farm

    Guide for writing idiomatic Rust code based on Apollo GraphQL's best practices handbook.

    5.6k GitHub starsUsed in 3 repos~1.1k tokens
    DevelopmentAuto-check passed

  • OpenLogi macOS Permissions Triage

    AprilNEA/OpenLogi

    Decides whether an OpenLogi device problem on macOS is a privacy-permission (TCC) problem, using agent log lines, and says which identity needs which grant.

    23k GitHub stars~2.5k tokensUpdated 4 days ago
    DevelopmentAuto-check: notes

  • RTK Rust Design Patterns

    rtk-ai/rtk

    Describes seven Rust design patterns for the RTK CLI filter modules, with when to use each, RTK examples, and notes on when a pattern is overkill.

    83k GitHub stars~1.9k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Release Skills

    nexmoe/eve

    Universal release workflow. An agent skill from nexmoe/eve.

    421 GitHub starsUsed in 3 repos~3.3k tokens
    DevelopmentAuto-check passed

  • Pnpm Engine

    teambit/bit

    Work on the pnpm Rust engine (@pnpm/napi, the pacquet crates) that bit install runs through.

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

More from 0xMiden/protocol

All 34 skills in this repo

  • Advice Provider Hygiene

    0xMiden/protocol

    A skill your agent uses when writing kernel, account, or note MASM code that reads from or writes to the advice provider (advice stack / advice map) — validate advice data.

    133 GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

  • Cheap Masm Equivalents

    0xMiden/protocol

    A skill your agent uses when writing or reviewing MASM hot paths or loops — prefer the cheaper equivalent: loop counters and pointers on the operand stack instead of procedure locals, neq.0 over…

    133 GitHub stars~804 tokensUpdated yesterday
    Auto-check passed

  • Concise Changelog Entries

    0xMiden/protocol

    Keep CHANGELOG.md entries to a single concise sentence. An agent skill from 0xMiden/protocol.

    133 GitHub stars~805 tokensUpdated yesterday
    Auto-check passed

  • Concise PR And Issue Descriptions

    0xMiden/protocol

    Keep PR and issue descriptions short and decision-focused. An agent skill from 0xMiden/protocol.

    133 GitHub stars~1.8k tokensUpdated yesterday
    Auto-check passed

  • Decouple Component From Storage

    0xMiden/protocol

    A skill your agent uses when writing a generic MASM utility that accesses a caller-selected account storage slot — receive the slot as a parameter so the utility is portable across storage layouts.

    133 GitHub stars~529 tokensUpdated yesterday
    Auto-check passed

  • Felt Construction

    0xMiden/protocol

    A skill your agent uses when constructing a Felt from a numeric value in Rust — use checked construction unless the canonical bound is already proved.

    133 GitHub stars~439 tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Conversion Method Naming

What does Conversion Method Naming do?

A skill your agent uses when naming a conversion or accessor method in Rust — follow the Rust API naming conventions for the method's cost and ownership. Conversion Method Naming is an agent skill from 0xMiden/protocol. Use when naming a conversion or accessor method in Rust — follow the Rust API naming conventions for the method's cost and ownership.

When should I use Conversion Method Naming?

Conversion Method Naming fits situations like: naming a conversion; accessor method in Rust — follow the Rust API naming conventions for the methods cost and ownership.

How do I install Conversion Method Naming in Claude Code?

Run `npx skills add 0xMiden/protocol --skill conversion-method-naming -a claude-code`. Or copy the skill folder (.claude/skills/conversion-method-naming in 0xMiden/protocol) into .claude/skills/conversion-method-naming in your project. Claude Code loads it when a task matches its description.

How do I install Conversion Method Naming in Codex?

Run `npx skills add 0xMiden/protocol --skill conversion-method-naming -a codex`. Or copy the skill folder (.claude/skills/conversion-method-naming in 0xMiden/protocol) into .agents/skills/conversion-method-naming in your project. Codex loads it when a task matches its description.

Can I use Conversion Method Naming 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 0xMiden/protocol --skill conversion-method-naming -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/conversion-method-naming, .gemini/skills/conversion-method-naming, .github/skills/conversion-method-naming and .opencode/skills/conversion-method-naming in your project.

What does Conversion Method Naming need to run?

SKILL.md names no scripts, command-line tools or credentials: Conversion Method Naming is instructions for the agent only.

Does Conversion Method Naming 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 Conversion Method Naming 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 Conversion Method Naming use?

Conversion Method Naming is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Conversion Method Naming use?

About 450 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 Conversion Method Naming?

Skills that share tags, products or a category with Conversion Method Naming: Migrate Core Code to Submodules (tinyhumansai/openhuman, 41k stars), Rust Best Practices (farm-fe/farm, 5.6k stars), OpenLogi macOS Permissions Triage (AprilNEA/OpenLogi, 23k stars) and RTK Rust Design Patterns (rtk-ai/rtk, 83k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Conversion Method Naming?

0xMiden (a GitHub organization) maintains it in 0xMiden/protocol, which has 133 GitHub stars. The repository holds 34 skills in this directory. The repository was last updated on October 6, 2026.

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