M02 Resource
CheckedThis skill retrieves and manages resources (like files & links) for your project, streamlining workflow and ensuring easy access to necessary assets.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add actionbook/rust-skills --skill m02-resource -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
actionbook
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned actionbook/rust-skills at 5c40d3ad78.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 5c40d3ad78
- Manifest
- skills/m02-resource/SKILL.md
- Scanned
- 1 file, 154 lines
About this skill
What it does
The M02 Resource skill assists with managing resources, specifically focusing on choosing appropriate smart pointers in Rust code. It guides users through a decision-making process to determine the correct ownership pattern and thread safety requirements for data structures, helping prevent common errors like memory leaks or runtime panics. This skill doesn't directly manage files or links; it helps developers select the right tools (smart pointers) for managing those resources within their code.
When to use it
- When deciding between
Box,Rc,Arc, andWeaksmart pointers in Rust. - To troubleshoot memory management issues like potential reference cycles or unexpected panics.
- When needing to determine if shared ownership is required, and whether multi-threading needs to be supported.
- For understanding the implications of interior mutability using
CellorRefCell.
Key capabilities
- Provides guidance on choosing smart pointers based on ownership (single vs. shared) and thread safety requirements.
- Offers a decision flowchart for selecting appropriate pointer types (
Box,Rc,Arc,Weak,Cell,RefCell). - Suggests solutions to common errors related to memory management and interior mutability.
- References other skills (m07-concurrency, m03-mutability, m12-lifecycle) for deeper dives into specific areas.
Example prompts
- "I need a single owner heap data structure – what should I use?"
- "How do I avoid memory leaks when using shared ownership?"
- "What's the difference between
RcandArc, and when should I use each?"
Tips & gotchas
- This skill focuses on smart pointer selection in Rust, not general resource management.
- Understanding Rust’s ownership model is crucial for effectively using this skill.
- Consider the concurrency model (single-threaded vs. multi-threaded) as it significantly impacts the choice of smart pointers.