Agent skill

Logging

by y5-snowies in y5-snowies/nourish

How to log in the y5 compositor. An agent skill from y5-snowies/nourish.

Apache-2.0Auto-check passedDevOps & Cloud

Install Logging

skills CLI
$ npx skills add y5-snowies/nourish --skill logging -a claude-code

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

GitHub CLI
$ gh skill install y5-snowies/nourish logging --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/y5-snowies/nourish.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/logging .claude/skills/logging && 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
logging
GitHub stars
233
Token cost
~753 tokens
SKILL.md length
307 words
Files
1
Skills in repo
2
Repo updated
First seen
Licence
Apache-2.0

At a glance

How to log in the y5 compositor. An agent skill from y5-snowies/nourish.

  • Migrate logging — any time youd reach for a log/print statement
  • SKILL.md covers The rule, Wiring a crate to log…, Migrating tracing and Levels: two independent controls, plus 2 more sections
  • Calls npm
  • Tasks that involve Observability

What it does

Logging is an agent skill from y5-snowies/nourish. How to log in the y5 compositor. Use whenever you add, change, or migrate logging — any time you'd reach for a log/print statement, "add a log", debug output, tracing::!, println!, or a fatal panic! with a message. y5 has its own tracing-free structured logging; this skill is the source of truth for using it.

Its SKILL.md is about 750 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 DevOps & Cloud, covering Observability. It works with Linux. The repository describes itself as: Nourish OS. The modern way of using a computer. The licence is Apache-2.0.

When your agent uses it

  • Migrate logging — any time youd reach for a log/print statement
  • Tasks that involve Observability

Example prompts

  • “d reach for a log/print statement,”
  • “/logging”

What it can do on your machine

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

    • npm

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

  • Network

    No URLs in SKILL.md. Its commands use npm, 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

Logging loads about 753 tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 307 words of instructions outside code blocks.

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

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 y5-snowies/nourish at commit d6893ce, republished under its Apache-2.0 licence (© y5-snowies). 307 words, ~753 tokens.

Download SKILL.mdSave it as .claude/skills/logging/SKILL.md (or your agent's skills folder).
name
logging
description
How to log in the y5 compositor. Use whenever you add, change, or migrate logging — any time you'd reach for a log/print statement, "add a log", debug output, `tracing::*!`, `println!`, or a fatal `panic!` with a message. y5 has its own tracing-free structured logging; this skill is the source of truth for using it.

y5 logging

y5 has its own structured logging system. Never use tracing, log, or println!/ eprintln! for diagnostics in compositor code. Use the macros from compositor_model_debug_instance_record. Full reference: that crate's module docs (compositor.model/model.debug/debug.instance/instance.record).

The rule

  • Levels: error!, warn!, info!, trace! — same format! args as tracing.
  • Fatal: abort!("msg {x}") — logs at Error and panics (synchronously flushed first).
  • No tracing / log / tracing-subscriber deps in new/changed crates. If a crate you touch still imports them only for logging, migrate the call sites and drop the deps.

Wiring a crate to log (one-time per crate)

The add-crate template already inserts this. If a crate lacks it, add to its lib.rs (after any leading #![...] inner attributes):

rust
#[macro_use]
extern crate compositor_model_debug_instance_record;

and ensure its Cargo.toml has (it resolves via the workspace links — run compositor.workspace/link.all.sh if you just added the dep to a workspace that didn't have it):

toml
compositor_model_debug_instance_record = { workspace = true }

Then call the macros from any module in the crate — no per-module use needed. The crate name and function path are attached automatically as filter tags.

Migrating tracing

tracing::info!(...) → info!(...) (likewise error!/warn!/trace!). Confirm the two lib.rs lines above exist, then remove tracing + tracing-subscriber from the crate's Cargo.toml. Grep the crate for tracing:: to be sure none remain.

Levels: two independent controls

  • Compile-time: cargo features error/warn/info/trace on the record crate (set by the top-level execute dep). A disabled level compiles to nothing. abort! is never stripped.
  • Runtime: COMPOSITOR_LOG_LEVEL (e.g. info,warn,error,trace) selects what is emitted among compiled-in levels.

Viewing logs

Records stream over gRPC (/tmp/y5-compositor-logs.sock) to the compositor.developer/developer.tool Tauri viewer (filter by crate/function/level, timeline, presets, dumps). Run the compositor with COMPOSITOR_LOG_LEVEL set, then cd compositor.developer/developer.tool/developer.tool.window/logs && npm run tauri dev. They also print dmesg-style to the compositor's stderr.

Do NOT

  • Do not add tracing/log to Cargo.toml.
  • Do not println!/eprintln! for diagnostics (use info!/trace!).
  • Do not panic!("msg") for a logged fatal — use abort!("msg").
  • Do not hand-write a per-crate logger — instance!() is the only mechanism.

© y5-snowies, Apache-2.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 .claude/skills/logging of y5-snowies/nourish.

Open the folder on GitHubat commit d6893ce

Compare with similar skills

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

Logging compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Logging this skilly5-snowies/nourish233—~753Automated safety check: PassApache-2.0
Linux Troubleshooting with Inspektor Gadgetinspektor-gadget/inspektor-gadget2.9k—~2.4kAutomated safety check: NotesApache-2.0
Enterprise Agent Opsaffaan-m/ECC276k4 repos~384Automated safety check: PassMIT
Implementing Ebpf Security Monitoringmukul975/Anthropic-Cybersecurity-Skills34k—~2.4kAutomated safety check: NotesApache-2.0
Aliyun Sls Openclaw Integrationcinience/alicloud-skills397—~2.6kAutomated safety check: NotesMIT
Ebpfmohitmishra786/low-level-dev-skills253—~2.3kAutomated safety check: PassMIT

Similar skills

  • Linux Troubleshooting with Inspektor Gadget

    inspektor-gadget/inspektor-gadget

    Debugs a single Linux host or container runtime at the kernel level with the standalone ig binary and eBPF gadgets, read-only and without Kubernetes.

    2.9k GitHub stars~2.4k tokensUpdated today
    DevOps & CloudAuto-check: notes
  • Operational controls for long-lived or cloud-hosted agent systems — runtime lifecycle (start, pause, stop, restart), observability (logs, metrics, traces), least-privilege safety scopes and kill…

    276k GitHub starsUsed in 4 repos~384 tokens
    DevOps & CloudAuto-check passed
  • Implementing Ebpf Security Monitoring

    mukul975/Anthropic-Cybersecurity-Skills

    Implements eBPF-based security monitoring using Cilium Tetragon for real-time process execution tracking, network connection observability, file access auditing, and runtime enforcement.

    34k GitHub stars~2.4k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check: notes
  • Aliyun Sls Openclaw Integration

    cinience/alicloud-skills

    A skill your agent uses when the user needs to integrate OpenClaw with Alibaba Cloud SLS/Observability, including collector setup, machine groups, indexes, dashboards, collection configs, or Logtail…

    397 GitHub stars~2.6k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check: notes
  • Ebpf

    mohitmishra786/low-level-dev-skills

    eBPF skill for Linux observability and networking. An agent skill from mohitmishra786/low-level-dev-skills.

    253 GitHub stars~2.3k tokensUpdated 3 mo ago
    DevOps & CloudAuto-check passed
  • Eunomia Community Radar

    eunomia-bpf/eunomia.dev

    Monitor approved eBPF, Linux, observability, and AI-infrastructure communities through watchlist-opted-in read-only Slack archives plus ordinary visible browser UI, turn the strongest daily…

    236 GitHub stars~2.5k tokensUpdated today
    Knowledge ManagementAuto-check passed

More from y5-snowies/nourish

  • Add Crate

    y5-snowies/nourish

    Add a new member crate to a Cargo workspace in this repo using the y5-template binary.

    233 GitHub stars~1.5k tokensUpdated 1 mo ago
    Auto-check passed

Works with

Categories

Questions about Logging

What does Logging do?

How to log in the y5 compositor. An agent skill from y5-snowies/nourish. Logging is an agent skill from y5-snowies/nourish. How to log in the y5 compositor.

When should I use Logging?

Logging fits situations like: migrate logging — any time youd reach for a log/print statement; tasks that involve Observability.

How do I install Logging in Claude Code?

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

How do I install Logging in Codex?

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

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

What does Logging need to run?

Going by SKILL.md and its folder, Logging needs the command-line tools its instructions call (npm).

Does Logging access the network?

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

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

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

How many tokens does Logging use?

About 753 tokens (SKILL.md is roughly 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 Logging?

Skills that share tags, products or a category with Logging: Linux Troubleshooting with Inspektor Gadget (inspektor-gadget/inspektor-gadget, 2.9k stars), Enterprise Agent Ops (affaan-m/ECC, 276k stars), Implementing Ebpf Security Monitoring (mukul975/Anthropic-Cybersecurity-Skills, 34k stars) and Aliyun Sls Openclaw Integration (cinience/alicloud-skills, 397 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Logging?

y5-snowies (a GitHub organization) maintains it in y5-snowies/nourish, which has 233 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on September 4, 2026.

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