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

Rust Tracing Practices

by hashintel in hashintel/hash

HASH tracing and instrumentation practices for Rust. An agent skill from hashintel/hash.

AGPL-3.0Auto-check passedDevelopment

Install Rust Tracing Practices

skills CLI
$ npx skills add hashintel/hash --skill rust-tracing-practices -a claude-code

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

GitHub CLI
$ gh skill install hashintel/hash rust-tracing-practices --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/hashintel/hash.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/rust-tracing-practices .claude/skills/rust-tracing-practices && 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
rust-tracing-practices
GitHub stars
1.7k
Token cost
~606 tokens
SKILL.md length
184 words
Files
1
Skills in repo
17
Repo updated
First seen
Licence
AGPL-3.0

At a glance

HASH tracing and instrumentation practices for Rust. An agent skill from hashintel/hash.

  • [tracing::instrument] to Rust code
  • SKILL.md covers Event Recording and Instrumentation
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Rust Tracing Practices is an agent skill from hashintel/hash. HASH tracing and instrumentation practices for Rust. Use when adding spans, events, or [tracing::instrument] to Rust code.

Its SKILL.md is about 610 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: 🚀 The open-source, multi-tenant platform for self-building knowledge graphs and simulation. The licence is AGPL-3.0.

When your agent uses it

  • [tracing::instrument] to Rust code

Example prompts

  • “/rust-tracing-practices”

What it can do on your machine

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

Rust Tracing Practices loads about 606 tokens when it runs. Until then it costs about 37 tokens; SKILL.md has 184 words of instructions outside code blocks.

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

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 hashintel/hash at commit e189ab2, republished under its AGPL-3.0 licence (© hashintel). 184 words, ~606 tokens.

Download SKILL.mdSave it as .claude/skills/rust-tracing-practices/SKILL.md (or your agent's skills folder).
name
rust-tracing-practices
description
HASH tracing and instrumentation practices for Rust. Use when adding spans, events, or #[tracing::instrument] to Rust code.
license
AGPL-3.0

Rust Tracing Practices

Event Recording

  • Use level-specific macros for appropriate visibility: info!, debug!, trace!, warn!, error!
  • Provide structured data as named arguments to facilitate automated processing and filtering
  • Prefer lowercase log-message prose while preserving identifier and acronym spelling
  • Record ordinary error values with Display, using %error or error = %error
  • Record an error_stack::Report<Context> with Debug, using ?report or error = ?report on the complete report rather than its current_context() alone
  • Keep public-response sanitization separate from diagnostic reporting. Debug formatting does not itself redact sensitive data
  • Include relevant context through key-value pairs

These fragments assume a local user. Their error events are alternatives: e is an ordinary error value, and report is an error_stack::Report<_>.

rust
tracing::info!(user_id = user.id, action = "login", "user logged in successfully");
tracing::error!(error = %e, user_id = user.id, "failed to authenticate user");
tracing::error!(error = ?report, user_id = user.id, "failed to authenticate user");

A report's plain Display stops after the first context and omits attachments. Its Debug formatter traverses the frames and renders printable attachments or installed hook output.

Instrumentation

  • Apply the #[tracing::instrument] attribute to functions to automatically create trace spans
  • When an error return merits an automatic event, use err for an ordinary error and err(Debug) for an error_stack::Report<Context>
  • Exclude sensitive or large parameters using skip(password) or skip_all
  • Add custom context fields with fields(request_id = req.id())
rust
#[tracing::instrument(level = "debug", err, skip(password), fields(user_id = user.id))]
async fn authenticate_user(user: &User, password: &[u8]) -> Result<AuthToken, AuthError> {
    // Implementation
}

© hashintel, AGPL-3.0. 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 .agents/skills/rust-tracing-practices of hashintel/hash.

Open the folder on GitHubat commit e189ab2

Compare with similar skills

Rust Tracing Practices 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.

Rust Tracing Practices compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Rust Tracing Practices this skillhashintel/hash1.7k—~606Automated safety check: PassAGPL-3.0
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 today
    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 3 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 today
    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 today
    DevelopmentAuto-check passed

More from hashintel/hash

All 17 skills in this repo

  • Documenting Rust Code

    hashintel/hash

    Rust documentation practices for HASH codebase. An agent skill from hashintel/hash.

    1.7k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Handling Rust Errors

    hashintel/hash

    HASH error handling patterns using error-stack crate. An agent skill from hashintel/hash.

    1.7k GitHub stars~1k tokensUpdated today
    Auto-check passed

  • Managing Cargo Dependencies

    hashintel/hash

    Cargo.toml dependency management patterns for HASH workspace.

    1.7k GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • Testing Hashql

    hashintel/hash

    HashQL testing strategies including compiletest (UI tests), unit tests, and snapshot tests.

    1.7k GitHub stars~1.9k tokensUpdated today
    Auto-check passed

  • Writing Hashql Diagnostics

    hashintel/hash

    HashQL diagnostic writing patterns using hashql-diagnostics crate.

    1.7k GitHub stars~724 tokensUpdated today
    Auto-check passed

  • Writing Hashql Jexpr

    hashintel/hash

    HashQL J-Expr syntax for writing queries. An agent skill from hashintel/hash.

    1.7k GitHub stars~1.2k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Rust Tracing Practices

What does Rust Tracing Practices do?

HASH tracing and instrumentation practices for Rust. An agent skill from hashintel/hash. Rust Tracing Practices is an agent skill from hashintel/hash. HASH tracing and instrumentation practices for Rust.

When should I use Rust Tracing Practices?

Rust Tracing Practices fits situations like: [tracing::instrument] to Rust code.

How do I install Rust Tracing Practices in Claude Code?

Run `npx skills add hashintel/hash --skill rust-tracing-practices -a claude-code`. Or copy the skill folder (.agents/skills/rust-tracing-practices in hashintel/hash) into .claude/skills/rust-tracing-practices in your project. Claude Code loads it when a task matches its description.

How do I install Rust Tracing Practices in Codex?

Run `npx skills add hashintel/hash --skill rust-tracing-practices -a codex`. Or copy the skill folder (.agents/skills/rust-tracing-practices in hashintel/hash) into .agents/skills/rust-tracing-practices in your project. Codex loads it when a task matches its description.

Can I use Rust Tracing Practices 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 hashintel/hash --skill rust-tracing-practices -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/rust-tracing-practices, .gemini/skills/rust-tracing-practices, .github/skills/rust-tracing-practices and .opencode/skills/rust-tracing-practices in your project.

What does Rust Tracing Practices need to run?

SKILL.md names no scripts, command-line tools or credentials: Rust Tracing Practices is instructions for the agent only.

Does Rust Tracing Practices 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 Rust Tracing Practices 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 Rust Tracing Practices use?

Rust Tracing Practices is published under the AGPL-3.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Rust Tracing Practices use?

About 606 tokens (SKILL.md is roughly 2.4k 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 Rust Tracing Practices?

Skills that share tags, products or a category with Rust Tracing Practices: 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 Rust Tracing Practices?

hashintel (a GitHub organization) maintains it in hashintel/hash, which has 1,668 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on October 7, 2026.

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