Agent skill

Private Fields With Accessors

by 0xMiden in 0xMiden/protocol

A skill your agent uses when adding a public struct or changing a field's visibility in a Rust library crate — keep fields encapsulated so the layout can evolve without breaking callers.

MITAuto-check passedDevelopment

Install Private Fields With Accessors

skills CLI
$ npx skills add 0xMiden/protocol --skill private-fields-with-accessors -a claude-code

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

GitHub CLI
$ gh skill install 0xMiden/protocol private-fields-with-accessors --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/private-fields-with-accessors .claude/skills/private-fields-with-accessors && 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
private-fields-with-accessors
GitHub stars
133
Token cost
~335 tokens
SKILL.md length
107 words
Files
1
Skills in repo
35
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when adding a public struct or changing a field's visibility in a Rust library crate — keep fields encapsulated so the layout can evolve without breaking callers.

  • Adding a public struct
  • SKILL.md covers Rule, Why and Examples
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Changing a fields visibility in a Rust library crate — keep fields encapsulated so the layout can evolve without breaking callers

What it does

Private Fields With Accessors is an agent skill from 0xMiden/protocol. Use when adding a public struct or changing a field's visibility in a Rust library crate — keep fields encapsulated so the layout can evolve without breaking callers.

Its SKILL.md is about 340 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

  • Adding a public struct
  • Changing a fields visibility in a Rust library crate — keep fields encapsulated so the layout can evolve without breaking callers

Example prompts

  • “/private-fields-with-accessors”

What it can do on your machine

Read from SKILL.md and the folder at commit 5f6a246. 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

Private Fields With Accessors loads about 335 tokens when it runs. Until then it costs about 49 tokens; SKILL.md has 107 words of instructions outside code blocks.

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

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 5f6a246, republished under its MIT licence (© 0xMiden). 107 words, ~335 tokens.

Download SKILL.mdSave it as .claude/skills/private-fields-with-accessors/SKILL.md (or your agent's skills folder).
name
private-fields-with-accessors
description
Use when adding a public struct or changing a field's visibility in a Rust library crate — keep fields encapsulated so the layout can evolve without breaking callers.

Keep Struct Fields Private; Expose Accessors

Rule

Public structs in library crates have private fields. Read access goes through an pub fn field(&self) -> &T accessor; mutation goes through dedicated methods (no pub fn field_mut).

Exceptions:

  • "Open" data types whose layout is part of the contract (e.g. Point { x, y }) may have public fields, but they should be #[non_exhaustive].
  • Internal/pub(crate) types may have public fields when keeping them private adds no value.

Why

Public fields freeze the representation: you can't rename, retype, split, or compute-on-read them without breaking every caller. An accessor lets a field become a computed expression in a later release with no one noticing.

Examples

rust
// Good
pub struct FungibleTokenMetadata {
    name: Box<str>,
    supply: u64,
}

impl FungibleTokenMetadata {
    pub fn name(&self) -> &str { &self.name }
    pub fn supply(&self) -> u64 { self.supply }
}

// Bad: every consumer locked to these field names and types forever
pub struct FungibleTokenMetadata {
    pub name: String,
    pub supply: u64,
}

© 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/private-fields-with-accessors of 0xMiden/protocol.

Open the folder on GitHubat commit 5f6a246

Compare with similar skills

Private Fields With Accessors 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.

Private Fields With Accessors compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Private Fields With Accessors this skill0xMiden/protocol133—~335Automated safety check: PassMIT
Migrate Core Code to Submodulestinyhumansai/openhuman42k—~2.6kAutomated safety check: PassGPL-3.0
OpenLogi macOS Permissions TriageAprilNEA/OpenLogi23k—~2.5kAutomated safety check: NotesApache-2.0
Rust Best Practicesfarm-fe/farm5.6k3 repos~1.1kAutomated safety check: PassMIT
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.

    42k GitHub stars~2.6k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • 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 yesterday
    DevelopmentAuto-check: notes
  • 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
  • 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 35 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
  • Keep CHANGELOG.md entries to a single concise sentence. An agent skill from 0xMiden/protocol.

    133 GitHub stars~805 tokensUpdated yesterday
    Auto-check passed
  • 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
  • Conversion Method Naming

    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.

    133 GitHub stars~450 tokensUpdated yesterday
    Auto-check passed
  • 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

Works with

Categories

Questions about Private Fields With Accessors

What does Private Fields With Accessors do?

A skill your agent uses when adding a public struct or changing a field's visibility in a Rust library crate — keep fields encapsulated so the layout can evolve without breaking callers. Private Fields With Accessors is an agent skill from 0xMiden/protocol. Use when adding a public struct or changing a field's visibility in a Rust library crate — keep fields encapsulated so the layout can evolve without breaking callers.

When should I use Private Fields With Accessors?

Private Fields With Accessors fits situations like: adding a public struct; changing a fields visibility in a Rust library crate — keep fields encapsulated so the layout can evolve without breaking callers.

How do I install Private Fields With Accessors in Claude Code?

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

How do I install Private Fields With Accessors in Codex?

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

Can I use Private Fields With Accessors 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 private-fields-with-accessors -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/private-fields-with-accessors, .gemini/skills/private-fields-with-accessors, .github/skills/private-fields-with-accessors and .opencode/skills/private-fields-with-accessors in your project.

What does Private Fields With Accessors need to run?

SKILL.md names no scripts, command-line tools or credentials: Private Fields With Accessors is instructions for the agent only.

Does Private Fields With Accessors 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 Private Fields With Accessors 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 Private Fields With Accessors use?

Private Fields With Accessors 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 Private Fields With Accessors use?

About 335 tokens (SKILL.md is roughly 1.3k 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 Private Fields With Accessors?

Skills that share tags, products or a category with Private Fields With Accessors: Migrate Core Code to Submodules (tinyhumansai/openhuman, 42k stars), OpenLogi macOS Permissions Triage (AprilNEA/OpenLogi, 23k stars), Rust Best Practices (farm-fe/farm, 5.6k 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 Private Fields With Accessors?

0xMiden (a GitHub organization) maintains it in 0xMiden/protocol, which has 133 GitHub stars. The repository holds 35 skills in this directory. The repository was last updated on October 8, 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.