Skip to content
TrustedSkillsbeta
Back to all skills

O11Y Logging

Checked
joelhooks·vlatest·devops

O11Y Logging provides detailed, structured logs for rapid troubleshooting and observability, crucial for efficient incident resolution.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add joelhooks/joelclaw --skill o11y-logging -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

joelhooks

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned joelhooks/joelclaw at acb5544732.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
acb5544732
Manifest
skills/o11y-logging/SKILL.md
Scanned
4 files, 317 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The o11y-logging skill provides structured logging capabilities to AI agents. It allows agents to record events, errors, and other relevant information in a standardized format suitable for analysis and debugging. This facilitates improved observability and troubleshooting of agent behavior.

When to use it

  • Debugging complex workflows: When an agent is exhibiting unexpected behavior, use this skill to log each step and identify the source of the problem.
  • Monitoring agent performance: Track key metrics like task completion time or error rates by logging relevant events throughout the agent's execution.
  • Auditing agent actions: Log all actions taken by an agent for compliance or security purposes, creating a clear record of its activities.
  • Analyzing user interactions: Record details about user input and agent responses to understand how users are interacting with the agent and identify areas for improvement.

Key capabilities

  • Structured logging format
  • Event recording
  • Error tracking
  • Standardized output

Example prompts

  • "Log this error: 'Unable to connect to database'."
  • "Record a success event when the user confirms their order."
  • "Start logging all API calls with timestamps and request details."

Tips & gotchas

This skill requires an understanding of how to structure log messages effectively. Ensure that logged data is concise and relevant for efficient analysis.