Agent skill

Debug Logging Assistant

by dmitriiweb in dmitriiweb/extract-emails

Add purposeful debug logging to improve observability without changing behavior.

MITAuto-check passedDevOps & Cloud

Install Debug Logging Assistant

skills CLI
$ npx skills add dmitriiweb/extract-emails --skill debug-logging-assistant -a claude-code

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

GitHub CLI
$ gh skill install dmitriiweb/extract-emails debug-logging-assistant --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/dmitriiweb/extract-emails.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/debug-logging-assistant .claude/skills/debug-logging-assistant && 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
debug-logging-assistant
GitHub stars
111
Token cost
~426 tokens
SKILL.md length
200 words
Files
2 (incl. references)
Skills in repo
8
Repo updated
First seen
Licence
MIT

At a glance

Add purposeful debug logging to improve observability without changing behavior.

  • Works in 4 steps: Inspect → Place logs → Write messages → …
  • Tasks that involve Observability
  • SKILL.md covers Quick start, Workflow and Reference
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Debug Logging Assistant is an agent skill from dmitriiweb/extract-emails. Add purposeful debug logging to improve observability without changing behavior.

Its SKILL.md is about 430 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/logging_rules.md`).

It sits in DevOps & Cloud, covering Observability. The repository describes itself as: Extract emails and links to linkedin accounts from URLs. The licence is MIT.

When your agent uses it

  • Tasks that involve Observability

Example prompts

  • “/debug-logging-assistant”

Workflow steps

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

  1. Inspect
  2. Place logs
  3. Write messages
  4. Validate

What it can do on your machine

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

    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

Debug Logging Assistant loads about 426 tokens when it runs, and up to ~831 if it reads all its reference files. Until then it costs about 26 tokens; SKILL.md has 200 words of instructions outside code blocks.

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

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 dmitriiweb/extract-emails at commit 1f2bb40, republished under its MIT licence (© dmitriiweb). 200 words, ~426 tokens.

Download SKILL.mdSave it as .claude/skills/debug-logging-assistant/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
debug-logging-assistant
description
Add purposeful debug logging to improve observability without changing behavior.

Debug Logging Assistant

Quick start

  • Read the target code and recent failures to understand where visibility is missing.
  • Add debug logs only where they help explain flow, inputs, branching, or error context.
  • Keep logs small and descriptive: what is happening, key identifiers, and outcomes.
  • Do not change control flow or data; only add logs. Avoid logging every step.
  • See references/logging_rules.md for placement and messaging guidelines.

Workflow

  1. Inspect

    • Identify high-signal spots: entry points, external calls, branching paths, retries, and error handling.
    • Note important identifiers (IDs, counts, feature flags) that disambiguate paths.
  2. Place logs

    • Log before/after risky operations and around decisions that affect downstream behavior.
    • Prefer one concise log per logical block over multiple low-value messages.
    • Keep sensitive data out; include only safe identifiers or summaries.
  3. Write messages

    • Use consistent prefixes and log levels (debug/trace) already used in the codebase.
    • Capture intent: action, inputs of interest, and outcomes (success/failure, counts).
    • Avoid narrating trivial steps or restating obvious code.
  4. Validate

    • Ensure no functional changes: no refactors, no reordered logic, no added branching.
    • Confirm log volume is reasonable and won’t spam hot paths.
    • Re-run applicable tests if available; otherwise double-check for typos.

Reference

  • references/logging_rules.md: detailed rules for meaningful debug logging.

© dmitriiweb, 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 1 other file (references) in .codex/skills/debug-logging-assistant of dmitriiweb/extract-emails.

  • SKILL.md
  • references/logging_rules.md

Open the folder on GitHubat commit 1f2bb40

Compare with similar skills

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

Debug Logging Assistant compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Debug Logging Assistant this skilldmitriiweb/extract-emails111—~426Automated safety check: PassMIT
Motel Debugkitlangton/motel298—~2.2kAutomated safety check: PassMIT
Logging Observabilitygetsentry/toolkit917—~2.6kAutomated safety check: PassCustom licence
Rift Backend EffectCompound-inc/rift124—~1.8kAutomated safety check: PassCustom licence
Flueshadcn-labs/agentcn486—~2kAutomated safety check: PassMIT
Crash Instrumentationnexus-labs-automation/mobile-observability116—~744Automated safety check: PassMIT

Similar skills

  • Motel Debug

    kitlangton/motel

    Debug applications with motel, a local OpenTelemetry ingest and query server.

    298 GitHub stars~2.2k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check passed
  • Logging Observability

    getsentry/toolkit

    Official

    Review code for correct logging and error handling patterns.

    917 GitHub stars~2.6k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Rift Backend Effect

    Compound-inc/rift

    A skill your agent uses when adding, reviewing, or refactoring backend code in Rift's TanStack Start app that should follow apps/start/BACKENDEFFECTPLAYBOOK.md.

    124 GitHub stars~1.8k tokensUpdated 10 days ago
    DevOps & CloudAuto-check passed
  • Flue

    shadcn-labs/agentcn

    A skill your agent uses when building, debugging, reviewing, or documenting Flue agents, workflows, channels, skills, tools, sandboxes, targets, routing, persistence, observability, or CLI usage…

    486 GitHub stars~2k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Crash Instrumentation

    nexus-labs-automation/mobile-observability

    Set up crash instrumentation with actionable context. An agent skill from nexus-labs-automation/mobile-observability.

    116 GitHub stars~744 tokensUpdated 1 mo ago
    DevOps & CloudAuto-check passed
  • Correlates a Codex CLI session's local transcript with a model router's production logs to explain why a reply rendered the way it did.

    5.6k GitHub stars~4.5k tokensUpdated today
    DevOps & CloudAuto-check: warnings

More from dmitriiweb/extract-emails

All 8 skills in this repo
  • Git Commit Assistant

    dmitriiweb/extract-emails

    Generate high-quality conventional git commit messages and, with user approval, run the commit.

    111 GitHub stars~558 tokensUpdated 9 mo ago
    Auto-check passed
  • Agents Md Assistant

    dmitriiweb/extract-emails

    Inspect a repository and draft an AGENTS.md file using the standard template, capturing commands, structure, and workflow rules.

    111 GitHub stars~441 tokensUpdated 9 mo ago
    Auto-check passed
  • Code Review Assistant

    dmitriiweb/extract-emails

    Perform structured, actionable code reviews for Python code with clear findings and suggestions.

    111 GitHub stars~467 tokensUpdated 9 mo ago
    Auto-check passed
  • Format Lint Assistant

    dmitriiweb/extract-emails

    Run the project's formatter, linters, and mypy checks in the required order, fixing issues and managing any needed stub dependencies via uv.

    111 GitHub stars~395 tokensUpdated 9 mo ago
    Auto-check passed
  • Google Docstring Assistant

    dmitriiweb/extract-emails

    Write Python docstrings following the Google Python Style Guide, using clear sections and examples.

    111 GitHub stars~388 tokensUpdated 9 mo ago
    Auto-check passed
  • Pytest Testing Assistant

    dmitriiweb/extract-emails

    Write focused pytest tests as standalone functions (one test per function), avoiding test classes.

    111 GitHub stars~394 tokensUpdated 9 mo ago
    Auto-check passed

Questions about Debug Logging Assistant

What does Debug Logging Assistant do?

Add purposeful debug logging to improve observability without changing behavior. Debug Logging Assistant is an agent skill from dmitriiweb/extract-emails. Add purposeful debug logging to improve observability without changing behavior.

When should I use Debug Logging Assistant?

Debug Logging Assistant fits situations like: tasks that involve Observability.

How do I install Debug Logging Assistant in Claude Code?

Run `npx skills add dmitriiweb/extract-emails --skill debug-logging-assistant -a claude-code`. Or copy the skill folder (.codex/skills/debug-logging-assistant in dmitriiweb/extract-emails) into .claude/skills/debug-logging-assistant in your project. Claude Code loads it when a task matches its description.

How do I install Debug Logging Assistant in Codex?

Run `npx skills add dmitriiweb/extract-emails --skill debug-logging-assistant -a codex`. Or copy the skill folder (.codex/skills/debug-logging-assistant in dmitriiweb/extract-emails) into .agents/skills/debug-logging-assistant in your project. Codex loads it when a task matches its description.

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

What does Debug Logging Assistant need to run?

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

Does Debug Logging Assistant 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 Debug Logging Assistant 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 Debug Logging Assistant use?

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

How many tokens does Debug Logging Assistant use?

About 426 tokens (SKILL.md is roughly 1.7k 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 405 tokens, read only when the agent opens those files.

What are the alternatives to Debug Logging Assistant?

Skills that share tags, products or a category with Debug Logging Assistant: Motel Debug (kitlangton/motel, 298 stars), Logging Observability (getsentry/toolkit, 917 stars), Rift Backend Effect (Compound-inc/rift, 124 stars) and Flue (shadcn-labs/agentcn, 486 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Debug Logging Assistant?

dmitriiweb (a GitHub user) maintains it in dmitriiweb/extract-emails, which has 111 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on January 2, 2026.

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