skills.rest
sparq-org
sparq-orgOFFICIAL
Explore all skills by this author →
GitHub

unsafe-rust-attestation

Document and verify unsafe Rust code blocks within the Sparq project.

8|1|Updated Jun 7, 2026
Search Tags:#memory safety#Rust#Miri#unsafe code#Sparq
One-click install
npx skills add https://github.com/sparq-org/sparq --skill unsafe-rust-attestation
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: unsafe-rust-attestation
Source: https://github.com/sparq-org/sparq/tree/main/.claude/skills/unsafe-rust-attestation
Command: npx skills add https://github.com/sparq-org/sparq --skill unsafe-rust-attestation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps developers attest memory safety in Rust code, focusing on the Sparq project's approach to unsafe code handling.

Core Features & Use Cases

  • Memory Safety Attestation: Provides guidelines and tools for documenting and verifying unsafe code blocks in Rust, specifically within the Sparq project.
  • Use Case: Developers can use this Skill to understand Sparq's stance on memory safety, including the use of 'forbid(unsafe_code)', the Sparq-core unsafe surface, and the use of tools like Miri for verification.

Quick Start

Use the unsafe-rust-attestation skill to get an overview of Sparq's memory safety posture and the process of documenting unsafe code blocks.

Frequently Asked Questions about unsafe-rust-attestation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I attest memory safety for unsafe Rust code blocks?▼

Attesting memory safety involves documenting and verifying unsafe Rust code blocks, specifically by adhering to Sparq's forbid(unsafe_code) stance and using Miri to verify the Sparq-core unsafe surface.

What is Sparq's approach to handling unsafe Rust code?▼

Sparq's approach enforces a forbid(unsafe_code) stance project-wide while managing a specific Sparq-core unsafe surface that requires explicit documentation and memory safety verification.

How does Miri verify memory safety in Rust?▼

Miri verifies memory safety in Rust by executing unsafe code blocks to detect undefined behavior, serving as the verification tool for validating the Sparq-core unsafe surface.

Do I need knowledge of the Sparq codebase to document unsafe Rust blocks?▼

Yes, attesting memory safety requires knowledge of the Sparq codebase and Rust's unsafe features to properly document unsafe blocks and navigate the Sparq-core unsafe surface.

What are the limitations of using forbid(unsafe_code) for memory safety?▼

Forbid(unsafe_code) limits memory safety attestation to the Sparq-core unsafe surface, requiring manual documentation and Miri verification for unavoidable unsafe blocks rather than eliminating them project-wide.

Related Skills

Explore More Software Engineering Skills→
po4ykapo4yka
58

rust-sanitizers-miri

Detect undefined behavior in Rust with Miri and sanitizers.

Community
Advanced
sammcjsammcj
155

rust-engineer

Analyze Rust workspace and Cargo configuration for safety and performance constraints.

Community
Advanced
po4ykapo4yka
58

rust-unsafe

Audit unsafe Rust usage across RIPDPI crates for safety invariants.

Community
Advanced
flexisuite-orgflexisuite-org

unsafe-checker

Analyze unsafe Rust code for FFI and memory safety risks.

Official
Advanced