New: 98,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

Logging Sucks

by elithrar in elithrar/dotfiles

Design or review structured application logging, canonical request events, correlation, redaction, and sampling.

MITAuto-check passedDevelopment

Install Logging Sucks

skills CLI
$ npx skills add elithrar/dotfiles --skill logging-sucks -a claude-code

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

GitHub CLI
$ gh skill install elithrar/dotfiles logging-sucks --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/elithrar/dotfiles.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/logging-sucks .claude/skills/logging-sucks && 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-sucks
GitHub stars
202
Token cost
~720 tokens
SKILL.md length
347 words
Files
3 (incl. references)
Skills in repo
12
Repo updated
First seen
Licence
MIT

At a glance

Design or review structured application logging, canonical request events, correlation, redaction, and sampling.

  • Changing logging instrumentation
  • SKILL.md covers Event design, Privacy and cost and Review and validation
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Auditing log quality

What it does

Logging Sucks is an agent skill from elithrar/dotfiles. Design or review structured application logging, canonical request events, correlation, redaction, and sampling. Use when changing logging instrumentation or auditing log quality, not for every debugging task.

Its SKILL.md is about 720 tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `evals/evals.json` and `references/event-design.md`).

It sits in Development. The repository describes itself as: dotfiles for my macOS & Linux environments ⌨️. The licence is MIT.

When your agent uses it

  • Changing logging instrumentation
  • Auditing log quality
  • Not for every debugging task

Example prompts

  • “/logging-sucks”

What it can do on your machine

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

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

  • Network

    Links to these hosts (documentation or services it may open):

    • loggingsucks.com

    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 Sucks loads about 720 tokens when it runs, and up to ~1.1k if it reads all its reference files. Until then it costs about 56 tokens; SKILL.md has 347 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~56
When it runs · the whole SKILL.md, loaded when a task matches
~720
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.1k

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 elithrar/dotfiles at commit e007b24, republished under its MIT licence (© elithrar). 347 words, ~720 tokens.

Download SKILL.mdSave it as .claude/skills/logging-sucks/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
logging-sucks
description
Design or review structured application logging, canonical request events, correlation, redaction, and sampling. Use when changing logging instrumentation or auditing log quality, not for every debugging task.
license
MIT
metadata.source
https://loggingsucks.com/
metadata.author
Boris Tane

Structured request logging

Adapted from Boris Tane's logging guide. Preserve the existing logger, transport, field schema, and runtime constraints unless changing them is part of the request.

Event design

Start with the incident question the logs must answer. Prefer a canonical completion event for each request or job when the runtime can emit it reliably. Accumulate outcome, duration, correlation, and relevant domain context during execution. Retain separate events for independently actionable failures, long-running progress, or required audit records; do not force every event into a single request summary.

Use the logger's structured fields and established naming conventions. Include a stable event name, severity, timestamp, service, and outcome where applicable, reusing metadata the platform already supplies. Attach request, trace, or job identifiers when available and appropriate. Use only fields that answer a concrete query; there is no field-count target.

Propagate correlation through HTTP, queues, and asynchronous jobs using the runtime's supported mechanism. Avoid mutable global context that can leak identifiers between concurrent requests.

Privacy and cost

Allowlist useful context and redact before emission. Do not serialize full request objects, credentials, cookies, raw bodies, private URLs, or personal data merely because they are available. Include permitted identifiers according to the product's data policy and retention needs. Bound event sizes and avoid logs in tight loops.

Choose retention and sampling from the actual traffic, budget, and incident needs. Favor retaining errors and diagnostically useful slow requests, but do not mandate 100% retention, VIP tracking, or a fixed success-sampling rate. Account for crashes or cancellations that can prevent completion events from being emitted.

For a concrete event schema or sampling design, read references/event-design.md.

Review and validation

For an audit, report evidence-backed findings without editing. For requested instrumentation changes, implement them and check the affected success, failure, or concurrency path. Verify correlation isolation, redaction, and emission behavior where the change puts them at risk. Once those checks pass, stop optional validation.

Report the incident query enabled by the change and any remaining visibility gap. Do not replace the logging stack or rewrite unrelated call sites solely to enforce this skill's preferred pattern.

© elithrar, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in .agents/skills/logging-sucks of elithrar/dotfiles.

  • SKILL.md
  • evals/evals.json
  • references/event-design.md

Open the folder on GitHubat commit e007b24

Compare with similar skills

Logging Sucks 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 Sucks compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Logging Sucks this skillelithrar/dotfiles202—~720Automated safety check: PassMIT
Vercel Composition Patternssupabase/supabase111k58 repos~726Automated safety check: PassMIT
Finishing a Development Branchobra/superpowers297k5 repos~1.9kAutomated safety check: PassMIT
Typescript Advanced Typesrolling-scopes/rsschool-app10k25 repos~4.2kAutomated safety check: PassMPL-2.0
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Code Review ChecklistshareAI-lab/learn-claude-code78k5 repos~1.1kAutomated safety check: PassMIT

Similar skills

  • Vercel Composition Patterns

    supabase/supabase

    Official

    React composition patterns that scale. An agent skill from supabase/supabase.

    111k GitHub starsUsed in 58 repos~726 tokens
    DevelopmentAuto-check passed

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

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

  • Typescript Advanced Types

    rolling-scopes/rsschool-app

    Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.

    10k GitHub starsUsed in 25 repos~4.2k tokens
    DevelopmentAuto-check passed

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k 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

  • Greploop

    onyx-dot-app/onyx

    Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.

    32k GitHub starsUsed in 4 repos~3.3k tokens
    DevelopmentAuto-check passed

More from elithrar/dotfiles

All 12 skills in this repo

  • Prompt Engineer

    elithrar/dotfiles

    Audit and revise system prompts, developer instructions, tool descriptions, and reusable LLM prompt templates.

    202 GitHub stars~1.7k tokensUpdated yesterday
    Auto-check passed

  • Code Reviewer

    elithrar/dotfiles

    Review a specified code change for actionable defects. An agent skill from elithrar/dotfiles.

    202 GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

  • Cut Ready

    elithrar/dotfiles

    Prepare or review CAD and vector artwork for physical fabrication, cutting, printing, or machining.

    202 GitHub stars~1.9k tokensUpdated yesterday
    Auto-check passed

  • Motronic

    elithrar/dotfiles

    Diagnose Porsche Carrera 3.2 Bosch Motronic faults and interpret DME ROMs or calibration changes.

    202 GitHub stars~753 tokensUpdated yesterday
    Auto-check passed

  • Neo Industrial Design

    elithrar/dotfiles

    Design or restyle web interfaces in the user's neo-industrial or editorial-brutalist style.

    202 GitHub stars~940 tokensUpdated yesterday
    Auto-check passed

  • Web Perf

    elithrar/dotfiles

    Diagnose page-load and interaction performance using browser traces, network evidence, and source code.

    202 GitHub stars~721 tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Logging Sucks

What does Logging Sucks do?

Design or review structured application logging, canonical request events, correlation, redaction, and sampling. Logging Sucks is an agent skill from elithrar/dotfiles. Design or review structured application logging, canonical request events, correlation, redaction, and sampling.

When should I use Logging Sucks?

Logging Sucks fits situations like: changing logging instrumentation; auditing log quality; not for every debugging task.

How do I install Logging Sucks in Claude Code?

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

How do I install Logging Sucks in Codex?

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

Can I use Logging Sucks 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 elithrar/dotfiles --skill logging-sucks -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-sucks, .gemini/skills/logging-sucks, .github/skills/logging-sucks and .opencode/skills/logging-sucks in your project.

What does Logging Sucks need to run?

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

Does Logging Sucks access the network?

SKILL.md names 1 domain. As links in the text: loggingsucks.com. This is read from the text; nothing was executed.

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

Logging Sucks is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Logging Sucks use?

About 720 tokens (SKILL.md is roughly 2.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 401 tokens, read only when the agent opens those files.

What are the alternatives to Logging Sucks?

Skills that share tags, products or a category with Logging Sucks: Vercel Composition Patterns (supabase/supabase, 111k stars), Finishing a Development Branch (obra/superpowers, 297k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars) and PR Babysitter (openinterpreter/openinterpreter, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Logging Sucks?

elithrar (a GitHub user) maintains it in elithrar/dotfiles, which has 202 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on October 8, 2026.

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