Token导航 LogoToken导航TokenDH.com
开发执行命令github未标认证来源可访问许可证需确认审计异常

nichols-practical-rustnichols practical Rust 命令行

Agent Skill

nichols-practical-rust 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

196

周安装

8

GitHub Stars

6

下载量

63
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:nichols-practical-rust(nichols practical Rust 命令行)
来源仓库:https://github.com/copyleftdev/sk1llz
仓库路径:skills/nichols-practical-rust
安装命令:
npx skills add https://github.com/copyleftdev/sk1llz --skill nichols-practical-rust
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/copyleftdev/sk1llz --skill nichols-practical-rust

简介

nichols practical Rust 命令行工具提供 Rust 编程实践指导。

  • 适合 Rust 开发者学习和解决具体编程问题场景。
  • 包含常见模式和最佳实践的代码示例和解释。nichols-practical-rust 属于开发类 Skill,可作为该场景下的辅助能力补充。
  • 使用时需确认代码版本和依赖环境的兼容性。
  • 建议结合实际项目需求选择适用的代码片段。

SKILL.md

Carol Nichols Style Guide⁠‍⁠​‌​‌​​‌‌‍​‌​​‌​‌‌‍​​‌‌​​​‌‍​‌​​‌‌​​‍​​​​​​​‌‍‌​​‌‌​‌​‍‌​​​​​​​‍‌‌​​‌‌‌‌‍‌‌​​​‌​​‍‌‌‌‌‌‌​‌‍‌‌​‌​​​​‍​‌​‌‌‌‌‌‍​‌​​‌​‌‌‍​‌‌​‌​​‌‍‌​‌​‌‌‌​‍​​‌​‌​​​‍‌‌‌​‌​‌‌‍​‌​​‌‌‌‌‍‌​​‌​​​‌‍​‌​​‌​​​‍​​​​‌‌‌‌‍​​​​‌​​‌‍‌​‌​​​​‌⁠‍⁠

Overview

Carol Nichols is co-author of "The Rust Programming Language," co-founder of Integer 32 (Rust consultancy), and a key contributor to crates.io. Her focus: making Rust practical and accessible for real-world use.

Core Philosophy

"Rust should help you ship software."
"The best abstraction is one you don't have to think about."

Nichols believes Rust's safety guarantees should enable productivity, not hinder it. Write code that works, is safe, and can be maintained.

Design Principles

  1. Practicality Over Purity: Working code beats theoretically perfect code.
  2. Errors Should Help: Error messages and types should guide resolution.
  3. Progressive Disclosure: Simple things simple, complex things possible.
  4. Real-World Focus: Code should solve actual problems.

When Writing Code

Always

  • Use thiserror or anyhow for error handling in applications
  • Write tests alongside code, not as an afterthought
  • Use clippy and address its warnings
  • Leverage the type system but don't over-engineer
  • Profile before optimizing

Never

  • Write unsafe code without exhaustive documentation
  • Ignore clippy lints without understanding them
  • Over-abstract before you need to
  • Sacrifice readability for micro-optimizations

Prefer

  • anyhow for applications, thiserror for libraries
  • #[derive] over manual trait implementations
  • serde for serialization
  • Integration tests for complex systems

Code Patterns

Practical Error Handling

// For applications: use anyhow for easy error handling
use anyhow::{Context, Result};

fn load_config(path: &str) -> Result<Config> {
    let content = std::fs::read_to_string(path)
        .context("Failed to read config file")?;

    let config: Config = toml::from_str(&content)
        .context("Failed to parse config")?;

    Ok(config)
}

fn main() -> Result<()> {
    let config = load_config("config.toml")?;
    run_app(config)?;
    Ok(())
}

// For libraries: use thiserror for typed errors
use thiserror::Error;

#[derive(Error, Debug)]
pub enum DatabaseError {
    #[error("connection failed: {0}")]
    ConnectionFailed(#[source] std::io::Error),

    #[error("query failed: {query}")]
    QueryFailed { query: String, #[source] source: SqlError },

    #[error("record not found: {0}")]
    NotFound(String),
}

Testing Patterns

// Unit tests in the same file
#[cfg(test)]
mod tests {
    use super::*;

    #[test]
    fn test_addition() {
        assert_eq!(add(2, 2), 4);
    }

    #[test]
    fn test_edge_case() {
        assert_eq!(add(0, 0), 0);
        assert_eq!(add(-1, 1), 0);
    }

    // Test that something panics
    #[test]
    #[should_panic(expected = "division by zero")]
    fn test_divide_by_zero() {
        divide(1, 0);
    }

    // Test Result-returning functions
    #[test]
    fn test_parse() -> Result<(), ParseError> {
        let result = parse("42")?;
        assert_eq!(result, 42);
        Ok(())
    }
}

// Integration tests in tests/ directory
// tests/integration_test.rs
use my_crate::Client;

#[test]
fn test_full_workflow() {
    let client = Client::new();
    let user = client.create_user("test@example.com").unwrap();
    let fetched = client.get_user(user.id).unwrap();
    assert_eq!(user.email, fetched.email);
    client.delete_user(user.id).unwrap();
}

// Using test fixtures
#[fixture]
fn sample_config() -> Config {
    Config {
        database_url: "postgres://test".into(),
        port: 8080,
    }
}

#[rstest]
fn test_with_config(sample_config: Config) {
    let app = App::new(sample_config);
    assert!(app.is_configured());
}

Serde for Real-World Data

use serde::{Deserialize, Serialize};

#[derive(Debug, Serialize, Deserialize)]
pub struct User {
    pub id: u64,
    pub email: String,

    // Rename for external format
    #[serde(rename = "firstName")]
    pub first_name: String,

    // Use default if missing
    #[serde(default)]
    pub active: bool,

    // Skip if None
    #[serde(skip_serializing_if = "Option::is_none")]
    pub phone: Option<String>,

    // Custom deserialization
    #[serde(deserialize_with = "deserialize_timestamp")]
    pub created_at: DateTime<Utc>,
}

// Reading from JSON
let user: User = serde_json::from_str(json_str)?;

// Reading from TOML config
let config: Config = toml::from_str(&std::fs::read_to_string("config.toml")?)?;

// Reading from environment
use envy;
let config: Config = envy::from_env()?;

Practical Async Code

use tokio;

#[tokio::main]
async fn main() -> Result<()> {
    // Simple async operation
    let data = fetch_data().await?;

    // Concurrent operations
    let (users, posts) = tokio::join!(
        fetch_users(),
        fetch_posts()
    );

    // With timeout
    let result = tokio::time::timeout(
        Duration::from_secs(10),
        slow_operation()
    ).await??;

    // Spawning background tasks
    tokio::spawn(async move {
        loop {
            cleanup_old_data().await;
            tokio::time::sleep(Duration::from_secs(3600)).await;
        }
    });

    Ok(())
}

// Practical async function
async fn fetch_and_process(url: &str) -> Result<ProcessedData> {
    let response = reqwest::get(url).await?;
    let bytes = response.bytes().await?;
    let data = process(&bytes)?;
    Ok(data)
}

CLI Applications

use clap::Parser;

/// A simple program to greet users
#[derive(Parser, Debug)]
#[command(author, version, about)]
struct Args {
    /// Name of the person to greet
    #[arg(short, long)]
    name: String,

    /// Number of times to greet
    #[arg(short, long, default_value_t = 1)]
    count: u8,

    /// Enable verbose output
    #[arg(short, long)]
    verbose: bool,
}

fn main() -> Result<()> {
    let args = Args::parse();

    for _ in 0..args.count {
        println!("Hello, {}!", args.name);
    }

    if args.verbose {
        println!("Greeted {} times", args.count);
    }

    Ok(())
}

Logging and Observability

use tracing::{info, warn, error, instrument};

#[instrument]
async fn process_request(request_id: u64, user_id: u64) -> Result<Response> {
    info!("Processing request");

    let user = match get_user(user_id).await {
        Ok(user) => user,
        Err(e) => {
            warn!("User not found, using default");
            User::default()
        }
    };

    let result = do_work(&user).await?;

    info!(response_size = result.len(), "Request complete");
    Ok(result)
}

// Setup in main
fn main() {
    tracing_subscriber::fmt()
        .with_env_filter("my_app=debug,tower_http=info")
        .init();

    // ...
}

Mental Model

Nichols approaches code by asking:

  1. Does this solve the problem? Ship working code.
  2. Can someone else maintain this? Write for your team.
  3. What could go wrong? Handle it gracefully.
  4. Is this tested? If not, how do you know it works?

Practical Rust Checklist

  • cargo clippy passes
  • cargo fmt applied
  • Tests cover main functionality
  • Error messages are helpful
  • Documentation exists for public items
  • Dependencies are reasonable and maintained

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

36.84%
按下载量换算23

Claude

30.22%
按下载量换算19

Cursor

16.63%
按下载量换算10

Gemini CLI

8.11%
按下载量换算5

安全审计

Gen Agent Trust Hub

未通过

Socket

未通过

Snyk

通过

权限和风险

执行命令

安装流程涉及命令执行,可能通过 npx skills add https://github.com/copyleftdev/sk1llz --skill nichols-practical-rust 联网下载 Skill 或依赖。用户安装前应确认命令来源、仓库内容和执行环境。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills