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

Instrumentation

by Moosync in Moosync/Moosync

Hermetic tracing instrumentation rules and validation. An agent skill from Moosync/Moosync.

GPL-3.0Auto-check passedDevelopment

Install Instrumentation

skills CLI
$ npx skills add Moosync/Moosync --skill instrumentation -a claude-code

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

GitHub CLI
$ gh skill install Moosync/Moosync instrumentation --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/Moosync/Moosync.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/instrumentation .claude/skills/instrumentation && 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
instrumentation
GitHub stars
259
Token cost
~570 tokens
SKILL.md length
219 words
Files
1
Skills in repo
5
Repo updated
First seen
Licence
GPL-3.0

At a glance

Hermetic tracing instrumentation rules and validation. An agent skill from Moosync/Moosync.

  • Works in 2 steps: Instrumentation on All Functions: Every… → Skip All Parameters (skip_all): To…
  • Development work in your project
  • SKILL.md covers Description, Requirements, Commands and Git Pre-Commit Hook Integration
  • Calls bazel, python3 and git

What it does

Instrumentation is an agent skill from Moosync/Moosync. Hermetic tracing instrumentation rules and validation. Covers the requirement for

Its SKILL.md is about 570 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 Git. The licence is GPL-3.0.

When your agent uses it

  • Development work in your project

Example prompts

  • “/instrumentation”

Requirements

  • Python 3

Workflow steps

2 steps, taken from the first numbered list in SKILL.md.

  1. Instrumentation on All Functions: Every function definition (with a body) must have a #[tracing::instrument] attribute, unless it is
  2. Skip All Parameters (skip_all): To prevent compilation errors caused by non-Debug types (such as JNIEnv, callbacks, closures, platform…

What it can do on your machine

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

    Shell commands in SKILL.md call:

    • bazel
    • python3
    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    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

Instrumentation loads about 570 tokens when it runs. Until then it costs about 24 tokens; SKILL.md has 219 words of instructions outside code blocks.

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

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 Moosync/Moosync at commit a2b81ce, republished under its GPL-3.0 licence (© Moosync). 219 words, ~570 tokens.

Download SKILL.mdSave it as .claude/skills/instrumentation/SKILL.md (or your agent's skills folder).
name
instrumentation
description
Hermetic tracing instrumentation rules and validation. Covers the requirement for

Instrumentation Skill

Description

The Instrumentation skill enforces logging best practices in the Moosync repository. To preserve stack traces and keep execution flows observable, every function definition in Rust source files must be decorated with the #[tracing::instrument] attribute.

Requirements

  1. Instrumentation on All Functions: Every function definition (with a body) must have a #[tracing::instrument] attribute, unless it is:
    • A test function or inside a test module (e.g., mod tests).
    • A trait declaration signature (without a body).
    • A common built-in trait method: main, default, from, into, try_from, fmt, clone, drop.
  2. Skip All Parameters (skip_all): To prevent compilation errors caused by non-Debug types (such as JNIEnv, callbacks, closures, platform context objects, or dyn trait objects), always skip all function parameters using skip_all.
Preferred Pattern:
rust
#[tracing::instrument(level = "debug", skip_all)]
pub fn my_function(param1: NonDebugClosure, param2: JniContext) -> Result<(), MyError> {
    // ...
}

Commands

CommandDescriptionExample
Verify InstrumentationRuns recursive checks on all .rs files to find missing instrumentation.bazel run //tools:check_instrument
Fix Skips/InstrumentationProgrammatically updates all tracing::instrument attributes to standardized skip_all.python3 tools/fix_instrumentation_skips.py

Git Pre-Commit Hook Integration

The instrumentation check is integrated into the Git pre-commit hook:

  • When you stage any .rs or .slint files and run git commit, the pre-commit hook (located in .git/hooks/pre-commit) runs bazel run //tools:check_instrument.
  • If any function is missing the instrumentation attribute, the pre-commit hook fails with exit code 1 and blocks the commit, reporting the exact files and line numbers needing attention.

© Moosync, GPL-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/instrumentation of Moosync/Moosync.

Open the folder on GitHubat commit a2b81ce

Compare with similar skills

Instrumentation 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.

Instrumentation compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Instrumentation this skillMoosync/Moosync259—~570Automated safety check: PassGPL-3.0
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT
Code Review ChecklistshareAI-lab/learn-claude-code78k5 repos~1.1kAutomated safety check: PassMIT
Codebase Knowledge Graph Q&AEgonex-AI/Understand-Anything85k1 repos~1.2kAutomated safety check: PassMIT
Code Design Rationale Investigatorcursor/plugins10k9 repos~2.6kAutomated safety check: PassNone
Understand Diff AnalysisEgonex-AI/Understand-Anything85k1 repos~1.4kAutomated safety check: PassMIT

Similar skills

  • Finishing a Development Branch

    obra/superpowers

    Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    296k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed

  • Code Review Checklist

    shareAI-lab/learn-claude-code

    Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.

    78k GitHub starsUsed in 5 repos~1.1k tokens
    DevelopmentAuto-check passed

  • Codebase Knowledge Graph Q&A

    Egonex-AI/Understand-Anything

    Answers questions about a codebase by searching a prebuilt knowledge graph of its files, functions, classes and dependencies, not by rereading every source file.

    85k GitHub starsUsed in 1 repo~1.2k tokens
    DevelopmentAuto-check passed

  • Code Design Rationale Investigator

    cursor/plugins

    Official

    Digs into why code is shaped the way it is by checking git history, pull requests and connected tools in parallel, then reporting a cited read on the tradeoffs.

    10k GitHub starsUsed in 9 repos~2.6k tokens
    DevelopmentAuto-check passed

  • Understand Diff Analysis

    Egonex-AI/Understand-Anything

    Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.

    85k GitHub starsUsed in 1 repo~1.4k tokens
    DevelopmentAuto-check passed

  • Understand Explain

    Egonex-AI/Understand-Anything

    Gives an in-depth explanation of one file, function or module by reading the project's knowledge graph and checking that the graph is still fresh.

    85k GitHub starsUsed in 1 repo~1.3k tokens
    DevelopmentAuto-check passed

More from Moosync/Moosync

  • Bazel

    Moosync/Moosync

    Hermetic Bazel build, test, and packaging commands for the Moosync project.

    259 GitHub stars~722 tokensUpdated 5 days ago
    Auto-check passed

  • Moosync

    Moosync/Moosync

    Project-wide helpers for adding new features to Moosync. An agent skill from Moosync/Moosync.

    259 GitHub stars~2.5k tokensUpdated 5 days ago
    Auto-check passed

  • Rust

    Moosync/Moosync

    Hermetic Rust crate building, testing, and formatting via Bazel targets.

    259 GitHub stars~665 tokensUpdated 5 days ago
    Auto-check passed

  • Slint

    Moosync/Moosync

    Expert guidance for building, debugging, and working with Slint GUI applications.

    259 GitHub stars~2.4k tokensUpdated 5 days ago
    Auto-check passed

Works with

Categories

Questions about Instrumentation

What does Instrumentation do?

Hermetic tracing instrumentation rules and validation. An agent skill from Moosync/Moosync. Instrumentation is an agent skill from Moosync/Moosync. Hermetic tracing instrumentation rules and validation.

When should I use Instrumentation?

Instrumentation fits situations like: development work in your project.

How do I install Instrumentation in Claude Code?

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

How do I install Instrumentation in Codex?

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

Can I use Instrumentation 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 Moosync/Moosync --skill instrumentation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/instrumentation, .gemini/skills/instrumentation, .github/skills/instrumentation and .opencode/skills/instrumentation in your project.

What does Instrumentation need to run?

Going by SKILL.md and its folder, Instrumentation needs the command-line tools its instructions call (bazel, python3 and git). Our summary lists: Python 3.

Does Instrumentation access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Instrumentation 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 Instrumentation use?

Instrumentation is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Instrumentation use?

About 570 tokens (SKILL.md is roughly 2.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 Instrumentation?

Skills that share tags, products or a category with Instrumentation: Finishing a Development Branch (obra/superpowers, 296k stars), Code Review Checklist (shareAI-lab/learn-claude-code, 78k stars), Codebase Knowledge Graph Q&A (Egonex-AI/Understand-Anything, 85k stars) and Code Design Rationale Investigator (cursor/plugins, 10k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Instrumentation?

Moosync (a GitHub organization) maintains it in Moosync/Moosync, which has 259 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 1, 2026.

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